Home » RDBMS Server » Server Administration » ORA-04063: view "SYS.DBA_CAPTURE" has errors (Ora 10.2.0.1, AIX5.3)
ORA-04063: view "SYS.DBA_CAPTURE" has errors [message #449699] Wed, 31 March 2010 08:54 Go to next message
msantos@edemsa.com
Messages: 1
Registered: March 2010
Location: Mendoza, Argentina
Junior Member
Last weekend we changed our production server via backup-restore with RMAN. Everything went OK except when our DBA tried to drop de repository in order to use the EM (as the IP address changed) using emca with the option -repos drop. Apparently, he used SYSTEM user instead or SYSMAN as the repository owner because the system user was dropped. He tried to recreate it exporting the user from old system and importing it in the new one. Everything seemed fine until we tried to make a backup with RMAN and got the 'ORA-04063: view "SYS.DBA_CAPTURE" has errors' error. We are trying to recompile all the invalid packages but we get the following error:

1/14 PLS-00304: cannot compile body of 'DBMS_DEFER_QUERY' without its specification

1/14 PLS-00905: object SYS.DBMS_DEFER_QUERY is invalid

Any help?

Thanks.
Re: ORA-04063: view "SYS.DBA_CAPTURE" has errors [message #449703 is a reply to message #449699] Wed, 31 March 2010 09:03 Go to previous message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
  1* select owner, object_type from dba_objects where object_name = 'DBMS_DEFER_QUERY'
SQL> /

OWNER			       OBJECT_TYPE
------------------------------ -------------------
SYS			       PACKAGE
SYS			       PACKAGE BODY
PUBLIC			       SYNONYM

SQL> select owner, object_type from dba_objects where object_name = 'DBA_CAPTURE';

OWNER			       OBJECT_TYPE
------------------------------ -------------------
SYS			       VIEW
PUBLIC			       SYNONYM

04063, 00000, "%s has errors"
// *Cause:  Attempt to execute a stored procedure or use a view that has
//          errors.  For stored procedures, the problem could be syntax errors
//          or references to other, non-existent procedures.  For views,
//          the problem could be a reference in the view's defining query to
//          a non-existent table.
//          Can also be a table which has references to non-existent or
//          inaccessible types.
// *Action: Fix the errors and/or create referenced objects as necessary.
Previous Topic: Growth Estimation
Next Topic: patch
Goto Forum:
  


Current Time: Sat Jun 29 00:04:58 CDT 2024