My Oracle Support Banner

Errors in Order Management Caused Because of Memory Leak Issue in Rdbms Version 9.2.0.6 (Doc ID 464569.1)

Last updated on MARCH 24, 2024

Applies to:

Oracle Order Management - Version 11.5.8 to 11.5.10.0 [Release 11.5.8 to 11.5.10]
Information in this document applies to any platform.

Symptoms

On <IP_ADDRESS>:


When attempting to run Workflow background process is failing with the parameters OEOL deferred set to YES, Time-out NO, Process Stuck No.

ERROR
-----------------------
ORACLE error 3113 in FDPSTP
Cause: FDPSTP failed due to ORA-03113: end-of-file on communication channel
The SQL statement being executed at the time of the error was: and was executed from the file .

APP-FND-01564: ORACLE error 1000 in AFPGRG
Cause: AFPGRG failed due to ORA-01000: maximum open cursors exceeded.

 

RDBMS version of 9.2.0.6 has a memory leak issue and the same can be found out using the following simple test case.

 declare 
 
l_org number; 
l_org_str varchar2(100); 
 
begin 
 
for i in 1..400000 LOOP 
l_org_str := USERENV('CLIENT_INFO'); 
-- l_org_str := SYS_CONTEXT ('USERENV', 'CLIENT_INFO'); 
end loop; 
 
end; 

  
When the above  anonymous block is run from one session, and pga memory growth of this session is monitored from another session one will  observe continued growth. If the USERENV call is commented out, and replaced wih the SYS_CONTEXT call, the leak does not occur

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
 Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.