Use sempre a $ORACLE_HOME\/rdbms\/admin\/ultrp.sql <\/p>\n
sqlplus \/ as sysdba<\/p>\n
sql>@$ORACLE_HOME\/rdbms\/admin\/ultrp.sql;<\/p>\n
Conectado a:
Oracle Database 10g Express Edition Release 10.2.0.1.0 – Production<\/p>\n
SQL> @C:oraclexeapporacleproduct10.2.0serverRDBMSADMINutlrp.sql<\/p>\n
TIMESTAMP
—————————————————————————–<\/p>\n
COMP_TIMESTAMP UTLRP_BGN 2008-03-15 16:01:59<\/p>\n
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>#<\/p>\n
Procedimento PL\/SQL conclu\u03c6do com sucesso.<\/p>\n
TIMESTAMP
—————————————————————————–<\/p>\n
COMP_TIMESTAMP UTLRP_END 2008-03-15 16:02:05<\/p>\n
Procedimento PL\/SQL conclu\u03c6do com sucesso.<\/p>\n
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>#<\/p>\n
OBJECTS WITH ERRORS
——————-
0<\/p>\n
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>#<\/p>\n
ERRORS DURING RECOMPILATION
—————————
0<\/p>\n
Procedimento PL\/SQL conclu\u03c6do com sucesso.<\/p>\n
Advert\u03a9ncia: Voc\u03a9 n\u03c0o est\u00df mais conectado ao ORACLE.
SQL>
Conectado.
SQL> select count(*) from user_objects;<\/p>\n
COUNT(*)
———-
195<\/p>\n
SQL> select count(*) from user_objects where status = ‘INVALID’;<\/p>\n
COUNT(*)
———-
0<\/p>\n
SQL> select count(*) from user_objects where status = ‘INVALID’;<\/p>\n
COUNT(*)
———-
0<\/p>\n
SQL><\/p>\n","protected":false},"excerpt":{"rendered":"
Use sempre a $ORACLE_HOME\/rdbms\/admin\/ultrp.sql sqlplus \/ as sysdba sql>@$ORACLE_HOME\/rdbms\/admin\/ultrp.sql; Conectado a:Oracle Database 10g Express Edition Release 10.2.0.1.0 – Production SQL> @C:oraclexeapporacleproduct10.2.0serverRDBMSADMINutlrp.sql TIMESTAMP—————————————————————————– COMP_TIMESTAMP UTLRP_BGN 2008-03-15 16:01:59 DOC> The following PL\/SQL block invokes UTL_RECOMP to recompile invalidDOC> objects in the database. … Continue lendo