SQL1344N Orphan rows found in the system catalogs.

[MarcinOzdzinski]

Hi

I've started preparation to upgrade db from 10.1FP2 to 10.5FP3. During db2ckupgrade following error appeared:

Version of DB2CKUPGRADE being run: VERSION "10.5"

Database: "RA1"

SQL1344N  Orphan rows found in the system catalogs. Contact your technical service representative prior to attempting a database upgrade.

DBT5537I  The db2ckupgrade utility has completed processing for database "RA1".

DBT5529N  The db2ckupgrade utility did not complete successfully. The database cannot be upgraded. The output log file is named "upgrade.lo

g".

As SAP IBM OEM license customer created message to SAP: 400146 / 2014

Question is how long does it take to process this message with IBM support more / less ( i had to postpone db upgrade from this weekend service window):

IBM DB2 10.1 for Linux, UNIX, and Windows

Regards

Marcin

[Former Member · Accepted solution]

Hello Marcin,

IBM will send a db2cleancat tool with a password and description. It may take a few days.

You can speed up the process when you increase the priority.

For the tool IBM need the database level.

Best regards

Joachim

[MarcinOzdzinski · Accepted solution]

Thanks Joachim.

I don't want to use very high cause of course system is running on previous db level smoothly.

Just pass it to IBM please and if it take  no more than week will be OK

Updated message with db2level output.

Regards

Marcin

[Former Member · Accepted solution]

Hi Marcin,

Good news from IBM:

[ Because of changes inside db2ckupgrade introduced in 10.5 Fix Pack 3, APAR IT01225 was created to address this issue:
http://www-01.ibm.com/support/docview.wss?uid=swg1IT01225

Consequence of this changes is possible failure of database upgrade to 10.5 Fix Pack 3, because of extended validation of object and its references.
In order to proceed with migration to 10.5 Fix Pack 3 dropping or fixing dependencies for INVALIDOBJECTS from database is needed:
db2 "SELECT SUBSTR(OBJECTNAME,1,20) OBJECTNAME, SUBSTR(ROUTINENAME, 1,20) ROUTINENAME, OBJECTTYPE FROM SYSCAT.INVALIDOBJECTS"]

Best regards

Joachim

[MarcinOzdzinski · Accepted solution]

Hi Joachim

Your collegue helped me very quickly and upgrade is going now.

The problem was related to SCM upgrade from 701 to 702 performed two years ago. Nearly 300 views were not deleted from shadow instance and after dropping them i was able to continue.

Many thanks for you and Frank.

Regards

Marcin

[sachin_vagyani · Accepted solution]

Hi Marcin,

We are getting the same issue during DB2 upgrade to 10.5. It was complaining about 23 orphan objects most of which we fixed by using SAP Note 2044772. But 7 are still left over and these are objects from shadow instance which was created as part of upgrade done in 2013.

db2 "SELECT SUBSTR(OBJECTSCHEMA,1,10) OBJECTSCHEMA, SUBSTR(OBJECTMODULENAME,1,20) OBJECTMODULENAME, SUBSTR(OBJECTNAME,1,20) OBJECTNAME, SUBSTR(ROUTINENAME, 1,20) ROUTINENAME, OBJECTTYPE, SQLCODE, SQLSTATE, SUBSTR(ERRORMESSAGE,1,30) ERRORMESSAGE, LINENUMBER, SUBSTR(INVALIDATE_TIME,1,20) INVALIDATE_TIME, SUBSTR(LAST_REGEN_TIME,1,20) LAST_REGEN_TIME FROM SYSCAT.INVALIDOBJECTS"

OBJECTSCHEMA OBJECTMODULENAME     OBJECTNAME           ROUTINENAME          OBJECTTYPE SQLCODE     SQLSTATE ERRORMESSAGE                   LINENUMBER  INVALIDATE_TIME      LAST_REGEN_TIME

------------ -------------------- -------------------- -------------------- ---------- ----------- -------- ------------------------------ ----------- -------------------- --------------------

SAPSR3SHD    -                    RSBCTCB_RTXT_V       -                    V                 -204          SQL0204N  "SAPSR3SHD.AGR_TEXTS           - 2013-01-24-19.54.14. 2014-12-30-11.49.28.

SAPSR3SHD    -                    /SDF/V_EM_IPA        -                    V                 -204          SQL0204N  "SAPSR3SHD./SDF/EM_B           - 2013-01-24-19.54.13. 2014-12-30-11.53.24.

SAPSR3SHD    -                    U_11119              -                    V                 -204          SQL0204N  "SAPSR3SHD.BUT020" i           - 2013-01-24-19.54.17. 2014-12-30-11.44.35.

SAPSR3SHD    -                    V_BUT021_FS_BW2      -                    V                 -204          SQL0204N  "SAPSR3SHD.BUT020" i           - 2013-01-24-19.54.17. 2014-12-30-11.44.35.

SAPSR3SHD    -                    SWK1OUT1             -                    V                 -204          SQL0204N  "SAPSR3SHD.SWWWIHEAD           - 2013-01-24-19.54.17. 2014-12-30-11.44.35.

SAPSR3SHD    -                    RSODP_BWA_INDEXP     -                    V                 -204          SQL0204N  "SAPSR3SHD.RSODP_BWA           - 2013-01-24-19.54.19. 2014-12-30-11.44.35.

SAPSR3SHD    -                    EPM_V_PROD_TXT       -                    V                 -204          SQL0204N  "SAPSR3SHD.SNWD_PD"            - 2013-01-24-19.54.25. 2014-12-30-11.44.35.

  7 record(s) selected.

Please confirm how did you and SAP fixed this issue - did they simply dropped these shadow instance objects?

Thanks

Davinder

[MarcinOzdzinski · Accepted solution]

Yes , that was the solution.

[sachin_vagyani · Accepted solution]

Thanks, did SAP confirmed the reason for these invalid objects still existing for shadow instance schema. Ideally it should have been cleaned up post upgrade automatically, infact SAPSR3SHD schema should have been dropped automatically by SUM

Reason i am trying to understand is our next systems in the landscape including production system have the same 7 invalid objects.

[MarcinOzdzinski · Accepted solution]

They suppose it was due to error in earlier version of SUM tool. If your upgrade was done using same vesion all your db will be affected.

Regards

Marcin