Dear Experts,We have developed a custom APIs to post transaction data (both header and line-level structures). These APIs have been tested successfully in DEV, TEST, and UAT environments without any issues.Recently, we cloned the UAT environment into a new environment (UAT2). However, in UAT2 the same custom integration fails with the following error:ORA-22813: operand value exceeds system limits The response is always 500 Internal Server Error.We already tried the following: Tested with the original payload (works fine in other environments). Sent a blank/empty JSON payload → still fails with the same error. Verified that standard IFS APIs with POST methods are working fine in UAT2. The problem seems to occur only with the custom API in UAT2. Since the environments are cloned, we expected the behavior to be identical.What could be the possible cause of this error in the cloned environment (UAT2), and what areas should we check (DB settings, CLOB handling, API configuration, etc.) to resolve it? We are using 24R1.

ORA-22813 error on Custom API after Environment Clone

Dear Experts,

We have developed a custom APIs to post transaction data (both header and line-level structures). These APIs have been tested successfully in DEV, TEST, and UAT environments without any issues.

Recently, we cloned the UAT environment into a new environment (UAT2). However, in UAT2 the same custom integration fails with the following error:

ORA-22813: operand value exceeds system limits

The response is always 500 Internal Server Error.

We already tried the following:

Tested with the original payload (works fine in other environments).
Sent a blank/empty JSON payload → still fails with the same error.
Verified that standard IFS APIs with POST methods are working fine in UAT2.
The problem seems to occur only with the custom API in UAT2.

Since the environments are cloned, we expected the behavior to be identical.

What could be the possible cause of this error in the cloned environment (UAT2), and what areas should we check (DB settings, CLOB handling, API configuration, etc.) to resolve it? We are using 24R1.

Page 1 / 1

The issue was due to an Oracle patch update, which changed how memory is allocated for response structure arrays. Specifically, attributes in the response object that hold string values larger than 32,000 characters were no longer handled the same way, causing the API call to fail. This is sorted now.

Reply

Did you find what you're looking for? If not:

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded