Syed Saad Ali
Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

AutoConfig Failing With NegativeArraySizeException After Upgrading To 11gR2 Database

AutoConfig Failing With NegativeArraySizeException After Upgrading To 11gR2 Database

ERROR

Error stack while running autoconfig:

Updating Context file…COMPLETED

Attempting upload of Context file and templates to database…ERROR: InDbCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; Oracle error -29532: ORA-29532: Java call terminated by uncaught Java exception: java.lang.NegativeArraySizeException has been detected in FND_GSM_UTIL.upload_context_file.
oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; Oracle error -29532: ORA-29532: Java call terminated by uncaught Java exception: java.lang.NegativeArraySizeException has been detected in FND_GSM_UTIL.upload_context_file.
at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java:281)
at oracle.apps.ad.autoconfig.oam.CtxSynchronizer.uploadToDb(CtxSynchronizer.java:328)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBInf(FileSysDBCtxMerge.java:735)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBFiles(FileSysDBCtxMerge.java:224)
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1663)
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:709)
FAILED

SOLUTION

Step 1. Run below query from APPS User

SQL>select is_compiled from user_java_methods where name = ‘oracle/xml/parser/v2/SAXAttrList’ and method_name=’addAttr’ and arguments=7;

if it return YES then proceed further.

 

Step 2. Execute following SQL statement from APPS User.

SQL>call dbms_java.set_native_compiler_option(‘optimizerThrowConversion’, ‘false’);

Step 3. Execute the following SQL statement from SYS User.

SQL>call dbms_java.set_native_compiler_option(‘optimizerThrowConversion’, ‘false’);

Step 4. Delete JIT-compiled code from the database by using following as SYS user.

SQL>truncate table java$mc$;
SQL>commit;

Step 5. Finally, restart database and Run Autoconfig again.

 

 

Related Posts
Write a comment