Identification of additional Invalid Objects of Apps Patches in Test mode!

All,
Could anyone please share if there is an option to "Identify additional Invalid Objects creation while applying Apps Patches in Test mode!"
EBS R12.1.1
DB:11.1.0.7
O/S:Linux Red Hat
Thanks for your time!
Regards,

Could anyone please share if there is an option to "Identify additional Invalid Objects creation while applying Apps Patches in Test mode!"There is no such an option and you will need to get that list manually -- Troubleshooting Guide - invalid objects in the E-Business Suite Environment 11i and 12 [ID 1325394.1]
Invalid Objects
https://forums.oracle.com/forums/search.jspa?threadID=&q=Invalid+AND+Objects&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Patch Analysis Report
https://forums.oracle.com/forums/search.jspa?threadID=&q=Patch+AND+Analysis+AND+Report&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Similar Messages

How to recompile all invalid objects of APPS?

Dear all:
How to recompile all invalid objects of APPS? my environment is ORACLE 9.2.0.5 32bit.
Regards
Terry

varun4dba wrote:
hi Terry,
did you tried adadmin?
thanks.Do you mean:
Compile/Reload Database Objects
1. Compile APPS schema
2. Compile menu information
3. Recreate grants and synonyms for APPS schema
4. Compile flexfield data in AOL tables
5. Reload JAR files to database
6. Return to Main Menu

Does patching in test mode requires Maintenance mode on?

Does patching in test mode requires Maintenance mode on or I have apply it with options=hotpatch
I am applying a patch in test mode and its erroring out giving error
AutoPatch error:
You must be in Maintenance Mode to apply patches.
You can use the AD Administration Utility to set Maintenance Mode.
Command I ran
*$ adpatch apply=n*
EBS 11.5.10.2

Srini Chavali wrote:
Maintenance mode is required for all adpatch runs where hotpatch option is not specified.Hi
SriniSo even in test mode, we have to run it in maintenance mode or hotpatch mode...wow!!

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.3

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.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

Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.

SP 2013 Server + Dec 2013 CU. Upgrading from SharePoint 2010.
We have a web application that is distributed over 7-8 content databases from SharePoint 2010. All but one database are upgradable. However, one database gives:
Invalid object name 'Webs'.
while running Test-SPContentDatabase or Mount-SPContentDatabase.
EventViewer has the following reporting 5586 event Id:
Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.
After searching a bit, these links do not help:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/fd020a41-51e6-4a89-9d16-38bff9201241/invalid-object-name-webs?forum=sharepointadmin
we are trying PowerShell only.
http://blog.thefullcircle.com/2013/06/mount-spcontentdatabase-and-test-spcontentdatabase-fail-with-either-invalid-object-name-sites-or-webs/
In our case, these are content databases. This is validated from Central Admin.
http://sharepointjotter.blogspot.com/2012/08/sharepoint-2010-exception-invalid.html
Our's is SharePoint 2013
http://zimmergren.net/technical/findbestcontentdatabaseforsitecreation-problem-after-upgrading-to-sharepoint-2013-solution
Does not seem like the same exact problem.
Any additional input?
Thanks, Soumya | MCITP, SharePoint 2010

Hi,
“All but one database are upgradable. However, one database gives:
Invalid object name 'Webs'.”
Did the sentence you mean only one database not upgrade to SharePoint 2013 and given the error?
One or more of the following might be the cause:
Insufficient SQL Server database permissions
SQL Server database is full
Incorrect MDAC version
SQL Server database not found
Incorrect version of SQL Server
SQL Server collation is not supported
Database is read-only
To resolve the issue, you can refer to the following article which contains the causes and resolutions.
http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

FRM-92160: WEB Client Version too old & Vis R12.0.4 invalid objects

Hello all,
I'm installing Vision R12.0.4 in a server. That server used to contain Vision R12.0.0 which I upgraded to R12.0.4 but still had some invalid objects (I already submitted that problem in another thread). I installed the new vision instance to the same folder used to contain R12.0.0 vision after remove the old installation.
After all installation steps completed I tried to connect from my laptop but I got this error message :
FRM-92160: WEB Client Version too old
Had tried to uninstall all java from my laptop but still had the same error message. I had oracle form & report developer 6i and 10g in my laptop. Tried to remove that installation and cleaned the registry but failed to delete LEGACY_ORACLE_LOAD_BALANCER_GO_CLIENT and some other objects.
I checked the installation and found 35 invalid objects, do APPS compile and left with 32 invalid objects. Here are the invalid objects :
OWNER     OBJECT_NAME
APPS     IGCBG_CC_NUMBER_METHODS
APPS     IGCFG_CC_NUMBER_METHODS
ORDSYS     ORDIMGEXTCODEC_PKG
ORDSYS     ORDIMG_PKG
SYS     XMLGENFORMATTYPE
SYS     LCR$_ROW_LIST
SYS     LCR$_ROW_UNIT
SYS     AQ$_SRVNTFN_MESSAGE
SYS     AQ$_REG_INFO
SYS     AQ$_REG_INFO_LIST
SYS     DBMS_SUMADV
SYS     AQ$_REG_INFO_LIST
SYS     DBMS_XPLAN_TYPE
SYS     DBMS_XPLAN_TYPE_TABLE
SYS     AQ$_DESCRIPTOR
SYS     AQ$_SRVNTFN_MESSAGE
SYS     AQ$_EVENT_MESSAGE
SYS     AQ$_REG_INFO
SYS     AQ$_SRVNTFN_MESSAGE
SYS     MSG_PROP_T
SYS     AQ$_DESCRIPTOR
XDB     servlet-list46_T
XDB     servlet52_COLL
XDB     servlet47_T
XDB     xdbconfig58_T
XDB     servlet-config-type42_T
XDB     webappconfig65_T
XDB     sysconfig59_T
XDB     XDB$RESOURCE_T
XDB     protocolconfig60_T
XDB     sysconfig59_T
XDB     xdbconfig58_T
XDB     httpconfig64_T
XDB     protocolconfig60_T
XDB     httpconfig64_T
How to solve those problems? Thanks.

