Activating Objects after Upgrade

i have done a BW 3.5 to 7.0 Upgrade
After upgrade i see that some of the objects are in active.
Please let me know whehter there is any program/report to active the objects which was active before

Hi,
Try this,
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f232446011d189700000e8322d00/frameset.htm
Also have a look at SAP Note 861890
Regards,
Prateek

Similar Messages

I am not able to change the object after upgrade(SPAU Activity).

HI All,
I am not able to change the object after upgrade(SPAU Activity). Please any one can tell what is the reason with below details.
You are not authorized to make changes
Message no. 37202
Diagnosis
You have no authorization for the authorization object 'S_DEVELOP', which would allow you to change the screen concerned.
There is also a second possibility:
You want to edit a modified SAP screen in a customer system after an upgrate (SAP transport). The screen remains locked for editing until the new SAP version and the customer version have been aligned (Transaction SPAU).
System Response
Authorizations are assigned to users in profiles. Profiles are stored in the user master record.
Procedure
Comsult your system administrator.
Thanks in Advance,
Mahesh Devershetty

Hi,
Does the user who would like to change the screen have the authorisation
for S_DEVELOP in his profile? Please run transaction /NSU53 after the
failed authorisation. You will get an information which authorisation
is missing.
Additional please check if you have open entries in transaction SPAU for
that object.
If you couldn´t solve the issue I need an user to analyse it in your
development system.
That user needs all authorisation for development and has to be
registrated as developer.
The system uses the authorization object S_DEVELOP for Workbench objects
can you please check your user master record whether it contains the
required autorization or not.
Please also ensure that modification adjustment is turned on as per note:
197600 Switching the Modification Assistant off and on
Aidan

In which situation I need to active objects after transport

Hi Experts,
I'm wondering in which situation I need to active object after transport? In some cases, I have to active transformation, DTP, infoobject, multiprovider.... Does any one make a conclusion of that?
thanks in advance.
Eric

Sometimes, because of impact of a transport some other objects will be deactivated, then we need to manuaaly activate the objects after transport.
Also, sometimes transport after import process could not be able to activate the objects, then also we have to activate them manually.
Or suppose, you have moved and infoobject, due to which some other objects become inactive (where ever infoobjects is being used), then we have to activate them manually, if you dont want to transport them.

Note 1054131 - Invalid DB objects after upgrade

HI,
We performed a migration from SAP 4.6C/Oracle9i.solaris to SAP 4.6C/Oracle10g/HPUX.
Now we need to upgrade SAP4.6C/Oracle10g/HPUX to ECC6.0.
As a prerequisite, I have checked the note
Note 1054131 - Invalid DB objects after upgrade
And I ran the script
SQL> SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS
2 WHERE STATUS='INVALID'
3 AND
4 OWNER='SYS';
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
SYS
DBMS_REPCAT_FLA
PACKAGE BODY        INVALID
SYS
DBMS_REPCAT_MAS
PACKAGE BODY        INVALID
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
SYS
DBMS_REPCAT_UTL2
PACKAGE BODY        INVALID
SYS
DBMS_REDEFINITION
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
PACKAGE BODY        INVALID
All the invalid objects are package body, can anyone help me how to proceed with this, can I proceed my upgrade to ECC 6.0 or do I need to delete the package body.
If I want to delete the package body,can you pl give me the commands and also post which whether I need to execute any steps
Pl help
Thanks
Senthil

