Invalid Objects in Database

Hi sawwan,
we have one one year old apps environment R12.0.5 and db 10.2.0.2, we are getting daily invalid objects in database,we have not applied any patches and we have not made any changes recently ,
daily we used to compile all invalids at night time, before starting our work hrs in morning we can see some of invalids objects,
normally why we get invalids even we just running some scheduled concurrent requests in database but we have not got before such invalids now we are getting invalids in database.

Sawwan,
here are invalid objects , i can see lot of invalid objects are system /public user.
PUBLIC DBA_HIST_FILESTATXS SYNONYM
PUBLIC DBA_HIST_SQLSTAT SYNONYM
PUBLIC DBA_HIST_SQLBIND SYNONYM
PUBLIC DBA_HIST_SYSTEM_EVENT SYNONYM
PUBLIC DBA_HIST_WAITSTAT SYNONYM
PUBLIC DBA_HIST_LATCH SYNONYM
PUBLIC DBA_HIST_LATCH_MISSES_SUMMARY SYNONYM
PUBLIC DBA_HIST_DB_CACHE_ADVICE SYNONYM
PUBLIC DBA_HIST_ROWCACHE_SUMMARY SYNONYM
PUBLIC DBA_HIST_SGASTAT SYNONYM
PUBLIC DBA_HIST_SYSSTAT SYNONYM
PUBLIC DBA_HIST_SYS_TIME_MODEL SYNONYM
PUBLIC DBA_HIST_OSSTAT SYNONYM
PUBLIC DBA_HIST_PARAMETER SYNONYM
PUBLIC DBA_HIST_SEG_STAT SYNONYM
PUBLIC DBA_HIST_ACTIVE_SESS_HISTORY SYNONYM
PUBLIC DBA_HIST_TABLESPACE_STAT SYNONYM
PUBLIC DBA_HIST_SERVICE_STAT SYNONYM
PUBLIC DBA_HIST_SERVICE_WAIT_CLASS SYNONYM
SYSTEM EMP SYNONYM
SYSTEM DEPT SYNONYM
SYSTEM MLOG$_EMP SYNONYM
SYSTEM RUPD$_EMP SYNONYM
SYSTEM EMP_SNAPSHOT SYNONYM
SYSTEM WF_LOCAL_ROLES_STAGE SYNONYM
READONLY EMP SYNONYM
READONLY DEPT SYNONYM
READONLY MLOG$_EMP SYNONYM
READONLY RUPD$_EMP SYNONYM
READONLY EMP_SNAPSHOT SYNONYM
READONLY WF_LOCAL_ROLES_STAGE SYNONYM

Similar Messages

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

SSRS Error : Query execution failed for dataset 'dataSet'. (rsErrorExecutingCommand) Semantic query execution failed. Invalid object name 'RPT.*********'. (rsSemanticQueryEngineError)

