Service Limits

Review the following service limits for Oracle Integration Generation 2 resources. A service limit is the quota or allowance set on a resource. You cannot change the service limits configured for your cloud account.

Oracle Cloud Infrastructure Console Service Limits

Resource Service Limit
Integration instance count 200 instances per region.

Oracle Integration Components Service Limits

Note:

The supported message payload size for trigger and invoke connections is 50 MB for endpoints accessed using the SOAP Adapter, REST Adapter, SAP Adapter, File Adapter, and FTP Adapter. This means that an external application can send XML or JSON payloads of up to 50 MB in size to Oracle Integration. The same limit applies to these endpoints returning structured payload (XML/JSON) back to Oracle Integration as part of an invoke connection.

Note that this increase may lead to additional memory consumption in Oracle Integration. To ensure stability, it is recommended that the percentage of large payloads coming into Oracle Integration should not increase the number of total messages by more than 3%.

Table 1-1 Adapters

Resource Service Limit
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.
Timeouts for all connectivity agent-based outbound adapter invocations Connection timeout is set to 4 minutes.
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 agent-based endpoints

Write File operation:

  • 1 GB when used without a schema (with a connectivity agent).
  • 50 MB when using a schema for transformation.
  • 50 MB for agent-based endpoints

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 (with a connectivity agent).
  • 50 MB when using a schema for transformation.
  • 50 MB for agent-based endpoints

Write File operation:

  • 1 GB when used without a schema (with a connectivity agent).
  • 50 MB when using a schema for transformation.
  • 50 MB for agent-based endpoints

Download File operation: 1 GB.

AS2 Adapter - file size limit 10 MB
REST Adapter

For trigger configurations

  • XML document size for schema generation: 3 MB. See REST Adapter Capabilities.
  • Incoming message size (without attachment): 50 MBMessages with attachments, for example, multipart/mixed and multipart/form-data, are not subject to this constraint.
  • Incoming JSON attachments size: 1 GB.
  • Incoming structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML):
    • JSON or XML: 50 MB
    • HTML, YAML, or YML: 10 MB
  • Incoming content as raw bytes (application/octet-stream as content type): 1 GB.
  • Specifying the response payload format: JSON sample files of up to 100 KB in size are supported.

For invoke configurations

  • XML document size for data definition generation: 3 MB. See REST Adapter Capabilities.
  • Attachment size in outbound requests: 1 GB. These attachments can be multipart/mixed, multipart/form-data, or application/octet-stream.
  • Outgoing structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML):
    • JSON or XML: 50 MB
    • HTML, YAML, or YML: 10 MB
  • Outgoing unstructured message payload size (multipart/form-data and binary/octet-stream): 1 GB.
  • Specifying the request payload format: JSON sample files of up to 100 KB in size are supported.
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 Adapter, and so on.

For trigger configurations (wherever applicable)

  • XML document size for schema generation: 3 MB. See REST Adapter Capabilities.
  • Incoming message size (without attachment): 10 MB. Messages with attachments, for example, multipart/mixed and multipart/form-data, are not subject to this constraint.
  • Incoming JSON attachments size: 1 GB.
  • Incoming structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML):
    • JSON or XML: 10 MB
    • HTML, YAML, or YML: 10 MB
  • Incoming content as raw bytes (application/octet-stream as content type): 1 GB.
  • Specifying the response payload format: JSON sample files of up to 100 KB in size are supported.

For invoke configurations (wherever applicable)

  • XML document size for data definition generation: 3 MB. See REST Adapter Capabilities.
  • Attachment size in outbound requests: 1 GB. These attachments can be multipart/mixed, multipart/form-data, or application/octet-stream.
  • Outgoing structured message payload size (any content-type header containing JSON, XML, HTML, YAML, or YML):
    • JSON or XML: 10 MB
    • HTML, YAML, or YML: 10 MB
  • Outgoing unstructured message payload size (multipart/form-data and binary/octet-stream): 1 GB.
  • Specifying the request payload format: JSON sample files of up to 100 KB in size are supported.
Salesforce Adapter - batch file size 8 MB (10,000 records). See Process Large Data Sets Asynchronously with Different Bulk Operations.
SAP Ariba Adapter

See SAP Ariba Adapter Restrictions.

SAP Adapter - Payload size limits
  • 50 MB for SAP endpoints
  • 50 MB for agent-based endpoints
SOAP Adapter

For trigger configurations

  • Structured payload (XML) size in Request and Response: 50 MB.

For invoke configurations

  • Structured payload (XML) size in Request and Response: 50 MB.
  • MTOM attachment (binary and non-binary content) size in Request and Response: 1 GB.
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: 10 MB.