Hi,
I guess you are talking about the Oracle Upgrade and not ECC Upgrade, as following are the pre-requisites for an ECC upgrade.
Making Database-Specific Preparations for Oracle
1. Check the value of parameter shared_pool_size:
4 Preparation
Making Preparations at the Database Level
Oracle 9.2: Check the value in file $ORACLE_HOME/dbs/init<SID>.ora.
Oracle 10.1 and higher:
select NAME, VALUE from v$parameter where name=shared_pool_size;
select NAME, VALUE from v$parameter where name=shared_pool_reserved_size;
If the value is lower than 150 MB, increase it to at least 150 MB (400 MB is better), and restart the
database.
2. Log on as user <sapsid>adm at the operating system level.
3. Log on to the database as the Oracle user system with sqlplus
4. Check the resource quotas of the database user SAPR3 or SAP<SAPSID>:
Oracle error 1536 can occur during the upgrade if the resource quotas of database user SAPR3
orSAP<SAPSID> are limited. Make sure that these quotas are unlimited. Check whether the table
DBA_SYS_PRIVS contains one of the following entries:
grantee=SAPR3/SAP<SAPSID>,privilege=UNLIMITED TABLESPACE,adm=YES
grantee=SAPR3/SAP<SAPSID>,privilege=UNLIMITED TABLESPACE,adm=NO
To do this, enter the following SQLPLUS statement:
select * from dba_sys_privs where grantee = SAPR3/SAP<SAPSID>;
If this entry does not exist, enter the SQLPLUS statement:
grant unlimited tablespace to sapr3/SAP<SAPSID>;
5. Log off from the database with the command quit.
6. Only if using the dictionary managed tablespaces function:
Make sure that the storage parameters MAXEXTENTS and NEXT have the correct values for certain tables and indexes. Otherwise, they may overflow during the upgrade. The Oracle-specific upgrade SAP Note contains the tables and the required minimum values.You can display the current settings with BRSPACE. The index names are not constant. However, you can also determine these names with BRSPACE. SAP Note 11777 describes how to change the parameters NEXT and MAXEXTENTS.
7. Only valid for: SAP R/3 3.1I
Make sure that parameter OPTIMIZER_MODE is set to OPTIMIZER_MODE=RULE.
For Oracle 9.2, check and, if necessary, edit the following Oracle profile:
$ORACLE_HOME/dbs/init<SAPSID>.ora
For Oracle 10.1. and higher, use the following statements:
Sqlplus /nolog
Connect /as sysdba
Alter system set OPTIMIZER_MODE=RULE scope=spfile;
8. Only if you do not switch off archiving during the upgrade:
If you want to leave brarchive running during the upgrade to avoid archiver stuck situations (brarchive -f ...), proceed as follows:
a) Create a temporary copy of brarchive:
4 Preparation
4.23 Making Preparations at the SAP System Level
cp /usr/sap/<SAPSID>/SYS/exe/run/brarchive /tmp
b) Start brarchive as user ora<sapsid> from the temporary directory /tmp/brarchive -f ...
c) After the upgrade, delete the copy of brarchive.
This procedure avoids upgrade errors caused by the program files being overwritten during the upgrade.
9. If your database version is already higher than the minimum version for the new release, we recommend that you exchange the DBA tools (such as BRSPACE) for the upgrade. The Database Software Oracle DVD for the database contains the up-to-date tools that you unpacked on the current kernel when you migrated the database. After you execute PREPARE, unpack this archive again into the exe subdirectory of the upgrade directory. This overwrites the DBA tools optimized for the minimum required database version with the tools best suited to your database version.
And if you are talking about an Oracle Upgrade then you just need these to compare once you have upgraded to 10g.
3.9 Checking for Invalid Database Objects
This optional step lets you check if there are any invalid database objects before the database upgrade to Oracle database 10g starts. After the upgrade it helps you distinguish database objects that have become invalid due to the upgrade process from those that were already invalid to start with.
Procedure
1. Execute the following commands:
SQL> spool invalid_objects
SQL> select unique object_name, object_type, owner from dba_objects where status
= 'INVALID';
SQL> @?/rdbms/admin/utlrp.sql
SQL> select unique object_name, object_type, owner from dba_objects where status
= 'INVALID';
SQL> spool off
A list of invalid objects before the upgrade is now generated.
2. Check the list of invalid objects after the upgrade.
If any objects in the list from before the upgrade are also in the list of invalid objects after the upgrade, you can be sure that this is not due to the upgrade process.
Regards,
Suhas

"TypeError: undefined is not an object" after upgrading to 2014.1.1

I'm seeing the error: "TypeError: undefined is not an object (evaluating 'cpoint.getSymbolElement') in an _upgraded composition which is causing points and tooltips to not appear in the loaded composition.
Edge Animate version 2014.1.1
Mac OS 10.10.1
Safari 8.0.2, Chrome 40.0.2214.94, Firefox 35.0.1
This issue only began happening after upgrading to 2014.1.1
No changes were made to my computer and I've tested it on other computers with the same result
Here is the upgraded composition which is not working: http://inlightmedia.com/edge-interactive-svg-maps_upgraded/
Older composition which correctly shows the pins and tooltips: http://inlightmedia.com/edge-interactive-svg-maps/
Zip files of both compositions: Zip file
I am very much an Edge and JavaScript rookie and have been modifying this project (which was created by someone else who is no longer supporting it) to suit my needs. Any help getting this to work in the new version of Edge would be greatly appreciated.
Thanks,
Jansen

