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.

Oracle Cloud Infrastructure Console Service Limits

Resource Service Limit
Integration instance count 200 instances per region.

Oracle Integration Components Service Limits

Table 1-1 Adapters

Resource Service Limit
File Adapter - file size 10 MB.

Note:

The size of CSV files increases when translated into a message. Therefore, the file size must be less than 10 MB, so that the after-translation message size does not exceed 10 MB.
FTP Adapter - file size

For invoke configurations

Read File operation:

  • 1 GB when used without a schema (with a connectivity agent).
  • 10 MB when using a schema for transformation.

Write File operation:

  • 1 GB when used without a schema (with a connectivity agent).
  • 10 MB when using a schema for transformation.

Download File operation: 1 GB.

REST Adapter

For trigger configurations

  • 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): 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): 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, etc.)

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): 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): 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.

SOAP Adapter

For trigger configurations

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

For invoke configurations

  • Structured payload (XML) size in Request and Response: 10 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.
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.

Number of concurrent instances of given scheduled integration 1 scheduled, 1 run now.
Number of concurrent instances of scheduled integration 2 per node.
While 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.

Table 1-3 Processes

Resource Service Limit
Email attachment size 2 MB.
Document attachment size (Native as well as via Oracle Content and Experience) 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.