I am new to SSRS and I am trying to migrate reports from 2008 to 2012. As I have so many reports to migrate, I simply got the back up of ReportServer,
ReportServerTempDB, and Encryption Key and restored them to test environment. I made necessary configuration from RS configuration tool. I am able to see the reports now when I browse //hostname/reports. But when I open any particular report I am getting some
error.
· An error has occurred during report processing.
(rsProcessingAborted)
Query execution       failed for dataset 'dataSet'.
      (rsErrorExecutingCommand
Semantic query        execution failed. Invalid object name
       'RPT. ******'. (rsSemanticQueryEngineError)
****** - I am assuming this is a custom data class.
Does anyone have insight on this? or any better way that I can migrate the reports to new server with less efforts.
I don’t have the reports solution file to deploy the reports, so I have followed backup and restore process.

Hi Kishore237,
According to your description, you migrated some reports from Reporting Services (SSRS) 2008 to 2012. Now you get error when accessing the reports on SSRS 2012. Right?
In this scenario, did you modify the report data source in database after migration? You can try to open the report in Report Builder or Report designer and check the report dataset. If you can preview the report in Report builder or Report designer,
please try to redeploy the report to Report Server. If it is still not working, please try to restore the database from backup. And for migrating reports, please follow the "Content-Only Migration" in the link below:
http://msdn.microsoft.com/en-us/library/ms143724(v=sql.110).aspx
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

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

Invalid object error while migrating oracle forms 6i to APEX

Hi,
I have a form name abc.fmb and I did converted to xml and imported using application migration in APEX
With these I have nine PL/SQL libraries (PLL). converted it to PLD using rwconvertor and imported in APEX. Also, I have 4 tables i.e data base block in forms.
Now, when i m migrating forms to APEX it is giving an error message saying invalid objects and shows the table name and column name. But the column name that it shows is a text box in the form that is also a database item ...
eg:- addr is the block name in forms
item name dsp_name
error: invalid object
Please suggest.
Thanks,
AP.

Hi AP
i would suggest this...
Oracle Application Express (APEX)
Regards,
Abdetu...

Invalid objects after upgrade 8.1.7 to 9.2.0.6

I upgraded the database from 8.0.5 under EBS 11.0.3 to 8.1.7 then from 8.1.7 to 9.2.0.6 under EBS 11.5.10.2
in front of try to compile objects with utlrp, utlrcmp or compile i can't make these objects valid!
can any one help me please?
my invalids objects & errors from dba_errors are :
OWNER NAME TEXT
SYSTEM AD_APPS_PRIVATE PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_APPS_PRIVATE PL/SQL: SQL Statement ignored
SYSTEM AD_APPS_PRIVATE PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_APPS_PRIVATE PL/SQL: SQL Statement ignored
SYSTEM AD_COMPILE PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_COMPILE PL/SQL: SQL Statement ignored
SYSTEM AD_INST PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_INST PL/SQL: SQL Statement ignored
SYSTEM AD_INST PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_MCURR PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_MCURR PL/SQL: SQL Statement ignored
SYSTEM AD_PARALLEL_COMPILE_PKG PL/SQL: ORA-00942: table or view does not exist
SYSTEM AD_PARALLEL_COMPILE_PKG PL/SQL: SQL Statement ignored
CTXSYS CTX_ACCESS PLS-00201: identifier 'SYS.DBA_SYNONYMS' must be declared CTXSYS CTX_ACCESS PL/SQL: SQL Statement ignored
CTXSYS CTX_ACCESS PLS-00201: identifier 'SYS.DBA_OBJECTS' must be declared
CTXSYS CTX_ACCESS PL/SQL: SQL Statement ignored
CTXSYS CTX_ADM PLS-00905: object CTXSYS.DISPATCHER is invalid
CTXSYS CTX_ADM PL/SQL: Statement ignored
CTXSYS CTX_DDL PLS-00905: object CTXSYS.DISPATCHER is invalid
CTXSYS CTX_DDL PL/SQL: Item ignored
CTXSYS CTX_DDL PLS-00905: object CTXSYS.DISPATCHER is invalid
CTXSYS CTX_DML PLS-00201: identifier 'DBMS_LOCK' must be declared
CTXSYS CTX_DML PL/SQL: Statement ignored
CTXSYS CTX_LING PLS-00593: default value of parameter "LOG_MODE" in body
must match that of spec
CTXSYS CTX_QUERY PLS-00201: identifier 'DBA_OBJECTS' must be declared
CTXSYS CTX_QUERY PL/SQL: SQL Statement ignored
CTXSYS CTX_VP PLS-00201: identifier 'DBA_OBJECTS' must be declared
CTXSYS DISPATCHER PLS-00201: identifier 'DBMS_PIPE' must be declared
CTXSYS DISPATCHER PL/SQL: Declaration ignored
CTXSYS DMLQ PLS-00201: identifier 'DBMS_LOCK' must be declared
CTXSYS DMLQ PL/SQL: Statement ignored
CTXSYS DRASERM PLS-00593: default value of parameter "PERSON_MASK" in b
ody must match that of spec
CTXSYS DRDBG PLS-00201: identifier 'DBMS_PIPE' must be declared
CTXSYS DRDBG PLS-00201: identifier 'DBMS_PIPE' must be declared
CTXSYS DRDBG PL/SQL: Statement ignored
CTXSYS DRICON PLS-00201: identifier 'DBA_TAB_PRIVS' must be declared
CTXSYS DRICON PL/SQL: SQL Statement ignored
CTXSYS DRICON PL/SQL: SQL Statement ignored
CTXSYS DR_IDX PLS-00201: identifier 'DBMS_LOCK' must be declared
CTXSYS DR_IDX PL/SQL: Statement ignored
CTXSYS DR_REC PL/SQL: SQL Statement ignored
CTXSYS DR_REC PLS-00201: identifier 'SYS.USER$' must be declared
CTXSYS DR_REC PL/SQL: SQL Statement ignored
CTXSYS DR_REWRITE PLS-00905: object CTXSYS.DISPATCHER is invalid
CTXSYS DR_REWRITE PL/SQL: Statement ignored
CTXSYS DR_REWRITE PLS-00201: identifier 'SYS.USER$' must be declared
CTXSYS DR_REWRITE PLS-00905: object CTXSYS.DISPATCHER is invalid
CTXSYS DR_REWRITE PL/SQL: Item ignored
CTXSYS DR_RTM PLS-00201: identifier 'DBMS_LOCK' must be declared
CTXSYS DR_RTM PL/SQL: Statement ignored
CTXSYS DR_UTL PLS-00302: component 'IS_PARALLEL_SERVER' must be declar
ed
CTXSYS DR_UTL PL/SQL: Statement ignored
CTXSYS LISTENER PLS-00905: object CTXSYS.DISPATCHER is invalid
CTXSYS LISTENER PL/SQL: Item ignored
CTXSYS LISTENER PLS-00320: the declaration of the type of this expressio
n is incomplete or malformed
CTXSYS LISTENER PL/SQL: Statement ignored
CTXSYS LISTENER PLS-00320: the declaration of the type of this expressio
n is incomplete or malformed
CTXSYS PIPE PL/SQL: Statement ignored
CTXSYS PIPE PLS-00201: identifier 'DBMS_PIPE' must be declared
CTXSYS PIPE PL/SQL: Statement ignored
CTXSYS SVCQ PLS-00201: identifier 'DBMS_LOCK' must be declared
CTXSYS SVCQ PL/SQL: Statement ignored
APPS AD_DD PLS-00593: default value of parameter "P_DESCRIPTION" in
body must match that of spec
APPS AK_ATTRIBUTE_PVT PLS-00593: default value of parameter "P_DATA_TYPE" in b
ody must match that of spec
APPS AK_ATTRIBUTE_PVT PLS-00593: default value of parameter "P_PASS" in body m
ust match that of spec
APPS AK_OBJECT_GRP PLS-00593: default value of parameter "P_VALUE_VARCHAR2"
in body must match that of spec
APPS AS_OPPORTUNITY_PUB PLS-00593: default value of parameter "P_DEFAULT_FORECAS
TING_INFO" in body must match that of spec
APPS AS_OPPORTUNITY_PVT PLS-00593: default value of parameter "P_DEFAULT_FORECAS
TING_INFO" in body must match that of spec
APPS AS_QUOTE_PVT PLS-00593: default value of parameter "P_QUOTE_STATUS" i
n body must match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_PERIOD" in body
must match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_CCID" in body m
ust match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_BALSEGL" in bod
y must match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_BALSEGH" in bod
y must match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_ACCSEGL" in bod
y must match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_ACCSEGH" in bod
y must match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_TPID" in body m
ust match that of spec
APPS AX_CALCULATE_BALANCES_PKG PLS-00593: default value of parameter "P_SUBID" in body
must match that of spec
Regards.
e-mail : [email protected]

thank you for your answer,
i followed all documentation from oracle support, first document is
Upgrading Oracle Applications
Release 11i (11.5.10)
Part No. B13584-01
i used also "Installation Guide Using Rapid Install.pdf" chapter 4
first thing is that i upgraded database from 8.0.5 under EBS 11.0.3/win 2000 to 8.1.7 on an intermediate machine. then, i prepared environnement on an other machine with EBS 11.5.10.2 under windows 2003 (for the database, i have now only software) then i copied upgraded 8.1.7 database from intermediate machine to 11i machine then i upgraded it to 9.2.0.6 like it recommeded in category3 database tasks in "Upgrading Oracle Applications" documentation.
have u any idea, what's the probleme with these invalid objects?
regards.

Invalid object error, for @CURRMBRRANGE

Hi,
I have been getting the error invalid object in line 1, when trying to retrieve the member using smartview 11.1.2.1.
The formula in the member is:
@SUMRANGE (9999,@CURRMBRRANGE (Period,Gen,4, ,0 ));
I have tried changing it to:
@SUMRANGE (9999,@CURRMBRRANGE (Period,LEV,0, ,0 ));
Can anyone suggest any other changes I can try out?
Thanks in advance.
Anindyo

I guess the first question is: does the member formula (I am guessing a member formula) verify in EAS?
If yes, are you trying to write a YTD member formula?
When I put this formula into a new member in My Very Favorite BSO Database In The Whole Wide World, aka Sample.Basic:
@SUMRANGE("Sales", @CURRMBRRANGE("Year", LEV, 0, , 0)) ;It works on retrieval as below:
      Product       Market       Scenario
      Jan       Feb       Mar       Apr       May       Jun       Jul       Aug       Sep       Oct       Nov       Dec       Year
Sales       31,538       32,069       32,213       32,917       33,674       35,088       36,134       36,008       33,073       32,828       31,971       33,342       400,855
YTDSales       31,538       63,607       95,820       128,737       162,411       197,499       233,633       269,641       302,714       335,542       367,513       400,855       2,589,510 You can see how the months sum up -- is that what you want?
Regards.
Cameron Lackpour

Migration from windows to Linux -- Invalid objects.

Hi DBA's
After Migration there are no of invalid objects are there, specially APPLSYS, what action should I take.
SQL> select owner, object_name, object_type from all_objects where status<>'VALID' order by owner;
OWNER OBJECT_NAME OBJECT_TYPE
APPLSYS AQ$WF_CONTROL VIEW
APPLSYS AQ$WF_JAVA_DEFERRED VIEW
APPLSYS AQ$WF_JAVA_ERROR VIEW
APPLSYS AQ$WF_JMS_IN VIEW
APPLSYS AQ$WF_JMS_JMS_OUT VIEW
APPLSYS AQ$WF_JMS_OUT VIEW
APPLSYS AQ$WF_NOTIFICATION_IN VIEW
APPLSYS AQ$WF_NOTIFICATION_OUT VIEW
APPLSYS AQ$WF_WS_JMS_IN VIEW
APPLSYS AQ$WF_WS_JMS_OUT VIEW
APPLSYS AQ$WF_WS_SAMPLE VIEW
OWNER OBJECT_NAME OBJECT_TYPE
APPS AMV_IMT_PUB PACKAGE
APPS AMV_IMT_PUB PACKAGE BODY
APPS CSS_DEF_IMT_PUB PACKAGE
APPS CSS_DEF_IMT_PUB PACKAGE BODY
APPS CS_KB_CONC_PROG_PKG PACKAGE BODY
APPS CS_SR_ADDR_SYNC_INDEX_PKG PACKAGE BODY
APPS CS_SR_SYNC_INDEX_PKG PACKAGE BODY
APPS EDR_INDEXED_XML_UTIL PACKAGE BODY
APPS EDW_GEOGRAPHY_M_C PACKAGE BODY
APPS EDW_HR_AGE_BAND_M_C PACKAGE BODY
APPS EDW_HR_ASG_CHNG_M_C PACKAGE BODY
OWNER OBJECT_NAME OBJECT_TYPE
APPS EDW_HR_ASSGNMNT_M_C PACKAGE BODY
APPS EDW_HR_GRADE_M_C PACKAGE BODY
APPS EDW_HR_JOBS_M_C PACKAGE BODY
APPS EDW_HR_MVMNT_TYP_M_C PACKAGE BODY
APPS EDW_HR_POSITION_M_C PACKAGE BODY
APPS EDW_HR_PRSN_TYP_M_C PACKAGE BODY
APPS EDW_HR_REASON_M_C PACKAGE BODY
APPS EDW_HR_REC_ACT_M_C PACKAGE BODY
APPS EDW_HR_RQN_VCNCY_M_C PACKAGE BODY
APPS EDW_HR_SERVICE_M_C PACKAGE BODY
APPS EDW_MRP_DM_CLS_M_C PACKAGE BODY
OWNER OBJECT_NAME OBJECT_TYPE
APPS EDW_MRP_FORECAST_M_C PACKAGE BODY
APPS EDW_MRP_PLAN_M_C PACKAGE BODY
APPS EDW_MTL_INVENTORY_LOC_M_C PACKAGE BODY
APPS EDW_OPI_ACTV_M_C PACKAGE BODY
APPS EDW_OPI_LOT_M_C PACKAGE BODY
APPS EDW_OPI_OPRN_M_C PACKAGE BODY
APPS EDW_OPI_PRDL_M_C PACKAGE BODY
APPS EDW_ORGANIZATION_M_C PACKAGE BODY
APPS EDW_POA_LN_TYPE_M_C PACKAGE BODY
APPS EDW_POA_SPLRITEM_M_C PACKAGE BODY
APPS EE PROCEDURE
OWNER OBJECT_NAME OBJECT_TYPE
APPS EGO_ITEM_TEXT_PVT PACKAGE BODY
APPS EGO_ITEM_TEXT_UTIL PACKAGE
APPS EGO_ITEM_TEXT_UTIL PACKAGE BODY
APPS EGO_MTL_SYSTEM_ITEMS_B_TR1 TRIGGER
APPS EGO_MTL_SYSTEM_ITEMS_TL_TR1 TRIGGER
APPS EMAIL PROCEDURE
APPS EMAIL PACKAGE BODY
APPS ENI_DENORM_HRCHY PACKAGE BODY
APPS FII_AP_HOLD_DATA_F_C PACKAGE BODY
APPS FII_AP_INV_LINES_F_C PACKAGE BODY
APPS FII_AP_INV_ON_HOLD_F_C PACKAGE BODY
OWNER OBJECT_NAME OBJECT_TYPE
APPS FII_AP_INV_PAYMTS_F_C PACKAGE BODY
APPS FII_AP_SCH_PAYMTS_F_C PACKAGE BODY
APPS FII_AR_E_REVENUE_F_C PACKAGE BODY
APPS FII_AR_TRX_DIST_F_C PACKAGE BODY
APPS FII_PA_BUDGET_F_C PACKAGE BODY
APPS FII_PA_COST_F_C PACKAGE BODY
APPS FII_PA_REVENUE_F_C PACKAGE BODY
APPS FII_PA_UOM_CONV_F_C PACKAGE BODY
APPS FND_IMUTL PACKAGE BODY
APPS FND_TS_MIG_UTIL PACKAGE BODY
APPS HR_EDW_WRK_CMPSTN_F_C PACKAGE BODY
OWNER OBJECT_NAME OBJECT_TYPE
APPS HZ_DQM_SYNC PACKAGE BODY
APPS HZ_PARTY_STAGE PACKAGE BODY
APPS HZ_PURGE PACKAGE BODY
APPS IBC_IMT_PUB PACKAGE
APPS IBC_IMT_PUB PACKAGE BODY
APPS IBE_SEARCHUPDATE_PVT PACKAGE BODY
APPS IBE_SEARCH_SETUP_PVT PACKAGE BODY
APPS ICX_POR_INTERMEDIA_INDEX PACKAGE BODY
APPS IRC_DOCUMENT_API PACKAGE BODY
APPS IRC_POSTING_CONTENT_API PACKAGE BODY
APPS ISC_EDW_BOOK_SUM1_F_C PACKAGE BODY
OWNER OBJECT_NAME OBJECT_TYPE
APPS JTA_NOTES_IMT_PUB PACKAGE
APPS JTA_NOTES_IMT_PUB PACKAGE BODY
APPS JTF_AMVIMT_PUB PACKAGE
APPS JTF_AMVIMT_PUB PACKAGE BODY
APPS JTF_TASK_IDX_UTL PACKAGE BODY
APPS OKC_ARTICLE_KEYWORD_PVT PACKAGE BODY
APPS OKC_TEMPLATE_KEYWORD_PVT PACKAGE BODY
APPS OPI_EDW_COGS_F_C PACKAGE BODY
APPS OPI_EDW_OPMCOGS_F_C PACKAGE BODY
APPS OPI_EDW_OPMINV_DAILY_STAT_F_C PACKAGE BODY
APPS OPI_EDW_OPM_JOB_DETAIL_F_C PACKAGE BODY
OWNER OBJECT_NAME OBJECT_TYPE
APPS OPI_EDW_OPM_JOB_RSRC_F_C PACKAGE BODY
APPS OPI_EDW_UOM_CONV_F_C PACKAGE BODY
APPS RA_CUSTOMER_TEXT_PKG PACKAGE BODY
APPS WF_DIAGNOSTICS PACKAGE BODY
ODM AQ$DMS_QUEUE_TABLE VIEW
OWAPUB DEBUG_CARTX PACKAGE BODY
OWAPUB OWA_OPT_LOCK PACKAGE BODY
OWAPUB OWA_UTIL PACKAGE BODY
XXQUDRA XXQUDRA_GETPHONE FUNCTION
97 rows selected.
Best Regards,
Suresh Gelda

Hi Sawwan,
I created the dblink.
SQL> select * from user_db_links;
no rows selected
SQL> create database link APPS_TO_APPS connect to
apps identified by apps
using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(Host=aqherp)
(Port=1526))(CONNECT_DATA=(SID=PROD)))'
/ 2 3 4 5 6
Database link created.
SQL> alter view APPLSYS.AQ$WF_CONTROL compile;
Warning: View altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.EDW_GEOGRAPHY_M_C:
LINE/COL ERROR
109/4 PL/SQL: SQL Statement ignored
147/9 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_LOCATION_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
211/4 PL/SQL: SQL Statement ignored
259/7 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_POSTCODE_CITY_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
LINE/COL ERROR
304/4 PL/SQL: SQL Statement ignored
349/9 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_CITY_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
394/4 PL/SQL: SQL Statement ignored
439/8 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_POSTCODE_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
LINE/COL ERROR
ORA-12154: TNS:could not resolve service name
492/4 PL/SQL: SQL Statement ignored
537/8 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_STATE_REGION_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
583/4 PL/SQL: SQL Statement ignored
628/8 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_STATE_LCV@APPS_TO_APPS.QUDRAH.COM
LINE/COL ERROR
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
681/4 PL/SQL: SQL Statement ignored
726/8 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_REGION_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
771/4 PL/SQL: SQL Statement ignored
816/8 PL/SQL: ORA-04052: error occurred when looking up remote object
LINE/COL ERROR
APPS.EDW_GEOG_COUNTRY_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
871/3 PL/SQL: SQL Statement ignored
902/8 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_AREA2_LCV@APPS_TO_APPS.QUDRAH.COM
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name
953/4 PL/SQL: SQL Statement ignored
LINE/COL ERROR
983/9 PL/SQL: ORA-04052: error occurred when looking up remote object
APPS.EDW_GEOG_AREA1_LCV@APPS_TO_APPS.QUDRAH.COM
Thanks
ORA-00604: error occurred at recursive SQL level 3
ORA-12154: TNS:could not resolve service name