Hi,
It comes from compositionReady, line #34:
You wrote: var cpoint = sym.createChildSymbol("point", "stage");
and it was: var cpoint = sym.createChildSymbol("point", "Stage");
stage must be capitalized: Stage.

Compile objects after upgrade

I have a question regarding compiling object after database upgrade
I am upgrading E-BS database from 9i to 10g and i came across two different method to compile objects after the upgrade.
the first solution is using the dbua built in option to compile all objects however this method takes about 14 hours
the second solution is using the script utlrp.sql which is located in <ORACLE_HOME>/rdbms/admin/ this method takes 6 hours on the same database
i am wondering why one is taking so long Vs the other on. which one is recommended and why

You can use both methods. Duration of recompiling depends on count of invalid objects and how much cpu resources are available.
I'm not sure what tehnique is used in dbua, but I think it is the same utlrp.sql.
Looked at documentation, it says it is the same:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28301/software003.htm#BABEAGDG
Selecting Recompile invalid objects at the end of upgrade is equivalent to running the Oracle_home/rdbms/admin/utlrp.sql script, which is used to recompile stored PL/SQL and Java code.
Edited by: Laura Gaigala on May 4, 2009 5:06 PM

Query on new Authorization Objects after Upgrade&SAP_NEW profile

Dear Experts,
We have upgraded our system from 4.5 to 7.0 version, i was checking what are the new authorization Objects introduced after upgrade comparing older system ojects. I got few objects which are new in upgraded system,
But when i check SAP_NEW profile, and in the latest profile SAP_NEW_7000 profile i can not see all those new Ojects which are new.
generally SAP_NEW should contain all new objects which come after upgrade? i can see those in SAP_ALL but not in SAP_NEW
is there any issue in system? how should I know and where should i check what are the new Objects come in upgrade,
Please advise.
Thanks#Regards,
Vijay

Hi Jurjen Heeck ,
see my previous post
I did 'nt get this.
SAP_NEW is your friend here
does the SAP_NEW profile contains all the new authorization Objects.
Regards,
Anthony

Invalid Objects after upgrading 12.1.3

