Shulou(Shulou.com)05/31 Report--

This article mainly explains how to deal with the error of Oracle 12c ORA-29548. Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Now let the editor to take you to learn "Oracle 12c ORA-29548 error handling method"!

I. introduction of the basic environment

OS:Red Hat Enterprise Linux Server release 6.6

GI:12.1.0.2

DB:12.1.0.2

PSU:12.1.0.2.180717

Opatch:12.2.0.1.14

Process 1. Check the jdk version of the operating system

Cd $ORACLE_HOME/jdk/bin

. / java-version

Java version "1.6.0,75"

Java (TM) SE Runtime Environment (build 20.75 copyright b01 mixed mode)

2. Check the OPATCH version

Cd $ORACLE_HOME/Opatch

. / opatch lsinv

3. Check the JDK version in the database

SQL > select dbms_java.get_jdk_version () from dual

ERROR at line 1:

ORA-29548: Java system class reported: release of classes.bin in the database (12.1.0.2.0.1.6)

Does not match that of the oracle executable (12.1.0.2.180717.1.6)

4. Repair the java objects in the database

SQL > @? / javavm/install/update_javavm_db.sql

SQL > SET FEEDBACK 1

SQL > SET NUMWIDTH 10

SQL > SET LINESIZE 80

SQL > SET TRIMSPOOL ON

SQL > SET TAB OFF

SQL > SET PAGESIZE 100

SQL >

SQL > alter session set "_ ORACLE_SCRIPT" = true

Session altered.

SQL >-If Java is installed, do CJS.

SQL >

SQL >-If CJS can deal with the SROs inconsistent with the new JDK

SQL >-the drop_sros () call here can be removed.

SQL > call initjvmaux.drop_sros ()

Call completed.

SQL > create or replace java system

2 /

Java created.

SQL > update dependency$

2 set pendant timestamp = (select stime from obj$ where obj#=p_obj#)

3 where (select stime from obj$ where obj#=p_obj#)! = p_timestamp and

4 (select type# from obj$ where obj#=p_obj#) = 29 and

5 (select owner# from obj$ where obj#=p_obj#) = 0

0 rows updated.

SQL > commit

Commit complete.

SQL >

SQL > alter session set "_ ORACLE_SCRIPT" = false

Session altered.

5. Verification

The jdk version of the database can be checked in CDB, but the error is still reported in pdb

SQL > select dbms_java.get_jdk_version () from dual

ERROR at line 1:

ORA-29548: Java system class reported: release of classes.bin in the database (12.1.0.2.0.1.6)

Does not match that of the oracle executable (12.1.0.2.180717.1.6)

-solution

Execute again in pdb

SQL > @? / javavm/install/update_javavm_db.sql

When migrating and upgrading the Oracle 12c database in the production environment, if the application system uses the java object in the database, ORA-29548 is a common error. I have encountered this error when I used rman or data pump in the process of migration and upgrade.

At this point, I believe you have a deeper understanding of the "Oracle 12c ORA-29548 error handling method". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.