Invalid OLAP-Related Java Objects (Doc ID 1340850.1)

Last updated on DECEMBER 31, 2024

Applies to:

Symptoms

The following errors can be found either during a database migration or switch of platform:

call dbms_java.dropjava('-force -synonym olap/api/lib/awxml.jar')
     *
ERROR at line 1:
ORA-29532: Java call terminated by uncaught Java exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: 27
ORA-06512: at "SYS.DBMS_JAVA", line 661


call dbms_java.dropjava('-force -synonym olap/api/lib/olap_api_spl.jar')
     *
ERROR at line 1:
ORA-29532: Java call terminated by uncaught Java exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: 34
ORA-06512: at "SYS.DBMS_JAVA", line 661


call dbms_java.loadjava('-force -resolve -grant PUBLIC -synonym olap/api/lib/olap_api_spl.jar')
     *
ERROR at line 1:
ORA-00600: internal error code, arguments: [26599], [1], [19], [], [], [], [],
[], [], [], [], []
ORA-06512: at "SYS.DBMS_JAVA", line 649


call dbms_java.loadjava('-force -resolve -grant PUBLIC -synonym olap/api/lib/awxml.jar')
     *
ERROR at line 1:
ORA-00600: internal error code, arguments: [26599], [1], [19], [], [], [], [],
[], [], [], [], []
ORA-06512: at "SYS.DBMS_JAVA", line 649

As a result, many OLAP-related Java objects are flagged as invalid.

However, the components in the database (including OLAP) are shown as valid.

Changes

The issue where this was originally reported during the use of Transportable Tablespaces (TTS)  to migrate a database between platforms. Most likely there are more scenarios where this can come up , so this is not limited to this scenario alone.

Cause