oracle-04063,ORA-04063 错误问题（package body "SYS.DBMS_LOGSTDBY" has errors）

SQL> @?/rdbms/admin/dbmslsby.sql

Package created.

No errors.

Synonym created.

PL/SQL procedure successfully completed.

Grant succeeded.

CREATE ROLE logstdby_administrator

*

ERROR at line 1:

ORA-01921: role name 'LOGSTDBY_ADMINISTRATOR' conflicts with another user or

role name

Grant succeeded.

Grant succeeded.

Grant succeeded.

Library created.

SQL> @?/rdbms/admin/prvtlsby.plb

Warning: Package Body created with compilation errors.

Errors for PACKAGE BODY SYS.DBMS_LOGSTDBY:

LINE/COL ERROR

-------- -----------------------------------------------------------------

646/3    PL/SQL: SQL Statement ignored

647/10   PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors

grant select on dba_logstdby_progress to select_catalog_role

*

ERROR at line 1:

ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors

grant select on dba_logstdby_log to select_catalog_role

*

ERROR at line 1:

ORA-04063: view "SYS.DBA_LOGSTDBY_LOG" has errors

0 rows updated.

Commit complete.

SQL>

SQL> @?/rdbms/admin/utlrp.sql

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP UTLRP_BGN  2012-12-22 20:20:47

DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid

DOC>   objects in the database. Recompilation time is proportional to the

DOC>   number of invalid objects in the database, so this command may take

DOC>   a long time to execute on a database with a large number of invalid

DOC>   objects.

DOC>

DOC>   Use the following queries to track recompilation progress:

DOC>

DOC>   1. Query returning the number of invalid objects remaining. This

DOC>      number should decrease with time.

DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);

DOC>

DOC>   2. Query returning the number of objects compiled so far. This number

DOC>      should increase with time.

DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;

DOC>

DOC>   This script automatically chooses serial or parallel recompilation

DOC>   based on the number of CPUs available (parameter cpu_count) multiplied

DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).

DOC>   On RAC, this number is added across all RAC nodes.

DOC>

DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel

DOC>   recompilation. Jobs are created without instance affinity so that they

DOC>   can migrate across RAC nodes. Use the following queries to verify

DOC>   whether UTL_RECOMP jobs are being created and run correctly:

DOC>

DOC>   1. Query showing jobs created by UTL_RECOMP

DOC>         SELECT job_name FROM dba_scheduler_jobs

DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';

DOC>

DOC>   2. Query showing UTL_RECOMP jobs that are running

DOC>         SELECT job_name FROM dba_scheduler_running_jobs

DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';

DOC>#

DECLARE

*

ERROR at line 1:

ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors

ORA-06508: PL/SQL: could not find program unit being called:

"SYS.DBMS_INTERNAL_LOGSTDBY"

ORA-06512: at "SYS.UTL_RECOMP", line 827

ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors

ORA-06508: PL/SQL: could not find program unit being called:

"SYS.DBMS_INTERNAL_LOGSTDBY"

ORA-06512: at line 4

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP UTLRP_END  2012-12-22 20:20:48

DOC> The following query reports the number of objects that have compiled

DOC> with errors (objects that compile with errors have status set to 3 in

DOC> obj$). If the number is higher than expected, please examine the error

DOC> messages reported with each object (using SHOW ERRORS) to see if they

DOC> point to system misconfiguration or resource constraints that must be

DOC> fixed before attempting to recompile these objects.

DOC>#

OBJECTS WITH ERRORS

-------------------

59

DOC> The following query reports the number of errors caught during

DOC> recompilation. If this number is non-zero, please query the error

DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors

DOC> are due to misconfiguration or resource constraints that must be

DOC> fixed before objects can compile successfully.

DOC>#

ERRORS DURING RECOMPILATION

---------------------------

0

Function created.

PL/SQL procedure successfully completed.

Function dropped.

Warning: XDB now invalid, could not find xdbconfig

PL/SQL procedure successfully completed.

SQL> select object_name,status from dba_objects where status like '%INVALID%' and owner='SYS' and object_name like '%DBMS%';

OBJECT_NAME                              STATUS

---------------------------------------- -------

DBMS_XSTREAM_UTL_IVK                     INVALID

DBMS_XSTREAM_ADM_UTL                     INVALID

DBMS_STREAMS_SM                          INVALID

DBMS_STREAMS_MC                          INVALID

DBMS_STREAMS_AUTO_INT                    INVALID

DBMS_STREAMS_ADM                         INVALID

DBMS_RCVMAN                              INVALID

DBMS_LOGSTDBY                            INVALID

DBMS_LOGREP_UTIL                         INVALID

DBMS_LOGMNR_SESSION                      INVALID

DBMS_LOGMNR_LOGREP_DICT                  INVALID

DBMS_LOGMNR_INTERNAL                     INVALID

DBMS_LOGMNR_FFVTOLOGMNRT                 INVALID

DBMS_INTERNAL_LOGSTDBY                   INVALID

DBMS_CAPTURE_SWITCH_INTERNAL             INVALID

DBMS_CAPTURE_SWITCH_ADM                  INVALID

DBMS_CAPTURE_PROCESS                     INVALID

DBMS_CAPTURE_ADM_INTERNAL                INVALID

DBMS_CAPTURE_ADM                         INVALID

DBMS_APPLY_HANDLER_ADM                   INVALID

DBMS_APPLY_ADM_INTERNAL                  INVALID

DBMS_APPLY_ADM                           INVALID

22 rows selected.