Invalid objects found with PRE UPGRADE CHECK while upgrading oracle

[Former Member]

Invalid objects found with PRE UPGRADE CHECK as below while upgrading Oracle 10G to 11GR2 , Should I ignore these as warning or fix the invalid objects before upgrade, what is the consequences if these are not fixed before upgrade.

*********************************************************************

Invalid Objects:

**********************************************************************

WARNING: -

---

> Invalid Objects in SYS schema

.... USER SYS has 5 INVALID object(s).

WARNING: -

---

> Invalid Objects in SAP schema

.... USER SAPSR3 has 2 INVALID object(s).

WARNING: -

---

> Invalid Objects in any other schema

.... USER PUBLIC has 5 INVALID object(s).

.... USER OPS$SAPSERVICESRP has 1 INVALID object(s).

.... USER OPS$SAPSERVICESRQ has 1 INVALID object(s).

.... USER OPS$SAPSERVICESRE has 1 INVALID object(s).

List of invalid objects:

OPS$SAPSERVICESRE.SAPUSER (SYNONYM)

OPS$SAPSERVICESRP.SAPUSER (SYNONYM)

OPS$SAPSERVICESRQ.SAPUSER (SYNONYM)

PUBLIC.DBA_LOGSTDBY_LOG (SYNONYM)

PUBLIC.DBA_LOGSTDBY_PROGRESS (SYNONYM)

PUBLIC.DBA_REGISTERED_ARCHIVED_LOG (SYNONYM)

PUBLIC.DBA_REGISTRY_DATABASE (SYNONYM)

PUBLIC.SAP_DBSTATC (SYNONYM)

SAPSR3.RSRVARIANTVIEW (VIEW)

SAPSR3.V_REP_JOIN (VIEW)

SYS.DBMS_LOGMNR_LOGREP_DICT (PACKAGE BODY)

SYS.DBMS_LOGMNR_SESSION (PACKAGE BODY)

SYS.DBMS_SUMADV (PACKAGE BODY)

SYS.DBA_REGISTERED_ARCHIVED_LOG (VIEW)

SYS.DBA_REGISTRY_DATABASE (VIEW)

.

**********************************************************************

SAP specific Warnings

**********************************************************************

WARNING: -

---

> Invalid objects in SYS schema

Check why these objects are invalid before database upgrade.

Invalid SYS objects can cause the database upgrade to fail.

WARNING: -

---

> Invalid objects in SAP schema

Check why these objects are invalid before database upgrade.

WARNING: -

---

> Invalid objects in other schema

Check why these objects are invalid before database upgrade.

WARNING: -

---

> Table(s) PLAN_TABLE exist(s) in SAP schema.

The table(s) will get dropped after the upgrade and

recreated with new structure.

SAPSR3.PLAN_TABLE

WARNING: -

---

> AWR retention is too small.

Current AWR retention: 7 days. Recommended: 42 or higher

See SAP note 1326067.

.

[baby_fabrice · Accepted solution]

hello,

Do you have run the script PRE_UPGRADE_TASKS wich is in the same folder?

If yes you can run an other time the script PRE_UPGRADE_STATUS and you will see that there will not stay invalid object.

Regards

[Former Member · Accepted solution]

Hi BABY

Incase we still find Invalid Objects in SAP schema for BW systems is it ok to ignore and proceed with upgrade?

[Former Member]

Are you following Upgrade guide?

If yes, It will tell you what you have to do next...

Regards,

Nick Loy