Invalid objects in APEX Schemas after import.

Hi,
After importing the APEX_040100 user in the database I got several invalid objects that are causing APEX not to work.
I gave up to compile them. After using all kind of tricks such as compile one schema at a time or compile all of them using the utlprp.sql script
or using EXEC DBMS_DDL.alter_compile('PACKAGE', 'MY_SCHEMA', 'MY_PACKAGE');
or one object art a time using command sililar to:
ALTER PACKAGE my_package COMPILE;
ALTER PACKAGE my_package COMPILE BODY;
ALTER PROCEDURE my_procedure COMPILE;
ALTER FUNCTION my_function COMPILE;
ALTER TRIGGER my_trigger COMPILE;
ALTER VIEW my_view COMPILE;
I can't find any documentation to show how to recompile them properly.
So I am asking:
1. How can we recompile all objects in APEX?
2. How can we re-install APEX?
3. How can we revert to previous version if both have problems?
Thanks
Yannis
Here is the list of invalid objects:
APEX_040100     PACKAGE     WWV_FLOW_DYNAMIC_EXEC     INVALID
APEX_040100     PACKAGE     WWV_FLOW_LOAD_DATA     INVALID
APEX_040100     PACKAGE     WWV_FLOW_SAMPLE_APP     INVALID
APEX_040100     PACKAGE     WWV_FLOW_UTILITIES     INVALID
APEX_040100     PACKAGE BODY     APEXWS     INVALID
APEX_040100     PACKAGE BODY     HTMLDB_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_4000_UI     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ADMIN_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ADVISOR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AJAX     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_APPLICATION_INSTALL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ASFCOOKIE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUDIT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUTHENTICATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUTHENTICATION_ENGINE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUTHORIZATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_BUILDER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_BUTTON     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CALENDAR3     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CALENDAR_AJAX     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CHECK     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_COLLECTION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CONDITIONS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_COPY_PAGE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CREATE_APP_FROM_QUERY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CREATE_MODEL_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CSS_API_PRIVATE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CUSTOM_AUTH     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CUSTOM_AUTH_STD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DATALOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DATA_QUICK_FLOW     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DATA_UPLOAD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DICTIONARY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DISP_PAGE_PLUGS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DML     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DOWNLOAD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DRAG_LAYOUT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DYNAMIC_EXEC     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ERROR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_F4000_P4150     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_F4000_PLUGINS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_F4000_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FILE_MGR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART2     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART5     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART5_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FND_DEVELOPER_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FND_USER_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FORMS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FORM_CONTROL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GENERATE_DDL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GENERATE_TABLE_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GENERIC_ATTR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GEN_API2     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_HINT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_HTML_API_PRIVATE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_IMP_PARSER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_INSTALL_WIZARD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_INSTANCE_ADMIN     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ITEM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_JAVASCRIPT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_JOB     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LANG     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LDAP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LIST     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LOAD_DATA     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LOAD_EXCEL_DATA     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LOGIN     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_MAIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_META_DATA     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_META_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_MODEL_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_NATIVE_AUTHENTICATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_NATIVE_DYNAMIC_ACTION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_NATIVE_ITEM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PAGE_CACHE_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLSQL_EDITOR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLSQL_JOB     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLUGIN_ENGINE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLUGIN_F4000     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLUGIN_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PPR_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PRINT_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROCESS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROCESS_UTILITY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROVISION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROVISIONING     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_QUERY_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_REGEXP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_REGION_LAYOUT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_RENDER_QUERY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_RENDER_SHORTCUT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_REST     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SAMPLE_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SC_TRANSACTIONS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SECURITY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SERIES_ATTR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SESSION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SESSION_MON     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SVG     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_PAGE_CALLS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_PARSER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_SCRIPT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TABLE_DRILL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TAB_MGR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TEAM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TEAM_GEN_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TEMPLATES_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_THEME_FILES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_THEME_MANAGER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TREE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TREE_REGION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_UPGRADE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_UPGRADE_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_UTILITIES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_VALIDATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WEBSERVICES_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WEB_SERVICES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WIZARD_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WIZ_CONFIRM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_AJAX     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_DIALOGUE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_EXPR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_FORM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_STANDARD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSPACE_REPORTS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_ATTACHMENT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_DIALOG     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_EXPORT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_FLASH_CHART     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_FORM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_GEOCODE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_IMPORT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_IMPORT_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_SECURITY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_SETUP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_STICKIES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_UI     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_WEBPAGE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_XLIFF     INVALID
APEX_040100     PACKAGE BODY     WWV_META_CLEANUP     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_ACC_LOAD     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRMMENU_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_OLB_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_UPDATE_APX_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_UTILITIES     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_RPT_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_RENDER_CALENDAR2     INVALID
APEX_040100     PACKAGE BODY     WWV_RENDER_CHART2     INVALID
APEX_040100     PACKAGE BODY     WWV_RENDER_REPORT3     INVALID
APEX_040100     PROCEDURE     APEX_ADMIN     INVALID
APEX_040100     PROCEDURE     F     INVALID
APEX_040100     PROCEDURE     HTMLDB_ADMIN     INVALID
APEX_040100     PROCEDURE     WS     INVALID
APEX_040100     SYNONYM     APEX_COLLECTIONS     INVALID
APEX_040100     SYNONYM     HTMLDB_COLLECTIONS     INVALID
APEX_040100     TRIGGER     WWV_FLOW_FEEDBACK_T1     INVALID
APEX_040100     VIEW     WWV_FLOW_ADVISOR_RESULT     INVALID
APEX_040100     VIEW     WWV_FLOW_COLLECTIONS     INVALID
APEX_040100     VIEW     WWV_FLOW_SEARCH_RESULT     INVALID
APEX_040100     VIEW     WWV_MULTI_COMPONENT_EXPORT     INVALID