For invoke configurations (wherever applicable)

  • Structured payload (XML) size in Request and Response: 10 MB.
  • MTOM attachment (binary and non-binary content) size in Request and Response: 1 GB.
Database Adapters (Oracle Database Adapter, IBM DB2 Adapter, Microsoft SQL Server Adapter, MySQL Adapter, Oracle Autonomous Data Warehouse Adapter, Oracle Autonomous Transaction Processing Adapter, and Oracle Database Cloud Service Adapter)

For trigger configurations

  • Polling Operation: 10 MB with schema transformation.

For invoke configurations

  • Stored Procedure/Operation on Table/Run PureSQL Statement Operations: 10 MB with schema transformation for all the outbound operations.
Apache Kafka Adapter

For invoke configurations

  • Produce/Consume Message Operations: 10 MB with schema transformation for all the outbound operations.
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.
Oracle CPQ Cloud Adapter - response payload 10 MB.

Note:

When the message payload in an integration exceeds 10 MB, the message is rejected and an error message is displayed. The error message describes remedial actions to perform. See Perform Remedial Actions When the Payload Exceeds 10 MB.

Table 1-2 Integrations

Resource Service Limit
Connectivity agent - memory

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

  • 10 MB as request.
  • 10 MB as response.

SOAP and REST adapters configured with connectivity agent

  • 10 MB (structured XML/JSON document) as request.
  • 10 MB (structured XML/JSON document) as response from private SOAP/REST endpoints.
  • 1 GB for attachments as part of a request.
  • 1 GB for attachments as part of a response from private SOAP/REST endpoints.
Stage File action (in orchestrated integrations) - file size

Read Entire File operation: 10 MB. For files greater than 10 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.
Activity stream size 100 MB.

The maximum size for payloads inside the activity stream is 512 KB, at which time the payloads are truncated.

Activity stream logs - file size 10 MB.
Incident package You are restricted to reading the last 1000 lines from each log when creating an incident package during an incident.
Notification action - attachments size
  • 1 MB for Oracle Integration.
  • 2 MB for Oracle Integration Generation 2.

Both the email body and attachment are considered in calculating the total size.

Maximum number of daily outbound emails you can send from Oracle Integration 5000 emails per day.
JavaScript action timeout threshold 15 seconds
JavaScript function maximum parameter support 20 parameters
Number of concurrent instances of given scheduled integration 1 for scheduled and out-of-band and 1 for ad-hoc.
Where:
  • Out-of-band: A run now run associated with a schedule.
  • Ad-hoc: A run now run not associated with a schedule.
Execution time threshold for long running scheduled integrations Terminated by Oracle Integration if integration exceeds 6 hours. See Execution Time Threshold for Long Running Scheduled Integrations in Using Integrations in Oracle Integration.
Oracle Asserter recording size 25 MB

There are additional asserter limits. See Restrictions in Using Integrations in Oracle Integration.

While loop iterations 5000.
For each loop iterations 5000.
Tracking variable - value 100 characters. If the value is greater than the limit, it's truncated.
Schedule parameter - value 256 characters.
Integration properties - value 256 characters.
Integration/Connection - name 50 characters on the UI; 200 characters in the database.
Integration/Connection - package name 50 characters on the UI; 200 characters in the database.
Integration/Connection - version 10 characters on the UI; 50 characters in the database.
Integration/Connection - description 1024 characters on the UI; 2000 characters in the database.
Log file downloads and log level settings You cannot download logs or set logging levels in Oracle Integration Generation 2. Instead, use the activity stream to view instance details. See View the Dashboard and Track Business Identifiers in Integrations During Runtime in Using Integrations in Oracle Integration.
B2B for Oracle Integration - Trading partner management and B2B message tracking These features are only supported in Oracle Integration Generation 2.

See Manage Trading Partners and Track B2B Messages in Using B2B for Oracle Integration.

Oracle API Gateway - Activate and deploy integrations from Oracle Integration This feature is only supported in Oracle Integration Generation 2.

See Connect to Oracle API Gateway in Using Integrations in Oracle Integration.

Table 1-3 Processes

Resource Service Limit
Email attachment size 2 MB.
Document attachment size (native as well as via Oracle Content Management) 15 MB.
Maximum payload size in REST APIs
  • 10 MB, for any content-type header containing JSON, XML, HTML, YAML, or YML.
  • 20 MB for other content types.
Maximum number of times a given activity can execute per instance (via direct or indirect loops) in a single process instance 1000.

Table 1-4 File Server

Resource Service Limit
Storage 500 GB.
Concurrent connections Maximum of 20 connections per service instance

Oracle Cloud Infrastructure also has service limits. See Service Limits