BEGIN dbms_java.set_output(10000); END; * ERROR at line 1: ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.SET_OUTPUT' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignored BEGIN dbms_java.loadjava('-force -synonym -schema ORDSYS -resolve -grant PUBLIC ord/jlib/ordimsvr.jar'); END; * ERROR at line 1: ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.LOADJAVA' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignoredAlso errors about missing oracle/aurora/jvm/OracleRuntime. Can you give me any advice?
My first question would be whether catpatch.sql had been run as the SYS user. The script must be run as SYS. Another possibility is that the JAVA_POOL_SIZE is not sized sufficiently, or that not enough physical resources have been allocated to the database for this upgrade to complete successfully.
There are reported problems with the JVM and running the January 2006 CPU catcpu.sql script, but I have not encountered the problem you describe above while applying the 126.96.36.199 patchset.
You could try reloading the JVM to see if that clears up the problem (take a database backup first!). There is a document on Oracle's Metalink Web site (Doc ID: 209870.1) which details how to do this. Note that this is a highly destructive procedure and should not be undertaken without some expertise. Prior to doing this, I would contact Oracle support about your problem and open an iTAR.
This was first published in July 2006