yannisr wrote:
Hi,
After importing the APEX_040100 user in the database I got several invalid objects that are causing APEX not to work.Hi,
You mean you did export APEX_040100 schema from one database and import it to another database?
There is also public synonyms and if I recall correct some objects are in SYS schema that belongs to Apex and are needed.
Regards,
Jari
http://dbswh.webhop.net/dbswh/f?p=BLOG:HOME:0

Invalid object name 'dbo.v_R_System'

Hi,
About six months ago I implemented SCCM in our domain and it's been working great. This morning, when I attempted to run one of the Asset Intelligence reports in the console, I received the following error...
An error has occurred during report processing. (rsProcessingAborted)
...uh oh! So I logged onto our SQL database server, opened up the Report Manager in IE and attempted to run the same report. This time I got a bit more...
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet0'. (rsErrorExecutingCommand)
Invalid object name 'dbo.v_R_System'. Could not use view or function 'fn_rbac_R_System_Valid' because of binding errors.
...I'm no SQL admin, so time to ask Mr Internet. The only related post I could find was the first one you get when you search "dbo.v_R_System missing" on any search engine (the ones I tried anyway).
...which wasn't particularly helpful.
One thing I did try, which I thought was worth a shot, was to create a new database in Reporting Services Configuration Manager. After a few minutes that populated nicely with all the reports,
but I'm still getting the same problem.
We've got a really simple environment. Two Windows Server 2008 R2 servers for SCCM,
one running the site database and reporting server and the other doing everything else. Database is running on Microsoft SQL Server 2012.
Any ideas?
Cheers,
Dave

