Problems with migrating Oracle DB after 32-bit processor upgrade to 64-bit

The processor changed from 32 bits to 64 bits, and after the Oracle software was replaced, the db I chose to migrate the cold standby direct hook, and then the problem was encountered after the migration.

After a successful mount of DB, errors such as ora-06553:pls-801:internal error [56319] occur when connecting through an application or Third-party tools such as Plsql developer. The workaround is as follows:

sql> shutdown Immediate

Sql> Startup upgrade

Sql> set echo on

sql> @ $ORACLE _home/rdbms/admin/utlirp.sql

Sql> Select status from Dba_objects

2 where object_name= ' Dbms_standard '

3 and object_type= ' PACKAGE '

4 and owner= ' SYS ';

If invalid, you will need to recompile and execute the following statement

Sql> alter package Dbms_standard compile;

If it is valid, you do not need to execute the above statement

Sql> Select object_name from dba_objects where status= ' INVALID ';

This column more highlights: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/

If the return value is not empty, you need to execute the following statement

sql> @ $ORACLE _home/rdbms/admin/utlrp.sql

If the statement fails to execute, execute the following statement sequentially

$ cd/u01/app/oracle/product/102/db_1/olap/admin/

Sql> @?/olap/admin/catnoamd.sql

Sql> @?/olap/admin/catnoaps.sql

Sql> @?/olap/admin/catnoxoq.sql

Sql> @?/olap/admin/olapidrp.plb

Sql>@?/olap/admin/olap.sql Sysaux TEMP;

And then execute again

sql> @ $ORACLE _home/rdbms/admin/utlrp.sql

Query again

Sql> Select object_name from dba_objects where status= ' INVALID ';

Should be empty at this time

Sql> set echo off

sql> shutdown immediate;

Sql> Startup

51cto Blog Oracle Little Bastard