How to compile invalid objects parallel
how to compile invalid objects parallelly in EBS 11i / 11g R2 DB in Linux
SQL> alter package apps.AD_PA_SUBMIT_REQUEST compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.AD_PA_SUBMIT_REQUEST:
LINE/COL ERROR
674/4 PL/SQL: Statement ignored
674/16 PLS-00302: component 'SET_AGGREGATE_LIST' must be declared
SQL> alter package AD_PA_SUBMIT_REQUEST compile;
alter package AD_PA_SUBMIT_REQUEST compile
ERROR at line 1:
ORA-04043: object AD_PA_SUBMIT_REQUEST does not existPlease run adpasrb.pls and adpasrs.pls under $AD_TOP/patch/115/sql directory to recreate this package and see if you get the same error or not.
SQL> alter package apps.AD_PA_INSERT_PACKAGE compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.AD_PA_INSERT_PACKAGE:
LINE/COL ERROR
149/3 PL/SQL: SQL Statement ignored
186/24 PL/SQL: ORA-02289: sequence does not exist
SQL> show error
Errors for PACKAGE BODY APPS.AD_PA_INSERT_PACKAGE:
LINE/COL ERROR
149/3 PL/SQL: SQL Statement ignored
186/24 PL/SQL: ORA-02289: sequence does not existPlease run adpaipb.pls and adpaips.pls under $AD_TOP/patch/115/sql directory to recreate this package and see if you get the same error or not.
SQL> alter package apps.CS_WF_ACTIVITIES_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.CS_WF_ACTIVITIES_PKG:
LINE/COL ERROR
611/9 PL/SQL: SQL Statement ignored
624/35 PL/SQL: ORA-00918: column ambiguously definedPlease see these docs.
CS_WF_ACTIVITIES_PKG Invalid Package With "ORA-00918: column ambiguously defined" [ID 464633.1]
Invalid Package CS_WF_ACTIVITIES_PKG [ID 375355.1]
Thanks,
Hussein
Similar Messages
-
Hi,
We have total 31000 invalid object after 10.2.0.2 to 10.2.0.5 upgrade in EBS R12. How we compile these objects?Ashish,
if you are seeing PLS-00801: internal error [1041] when trying to compile a package that is invalid, you may need to run utlirp.sql against the instance and then the utlrp.sql script. You need to pay attention to the manner in which you run these scripts. To run the utlirp.sql script you need to:
shutdown the instance
restart instance in upgrade mode
startup upgrade
run the utlirp.sql script @utlirp or @?/rdbms/admin/utlirp
shutdown the instance and restart normally
run utlrp.sql @utlrp or @?/rdbms/admin/utlrp
If you are running an auto-config instance, you can source the db environment, optionally switch to the $ORACLE_HOME/rdbms/admin folder and shutdown the instance:
sqlplus 'as /sysdba'
shutdown immediate
startup upgrade;
@utilrp
shutdown
startup
@utlrp
After compiling everything, I would shutdown the instance using the ./addbctl stop script and then restart it. As stated elsewhere, it can take time to compile the invalids--many hours in some cases. The utlirp.sql script may run for quite awhile before it completes since it is invalidating objects.
Please make sure you read up on utlirp.sql and PLS-00801 if that's what you are encountering.
Riley -
Compile invalid objects in apps schema
i make compiled the apps schema by
adadmin,utlrp.sql,compiled manual but still i am getting INVALID objects .. how to compile these objects ?
Below is the output
SQL>
column owner format A9
column object_name format A31
column object_type format A15
column last_ddl_time format A10
spool invalids.lst
select OWNER, OBJECT_NAME,OBJECT_TYPE,LAST_DDL_TIME
from dba_objects where status='INVALID'
order by owner;
OWNER OBJECT_NAME OBJECT_TYPE LAST_DDL_T
APPS FV_FACTS_TBAL_TRANSACTIONS PACKAGE BODY 03-MAR-13
APPS IGI_IAC_REINSTATE_PKG PACKAGE BODY 03-MAR-13
APPS IGI_IAC_RETIREMENT PACKAGE BODY 03-MAR-13
APPS CST_PERIODIC_ABSORPTION_PROC PACKAGE BODY 03-MAR-13
APPS FV_SLA_UTL_PROCESSING_PKG PACKAGE BODY 03-MAR-13
APPS FV_CCR_UTIL_PVT PACKAGE BODY 03-MAR-13
APPS PSA_AP_BC_PVT PACKAGE BODY 03-MAR-13
APPS XLA_00200_AAD_S_000012_PKG PACKAGE BODY 03-MAR-13
APPS AR_RECEIPT_UPDATE_API_PUB PACKAGE BODY 03-MAR-13
APPS AR_AUTOREC_API PACKAGE BODY 03-MAR-13
10 rows selected.
SQL> alter package APPS.FV_FACTS_TBAL_TRANSACTIONS compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_FACTS_TBAL_TRANSACTIONS:
LINE/COL ERROR
1742/6 PL/SQL: SQL Statement ignored
1743/4 PL/SQL: ORA-00918: column ambiguously defined
SQL> alter package APPS.IGI_IAC_REINSTATE_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.IGI_IAC_REINSTATE_PKG:
LINE/COL ERROR
3470/3 PL/SQL: Statement ignored
3470/10 PLS-00306: wrong number or types of arguments in call to
'GET_ASSET_RETIRE_REC'
SQL> alter package APPS.IGI_IAC_RETIREMENT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.IGI_IAC_RETIREMENT:
LINE/COL ERROR
4247/10 PL/SQL: Statement ignored
4247/18 PLS-00306: wrong number or types of arguments in call to
'GET_ASSET_RETIRE_REC'
SQL> alter package APPS.CST_PERIODIC_ABSORPTION_PROC compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.CST_PERIODIC_ABSORPTION_PROC:
LINE/COL ERROR
3901/3 PL/SQL: Statement ignored
3901/3 PLS-00306: wrong number or types of arguments in call to
'ITERATION_PROCESS'
SQL> alter package APPS.FV_SLA_UTL_PROCESSING_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_SLA_UTL_PROCESSING_PKG:
LINE/COL ERROR
49/7 PL/SQL: Statement ignored
49/22 PLS-00302: component 'PSA_XLA_ERROR' must be declared
SQL> alter package APPS.FV_CCR_UTIL_PVT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_CCR_UTIL_PVT:
LINE/COL ERROR
2926/3 PL/SQL: Statement ignored
2926/19 PLS-00302: component 'CONTACT_NAME' must be declared
2928/4 PL/SQL: Statement ignored
2928/20 PLS-00302: component 'CONTACT_PHONE' must be declared
2929/8 PL/SQL: Statement ignored
2929/24 PLS-00302: component 'CONTACT_PHONE' must be declared
2931/3 PL/SQL: Statement ignored
2931/19 PLS-00302: component 'CONTACT_EMAIL' must be declared
2932/3 PL/SQL: Statement ignored
2932/19 PLS-00302: component 'CONTACT_FAX' must be declared
SQL> alter package APPS.PSA_AP_BC_PVT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.PSA_AP_BC_PVT:
LINE/COL ERROR
291/11 PL/SQL: Statement ignored
291/26 PLS-00302: component 'PSA_XLA_ERROR' must be declared
346/13 PL/SQL: Statement ignored
346/28 PLS-00302: component 'PSA_XLA_ERROR' must be declared
835/7 PL/SQL: Statement ignored
835/12 PLS-00313: 'ISPREPAYDIST' not declared in this scope
1002/15 PL/SQL: Statement ignored
1002/34 PLS-00201: identifier 'J' must be declared
1014/13 PL/SQL: Statement ignored
1014/48 PLS-00201: identifier 'I' must be declared
1020/13 PL/SQL: Statement ignored
LINE/COL ERROR
1020/43 PLS-00201: identifier 'I' must be declared
1022/13 PL/SQL: Statement ignored
1024/73 PLS-00201: identifier 'I' must be declared
1055/11 PL/SQL: Statement ignored
1055/48 PLS-00201: identifier 'I' must be declared
1057/11 PL/SQL: SQL Statement ignored
1057/51 PLS-00201: identifier 'I' must be declared
1080/80 PLS-00201: identifier 'I' must be declared
1080/80 PLS-00201: identifier 'I' must be declared
SQL> alter package APPS.XLA_00200_AAD_S_000012_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.XLA_00200_AAD_S_000012_PKG:
LINE/COL ERROR
157514/2 PLS-00103: Encountered the symbol "THEN" when expecting one of
the following:
( - + case mod new not null <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall merge time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe
<an alternatively-quoted string literal with character set
specification>
<an alternatively-quote
LINE/COL ERROR
SQL> alter package APPS.AR_RECEIPT_UPDATE_API_PUB compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.AR_RECEIPT_UPDATE_API_PUB:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/14 PLS-00201: identifier 'AR_RECEIPT_UPDATE_API_PUB' must be
declared
1/14 PLS-00304: cannot compile body of 'AR_RECEIPT_UPDATE_API_PUB'
without its specification
SQL> show err
Errors for PACKAGE BODY APPS.AR_AUTOREC_API:
LINE/COL ERROR
2724/9 PL/SQL: SQL Statement ignored
2740/27 PL/SQL: ORA-00904: "EXT"."SEQ_TYPE_LAST": invalid identifier
note:application v12.0.4 database 10.2.3SQL> alter package APPS.FV_FACTS_TBAL_TRANSACTIONS compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_FACTS_TBAL_TRANSACTIONS:
LINE/COL ERROR
1742/6 PL/SQL: SQL Statement ignored
1743/4 PL/SQL: ORA-00918: column ambiguously defined
SQL> alter package APPS.CST_PERIODIC_ABSORPTION_PROC compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.CST_PERIODIC_ABSORPTION_PROC:
LINE/COL ERROR
3901/3 PL/SQL: Statement ignored
3901/3 PLS-00306: wrong number or types of arguments in call to
'ITERATION_PROCESS'
SQL> alter package APPS.AR_RECEIPT_UPDATE_API_PUB compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.AR_RECEIPT_UPDATE_API_PUB:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/14 PLS-00201: identifier 'AR_RECEIPT_UPDATE_API_PUB' must be
declared
1/14 PLS-00304: cannot compile body of 'AR_RECEIPT_UPDATE_API_PUB'
without its specification
SQL> alter package APPS.XLA_00200_AAD_S_000012_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.XLA_00200_AAD_S_000012_PKG:
LINE/COL ERROR
157514/2 PLS-00103: Encountered the symbol "THEN" when expecting one of
the following:
( - + case mod new not null <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall merge time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe
<an alternatively-quoted string literal with character set
specification>
<an alternatively-quote
LINE/COL ERROR
SQL> alter package APPS.FV_CCR_UTIL_PVT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_CCR_UTIL_PVT:
LINE/COL ERROR
2926/3 PL/SQL: Statement ignored
2926/19 PLS-00302: component 'CONTACT_NAME' must be declared
2928/4 PL/SQL: Statement ignored
2928/20 PLS-00302: component 'CONTACT_PHONE' must be declared
2929/8 PL/SQL: Statement ignored
2929/24 PLS-00302: component 'CONTACT_PHONE' must be declared
2931/3 PL/SQL: Statement ignored
2931/19 PLS-00302: component 'CONTACT_EMAIL' must be declared
2932/3 PL/SQL: Statement ignored
2932/19 PLS-00302: component 'CONTACT_FAX' must be declared -
How to compile INVALID dba & user_objects...
Hi,
While upgrading 12.1.3, i am getting INVALID object error in more then 2103 objects, now i need to compile INVALID objects ONLY...
I have tried adadmin to compile but it has taken more then 20hrs to complete also this has compiling all the records, so i need to know how to compile those 2103 records..
Please some one suggest me the command or sql query to use for succeed this..
Thanks
Suresh
Edited by: Suresh on Mar 8, 2011 10:29 AMHi Hussein,
I have listed all invalid objects as per blow query...
select OBJECT_NAME, OWNER from dba_objects where status = 'INVALID';
NOTE: I have compiled invalid objects in database by using SQL> @utlrp.sql (as sysdba)
AND in application tier i tried through adadmin (APPS schema) even though its not compiling, invalid objects are not reducing..
OBJECT_NAME
OWNER
MTH_UDA_PKG
APPS
MTH_UTIL_PKG
APPS
OKL_DEAL_ASSET_PVT_W
APPS
OBJECT_NAME
OWNER
OKL_DEAL_CREAT_PVT_W
APPS
OKL_INTERNAL_BILLING_PVT
APPS
OE_OUTBOUND_INT
APPS
OBJECT_NAME
OWNER
OE_INBOUND_INT
APPS
OE_GENESIS_UTIL
APPS
OZF_SUPP_TRD_PRFLS_PKG
APPS
OBJECT_NAME
OWNER
OZF_SD_BATCH_PVT
APPS
OZF_SD_BATCH_FEED_PVT
APPS
OZF_SD_UTIL_PVT
APPS
OBJECT_NAME
OWNER
OZF_SUPP_TRADE_PROFILE_PVT
APPS
OZF_SUPP_TRADE_PROFILE_PVT_W
APPS
PA_CONTROL_API_PVT
APPS
OBJECT_NAME
OWNER
PAY_PAYJPCAD_XMLP_PKG
APPS
PAY_PAYJPGMT_XMLP_PKG
APPS
PAY_PAYJPLTX_XMLP_PKG
APPS
OBJECT_NAME
OWNER
PAY_PAYJPMAG_XMLP_PKG
APPS
PAY_PAYJPSDD_XMLP_PKG
APPS
PAY_PAYJPSQD_XMLP_PKG
APPS
OBJECT_NAME
OWNER
PAY_PAYJPSMT_XMLP_PKG
APPS
PAY_PAYJPWTM_XMLP_PKG
APPS
PAY_PYAURECP_XMLP_PKG
APPS
OBJECT_NAME
OWNER
PAY_DK_ARCHIVE_EIN
APPS
PAY_RETRO_STATUS_INTERNAL
APPS
HR_HELPDESK_UTIL_SS
APPS
OBJECT_NAME
OWNER
PER_GB_PENSRV_SVPN
APPS
PER_SUCCESSION_PLAN_API
APPS
PER_SUCCESSION_PLAN_SWI
APPS
OBJECT_NAME
OWNER
PN_MTM_ROLLFORWARD_PKG
APPS
RRS_SITE_UTILS
APPS
WSH_WSHRDINV_XMLP_PKG
APPS
OBJECT_NAME
OWNER
WSH_WSHRDPAK_XMLP_PKG
APPS
XLA_HIST_LEDGER_UPG_PKG
APPS
PER_SUCCESSION_PLAN_BK1
APPS
OBJECT_NAME
OWNER
PER_SUCCESSION_PLAN_BK2
APPS
MSC_CURRENCY_CONV_MV
APPS
MSD_DEM_OBI_DEMANTRA_MV
APPS
OBJECT_NAME
OWNER
FFP62356_01012000
APPS
FFP62357_01012000
APPS
FFP62358_01012000
APPS
OBJECT_NAME
OWNER
FFP62359_01012000
APPS
FFP62376_01012000
APPS
FFP62377_01012000
APPS
OBJECT_NAME
OWNER
FFP62378_01012000
APPS
FFP62379_01012000
APPS
F
CA
OBJECT_NAME
OWNER
G
CA
2032 rows selected.
SQL>
please guide me how to move forward ....
Thanks & Regard...
Suresh -
Compile Invalid Objects fails on first error
When attempting to compile invalid objects (Views or Packages) from the connection tree, the process fails on the first generated error and does not continue with the remaining invalid objects.
This is the code used by SQL Developer...
begin
FOR cur IN (SELECT OBJECT_NAME, OBJECT_TYPE, owner
FROM all_objects
WHERE object_type = :OBJECT_TYPE
and owner = :OBJECT_OWNER
AND status = 'INVALID' ) LOOP
if cur.OBJECT_TYPE = 'PACKAGE BODY' then
EXECUTE IMMEDIATE 'alter ' || cur.OBJECT_TYPE || ' ' || cur.OBJECT_NAME || ' compile body';
else
EXECUTE IMMEDIATE 'alter ' || cur.OBJECT_TYPE || ' ' || cur.OBJECT_NAME || ' compile';
end if;
end loop;
end;
...and this is the code used by a 'leading competitor' doing the same kind of process (amended by us to provide feedback)...
DECLARE
V_OWNER varchar2(30);
V_VIEWNAME varchar2(30);
C_ID integer;
I_RESULT integer;
CURSOR c is select OWNER, OBJECT_NAME from all_objects where owner in ('OCTOPUS', 'MILOGUSER') and object_type = 'VIEW' and STATUS = 'INVALID';
BEGIN
I_RESULT := -1;
OPEN c;
LOOP
FETCH c into V_OWNER, V_VIEWNAME;
EXIT WHEN c%NOTFOUND;
DBMS_OUTPUT.PUT_LINE(V_OWNER ||'.' ||V_VIEWNAME);
BEGIN
C_ID := DBMS_SQL.open_cursor;
DBMS_SQL.PARSE(C_ID, 'ALTER VIEW '|| V_OWNER || '.' || V_VIEWNAME || ' COMPILE', DBMS_SQL.v7);
I_RESULT := DBMS_SQL.EXECUTE(C_ID);
EXCEPTION
WHEN OTHERS THEN I_RESULT := -1; END;
DBMS_OUTPUT.PUT_LINE(I_RESULT);
DBMS_SQL.CLOSE_CURSOR(C_ID);
END LOOP;
END;
Note: the exception part of the code allows the process to continue and wouldn't take much to incorporate into SQL DeveloperBug logged andy.
B -
How to compile all objects.....in Oracle10g
Hi ,
The Oracle Doc about PL/SQL Packages and Types reffering to DBMS_UTILITY and the COMPILE_SCHEMA procedure....points out :
"Compiles all procedures, functions, packages, and triggers in the specified schema"
So how to compile views and possibly other db schema object types ......????
For example issuing the command :
select object_name from user_objects where status='INVALID';
we get all invalid objects, views , packages , e.t.c.
How to compile all types of objects ... except for EM10g env......
Many thanks....
SimYou may want to use Solomon Yakobson's utility available here:
http://apex.oracle.com/pls/otn/f?p=2853:5:4266218307366505 -
R12 - Compile Invalid objects (Fast Formula, Package Body and View) Urgent
Invalid objects about 43, in this Fast Formula 2 AP Package object, and 1 view
OWNER OBJECT_TYPE COUNT(*)
APPS PACKAGE BODY 37.00
APPS PROCEDURE 1.00
SCOTT PACKAGE BODY 1.00
APPS VIEW 1.00
APPS FUNCTION 3.00
any one can give idea to make it valid.
Awaiting for your reply.
FYI
the object list is below.
OWNER OBJECT_NAME
APPS FFP52474_01010001
APPS FFP61059_01010001
APPS FFP56168_01010001
APPS FFP56167_01010001
APPS FFP58579_01052004
APPS FFP56169_01010001
APPS FFP56170_01010001
APPS FFP56171_01010001
APPS FFP56172_01010001
APPS FFP56173_01010001
APPS FFP60309_01010001
APPS FFP60306_01010001
APPS FFP60308_01010001
APPS FFP60310_01010001
APPS FFP60307_01010001
APPS AP_IMPORT_VALIDATION_PKG
APPS FFP58576_01011951
APPS FFP60357_01011951
APPS FFP57511_01010001
APPS FFP57510_01010001
APPS FFP52473_01010001
APPS FFP60305_01010001
APPS FFP60545_01042004
APPS FFP60342_01010001
APPS FFP58887_01042004
APPS FFP58888_01042004
APPS FFP58870_01042004
APPS FFP58885_01042004
APPS FFP58907_01010001
APPS FFP58906_01010001
APPS FFP58861_01042004
APPS FFP61122_01010001
APPS FFP58871_01042004
APPS FFP58857_01042005
APPS FFP60917_01032006
SCOTT MK_PLS_XML_REP_TEST
APPS MK_PLS_XML_REP_TEST
APPS AP_FSX_PAYMENT_ADVICE
APPS RA_SITE_USES
APPS ZDBAR_CONTACT
APPS ZDBAR_FAX
APPS ZDBCLOAD
APPS ZDBAP_DV_PAYMENT_TYPE
Advanced thanks for reading and giving solution for this.
Thamaraiselvanany one can give idea to make it valid.Run "Compile APPS Schema" from adadmin.
For Fast Formulas, refer to:
Note: 155737.1 - How To Compile Oracle Fast Formulas
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=155737.1 -
R12.1.3 : Adadmin hangs while compiling invalid objects
Dear All ,
Recently we have upgraded 11i to R12.1.3, from the base upgrade we have 2 custom invalid object..(its default).
if the invalid objects increase we use to compile with adadmin to compiling those invalid objects. but while compiling this adadmin window hangs down those objects are compiled.
can anyone tell me what might be the problem., how to resolve this ?
Kindly help me
by putty i ran this adadmin utility
Our OS version is OEL 4.5
Upgraded Ebiz application version is R12.1.3
Regards
HameedDear Hussein,
I didnt found any errors in database log file and in Adadmin utility log file.
No, i dint tried to relink using adrelink.sh..
i am going by your given metalink ID, and let u know in few hours
Regards
Hameed -
Hi friends,
how do i compile all the invalid objects in one time ???
thanks,
RajHi,
Here's what I do when I need to recompile a user's schema. Don't say it's bullet proof, but so far it has worked for me. I use it after each deployment to a schema.
procedure recompile_schema
is
l_type user_objects.object_type%type;
l_name user_objects.object_name%type;
l_stat user_objects.status%type;
compile_error exception;
pragma exception_init(compile_error, -24344);
cursor dep_cur
is
select object_id
from (select o1.object_id
,o1.object_name
,o1.object_type
,o1.status
,d1.referenced_name
,d1.referenced_type
,case
when exists (select null
from user_dependencies d2
where d2.referenced_name = d1.name
and d2.referenced_type = d1.type)
then
1
else
0
end
is_referenced
from user_dependencies d1, user_objects o1
where o1.object_type in
('PACKAGE'
,'PROCEDURE'
,'FUNCTION'
,'PACKAGE BODY'
,'VIEW'
,'MATERIALIZED VIEW'
,'TRIGGER'
,'SYNONYM')
and d1.name = o1.object_name
and d1.type = o1.object_type)
where is_referenced = 1
start with is_referenced = 0
connect by object_name = prior referenced_name
and object_type = prior referenced_type
group by object_id
order by max(level) desc, object_id;
procedure do_compile(pi_object_type in user_objects.object_type%type
,pi_object_name in user_objects.object_name%type)
is
begin
--dbms_output.put_line('Compiling: ' || pi_object_name);
if pi_object_type = 'PACKAGE BODY'
then
exe('ALTER PACKAGE ' || pi_object_name || ' COMPILE BODY');
else
exe('ALTER ' || pi_object_type || ' ' || pi_object_name || ' COMPILE');
end if;
exception
when compile_error
then
dbms_output.put_line(sqlerrm);
end do_compile;
begin
dbms_output.put_line('recompiling invalid objects in schema ' || user);
-- loop through all objects in order of dependancy.
for rec in dep_cur
loop
-- select the objects attributes (type, name and status).
select object_type, object_name, status
into l_type, l_name, l_stat
from user_objects
where object_id = rec.object_id;
-- if the object is invalid, recompile it.
if l_stat = 'INVALID'
then
dbms_output.put_line('Compiling(1): ' || l_name);
do_compile(l_type, l_name);
end if;
end loop;
-- Recompile all remaining INVALID OBJECTS (all those without dependencies).
for rec
in (select object_type, object_name
from user_objects
where status = 'INVALID'
and object_type in
('PACKAGE'
,'PROCEDURE'
,'FUNCTION'
,'TRIGGER'
,'PACKAGE BODY'
,'VIEW'
,'MATERIALIZED VIEW'
,'TRIGGER'
,'SYNONYM'))
loop
dbms_output.put_line('Compiling(2): ' || rec.object_name);
do_compile(rec.object_type, rec.object_name);
end loop;
end recompile_schema;Regards
Peter -
Hello,
In my 10.2 g database, I have 56 "invalid" objects in PUBLIC. All are synonyms.
After running the utlrp.sql utility, the same 56 synonyms are still invalid. ( I ran it 3 times)
How can I repair the invalids, if the repair utility will not repair them?
Thanks, JohnDBA_ERRORS shows errors if a previous compilation gave invalid status, or if the object has been invoked in a statement.
example:
SQL> select status from dba_objects where object_name='V';
STATUS
INVALID
SQL> select text from dba_errors where name='V';
no rows selected
SQL> select * from v;
select * from v
ERROR at line 1:
ORA-04063: view "MYUSER.V" has errors
SQL> select text from dba_errors where name='V';
TEXT
ORA-00942: table or view does not exist
answered by Nicolas
select *
from dba_dependencies
where name = 'YOUR_PACKAGE'
and referenced_owner = 'ANYUSER' --- Comment this out if you are looking for yourself
and owner = USER --- Or can be set to any user
answered by Girish Sharma reference: from thread: Invalid Object -
Unable to compile invalid objects post R12.1.1to R12.1.3 upgrades
Hi Experts,
Kindly note that post upgrade from R12.1.1 to R12.1.3.
I am unable to compile the below invalid objects.
APPS PACKAGE BODY BIS_TARGET_LEVEL_PVT
APPS PACKAGE BODY MSC_CL_PULL
APPS PACKAGE BODY RLM_MANAGE_DEMAND_SV
APPS PACKAGE BODY RLM_RD_SV
APPS PACKAGE BODY RLM_EXTINTERFACE_SV
APPS PACKAGE BODY CSC_ACTION_ASSEMBLER_PVT_W
APPS PACKAGE BODY ASO_OPP_QTE_PUB
APPS PACKAGE BODY ISC_EDW_BOOK_SUM1_F_C
APPS PACKAGE BODY OPI_EDW_OPMINV_DAILY_STAT_F_C
APPS PACKAGE BODY ASO_SECURITY_INT
APPS PACKAGE BODY ASO_QUOTE_PUB_W
APPS PACKAGE BODY ASO_QUOTE_HEADERS_PVT
Please advise.
Mohammed Abdul MuqeetKindly note that post upgrade from R12.1.1 to R12.1.3.
I am unable to compile the below invalid objects.
APPS PACKAGE BODY BIS_TARGET_LEVEL_PVT
APPS PACKAGE BODY MSC_CL_PULL
APPS PACKAGE BODY RLM_MANAGE_DEMAND_SV
APPS PACKAGE BODY RLM_RD_SV
APPS PACKAGE BODY RLM_EXTINTERFACE_SV
APPS PACKAGE BODY CSC_ACTION_ASSEMBLER_PVT_W
APPS PACKAGE BODY ASO_OPP_QTE_PUB
APPS PACKAGE BODY ISC_EDW_BOOK_SUM1_F_C
APPS PACKAGE BODY OPI_EDW_OPMINV_DAILY_STAT_F_C
APPS PACKAGE BODY ASO_SECURITY_INT
APPS PACKAGE BODY ASO_QUOTE_PUB_W
APPS PACKAGE BODY ASO_QUOTE_HEADERS_PVTWhat is the error you get when you compile those invalid objects manually?
Please see these docs.
ASO Invalid Objects in 12.1.3 [ID 1235496.1]
How To Resolve RLM Invalids [ID 1450159.1]
R12: Contact Center: Package CSC_ACTION_ASSEMBLER_PVT_W Invalid [ID 1126155.1]
BIS_TARGET_LEVEL_PVT is Invalid After Upgrade to EBS 12.1.3 [ID 1364996.1]
Thanks,
Hussein -
Error when compiling invalid object XLA_00555_AAD_C_011117_PKG
Hello folks,
i am getting error when compiling the following object.
XLA_00555_AAD_C_011117_PKG
here i have mentioned below is what i have done for that invalid object.
SQL> select owner,object_name,object_type
2 from dba_objects
3 where status='INVALID';
OWNER
OBJECT_NAME
OBJECT_TYPE
APPS
XLA_00555_AAD_C_011117_PKG
PACKAGE BODY
SQL> connect apps/apps
Connected.
SQL> alter package XLA_00555_AAD_C_011117_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show errors;
Errors for PACKAGE BODY XLA_00555_AAD_C_011117_PKG:
LINE/COL ERROR
32209/1 PLS-00103: Encountered the symbol "NVL" when expecting one of the
following:
* & - + / at mod remainder rem then <an exponent (**)> and or
|| multiset
The symbol "*" was substituted for "NVL" to continue.
32209/23 PLS-00103: Encountered the symbol "=" when expecting one of the
following:
. ( * % & - + / at mod remainder rem then <an exponent (**)>
and or ||
The symbol "* was inserted before "=" to continue.
LINE/COL ERROR
Please Provide me solution as soon as possible
Regards,
FarookNot exactly a custom object.
XLA%AAD%PKG packages will be built dynamically by the XLA's AAD compiler. This will be used while generating the accounting entries.
This error may occur due to two reasons:
a) missing source, which is used in the setup
SELECT *
FROM xla_conditions xc
WHERE application_id = &appl_id
AND xc.source_code IS NOT NULL
AND NOT EXISTS (SELECT 1
FROM xla_sources_b xsb
WHERE xc.source_application_id = xsb.application_id
AND xc.source_type_code = xsb.source_type_code
AND xc.source_code = xsb.source_code);
b) wrong conditions in setup
SELECT application_id,amb_context_code,entity_code,event_class_code
,accounting_line_type_code,accounting_line_code
,segment_rule_detail_id,description_prio_id
FROM xla_conditions xc
WHERE application_id = &appl_id
GROUP BY application_id,amb_context_code,entity_code,event_class_code
,accounting_line_type_code,accounting_line_code
,segment_rule_detail_id,description_prio_id
HAVING COUNT(*) > 1
AND SUM(NVL2(source_code,1,0)) <> SUM(NVL2(logical_operator_code,1,0)) + 1;
For (a) check any patch available for the missing source. Otherwise contact Oracle Support.
For (b) check the condition of the JLT / JED / ADR, whether anything is wrongly entered.
By
Vamsi -
Unable to Compile Invalid Objects
Why are the following Objects invalid?
All attempt to re-compile these objects files, what am I missing?
OWNER OBJECT_NAME OBJECT_TYPE STATUS
CASHAR WB_OLAP_LOAD_CUBE PROCEDURE INVALID
CASHAR WB_OLAP_LOAD_DIMENSION PROCEDURE INVALID
CASHAR WB_OLAP_LOAD_DIMENSION_GE PROCEDURE INVALIDIn general, the errors you get on compilation will point to the specific offending line and statement.
Being that all three of these procedures call OLAP DBMS_AWM packages, I would venture to guess there is something wrong with access to these packages.
Execute the following from OWB target schema:
select owner, object_name, procedure_name
from dba_procedures
where object_name like 'DBMS_AWM%'
If this query returns nothing, you most likely don't have an OLAP Server installed in the database. That would be indicated by the lack of OLAPSYS schema and nothing from this query:
select comp_name, version, status, schema
from dba_registry
where comp_name like '%OLAP%'
So install OLAP Server if you need to use these OWB procedures. Note that OLAP Server is the extra cost option to Oracle Enterprise Edition database.
Nikolai -
How to find invalid objects in specific schema?
Please let me know hoe to find invalid objects in specific schema such as SYS?
Please help and guide
Thanks,
Waheed.Ok i get invalid objects now if i want to delete these invalid objects which query i have to run?
also let me know there is no harm if i del invalid objects from SYS schema?
Please help and guide
Thanks,
Waheed. -
How to Compile Sys invalid objects
Dear,
We have found one invalid object in our database which owner is SYS.
How i compile this objects it's OBJECT_TYPE is package_body.
Please suggest me if any..
Wting
Rajhello.
I run this script, but sys's objects again to be with erros:
OWNER OBJECT_NAME
SYS ALL_WORKSPACES
SYS DBA_OUTLINES
SYS DBA_OUTLINE_HINTS
SYS DBA_WORKSPACES
SYS DBA_WORKSPACE_SESSIONS
SYS KU$_OUTLINE_VIEW
SYS LOGOFF_PROC
SYS LT
SYS LTADM
SYS LTDDL
SYS LTDTRG
SYS LTPRIV
SYS LTRIC
SYS LTUTIL
SYS LT_CTX_PKG
SYS NO_VM_CREATE
SYS NO_VM_CREATE_PROC
SYS NO_VM_DROP
SYS NO_VM_DROP_PROC
SYS OUTLN_PKG
SYS OWM_DDL_PKG
SYS OWM_MIG_PKG
SYS OWM_REPUTIL
SYS SYS_LOGOFF
SYS UD_TRIGS
SYS USER_OUTLINES
SYS USER_OUTLINE_HINTS
SYS USER_WORKSPACES
SYS WM$WORKSPACE_SESSIONS_VIEW
SYS WM_DDL_UTIL
SYS WM_INSTALLATION
MDSYS ALL_GEOMETRY_COLUMNS
MDSYS ALL_SDO_GEOM_METADATA
MDSYS ALL_SDO_INDEX_INFO
MDSYS ALL_SDO_INDEX_METADATA
MDSYS ALL_SDO_LRS_METADATA
MDSYS ALL_SDO_MAPS
MDSYS ALL_SDO_STYLES
MDSYS ALL_SDO_THEMES
MDSYS DBA_GEOMETRY_COLUMNS
MDSYS DBA_SDO_GEOM_METADATA
MDSYS DBA_SDO_INDEX_INFO
MDSYS DBA_SDO_INDEX_METADATA
MDSYS DBA_SDO_LRS_METADATA
MDSYS DBA_SDO_MAPS
MDSYS DBA_SDO_STYLES
MDSYS DBA_SDO_THEMES
MDSYS GEODETIC_SRIDS
MDSYS MD2
MDSYS SDO_CATALOG
MDSYS SDO_GEOM_TRIG_DEL1
MDSYS SDO_GEOM_TRIG_INS1
MDSYS SDO_GEOM_TRIG_UPD1
MDSYS SDO_LRS_TRIG_DEL
MDSYS SDO_LRS_TRIG_INS
MDSYS SDO_LRS_TRIG_UPD
MDSYS SDO_META
MDSYS SDO_MIGRATE
MDSYS SDO_RELATEMASK_TABLE
MDSYS SDO_RELATE_MASK
MDSYS TRANSFORM_MAP
MDSYS USER_GEOMETRY_COLUMNS
MDSYS USER_SDO_GEOM_METADATA
MDSYS USER_SDO_INDEX_INFO
MDSYS USER_SDO_INDEX_METADATA
MDSYS USER_SDO_LRS_METADATA
MDSYS USER_SDO_MAPS
MDSYS USER_SDO_STYLES
MDSYS USER_SDO_THEMES
Can I help you? thanks.
Oracle9i Enterprise Edition Release 9.2.0.2.0 - Production
Maybe you are looking for
-
Bonjour for windows gives this error - You do not have sufficient access...
I installed Bonjour for windows on a PC running XP. When I run the Bonjour app from windows I can see the printer I wish to connect to. It is shared off of my G3 server. When I try to connect I get the following error, "You do not have sufficient acc
-
Problems with 3.1.2 download, & iTunes dates...
So I purchased the 3.1.2 update and it did not download. It went to download 3.1.1. strange... It does not download citing a network connection. On my end I'm ok because you are reading my post so could it be from apple's side? Also, purchased it tod
-
Using Adobe Camera Raw as External Editor
I've recently purchased Aperture 2.1 and am very pleased with everything thus far. I capture the majority of my photos in the RAW format (Nikon NEF specifically), and the one thing I'm trying to work out is this - with iPhoto I am able to choose Adob
-
I have an older nano i've synched many tunes but when i try now it says can not synch
I have an older nano that i've synched many songs from i tunes but when i plug i pod in now it says can not synch #-39
-
Setting Flattener preferences when exporting PDF
Hi everyone, I'm trying to define a preset when exporting to PDF to make sure that layers transparency works properly independantly from what are the current presets in inDesign. var app:Application = InDesign.app; app.pdfExportPreferences.exportLaye