I was also missing that same view. I can't believe it. In production and in my test environment we are on ConfigMgr 2012 SP1 CU3. I started the upgrade on my test environment and it failed saying that it couldn't find that view.
I went to our production environment and the view existed. I scripted the creation of the view and then created the view in our test environment. The upgrade successfully completed after that. Thanks for leading me in the right direction!

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

Why its showing error : Invalid Object Name 'table name' when we try to insert data ?

Hi,
    When i try to insert data in the database with the following query
                con.Open();
                cmd = new SqlCommand("insert into good(ID,Name) values('" + textBox1.Text + "','" + textBox2.Text + "')", con);
                cmd.ExecuteNonQuery();
                MessageBox.Show("Insert success");
                con.Close();
    its showing following error Invalid Object Name 'good'

Use 3-part naming like: MyDatabase.dbo.good(ID,Name) .
Also consider using stored procedure for database INSERTs.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

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 object name 'dbo.uf_GetRateSrcMember'

Hello Friends,
We recently applied the SP3 (CPMBPC03P_1-20002499) for BPC 5.1. We are in Single Server environment. Our BPC 5.1 build was 5.0.486 which was required to install the SP3. After the installation it is 5.0.502
We are getting the error below when we are trying to change the appliction sets from from the main page.
Any help to resolve the issue is appreciated
Server Error in '/OSoft' Application. Invalid object name 'dbo.uf_GetRateSrcMember'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Exception: Invalid object name 'dbo.uf_GetRateSrcMember'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
Add the following section to the configuration file of your application:
<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
[Exception: Invalid object name 'dbo.uf_GetRateSrcMember'.]
   Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack) +905
   OSoft.Consumers.ZFP.WebBase.PageBase.GetCurrentView() +518
   OSoft.Consumers.ZFP.WebBase.PageBase.get_CurrentView(String strDimension) +43
   ASP.Landing_aspx.__Render__control1(HtmlTextWriter __output, Control parameterContainer) +95
   System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +27
   System.Web.UI.Control.Render(HtmlTextWriter writer) +7
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
   System.Web.UI.Page.ProcessRequestMain() +1926
