Discussion:
ora-04063 sys.dba_queue_tables has errors
(too old to reply)
Jeff Kish
2007-01-05 17:23:36 UTC
Permalink
Hi.

Is there some way to rebuild the data dictionary or otherwise solve this
problem?

I'm running Oracle 10g on Windows 2003 server.

I was running an app that installs data and it got:

java.sql.SQLException: ora-04963: PACKAGE BODY "sys.dbms_logstdby" has errors.

I went into Oracle Enterprise Manager Consol and used find database objects to
try to find "dbms_logstdby".

After running a bit it came back with a message box that said:

(caption) Find Database Objects
(body) The Following SQL error has ocurred.
"ORA-04063: VIEW " sys.dba_queue_tables" HAS ERRORS"
Please check the scope specification provided to correct the SQL error if
possible.

When I bring up the view sys.dba_queue_tables and try to compile it, I get an
error:
ORA-00942 table or view does not exist for a select from (partial) from

system.aq$_queue_tables t, sys.col$ c, sys.coltype$ ct, sys.obj$ o,


I assume the data dictionary is hosed, but I really, to be frank, am only
guessing.

thanks
Jeff Kish
DA Morgan
2007-01-05 20:33:02 UTC
Permalink
Post by Jeff Kish
Hi.
Is there some way to rebuild the data dictionary or otherwise solve this
problem?
I'm running Oracle 10g on Windows 2003 server.
java.sql.SQLException: ora-04963: PACKAGE BODY "sys.dbms_logstdby" has errors.
I went into Oracle Enterprise Manager Consol and used find database objects to
try to find "dbms_logstdby".
(caption) Find Database Objects
(body) The Following SQL error has ocurred.
"ORA-04063: VIEW " sys.dba_queue_tables" HAS ERRORS"
Please check the scope specification provided to correct the SQL error if
possible.
When I bring up the view sys.dba_queue_tables and try to compile it, I get an
ORA-00942 table or view does not exist for a select from (partial) from
system.aq$_queue_tables t, sys.col$ c, sys.coltype$ ct, sys.obj$ o,
I assume the data dictionary is hosed, but I really, to be frank, am only
guessing.
thanks
Jeff Kish
Assuming the data dictionary is "hosed" is not self-evident from what
you've posted.

Start here:

conn / as sysdba

SELECT object_name, object_type
FROM dba_objects
WHERE status = 'INVALID';

Then, if there are recompile them as follows:

SQL> ?/rdbms/admin/utlrp.sql

If it is beyond repair, and I'd sure want to know how and why and verify
things in the alertlog and with an SR at metalink ... you can rerun
catalog.sql.

But if you do so, without checking with Oracle first, don't blame me if
you make a bigger mess than you already may have.
--
Daniel A. Morgan
University of Washington
***@x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
Jeff Kish
2007-01-09 19:18:32 UTC
Permalink
<snip>
Post by DA Morgan
Assuming the data dictionary is "hosed" is not self-evident from what
you've posted.
probably right. I assumed because it could not find some important sounding
stuff. (system.aq$_queue_tables...) I was either wrong or didn't show enough
evidence.
Post by DA Morgan
conn / as sysdba
SELECT object_name, object_type
FROM dba_objects
WHERE status = 'INVALID';
SQL> ?/rdbms/admin/utlrp.sql
If it is beyond repair, and I'd sure want to know how and why and verify
things in the alertlog and with an SR at metalink ... you can rerun
catalog.sql.
But if you do so, without checking with Oracle first, don't blame me if
you make a bigger mess than you already may have.
Luckily this is not a production system. I ended up uninstalling and
reinstalling Oracle. kind of a pain, but the utlrp.sql did not fix it and I
ran out of time.

Listen.. thanks so much for your suggestions and time. I appreciate it.
(things get frantic sometimes)
Jeff Kish

Loading...