Hi,
I upgraded my EBS version to 12.1.3 from 12.1.2. And the database is 11.1.0.7, OS is RHEL 5.0.
After upgrading im getting some invalid objects of 272 that i mentioned below..
i did all the steps for the fix this ,
1. Ran utlrp.sql script in $ORACLE_HOME/rdbms/admin
2. Compiled the apps schema in adadmin on apps ties
3. Re-link options
4. SQL> @$FND_TOP/patch/115/sql/fndptmus.pls
SQL> @$FND_TOP/patch/115/sql/fndptmub.pls
5. SQL> ALTER PACKAGE BODY ASO_OPP_QTE_PUB COMPILE;
ALTER PACKAGE BODY ASO_OPP_QTE_PUB COMPILE
ERROR at line 1:
ORA-00922: missing or invalid option
INVALID OBJTCTS:
ASO_QUOTE_PUB_W
ASO_SECURITY_INT
ASO_QUOTE_HEADERS_PVT
MSC_SCH_WB
PJM_INQUIRY
OKL_REVERSE_CONTRACT_PVT
INV_OBJECT_GENEALOGY
OE_DELAYED_REQUESTS_UTIL
HXT_RETRO_PROCESS
OKL_PROCESS_TMPT_SET_PVT_W
OKL_TRANS_CONTRACTS_PVT_W
OKL_CONTRACT_PVT
OKL_FUNDING_PVT
OKL_GENERATE_ACCRUALS_PVT_W
OKL_PROCESS_TMPT_SET_PUB
OKL_GENERATE_ACCRUALS_PVT
OKL_AM_ASSET_DISPOSE_PVT
OKL_BLK_AST_UPD_PVT
OKL_CONTRACT_BOOK_PVT
OKL_KBK_APPROVALS_WF
OKL_CS_WF
OKL_FUNDING_WF
OKL_LA_JE_PVT
OKL_INSURANCE_POLICIES_PVT
OKL_INTEREST_CALC_PVT
OKL_AM_BTCH_EXP_LEASE_LOAN_PVT
OKL_LOSS_PROV_PVT
OKL_MISC_TRANS_PVT
OKL_MASS_REBOOK_PVT
OKL_AM_LEASE_LOAN_TRMNT_PVT
OKL_AM_LOAN_TRMNT_PVT
OKL_AM_LEASE_TRMNT_PVT
OKL_RELEASE_PVT
OKL_CONTRACT_REBOOK_PVT
OKL_AM_QUOTES_WF
OKL_REV_LOSS_PROV_PVT
OKL_AM_RECYCLE_TRMNT_PVT
OKL_SPLIT_CONTRACT_PVT
OKL_SPLIT_ASSET_PVT
OKL_TRANS_CONTRACTS_PVT
OKL_AM_TERMNT_QUOTE_PVT
OKL_CS_TRANSFER_ASSUMPTION_PVT
OKL_PROCESS_TMPT_SET_PVT
OKL_TRANSACTION_PVT
OKL_VARIABLE_INTEREST_PVT
OKL_COPY_CONTRACT_PUB_W
OKL_PROCESS_TMPT_SET_PUB_W
WIP_SF_CUSTOM_ATTRIBUTES
AS_SALES_LEAD_OPP_PVT
ASO_OPP_QTE_PUB
OPI_POR_EXPECTED_RCPT_MV
OPI_POR_BACKORDER_SUM_MV
OPI_POR_OVERDUE_RCPT_MV
OKL_CS_PRINCIPAL_PAYDOWN_PVT
AST_UWQ_WRAPPER_PKG
AST_UWQ_OLIST_WORK_ACTION
OKL_AM_CNTRCT_LN_TRMNT_PVT
OKL_AM_TERMINATE_INV_AGMT_PVT
OKL_INVESTOR_INVOICE_DISB_PVT
OKL_PERIOD_SWEEP_PVT
OKL_SEC_AGREEMENT_PVT
IGS_FI_CREDIT_PVT
CSC_ACTION_ASSEMBLER_PVT_W
OZF_EARNING_SUMMARY_MV
ImportExport
ImportExport
WWV_FLOW_LIST_OF_VALUES_DATA
WWV_FLOW_LISTS_OF_VALUES$
WWV_FLOW_GENERIC
WWV_FLOW_FIELD_TEMPLATES
RE_PROFILER
FFP58914_01010001
FFP58915_01010001
FFP58920_01010001
FFP58919_01010001
OKL_BPD_TERMINATION_ADJ_PVT
OKL_STREAM_MIGRATION_PVT
FFP60324_01010001
FFP58887_01042004
FFP58888_01042004
FFP58870_01042004
FFP53720_01011990
FFP58885_01042004
FFP51846_01011990
FFP60964_01012000
OKL_AM_BAL_WRITEOFF_PVT
OKL_LA_SALES_TAX_PVT
OKL_AM_TERMNT_VENDOR_PRG_PVT
WIP_WS_DL_UTIL
OZF_CUST_FUND_SUMMARY_MV
FFP61156_01010001
FFP61138_01010001
FFP61170_01010001
FFP61152_01010001
FFP61124_01010001
FFP61277_01011951
SYS_PLSQL_233217_87_1
FFP61440_01011990
FFP52982_01010001
WMS_WAVE_PLANNING_PVT
FFP61511_01012000
FFP61532_01011990
OKL_MULTIGAAP_ENGINE_PVT
XLA_00707_AAD_C_000026_PKG
XLA_20065_AAD_C_000030_PKG
FSAH_DUPLICATE_PKG
XLA_00707_AAD_C_000044_PKG
OKL_INTERNAL_BILLING_PVT
OE_ITEMS_MV
MSD_DEM_OBI_DEMANTRA_MV
FFP62356_01012000
Any solution for this..??.
Thanks,
vasanth