Really looking forward for answers.
I would really really really appreciate any help
Thanks

Kaji,
I had the same problem. Here is the solution:
Dear customer,
This issue looks similar to a previously reported bug.
In general there is the possibility that some service/process
remained in a bad status and this can be fixed by restarting the server
But could you please also check, whether this description fits
to your scenario:
This issue occurred because when there are no secured dimensions
in an appset,
The modified application process remove the user function
which is used for checking secured dimension.
In case there is no secured dimension in the appset the
problem occurres.
This issue looks similar to a previously reported bug.
In general there is the possibility that some service/process
remained in a bad status and this can be fixed by restarting the server
But could you please also check, whether this description fits
to your scenario:
This issue occurred because when there are no secured dimensions
in an appset,
The modified application process remove the user function
which is used for checking secured dimension.
In case there is no secured dimension in the appset the
problem occurres.
When modify application is run , the user function has been removed.
A workaround is this:
if you make Entity and RateSrc as secured dimension,
the user function will be made in the appset again.
Then you can change the user function as other name in database
by renaming. After finished the rename,
you can change the dimension as unsecured dimension like current.
Then, you have to replace the user function name
as original function name.
Because the user function name is dependent on dimension name.
If you can#t connect BPC Admin due to web page error,
you have to execute the EverestAdmin.exe file
in "C:\Program Files\BPC"
Hope it solves the prob...
Nic

