Home » Server Options » Data Guard » Error accessing package DBMS_APPLICATION_INFO
Error accessing package DBMS_APPLICATION_INFO [message #175623] Sat, 03 June 2006 09:17
Messages: 44
Registered: September 2005
Location: Mumbai

hello everbody
we need to test our standby database converting it in primary and need to check whethere reports are generating or not.....

we have installed oracle 92010(64 bit) on solaris 8(64 bit) on both side

Every time we i m able to successfully activate standby
db as primary but during report generation we got problem

So after that I have tried to connect as one of user in
new primary db but it is giving me this
error(at this time old primary db is shutdown) .

--- Error during connection

ORA-06553: PLS-801: internal error [56319]

Error accessing package DBMS_APPLICATION_INFO
ORA-06553: PLS-801: internal error [56319]

After this error sql prompt is appearing and if I m querying show user
it is showing me the particular usr…..

i have applied this steps to solve this problem

1. reinstall dbms_application_info by running standard.sql

so i have run that script catalog.sql n catproc.sql.....but while runnig
this script i got some error...

these are the errors occured while runnig CATALOG.SQL,CATPPROC.SQL AND
UTLPR.SQL and standard.sql

SQL> @/usr5/oracle/app/oracle/product/;
create or replace
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-06553: PLS-801: internal error [56319]

create or replace
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-06553: PLS-801: internal error [56319]

so, i thought there is some problem with above
.sql script may be it is invalid so we have
reinstall oracle software. and configure standby
db again..

but after converting standby to primary i m getting same
errors. we have also reinstalled os at standby side but problem is still there

steps which i have followed to convert standby db to primary db

1. took a cold backup of standby db so we can revert back.
2. archived and applied up to last sequence of archive log files from
3. now both db's are down
4. startup nomount(at standby)
5. alter database mount standby database(at standby )
6. recover standby database(at standby)
7. alter database activate standby database(at standby)
8. shutdown immediate(at standby )
9. starup(at standby)
now standby db is become primary db and primary db is down.

plz give me a solution because we r trying to solve this since last 4 months
Previous Topic: Standby Swtich over
Next Topic: logical standby method for applying SQL to primary ?
Goto Forum:

Current Time: Sun Jan 16 21:39:14 CST 2022