1: 使用ALTER *** COMPLIE语句手工进行编译，这个适用于少数、个别对象失效
alter package <schema name>.<package_name> compile;
alter package <schema name>.<package_name> compile body;
alter view <schema name>.<view_name> compile;
alter trigger <schema).<trigger_name> compile;
2：执行@$ORACLE_HOME/rdbms/admin/utlrp.sql脚本编译数据库失效对象。
许多情况下，由于数据库的升级或迁移，会导致数据库中的对象失效。由于对象之间可能存在复杂的倚赖关系，所以手工编译通常无法顺利通过。通常我们会在Oracle的升级指导中看到这个脚本，Oracle强烈推荐在migration/upgrade/downgrade之后，通过运行此脚本编译失效对象。但是注意,Oracle提醒，此脚本需要用SQLPLUS以SYSDBA身份运行，并且当时数据库中最好不要有活动事物或DDL操作，否则极容易导致死锁的出现（这是很容易理解的）。
Oracle highly recommends running this script towards the end of of any migration/upgrade/downgrade.
另外，utlrp.sql 里面其实调用了$ORACLE_HOME/rdbms/admin/utlrcmp.sql来编译失效对象。
3：ORACLE提供了自动编译的接口dbms_utility.compile_schema(user,false); 调用这个过程就会编译所有失效的过程、函数、触发器、包
exec dbms_utility.compile_schema( ‘SCOTT‘ )
set heading off ;
set feedback off ;
set echo off ;
Set lines 999 ;
Spool run_invalid.sql
select
‘ALTER ‘ ||
OBJECT_TYPE || ‘ ‘ ||
OWNER || ‘.‘ ||
OBJECT_NAME || ‘ COMPILE;‘
from
dba_objects
where
status = ‘INVALID‘
and
object_type in ( ‘PACKAGE‘ ,‘FUNCTION‘ , ‘PROCEDURE‘, ‘TRIGGER‘ ,‘JAVA
SOURCE‘, ‘JAVA CLASS‘, ‘‘ )
;
spool off;
set heading on ;
set feedback on ;
set echo on ;
SQL2：
DECLARE
v_objname user_objects.object_name% TYPE ;
v_objtype user_objects.object_type% TYPE ;
CURSOR cur IS
SELECT object_name,
object_type
FROM user_objects
WHERE status
= ‘INVALID‘
AND object_type IN ( ‘FUNCTION‘,
‘JAVA
SOURCE‘ ,
‘JAVA
CLASS‘ ,
‘PROCEDURE‘ ,
‘PACKAGE‘ ,
‘TRIGGER‘ );
BEGIN
OPEN cur;
LOOP
FETCH cur
INTO v_objname,
v_objtype;
EXIT WHEN cur% NOTFOUND;
BEGIN
EXECUTE IMMEDIATE ‘alter
‘ || v_objtype || ‘
‘ || v_objname ||
‘
Compile‘ ;
dbms_output.put_line( ‘编译‘ ||
v_objtype || ‘ ‘ ||
v_objname || ‘()成功‘ );
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line( ‘编译‘ ||
v_objtype || ‘ ‘ ||
v_objname ||
‘()失败.‘ || SQLERRM );
END ;
END LOOP ;
CLOSE cur;
END ;