Invalid Object Name When Executing from Report Manager

I ran some code to create a modified view of ExecutionLog3 on a SQL Server 2012 instance. The ReportServer and ReportServerTempDB were transferred from a 2005 instance and are still on that compatibility level. After creating the new view, I
created a report in SSDT and it runs fine. I deployed the dataset followed by the report. I went to Report Manager to test it and the report fails with the following:
An error has occurred during report processing. (rsProcessingAborted)
The execution failed for the shared data set
'ExecutionLog'. (rsDataSetExecutionError)
Query execution failed for dataset ''. (rsErrorExecutingCommand)
Invalid object name 'ExecutionLog3_Modified'.
The code for the view is below and it came from MSSQLTips. Why does the report run fine from SSDT and fail in Report Manager?
USE [ReportServer]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE VIEW [dbo].[ExecutionLog3_Modified]
AS
SELECT
EL.InstanceName,
COALESCE(C.Path, 'Unknown') AS ItemPath,
EL.UserName,
EL.ExecutionId,
CASE(EL.RequestType)
WHEN 0 THEN 'Interactive'
WHEN 1 THEN 'Subscription'
WHEN 2 THEN 'Refresh Cache'
ELSE 'Unknown'
END AS RequestType,
-- SubscriptionId,
EL.Format,
Parameters,
CASE(EL.ReportAction)
WHEN 1 THEN 'Render'
WHEN 2 THEN 'BookmarkNavigation'
WHEN 3 THEN 'DocumentMapNavigation'
WHEN 4 THEN 'DrillThrough'
WHEN 5 THEN 'FindString'
WHEN 6 THEN 'GetDocumentMap'
WHEN 7 THEN 'Toggle'
WHEN 8 THEN 'Sort'
WHEN 9 THEN 'Execute'
ELSE 'Unknown'
END AS ItemAction,
EL.TimeStart,
YEAR(EL.TimeStart) AS Start_Year,
MONTH(EL.TimeStart) AS Start_Month,
DATENAME(MONTH,EL.TimeStart) AS Start_Month_Name,
DATENAME(DW,EL.TimeStart) AS Start_Day_Of_Week,
DATEPART(WEEKDAY,EL.TimeStart) AS Start_Day_Number_of_Week,
EL.TimeEnd,
EL.TimeDataRetrieval,
EL.TimeProcessing,
EL.TimeRendering,
CASE(EL.Source)
WHEN 1 THEN 'Live'
WHEN 2 THEN 'Cache'
WHEN 3 THEN 'Snapshot'
WHEN 4 THEN 'History'
WHEN 5 THEN 'AdHoc'
WHEN 6 THEN 'Session'
WHEN 7 THEN 'Rdce'
ELSE 'Unknown'
END AS Source,
EL.Status,
EL.ByteCount,
EL.[RowCount],
EL.AdditionalInfo,
C.Name,
C.CreatedByID,
C.ModifiedByID,
C.Description,
C.CreationDate,
C.ModifiedDate,
CASE
WHEN C.TYPE=1 THEN 'Folder'
WHEN C.TYPE=2 THEN 'Report'
WHEN C.TYPE=3 THEN 'XML'
WHEN C.TYPE=4 THEN 'Linked Report'
WHEN C.TYPE=5 THEN 'Data Source'
WHEN C.TYPE=6 THEN 'Model'
WHEN C.TYPE=8 THEN 'Shared Dataset'
WHEN C.TYPE=9 THEN 'Report Part'
END AS Type_Description
FROM
ExecutionLogStorage AS EL
LEFT OUTER JOIN Catalog AS C ON (EL.ReportID = C.ItemID)
GO
Lee Markum

Hi Lee,
According to your description, you can't process the dataset when viewing the report on report server. Right?
In this scenario, as you can see the dataset name in error message is empty, and it says "Invalid Object Name". Because you have already created a view in your database. When you run this report again, this query be executed again so that you can
not create another view with same name. So you just need to query the view directly when creating dataset.
Select * from ExecutionLog3_Modify
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Invalid Objects in Database

Similar Messages

Maybe you are looking for