metalink上面的，你试验一下吧，文档的描述和你的一样Solution Description -------------------- If you do not need Java Option, first remove it by script: $ORACLE_HOME/javavm/install/rmjvm.sql (Notice that in 8.1.6 rmjvm.sql is wrong. Before running it you should change line: "call rmjvm.run(true)" to "execute rmjvm.run(true)" This is due to [BUG:1179670]. Be careful for having large rollback segments when running it. Then login from sqlplus as SYS user and issue the following commands: SQL> drop package dbms_java; SQL> drop public synonym dbms_java; If you need the Java Option check [NOTE:105472.1] for correct Java installation. Explanation ----------- Export tests whether the Synonym 'DBMS_JAVA' is defined. If it is defined, export assumes java has been installed and it uses dbms_java.longname to get the long version of synonym names. Otherwise, it assumes it can't use dbms_java and just takes the name out of sys.syn$. It looks like DBMS_JAVA was defined but initjvm didn't run (or failed somewhere).
If you do not need Java Option, first remove it by script: $ORACLE_HOME/javavm/install/rmjvm.sql (Notice that in 8.1.6 rmjvm.sql is wrong.
Before running it you should change line: "call rmjvm.run(true)" to "execute rmjvm.run(true)" This is due to [BUG:1179670]. Be careful for having large rollback segments when running it. Then login from sqlplus as SYS user and issue the following commands: SQL> drop package dbms_java; SQL> drop public synonym dbms_java; If you need the Java Option check [NOTE:105472.1] for correct Java installation. Explanation -----------
Export tests whether the Synonym 'DBMS_JAVA' is defined. If it is defined, export assumes java has been installed and it uses dbms_java.longname to get the long version of synonym names. Otherwise, it assumes it can't use dbms_java and just takes the name out of sys.syn$. It looks like DBMS_JAVA was defined but initjvm didn't run (or failed somewhere).