[[email protected] dbs]$ sqlplus /as sysdba

SQL*Plus: Release 11.2.0.4.0Production on Sat Oct 4 04:11:22 2014
Copyright (c) 1982, 2013,Oracle.  All rights reserved.
 
Connected to an idleinstance.
 
SQL> startup

ORACLE instance started.
 
Total System Global Area 2872786944bytes
Fixed Size                  2256712 bytes
Variable Size            2634023096 bytes
Database Buffers          218103808 bytes
Redo Buffers               18403328 bytes
Database mounted.

Database opened.

SQL> @?/rdbms/admin/utlrp
 
TIMESTAMP
--------------------------------------------------------------------------------

COMP_TIMESTAMPUTLRP_BGN  2014-10-04 04:14:57
DOC>   The following PL/SQL block invokesUTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation timeis 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 alarge number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to trackrecompilation progress:
DOC>
DOC>   1. Query returning the number of invalidobjects remaining. This
DOC>      number should decrease with time.
DOC>         SELECT COUNT(*) FROM obj$ WHERE statusIN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objectscompiled so far. This number
DOC>      should increase with time.
DOC>         SELECT COUNT(*) FROMUTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial orparallel recompilation
DOC>   based on the number of CPUs available(parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameterparallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RACnodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to createjobs for parallel
DOC>   recompilation. Jobs are created withoutinstance affinity so that they
DOC>   can migrate across RAC nodes. Use thefollowing queries to verify
DOC>   whether UTL_RECOMP jobs are being createdand 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 arerunning
DOC>         SELECT job_name FROMdba_scheduler_running_jobs
DOC>            WHERE job_name like'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL proceduresuccessfully completed.
 
TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMPUTLRP_END  2014-10-04 04:15:34
DOC> The following queryreports the number of objects that have compiled
DOC> with errors.
DOC>
DOC> If the number ishigher than expected, please examine the error
DOC> messages reportedwith each object (using SHOW ERRORS) to see if they
DOC> point to systemmisconfiguration or resource constraints that must be
DOC> fixed beforeattempting to recompile these objects.
DOC>#

OBJECTS WITH ERRORS
-------------------
                  0

DOC> The following queryreports the number of errors caught during
DOC> recompilation. Ifthis number is non-zero, please query the error
DOC> messages in thetable UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due tomisconfiguration or resource constraints that must be
DOC> fixed before objectscan compile successfully.
DOC>#
 
ERRORS DURING RECOMPILATION
---------------------------
                          0
 
Function created.
 
PL/SQL proceduresuccessfully completed.
 
Function dropped.
 
PL/SQL proceduresuccessfully completed.

SQL>