Note 1054131 - Invalid DB objects after upgrade

Question

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

Answer 1

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