Review the following service limits for Oracle Integration 3
resources. A service limit is the quota or allowance set on a resource. You cannot change
the service limits configured for your tenancy.
Note
The service limits described below are enforced.
Oracle Cloud
Infrastructure Console Service Limits
🔗
For more Oracle Cloud
Infrastructure
Console service limits, see Service Limits in the OCI
documentation.
Resource
Service Limit
Integration service instance count
200 service instances per region.
Note: This value is the number of service
instances you provision per region, and not the number of
integration instances (for example, application and schedule) that
you activate and monitor under the
Observability tab in Oracle Integration.
Service instance creation
The ability to create service instances outside your home
region depends on several factors. See Restrictions.
For structured payloads delivered on trigger connections
or as a response from invoke connections
100 MB limit for cloud endpoints (not using the
connectivity agent). The limit is 100 MB if the endpoint is enabled with
a private endpoint.
For binary (unstructured) payloads (for example,
attachments, MTOM)
1 GB limit for trigger connections and responses from
invoke connections.
For connectivity agent-based adapters, the payload
limits for structured payload (JSON, XML).
50 MB limit for SOAP and REST.
For file and FTP with the
connectivity agent, the limit for an invoke response is 50 MB for
structured payloads.
For any other protocol (for
example, database, JMS, MQ, Kafka, and others), the payload limit is
10 MB for structured payloads.
File Adapter - file size
Read File operation:
1 GB when used without a schema (with the
connectivity agent)
50 MB when using a schema for transformation
50 MB for a read operation with structured payload
(The File Adapter is only available with connectivity
agent.)
Polling with the connectivity agent: 50
MB
Download File
operation: 1 GB
Note
The size of CSV files
increases when translated into a message. Therefore, the file size
must be less than 50 MB, so that the after-translation message size
does not exceed 50 MB.
FTP Adapter - file size
For invoke configurations
Read File operation:
1 GB when used without a schema (when used both
with or without a connectivity agent).
100 MB for cloud-based endpoints when using a
schema for transformation.
50 MB for agent-based endpoints when using a
schema for transformation.
100 MB for public internet-based
endpoints.
100 MB for private endpoints.
Download File operation: 1 GB (when used both with or
without a connectivity agent).
Note: If the string length for fields
in a JSON payload exceeds 20 MB, you receive a
translation failure error. See ORABPEL-15235 Translation Failure Occurrence
in Using the REST Adapter
with Oracle Integration 3.
Incoming content as raw bytes
(application/octet-stream as content type): 1 GB.
Specifying the response payload format in the
Adapter Endpoint Configuration Wizard: JSON sample files of
up to 100 KB in size are supported.
Specifying the request payload format in the
Adapter Endpoint Configuration Wizard: JSON sample files of
up to 100 KB in size are supported.
Response returned as part of invoke runtime
binary data (application/octet-stream): 1 GB
Response returned from agent-based endpoints
for structured content (for example, JSON/CSV/XML, and so
on): 50 MB
Response returned from private endpoints for
structured content (for example, JSON/CSV/XML, and so on):
100 MB
Response returned from public internet-based
endpoints for structured content (for example, JSON/CSV/XML,
and so on):100 MB
REST-Based Adapters (Adapters that expose REST endpoints
on the inbound or adapters invoking external REST endpoints. For
example, Oracle Commerce Cloud
Adapter, Oracle Field Service
Cloud Adapter, and so on.)
Specifying the request payload format: JSON
sample files of up to 100 KB in size are supported.
Agent-based endpoints: 50 MB
Private endpoints: 100 MB
Public internet-based endpoints: 100
MB
SOAP Adapter
For trigger configurations
Structured payload (XML) size in Request and
Response: 100 MB.
For invoke configurations
Structured payload (XML) size in Request and
Response: 100 MB.
Agent-based endpoints: 50 MB
Private endpoints: 100 MB
Public internet-based endpoints: 100
MB
SOAP-Based Adapters (Adapters that expose SOAP endpoints
on the inbound or adapters invoking external SOAP endpoints. For
example, Oracle Logistics
Adapter.)
For trigger configurations (wherever
applicable)
Structured payload (XML) size in request and
response: 100 MB.
For invoke configurations (wherever
applicable)
Structured payload (XML) size in response: 100
MB.
Agent-based endpoints: 50 MB
Private endpoints: 100 MB
Database Adapters (Oracle Database Adapter, IBM DB2 Adapter, Microsoft SQL Server
Adapter, MySQL Adapter, Netezza Adapter, PostgreSQL Adapter, Oracle Autonomous Data Warehouse
Adapter, Oracle Autonomous Transaction Processing
Adapter, Oracle Database Cloud Service
Adapter, SAP ASE (Sybase) Adapter, and Snowflake Adapter)
For trigger configurations
Polling operation:
50 MB with schema transformation for
agent-based endpoints.
100 MB with schema transformation
through private endpoints
For invoke configurations
Stored Procedure/Operation on Table/Run PureSQL
Statement Operations: 10 MB with schema transformation for
all the outbound operations.
Database select
operation:
100 MB for public internet-based
endpoints
100 MB for private endpoints
50 MB for agent-based endpoints
JMS Adapters (Oracle
WebLogic JMS Adapter and IBM MQ Series JMS
Adapter)
For trigger configurations
Consume Message Operation: 10 MB with schema
transformation.
For invoke configurations
Produce Message Operation: 10 MB with schema
transformation.
Apache Kafka Adapter
For invoke configurations
Produce/Consume Message Operations: 10 MB with
schema transformation for all the outbound operations.
Oracle E-Business Suite
Adapter
100 MB (for public internet-based endpoints)
50 MB (for agent-based endpoints)
SAP Adapter
50 MB
For the SAP Adapter as a trigger
connection, the limit is 50 MB for all document types.
.
Oracle CPQ Adapter - response payload
50 MB.
AS2 Adapter file size
limit
10 MB.
Timeouts for all connectivity agent-based outbound
adapter invocations
Connection timeout is set to 4 minutes.
Timeouts for all outbound adapter invocations
The following values are set and cannot be changed:
READ timeout is set to 5 minutes.
Connection timeout is set to 5 minutes.
Oracle Autonomous Data Warehouse
Adapter, Oracle Autonomous Transaction Processing
Adapter, Oracle Database Cloud Service
Adapter, MySQL Adapter, Microsoft SQL Server
Adapter, Oracle Database Adapter, and IBM DB2 Adapter
Starting with the August 2021 release, all new
integrations that include stored procedure or PureSQL database
operations must finish within 240 seconds. Otherwise, the query times
out.
A minimum of 8 GB memory with 4 GB of heap size dedicated
to the on-premise agent's Java Virtual Machine (JVM). To include any
other processes on the host besides the agent, increase the physical
memory to a value greater than 8 GB.
Connectivity agent - message payload
10 MB, through the use of compression.
All connectivity-agent-enabled adapters
50 MB as request.
50 MB as response.
SOAP and REST adapters configured with connectivity
agent
50 MB (structured XML/JSON document) as
response from SOAP/REST endpoints.
1 GB for attachments as part of a response from
SOAP/REST endpoints.
For example, a parent
integration (schedule integration) invokes a child integration
(application integration), which in turn recursively invokes the
parent integration.
Integration entry points
along the request execution path are counted towards the limit. When
16 is exceeded, it results in an error.
String size limit
Restricted to 10,000 characters.
The limit
is applicable to all variables of type string, including global
variables. The limit is also applicable to all functions, including
a concat function used inside an assign, stitch, or
mapper.
Parallel action concurrency limits
Parallel action branches independent of the integration
type (synchronous, asynchronous, and so on) count towards the
concurrency limits on synchronous requests.
For example.
a parallel action with three branches needs two extra concurrency
slots for the duration of the parallel action; one branch is counted
towards the original flow already obtained.
Triggers (maximum number of concurrent requests)
Synchronous: A maximum of 600 concurrent requests.
Users receive 100 concurrent requests per message pack. This
concurrent request increase is useful if you have high
concurrency requirements in respect to synchronous integration
executions.
Asynchronous: No limit (50 at a time can execute,
the rest are queued).
Maximum number of integrations that can subscribe to
events
50 integrations can subscribe to events per service
instance.
Maximum number of tracking events per integration
instance
20,000 for non-error events
30,000 for error events (extra 10,000 if events are
associated with errors)
2000 max error recorded
After those limits are reached, events are no longer
recorded in the activity stream, but they continue to be processed
and the integration instance overall state is calculated. This
ensures that the integration instance state is updated in all
scenarios.
Maximum activity stream payload sizes
The total payload size stored per integration instance
in the activity stream is limited to 25 MB. There is no limit for
payloads stored in the Object Store. Only payloads under 32k are stored
in the activity stream.
Maximum duration for integration flows
Asynchronous: Six hours (The integration instance is
marked as aborted due to deadline timeout.)
Scheduled: Six hours (The integration instance is
marked as aborted due to deadline timeout.)
Synchronous: Five minutes (An HTTP
502 occurs.)
Stage file action (in integrations) - file size
Read Entire File operation: 100 MB. For files greater
than 100 MB, use the Read File in Segments operation.
Encrypt File operation: 1 GB.
Decrypt File operation: 1 GB.
Synchronous integration message timeout
300 seconds.
Synchronous integrations
(integrations that return a response payload) return a timeout error
if they run more than 300 seconds.
Oracle Integration Messaging - message size
10 MB.
Encode and decode file attachment content
(mapper)
The functions encodeReferenceToBase64(String
reference) and decodeBase64ToReference(String
base64Content) have a file size limit of 10 MB.
Lookup column length
1024 characters.
Notification action - attachments size
If using the default method: 2 MB.
If using your customer tenancy: A default value of
2 MB that can be increased until the maximum value supported by
the Oracle Cloud
Infrastructure Email Delivery Service is reached.
Both the email body and attachment are considered in
calculating the total size.
Maximum number of iterations to execute for a while
loop
5000.
Note: There
is no limit for a for-each loop.
Maximum number of iterations captured across all loops
for a single integration instance ID for which tracking data is
captured
1000.
Project limits
100 integrations, 20 connections, 50 lookups, and 20
JavaScript libraries per project.
50 deployments per project.
Deployments to Oracle Cloud Infrastructure API Gateway
An Oracle Cloud
Infrastructure API Gateway instance supports a maximum of 20
deployments. Each deployment can contain up to 50 routes. This provides
you with a capacity of 1000 integration endpoints to which to
deploy.
Maximum number of branches in a parallel action
5.
Tracking variable - value
8191 characters.
Service instance data retention
Retention is based on the trace level set during
integration activation:
Production: 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition
Note: After 24 hours, Debug (Not recommended) is
automatically reset to Production. See Activate an
Integration in Using Integrations
in Oracle Integration 3.
Time window for recovering a failed integration instance
that's recoverable
The integration instance is recoverable until one of the
following occurs:
It is aborted. This can happen due to integration
deactivation.
It is successfully recovered or the recovery leads
to a nonrecoverable error.
It is beyond its associated retention time, which is 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition.
Activity stream displayable rows
5000 rows maximum are displayable when expanding the
tree.
Total size of activity stream (REST response)
No limit.
Maximum number of integration instances shown on
Instances and Errors pages
50 (Can be overridden).
Maximum number of tracking events per integration
instance
40,000.
Maximum number of resubmissions allowed per integration
instance ID
10.
Schedule parameter - value length
256 characters.
Maximum number of schedule parameters per
integration
5 parameters.
Integration properties - value
256 characters.
Integration/Connection - name
50 characters.
Integration/Connection - package name
50 characters.
Integration/Connection - version
10 characters.
Integration/Connection - description
1024 characters.
B2B for Oracle Integration - Trading partner management and B2B
message tracking
Payload size for publishing and subscribing to events in
integrations
The same limit supported by the inbound (trigger)
adapter. See Component: Adapters.
Component: Robotic Process
Automation 🔗
Resource
Service limit
Maximum duration for a robot instance
4 hours.
Timeout for assigning a robot instance to an
environment
Varies, depending upon the environments:
If the environment pool contains no
environments:
0 seconds, and then the status of the robot
instance changes to Failed.
If the robot agent on the environment doesn't
accept the request:
30 seconds, and then Oracle Integration attempts to assign the robot instance
to a different environment.
If all environments in the environment pool have
a status of Unavailable:
240 seconds, and then the status of the robot
instance changes to Failed.
If at least one environment in the environment
pool has a status of Available:
No limit.
Maximum wait time for downloading a file
180 seconds by default but the robot builder can specify
a different value while creating a robot.
Maximum file size for downloading a file
50 MB.
Frequency at which the robot agent polls Oracle Integration for work
15 seconds.
Maximum time that Oracle Integration waits for the robot agent to poll for work
before changing its environment's status to Unavailable
35 seconds.
Maximum number of environments in an environment
pool
100 environments.
Character limits for robots
Name: 50 characters.
Description: 1024 characters.
Keywords: 1024 characters.
Character limits for environment pools
Name: 50 characters.
Description: 1024 characters.
Keywords: 1024 characters.
Character limits for robot connection types
Name: 50 characters.
Description: 1024 characters.
Keywords: 1024 characters.
Character limits for robot connections
Name: 50 characters.
Description: 1024 characters.
Keywords: 1024 characters.
Component: File Server 🔗
Resource
Service Limit
Storage
500 GB.
Concurrent connections
Maximum of 50 connections per service instance.
Component: Process
Automation 🔗
For Process
Automation service limits,
see Service Limits in Administering Oracle
Cloud Infrastructure Process Automation.
Message Pack Usage and Synchronous
Requests 🔗
The following table describes the request limits based on the number of
message packs.
Message Packs Assigned
Synchronous Request Limit
6
600
5
500
4
400
3
300
2
200
1
100
When to Increase Message Packs
Your message packs must equate with the number of messages you consume per
hour. Ensure you know your hourly throughput. An increase in message packs is also
beneficial if you want quicker processing of synchronous requests. The following
examples describe when you need higher concurrency.
Examples
Message Packs
How quickly can a customer consume message packs
with high synchronous concurrency?
Assume a customer has 2 message packs assigned (10K
messages per hour). Each synchronous request takes 5 seconds to
complete. Therefore:
A concurrency of 1 can execute 12 requests
per minute.
A concurrency of 200 can execute 2400
requests per minute.
A 10-minute burst with 200 concurrent
synchronous requests = 24000 messages, which provides an
overage of 14K messages (24K - 10K) for
that hour.
When is the 600 synchronous requests limit
reached?
The 600 concurrent synchronous request limit is
reached when the customer applies 6 message packs to the Oracle Integration instance. Consider
the following example in which each synchronous request takes 10
seconds to execute:
A concurrency of 1 can execute 6 requests
per minute.
A concurrency of 600 can execute 3600
requests per minute.
A 10-minute burst with 600 concurrent
synchronous requests equals 36000 messages, which
results in an overage of 6K messages (36K -
30K) for that hour.
Therefore, a customer with a high message throughput per hour already has a
larger number of message packs assigned to the service instance. The need for a customer
to increase the number of message packs to gain more synchronous request processing
concurrency is as follows:
Less than 5K messages per hour
A burst of synchronous requests that exceed 100 messages