The following views will remain invalid in 12.0.4:
APPS IGCBG_CC_NUMBER_METHODS
APPS IGCFG_CC_NUMBER_METHODS
This is documented in 12.0.4 Release Note:549389.1
under "Installation and Upgrade Customers"Thanks for the info. At least it solved 2 of my problem rows :P
anyway, I'm sorry that I can't tried to solve the problem anymore cause the storage was needed for another installation so I'd to remove this problem instance. Maybe if I can try it again I'll let you all know. Thanks

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 Muqeet

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_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

Invalid object after applying fa patch

Dear all,
Just now I had applied patch for FA & Generate message files from Generate Applications Files menu. How do I know that there are any invalid objects for FA after applying patch in order for me to run Compile APPS schema from adadmin to compile the invalid objects. What is the example for the invalid object message? What is the effect if I run Compile APPS schema eventhough there are no invalid object occur? Please advices.

HI,
Below is my last message after compiling the APPS Schema
======================================
There are now 1 jobs remaining (current phase=pc_errchk):
0 running, 1 ready to run and 0 waiting.
Assigned: file aderrchk.sql on worker 1 for product ad username APPLSYS.Spawned Process 29807
Completed: file aderrchk.sql on worker 1 for product ad username APPLSYS.
Done compiling APPS schema(s) in parallel.
Telling workers to quit...
All workers have quit.
Dropping FND_INSTALL_PROCESSES table...
FND_INSTALL_PROCESSES table dropped.
Dropping AD_DEFERRED_JOBS table...
AD_DEFERRED_JOBS table dropped.
Please check your log files for errors that may have occurred
while compiling invalid objects.
Be sure to look at the log file(s) for the parallel worker(s) which ran
adpcpcln.pls and aderrchk.sql. These scripts display compilation errors
and list objects which are still invalid.
sqlplus -s APPS/***** @/test/oracle/testappl/ad/11.5.0/admin/sql/adinvrst.pls *****
Spawned Process 29850
Review the messages above, then press [Return] to continue.
===========================================
I had run select owner, object_type, object_name from dba_objects where status = 'INVALID' order by 1,2; once again to look for an INVALID object but the INVALID object still appear.
Please advice. Do I need to run compile APPS Schema once again?

Is it ok to apply patch with invalid Objects?--Urgent

hello,
DB: 10.1.0.3.0
Patch: P4751926
OS: Linux
I have seven invlaid objects.
Is it ok to apply patch with invalid Objects?
sys.LEAF_CATEGORY_TYP------------------------------------TYPE BODY
sys.CUSTOMER_TYP----------------------------------------------TYPE
sys.CATALOG_TYP-------------------------------------------------TYPE BODY
sys.COMPOSITE_CATEGORY_TYP-------------------------TYPE BODY
sys.DBMS_STATS---------------------------------------------------PACKAGE BODY
sys.DBMS_STATS_INTERNAL--------------------------------- PACKAGE BODY
PUBLIC.DBMS_XDBUTIL_INT------------------------------------SYNONYM
DN

did u try to recompile the invalid objects with the utlrp.sql script? (the script is under, <oracle_home>/rdbms/admin
your dbms_stats is invalid, and that package is needed for getting the statistics so better to have it valid than invalid.

Tip : if patch 8708893 leaves lots of invalid objects after running pi.sq

after running post_install.sql you get lots of invalid objects
this has happened because the patch did not unzip properly [ occurred for me on Linux RH5 X86-64 ] .. it was unzipped by Grid Control itself in via a patch stage.
to fix : if you look at the files.sql in the patch directory you will see an execute of several.sql files.... just execute them manually and the errors will go away.
Chris.

Thanks Chris, good to know. I unfortunately went through the process of rolling back before finding your post.
I then reapplied the patch and it worked perfectly, so I never got to try your solution, but thought I'd post mine here with yours because google has it indexed already :)

Invalid objects after installing CU2 patch

hi,
i am getting following invalid objects which iam unable to compile , EBS version is 11.5.10.2 , database is 9.2.0.5
OBJECT_NAME OBJECT_TYPE T STATUS
XX_COMPLETE_PENDING_TRANS PROCEDURE N INVALID
WF_DEFERRED QUEUE N INVALID
WF_JAVA_ERROR QUEUE N INVALID
WF_JMS_IN QUEUE N INVALID
WF_JMS_OUT QUEUE N INVALID
WF_NOTIFICATION_IN QUEUE N INVALID
WF_NOTIFICATION_OUT QUEUE N INVALID
AS_CATALOG_MIGRATION PACKAGE BODY N INVALID
BIS_GRANTS_V VIEW N INVALID
CAC_SYNC_TASK_COMMON PACKAGE BODY N INVALID
CAC_SYNC_TASK_CURSORS PACKAGE N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
CAC_VIEW_PVT PACKAGE BODY N INVALID
CZ_SECURITY_PVT PACKAGE BODY N INVALID
EGO_CHANGE_PEOPLE_IMPORT_PKG PACKAGE BODY N INVALID
EGO_DATA_SECURITY PACKAGE BODY N INVALID
EGO_GROUP_WF_PKG PACKAGE BODY N INVALID
EGO_ITEM_PEOPLE_IMPORT_PKG PACKAGE BODY N INVALID
EGO_ITEM_PVT PACKAGE BODY N INVALID
EGO_PARTY_PUB PACKAGE BODY N INVALID
EGO_SECURITY_PUB PACKAGE BODY N INVALID
EGO_VALID_INSTANCE_SET_GRANTS PACKAGE BODY N INVALID
ENGECOBO PACKAGE BODY N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
ENG_CHANGE_ROUTE_UTIL PACKAGE BODY N INVALID
ENG_ECO_PVT PACKAGE BODY N INVALID
ENG_VALIDATE_ECO PACKAGE BODY N INVALID
ENG_WORKFLOW_UTIL PACKAGE BODY N INVALID
FND_DATA_SECURITY PACKAGE BODY N INVALID
FND_DM_SECURITY PACKAGE BODY N INVALID
FND_GRANTS_PKG PACKAGE BODY N INVALID
FND_OBJ_INS_GRANTS_V VIEW N INVALID
FND_OBJ_INS_SET_GRANTS_V VIEW N INVALID
GMF_LOTCOSTADJUSTMENT_PUB PACKAGE BODY N INVALID
HZ_DSS_GRANTS_PUB PACKAGE BODY N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
HZ_DSS_GRANTS_V VIEW N INVALID
HZ_DSS_UTIL_PUB PACKAGE BODY N INVALID
INV_EGO_REVISION_VALIDATE PACKAGE BODY N INVALID
INV_ITEM_PVT PACKAGE BODY N INVALID
JA_IN_GEM_RCP_TAX_HEADER_T1 TRIGGER N INVALID
JTA_SYNC_TASK_COMMON PACKAGE BODY N INVALID
JTA_SYNC_TASK_CURSORS PACKAGE N INVALID
JTF_CAL_GRANTS_PVT PACKAGE N INVALID
JTF_CAL_GRANTS_PVT PACKAGE BODY N INVALID
JTF_CAL_GRANTS_PVT_W PACKAGE N INVALID
JTF_CAL_GRANTS_PVT_W PACKAGE BODY N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
JTF_CAL_PVT PACKAGE BODY N INVALID
JTF_CAL_WF_PVT PACKAGE BODY N INVALID
JTF_TASK_SECURITY_PVT PACKAGE BODY N INVALID
JTF_TASK_SECURITY_V VIEW N INVALID
JTF_TASK_UTL PACKAGE BODY N INVALID
KPM_PC_REQUISIIONS_MAIL_PROC PROCEDURE N INVALID
MTL_CATEGORY_GRANTS_V VIEW N INVALID
MTL_OBJECT_GRANTS_V VIEW N INVALID
PA_ADVERTISEMENTS_PVT PACKAGE BODY N INVALID
PA_ASGMT_WFSTD PACKAGE BODY N INVALID
PA_ASSIGNMENTS_PUB PACKAGE BODY N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
PA_CANDIDATE_PUB PACKAGE BODY N INVALID
PA_CI_MERGE_PKG PACKAGE BODY N INVALID
PA_CI_SECURITY_PKG PACKAGE BODY N INVALID
PA_FCST_PERIODIC_DTL_V VIEW N INVALID
PA_FCST_PERIODIC_HDR_V VIEW N INVALID
PA_FCST_PERIODIC_SUM_V VIEW N INVALID
PA_FCST_PROJECT_DTL_V VIEW N INVALID
PA_FCST_PROJECT_HDR_V VIEW N INVALID
PA_FCST_PROJECT_LIST_V VIEW N INVALID
PA_FCST_PROJECT_SUM_V VIEW N INVALID
PA_NOMINATE_RES_LOV_STAFF_V VIEW N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
PA_ORG_AUTHORITY_V VIEW N INVALID
PA_PEOPLE_ROLE_ON_ORGS_V VIEW N INVALID
PA_PM_FUNCTION_SECURITY_PUB PACKAGE BODY N INVALID
PA_PROGRESS_REPORT_UTILS PACKAGE BODY N INVALID
PA_PROJECTS_CUST_360_V VIEW N INVALID
PA_PROJECT_LISTS_PORTLET_V VIEW N INVALID
PA_PROJECT_LISTS_USER_V VIEW N INVALID
PA_PROJECT_OPEN_ASSNS_STAFF_V VIEW N INVALID
PA_PROJECT_OPTIONS_SS_V VIEW N INVALID
PA_PROJECT_PARTIES_PVT PACKAGE BODY N INVALID
PA_PROJECT_SET_UTILS PACKAGE BODY N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
PA_PROJECT_STRUCTURE_PUB1 PACKAGE BODY N INVALID
PA_PROJECT_STRUCTURE_PVT1 PACKAGE BODY N INVALID
PA_PROJECT_STRUCTURE_UTILS PACKAGE BODY N INVALID
PA_PROJ_ELEMENTS_UTILS PACKAGE BODY N INVALID
PA_PROJ_MANAGER_V VIEW N INVALID
PA_PROJ_TASK_STRUC_PUB PACKAGE BODY N INVALID
PA_REPORT_UTIL PACKAGE BODY N INVALID
PA_REP_ALL_MGR_V VIEW N INVALID
PA_REP_ASMT_DTS_V VIEW N INVALID
PA_REP_FORECAST_ORG_V VIEW N INVALID
PA_REP_ORG_UTIL_V VIEW N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
PA_REP_REQT_DTS_V VIEW N INVALID
PA_RESOURCE_AUTHORITY_V VIEW N INVALID
PA_RESOURCE_AVAIL_STAFF_V VIEW N INVALID
PA_RESOURCE_UTILS PACKAGE BODY N INVALID
PA_RES_APRVL_ROLES_V VIEW N INVALID
PA_RES_AVL_HOURS_STAFF_V VIEW N INVALID
PA_RES_OVC_HOURS_STAFF_V VIEW N INVALID
PA_RES_SCH_TIMELINE_ROWLBL_V VIEW N INVALID
PA_RES_SCH_TIME_CHART_V VIEW N INVALID
PA_ROLE_STATUS_MENU_PVT PACKAGE BODY N INVALID
PA_ROLE_UTILS PACKAGE BODY N INVALID
OBJECT_NAME OBJECT_TYPE T STATUS
PA_SECURED_PROJECTS_V VIEW N INVALID
PA_SECURITY PACKAGE BODY N INVALID
PA_SECURITY_PVT PACKAGE N INVALID
PA_SECURITY_PVT PACKAGE BODY N INVALID
PA_STAFFED_ASSIGNMENT_PVT PACKAGE BODY N INVALID
PON_NEG_UPDATE_PKG PACKAGE BODY N INVALID
QA_SECURITY_PKG PACKAGE BODY N INVALID
QP_SECURITY PACKAGE BODY N INVALID
any suggestions

SQL> alter package FND_DATA_SECURITY compile body;
Warning: Package Body altered with compilation errors.
SQL> show errors
Errors for PACKAGE BODY FND_DATA_SECURITY:
LINE/COL ERROR
571/6553 PL/SQL: SQL Statement ignored
0
574/9 PL/SQL: ORA-00942: table or view does not exist
616/12 PL/SQL: SQL Statement ignored
617/17 PL/SQL: ORA-00942: table or view does not exist
660/6 PL/SQL: SQL Statement ignored
661/11 PL/SQL: ORA-00942: table or view does not exist
1743/10 PL/SQL: SQL Statement ignored
1745/17 PL/SQL: ORA-00942: table or view does not exist
1784/10 PL/SQL: SQL Statement ignored
LINE/COL ERROR
1786/17 PL/SQL: ORA-00942: table or view does not exist
1826/10 PL/SQL: SQL Statement ignored
1828/17 PL/SQL: ORA-00942: table or view does not exist
2254/19 PL/SQL: Statement ignored
2255/38 PLS-00364: loop index variable 'INSTANCE_SET_GRANTS_BKWD_REC' use
is invalid
2278/19 PL/SQL: Statement ignored
2280/30 PLS-00364: loop index variable 'INSTANCE_SET_GRANTS_BKWD_REC' use
is invalid
LINE/COL ERROR
2298/21 PL/SQL: Statement ignored
2299/40 PLS-00364: loop index variable 'INSTANCE_SET_GRANTS_REC' use is
invalid
2322/21 PL/SQL: Statement ignored
2324/32 PLS-00364: loop index variable 'INSTANCE_SET_GRANTS_REC' use is
invalid

Invalid Objects Need To Compile.

Hi,
Am having R12.1.3 instance, In that am having 61 invalid objects.
I was try to reduce by utlrp.sql script and also adadmin utility.
But its not reducing.
Below i have Mentioned invalid objects details.
SQL> select object_name,object_type,owner from dba_objects where status like 'INVALID';
OBJECT_NAME OBJECT_TYPE OWNER
HR_ENTRY_API PACKAGE BODY APPS
PAY_DYT_ELEMENT_ENTRY_VAL_PKG PACKAGE APPS
PAY_DYT_ELEMENT_ENTRY_VAL_PKG PACKAGE BODY APPS
WWV_FLOW_LIST_OF_VALUES_DATA SYNONYM PUBLIC
WWV_FLOW_PATCHES SYNONYM PUBLIC
WWV_FLOW_LISTS_OF_VALUES$ SYNONYM PUBLIC
WWV_FLOW_TEMP_TABLE SYNONYM PUBLIC
WWV_FLOW_CUSTOM_AUTH_SSO SYNONYM PUBLIC
WWV_FLOW_TEMPLATES_UTIL SYNONYM PUBLIC
HTMLDB_SQL_WORKSHOP SYNONYM PUBLIC
HTMLDB_DATA_WORKSHOP SYNONYM PUBLIC
OBJECT_NAME OBJECT_TYPE OWNER
WWV_FLOW_GENERIC SYNONYM PUBLIC
WWV_FLOW_DML SYNONYM PUBLIC
WWV_FLOW_FIELD_TEMPLATES SYNONYM PUBLIC
APPLICATION_AUTHENTICATION SYNONYM PUBLIC
WWV_RENDER_CALENDAR2 SYNONYM PUBLIC
WWV_FLOW_XML_REPORT SYNONYM PUBLIC
WWV_FLOW_XML_REPORT2 SYNONYM PUBLIC
DS_SQL_WORKSHOP SYNONYM PUBLIC
WWV_CREATE_FORUM_DEMO_SCRIPT SYNONYM PUBLIC
WWV_FLOW_LOOKUP_TABLES SYNONYM PUBLIC
WWV_FLOW_WEB_SERVICES SYNONYM PUBLIC
OBJECT_NAME OBJECT_TYPE OWNER
WWV_SPELING SYNONYM PUBLIC
WWV_FLOW_HELP SYNONYM PUBLIC
WWV_FLOW_REWRITE_QUERY SYNONYM PUBLIC
RE_PROFILER PACKAGE BODY RE
XXADT_PAY_REIMB_WF_PKG PACKAGE BODY APPS
WWV_FLOW_LOV_TEMP SYNONYM PUBLIC
RDT_1 TABLE HERMAN
MAIN_PROC PROCEDURE XX_CUST
SERIAL_MAIN_PROC PROCEDURE XX_CUST
TRO_HEADER_SRL_CONF PROCEDURE XX_CUST
GETSESSIONCOOKIE FUNCTION XX_CUST
OBJECT_NAME OBJECT_TYPE OWNER
PPGPL_POPULATE_TABLE PROCEDURE APPS
READ_PA_EXP_ITEM PROCEDURE APPS
TEST_PROC PROCEDURE APPS
VAR_BUDGET_PKG_1 PACKAGE BODY XX_CUST
PARENT_DEPARTMENT FUNCTION XX_CUST
EFFECTIVE_DATE FUNCTION XX_CUST
DECODE_POSITION FUNCTION XX_CUST
DECODE_ORGANIZATION FUNCTION XX_CUST
XLA_00707_AAD_C_000026_PKG PACKAGE BODY APPS
XLA_20065_AAD_C_000030_PKG PACKAGE BODY APPS
FSAH_DUPLICATE_PKG PACKAGE BODY APPS
OBJECT_NAME OBJECT_TYPE OWNER
XX_INVENTORY_ITEM_PKG PACKAGE BODY APPS
FN_ADD FUNCTION APPS
ADD_NEW FUNCTION APPS
XX_FND_USER_PKG PACKAGE BODY APPS
XX_ITEM_VALIDATE PROCEDURE APPS
XLA_00707_AAD_C_000044_PKG PACKAGE BODY APPS
SPEC PACKAGE APPS
XXGSC_ITEM_CREATION PACKAGE BODY APPS
SPECIFICATION PACKAGE APPS
XXHY_AMS_BUDGET_ORG_PKG PACKAGE BODY APPS
SAN_GET_SALARY FUNCTION APPS
OBJECT_NAME OBJECT_TYPE OWNER
SAN_GET_ELEMENTS_ENTRIES FUNCTION APPS
XXADT_AST_APP_HIST_V VIEW APPS
TRG TRIGGER APPS
MSD_DEM_OBI_DEMANTRA_MV MATERIALIZED VIEW APPS
F TABLE CA
G TABLE CA
61 rows selected.
If am compiling also it shows error.
SQL> alter package SPEC compile;
Warning: Package altered with compilation errors.
SQL> show error;
Errors for PACKAGE SPEC:
LINE/COL ERROR
1/15 PLS-00103: Encountered the symbol "XX_4I_INV_ITEM_CREATION_PKG"
when expecting one of the following:
is authid as compress compiled wrapped
The symbol "authid" was substituted for
"XX_4I_INV_ITEM_CREATION_PKG" to continue.
Please suggest me to reduce the invalid objects.

Please post the details of the database version and OS.
Was this application upgraded from 11i?
For XX% objects, these are custom ones and you need to visit the code and fix it (with the help of your developers).
For XLA objects, please see the following docs.
Invalid XLA Packages In Release 12.1.3 [ID 1496529.1]
Xla Invalids After Upgrade From 11i To Release 12 [ID 1302349.1]
XLA Package Invalid in 12.1.1 [ID 1093888.1]
R12: Invalid Xla Objects After Upgrade from 11i To R12 - Unable To Compile [ID 1238973.1]
Unable To Compile Invalid XLA Objects [ID 1468836.1]
For the rest of the invalid objects, please see the following docs.
Troubleshooting Guide - invalid objects in the E-Business Suite Environment 11i and 12 [ID 1325394.1]
R12.1:Invalid Objects After 11gr2 Db And Ebs 12.1.3 Upgrade [ID 1342701.1]
Just Upgraded To R12 And Now A Number Of Objects Won't Compile - Views: <PROD>BV_ -> <PROD>BG_ and <PROD>FV_ -> <PROD>FG_ [ID 560185.1]
R12.1.1 - Invalid Objects After Patching [ID 1093163.1]
If you still have invalid objects, please compile them manually and post the error here.
Thanks,
Hussein

INVALID Objects after upgrade from 12.1.1 to 12.1.3

Hi
Recently I have applied 9239090, 13984450, 10627841 patches to upgrade from 12.1.1 to 12.1.3, but now there are a number of Invalid objects in the DB.
I have tried to compile them through 'adadmin' utility, and even ran 'utlirp.sql' with 'utlrp.sql'. Tried bouncing all db, apps tier, apache but they still remains 'Invalid'. What kind of objects are they and whether they will have any impact on apps? How to compile them?
Any help will be really appreciated. Thanks.
As a test I tried to compile one object and get the following errors:
Package Body APPS.FFP55370_01011990@EBS12
Error(347,1): PL/SQL: Statement ignored
Error(347,5): PLS-00306: wrong number or types of arguments in call to 'ARREARAGE'
Error(382,1): PL/SQL: Statement ignored
Error(382,5): PLS-00306: wrong number or types of arguments in call to 'ARREARAGE'
Invalid Objects list
FFP55370_01011990
FFP50529_01011900
FFP50775_01011900
FFP52090_01011990
FFP50576_01011900
FFP54520_01011995
ImportExport
FFP58914_01010001
FFP60324_01010001
FFP56324_01011990
FFP50523_01011900
FFP54824_01012000
FFP59200_01011990
FFP55331_01011998
FFP55359_01011990
FFP58907_01010001
FFP55328_01011998
FFP55356_01011990
FFP58908_01010001
FFP59176_01012004
FFP57126_01011995
FFP60588_01011990
FFP61138_01010001
FFP61170_01010001
FFP61884_01010001
FFP61867_01010001
FFP62357_01012000
FFP62358_01012000
FFP62376_01012000
FFP51848_01011990
FFP50533_01011900
FFP50531_01011900
FFP54413_01011995
FFP54409_01011995
FFP52683_01071999
WWV_FLOW_LIST_OF_VALUES_DATA
WWV_FLOW_LISTS_OF_VALUES$
FFP58919_01010001
FFP58887_01042004
FFP51846_01011990
FFP59110_01011990
FFP57215_01011999
FFP56739_01011999
FFP56325_01011990
FFP59192_01011990
FFP1915_01010001
FFP56596_01012001
FFP1918_01010001
FFP57217_01012000
FFP59113_01011990
FFP55243_26121999
FFP56327_01011990
FFP54521_01011995
FFP60587_01011990
FFP60593_01011990
FFP60793_01012004
FSAH_DUPLICATE_PKG
FFP61920_01010001
FFP55366_01011990
FFP52681_01071999
FFP51840_01011990
FFP52621_01011996
FFP55065_01011990
FFP53477_01012001
FFP59131_01011990
FFP51850_01011990
FFP51838_01011990
FFP59273_01012004
FFP51849_01011990
FFP55077_01011990
FFP59251_01012004
FFP55240_26121999
FFP54414_01011995
FFP54393_01011995
FFP58912_01010001
FFP54823_01012000
FFP57196_01012000
FFP55362_01011990
FFP57216_01012000
FFP57125_01011995
FFP60833_01012000
FFP60943_01011990
FFP60964_01012000
FFP61532_01011990
XLA_00707_AAD_C_000026_PKG
FFP61919_01010001
FFP62359_01012000
FFP55060_01011990
FFP50510_01011900
FFP55355_01011990
FFP55058_01011990
FFP54406_01011995
FFP51867_01011990
FFP54474_01011995
FFP55361_01011990
FFP58885_01042004
FFP51844_01011990
FFP56716_01012001
FFP59175_01012004
FFP54525_01011995
FFP54909_01011990
FFP56329_01011990
FFP54407_01011995
FFP56052_01012000
FFP54524_01011995
FFP56056_01012000
FFP54404_01011995
FFP54523_01011995
FFP58913_01010001
FFP55306_01011995
FFP50525_01011900
FFP55333_01011998
FFP1916_01010001
FFP58911_01010001
FFP60555_01010001
FFP61156_01010001
FFP61152_01010001
FFP52982_01010001
FFP61511_01012000
FFP62356_01012000
FFP62378_01012000
FFP62379_01012000
FFP51404_01011997
FFP55358_01011990
FFP55067_01011990
FFP52115_01011990
FFP51887_01011990
FFP54398_01011995
FFP54411_01011995
WWV_FLOW_GENERIC
WWV_FLOW_FIELD_TEMPLATES
FFP53720_01011990
FFP54827_01012000
FFP50522_01011900
FFP55330_01011998
FFP54912_01011990
FFP59116_01011990
FFP59115_01011990
FFP54394_01011995
FFP56330_01011990
FFP56434_01012001
FFP58163_01011951
FFP59114_01011990
FFP56328_01011990
FFP58910_01010001
FFP60606_01011990
FFP61440_01011990
XLA_20065_AAD_C_000030_PKG
FFP55069_01011990
FFP53540_01012001
FFP55364_01011990
FFP55375_01011990
FFP50577_01011900
FFP52481_01010001
RE_PROFILER
FFP58915_01010001
FFP58920_01010001
FFP51888_01011990
FFP50928_01011997
FFP56333_01011990
FFP55063_01011990
FFP55367_01011990
FFP51068_01011997
FFP59111_01011990
FFP56332_01011990
FFP56323_01011990
FFP57190_01012000
FFP1919_01010001
FFP59191_01011990
FFP51966_01011998
FFP54403_01011995
FFP55368_01011990
FFP1917_01010001
FFP60592_01011990
FFP60607_01011990
FFP61277_01011951
FFP61871_01010001
FFP61926_01010001
FFP61897_01010001
FFP62377_01012000
FFP51837_01011990
FFP50512_01011900
FFP52744_01071999
FFP52724_01071999
FFP51411_01011999
FFP50527_01011900
FFP58888_01042004
FFP58870_01042004
FFP59117_01011990
FFP56331_01011990
FFP55080_01011990
FFP59112_01011990
FFP50583_01011900
FFP54518_01011995
FFP55079_01011990
FFP59195_01011990
FFP56053_01012000
FFP56322_01011990
FFP55373_01011990
FFP54449_01011995
FFP54522_01011995
FFP54948_01011990
FFP58918_01010001
FFP60591_01011990
RDT_1
FFP60944_01011990
FFP60963_01012000
FFP61124_01010001
FFP61912_01010001
MSD_DEM_OBI_DEMANTRA_MV
FFP55372_01011990
FFP50773_01011900
FFP53497_01012001
FFP51406_01011997
FFP50506_01011900
FFP50508_01011900
FFP51843_01011990
FFP55062_01011990
FFP55078_01011990
FFP55070_01011990
FFP57220_01012000
FFP56326_01011990
FFP51906_01011990
FFP53224_01011999
FFP56337_01011995
FFP58909_01010001
FFP58906_01010001
FFP58861_01042004
FFP51841_01011990
FFP50581_01011900
FFP56321_01011990
FFP50524_01011900
FFP60589_01011990
FFP61924_01010001
XLA_00707_AAD_C_000044_PKG
F
G

Hi Gents,
All objects starting with FF have been successfully compiled by the fix pointed out by you. Thanks v much for your help. Much appreciated.
Now a total of 15 invalid objects are remaining. I could manage to find solution of 14 objects (which I understand can be safely ignored, and highlighted the source of the solution below).
The only one remaining is this materialized view. I tried to compile it but but did not throw any errors, and still remains under invalid state. Not sure how to go about it. I can confirm that this is not a custom object.
MSD_DEM_OBI_DEMANTRA_MV     MATERIALIZED VIEW
--> I found an answer about them on *MOS [ID 967352.1]*, and will now safely ignore them now.
FSAH_DUPLICATE_PKG     PACKAGE BODY
RE_PROFILER     PACKAGE BODY
XLA_00707_AAD_C_000026_PKG     PACKAGE BODY
XLA_00707_AAD_C_000044_PKG     PACKAGE BODY
XLA_20065_AAD_C_000030_PKG     PACKAGE BODY
--> I followed this thread for resolution on these objects. I believe that they can be safely ignored now.
247 Invalids are not getting compiled
ImportExport     JAVA SOURCE
ImportExport     JAVA CLASS
WWV_FLOW_LIST_OF_VALUES_DATA     SYNONYM
WWV_FLOW_LISTS_OF_VALUES$     SYNONYM
WWV_FLOW_GENERIC     SYNONYM
WWV_FLOW_FIELD_TEMPLATES     SYNONYM
RDT_1     TABLE
F     TABLE
G     TABLE

After Upgrade R12.1.3 Invalid OBjects Found

Hi Friends,
My Environment*
Application Version: 12.1.3
Db Version : 11.1.0.7
OS Version : OEL4U5
Recently I have upgraded My application from R12.1.1 to R12.1.3 and upgraded successfully,
After upgrade i found that lot of invalid Objects are in Application (R12.1.3). for few objects i compiled manually and remaning i go with metalink id and then compiled.
But am not able to compile the Following invalid objects
owner object_name object_type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPS     XLA_00707_AAD_C_000026_PKG PACKAGE BODY
APPS     XLA_20065_AAD_C_000030_PKG PACKAGE BODY
APPS     XLA_00707_AAD_C_000044_PKG PACKAGE BODY
APPS     FSAH_DUPLICATE_PKG     PACKAGE BODY
i try to manually compile the above invalid objects it throwing the below error in compilation.
Please Find the error
Issue 1:*
SQL> alter package apps.XLA_00707_AAD_C_000044_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00707_AAD_C_000044_PKG:
LINE/COL ERROR
201067/1 PL/SQL: SQL Statement ignored
*201180/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
201501/1 PL/SQL: SQL Statement ignored
*201545/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
202327/5 PL/SQL: Statement ignored
*202327/2 PLS-00364: loop index variable 'HEADER_RECORD' use is invalid*
Issue 2:*
SQL> alter package apps.XLA_00707_AAD_C_000026_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00707_AAD_C_000026_PKG:
LINE/COL ERROR
110048/1 PL/SQL: SQL Statement ignored
*110161/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
110480/1 PL/SQL: SQL Statement ignored
*110524/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
Issue 3:*
SQL> alter package apps.XLA_20065_AAD_C_000030_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_20065_AAD_C_000030_PKG:
LINE/COL ERROR
30260/1 PL/SQL: SQL Statement ignored
30467/9 PL/SQL: ORA-00942: table or view does not exist
30605/1 PL/SQL: Item ignored
*30605/35 PLS-00201: identifier 'FSAH_MORTGAGES.TRANSACTION_DATE' must be declared*
30606/1 PL/SQL: Item ignored
*30606/35 PLS-00201: identifier 'FSAH_MORTGAGES.CUR_NET_BOOK_BAL' must be declared*
30607/1 PL/SQL: Item ignored
*30607/35 PLS-00201: identifier 'FSAH_MORTGAGES.DEFAULT_FLAG' must be declared*
30608/1 PL/SQL: Item ignored
*30608/35 PLS-00201: identifier 'FSAH_MORTGAGES.DEL_CUR_DAYS' must be declared*
30609/1 PL/SQL: Item ignored
*30609/36 PLS-00201: identifier 'FSAH_MORTGAGES.CUR_BOOK_BAL' must be declared*
30610/1 PL/SQL: Item ignored
*30610/36 PLS-00201: identifier 'FSAH_MORTGAGES.COMPANY_COST_CENTER_ORG_ID' must be declared*
30611/1 PL/SQL: Item ignored
*30611/36 PLS-00201: identifier 'FSAH_MORTGAGES.BRANCH_CODE' must be declared*
30612/1 PL/SQL: Item ignored
*30612/36 PLS-00201: identifier 'FSAH_MORTGAGES.PRODUCT_ID' must be declared*
30613/1 PL/SQL: Item ignored
*30613/36 PLS-00201: identifier 'FSAH_MORTGAGES.ACCRUED_INTEREST' must be declared*
Kindly advice me to fix this
Thanks
Athish

Athish,
Please run utlrp.sql and utlirp.sql scripts as per (R12.1.1 - Invalid Objects After Patching [ID 1093163.1]).
For some of the errors, looks like you have custom code, so please check with your development team to review/fix the code.
Thanks,
Hussein

Recompile all invalid objects in live database

Hi Expers,
Just need a clarification on recompiling all invalid objects in production database when the systems is busy.
i thought of recompile all the invalid objects using utlrp.sql script in my production database since some of few synonyms were invalid after application patch script been implemented last weekeend.
we have identifed the invalid objects now, i thought to run the utlrp.sql, what will be the consequences.
Regards,
Salai

Hi Hemanth,
I'd reserve utlrp.sql for upgrades, downgrades and patchsets. I do agree 101% with above point, I a not denying on that.
If you really have a large number of invalid objects, you might choose to compile a few "selected" objects every hour instead of running a single-shot "compile all invalid objects". Rare but a possible requirement.I came across such requirement during early days of career during pushing product enhancement to production and we would have get to know the things and number of objects which would go invalid as we use to carry out testing on test databases.
I agree completely utlrp.sql is suggested and should opt for.
- Pavan Kumar N

Identification of additional Invalid Objects of Apps Patches in Test mode!

Similar Messages

Maybe you are looking for