Hi,
SQL> show errors
Errors for PACKAGE BODY OKL_MULTIGAAP_ENGINE_PVT:
LINE/COL ERROR
0/0     PLS-00907: cannot load library unit APPS.OKL_TCN_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCN_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCL_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCL_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
LINE/COL ERROR
0/0     PLS-00907: cannot load library unit APPS.OKL_TCN_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCN_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCN_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCN_PVT (referenced
LINE/COL ERROR
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCL_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
0/0     PLS-00907: cannot load library unit APPS.OKL_TCL_PVT (referenced
     by APPS.OKL_TRX_CONTRACTS_PVT)
656/4     PL/SQL: Statement ignored
832/10     PL/SQL: Statement ignored
944/10     PL/SQL: Statement ignored
LINE/COL ERROR
971/10     PL/SQL: Statement ignored
1049/10 PL/SQL: Statement ignored
1150/10 PL/SQL: Statement ignored
1226/28 PL/SQL: Item ignored
1227/28 PL/SQL: Item ignored
1228/28 PL/SQL: Item ignored
1229/28 PL/SQL: Item ignored
i didnt get any errors before following that Metalink ID... it replied no errors
Now only im getting errors...
there is no errors in alert log file...
Thanks,
vasanth

System Tablespace objects after upgrade (mdsys, outln, ctxsys, etc)

I have objects in my system tablespace under listed owners. I believe by default with a new 10g install their home is SYSAUX. Is that correct? Oracle changes the default, but doesn't bother to move the objects during upgrade??!!?!!?!!!

Issue was I didn't know what shoudl be in the SYSTEM tablespace and what shoudl be in the SYSAUX tablespace. And what the default tablespace shoudl be for all these id's. I know I didn't communicate that, but I don't think I realized the full extent of the issue until I did further research, which, undfortunately I did after posting the message.
What I found is;
SYS, some SYSTEM and OUTLN objecst can reside in the SYSTEM tablespace
all others shoudl now be in SYSAUX and SYSAUX shoud be the default tablepsace for them.
SYS and OUTLN use SYSTEM as thier default tablespace, however, I haven't definitively identified the default tablespace for SYSTEM db userid.
Facilities owned by the SYSTEM db userid seem to have been diminished in stature, or maybe just determined to be detrimental to SYSTEM tablespace. I have seen notes in during the upgrae process from 8i to 10g that SYSTEM userid should not use SYSTEM as its default tablespace, but exactly what should be used is not clearly defined.
I support Financials E-BS, and we have migrated from 10.7 on 7.x to 11.5.10.2 on 10g. I am afraid that between patching and addressing user expectations, I have not caught all the nuances and adjustments that have coincided with the database upgrades. We have reached a relative level of stability (OCT and JAN CPU's still need to be applied), so I am looking at performance, database standards (through OEM), and tuning.
Thanks for your response.

Invalid objects after upgrade to 11gR2 database in 11i

Hi All
we have prod instance of 11i with 10gR2 database.
Currnetly we have upgraded database to 11gR2.
After upgrade to 11gR2 we have foung lot of "FPA" Invalids.
Please share your views. how to validate this invalids
Regards
Shaik

Please see these docs/threads.
Error PLS-00801: Internal Error [1401] When Compiling Invalid Apps Objects [Doc ID: 784179.1]
Difference between UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL? [Doc ID: 272322.1]
Many db objects error after Upgrate EBS 12.1.1 to EBS 12.1.2(7303033)
Thanks,
Hussein

Activation lock after upgrade

Hi all! I firs and only user of my iPhone 4s apple. But after upgrade AppleID for activation is not valid but i do not change it! and the iPhone buyed in USA CA unlocked and i have a package! Apple support not answer to me what can i do!

Hi all! I firs and only user of my iPhone 4s apple.
If you are the first and only user then call the relevant country number from this list
Apple ID: Contacting Apple for help with Apple ID account security
and with documentary proof of ownership from new and purchased from Apple or an Authorised Apple iPhone reseller they may be able to help

Role -- Object--- activity compare after upgrading from 4.6c to ECC 6.0

Hello,
Our team has recently upgrade the SAP system from 4.6 c to ECC6.0 , after successfully upgradation when i check the customized role some of the Objects and some of the profiles are in INACTIVE status.
So my question is what we have to do for cross check the authorizations with my older authorization and what are the ways to do that.
I have older 4.6C quality system to which i have to compare the newely upgraded ECC 6.0 roles.
will give full point for fast and proper reply.
thanks in advance.
Regards,

Hi,
After the upgrade, you will have to do the security upgrade.
Please follow these steps.
1. Go To SU25
2. Run step 2A to 2D.
3. In step 2C, you shall get the list of all the affected roles.
Click on first role. It will take you to authorizations of that role. Click on the "New" tab there to find the new objects added to the role after the upgrade.
Note: You can open the same role in the unupgraded system to check.
4. Provide the access to the required authorization objects.
5. Disable the unwanted authorization objects.
6. Generate the profile.
7. Follow the same steps for all the affected roles listed.
Please note that you will have a list of new objects added.You need to maintain them inorder to avoid any access issues.
8. After step 2C, complete 2D.
Regards,
Imran

Problem in activating bufferpool after upgrading to 9.5 ( fixpack 1)

After I upgrade the database from version 8 to 9.5 (fixpack 1) I get the error message that the bufferpool cannot be started because there was not enough memory available. The database comes up with smaller size(16K) hidden bufferpool.
However, It works fine when I set the registry Variable ( DB2_OVERRIDE_BPF) to the size which was defined originally ( i.e 50000 pages). The size of the bufferpool was never changed during the upgrade. I am uisng only one bufferpool ( IBMDEFAUlTBP) for the database. The database is running on dedicated server running AIX ( 5.3 ML 8).
Is there any way to activate the database and start the bufferpool(IBMDEFAULTBP) with 50000 without using the the registry variable.
Thanks,
Nasir Syed

Hello Nasir,
DB2 V9.5 requires more memory that your previous V8 installation. You most likely need to allocate more memory for the instance. Are you using STMM? Check the db2diag.log to see if there are any Memory allocation failure errors for the timeframe that you are getting the error. I suspect you will see the following in the db2diag.log :
"Insufficient INSTANCE_MEMORY to allocate new memory set."
Check the following SAP Note for the V9.5 parameter recommendations.
1086130: DB6: DB2 V9.5 Standard Parameter Settings
One more thing to consider:
APAR IZ36972 ACTIVATION OF DATABASE WITH 20% OVERFLOW MAY UNNECESSARILY FAIL DUE TO HITTING
INSTANCE_MEMORY LIMIT
Another defect that could be the reason for memory over allocation by DB2 is APAR IZ41879.
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ41879
So, please go to fixpack 4 to eliminate these possible defects.
This APAR is first fixed in fp 4 currently you are on fp 1.
Regards,
Adam Wilson
SAP Development Support

Invalid objects after upgrade to 9.2.0.6 from 8.1.7.4

Anyone have any input as to how I can validate the following objects that were invalid after my upgrade:
OBJECT_NAME OBJECT_TYPE
BALTOTDELETE PROCEDURE
HtoD JAVA CLASS
MILEXTRACT PROCEDURE
MilExtract PROCEDURE
TLRConvertHexToDecimal JAVA CLASS
UTL_FILE PACKAGE BODY
6 rows selected.
SQL> alter procedure BALTOTDELETE compile;
alter procedure BALTOTDELETE compile
ERROR at line 1:
ORA-04043: object BALTOTDELETE does not exist
SQL> alter procedure MILEXTRACT compile;
alter procedure MILEXTRACT compile
ERROR at line 1:
ORA-04043: object MILEXTRACT does not exist
SQL> alter procedure MilExtract compile;
alter procedure MilExtract compile
ERROR at line 1:
ORA-04043: object MILEXTRACT does not exist
SQL> alter package UTL_FILE compile body;
Warning: Package Body altered with compilation errors.
Any input you could provide would be greatly appreciated.

I know about the mixed case issue. Luckily we only use uppercase. The second case regarding the recompile is a valid, but not applicable in our case.
We are seeing these errors (it appears randomly [to us]) AT RUN-TIME! These objects are there [valid and being executed by many], and one-time it will work and the next maybe, maybe not.
It really makes no sense.
Anybody got any other ideas?
Thanks,
Jason

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.

Activating Objects after Upgrade

Similar Messages

Maybe you are looking for