Problem in Upgradphase - JOB_PSUPDEC

[Former Member]

Hello,

the upgrade stops with following error:

BATCHJOB RSUPTEC FAILED

The shadow instance are running and i can logon.

In the Transaction SM37 the Job RSUPDTEC are in status green : finished

Below are the 2 central Log-Files with error details:

PSUPDTEC.elg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ADJUSTMENTS FOR MCOD SYSTEMS Errors and RETURN CODE in RSUPDTEC.CDP

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2EETG011 "Internal error""(modify_tabspace)""1"

PSUPDTEC.LOG

de-phase "JOB_RSUPDTEC" ("20080609193950")

2 ETQ366 Connect variables are set for shadow instance access

4 ETQ399 System-nr = '50', GwService = 'sapgw50'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ora_schema=SAPSR3

4 ETQ399 auth_shadow_upgrade=1

4 ETQ260 Starting batchjob "RSUPDTEC"

4 ETQ010 Date & Time: 20080609193950

4 ETQ260 Starting batchjob "RSUPDTEC"

4 ETQ230 Starting RFC Login to: System = "CDP", GwHost = "drfeelgood", GwService = "sapgw50"

4 ETQ359 RFC Login to: System="CDP", Nr="50", GwHost="drfeelgood", GwService="sapgw50"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC

4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded

4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC

4 ETQ010 Date & Time: 20080609194211

4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ239 Logging off from SAP system

2EETQ241 Errors found in logfiles - accumulated in file "PSUPDTEC.ELG"

1EETQ203 Upgrade phase "JOB_RSUPDTEC" aborted with errors ("20080609194212")

Have anyone an idea, whats happen ? Can i ignore this phase ?

Cheers

Mario

Edited by: Mario Max on Jun 9, 2008 8:03 PM

[markus_doehr2]

Maybe note 1114850 - Upgrade of SAP systems based on 46D_EX2 kernel to 640 will help...

Markus

[Former Member]

No we havent`t

I only create one tablespace espacially for the upgrade....so you mean i can ignore it ?

[markus_doehr2]

Does the error occur again if you repeat?

Markus

[Former Member]

yes, its the same when i repeat the phase, but in SM37 the job successfully finished

[Former Member]

Here ist the Log from the RSUPTEC.CDP File

4 ETG010 "Table statistics" "SLOAD" "PSAPSR3" "14"

4 ETG010 "Table statistics" "SPROT" "PSAPSR3" "201"

4 ETG010 "Table statistics" "SSDEF" "PSAPSR3700X" "336"

4 ETG010 "Table statistics" "SSEXC" "PSAPSR3700X" "336"

4 ETG010 "Table statistics" "SSEXC" "PSAPSR3" "14"

4 ETG010 "Table statistics" "SSRC" "PSAPSR3" "229"

4 ETG010 "Table statistics" "USER" "PSAPSR3USR" "8"

2EETG011 "Internal error""(modify_tabspace)""1"

4 ETG011 "Resolve inconsistencies with DDART in table""TAORA"

4 ETG011 "Resolve inconsistencies with DDART in table""IAORA"

4 ETG011 "Adjust setting according to db-distribution""TAORA"

4 ETG011 "MOD TABART/Container old/container new""APPL0""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""APPL1""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""APPL2""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""CLUST""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""DDIM""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""DFACT""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""DODS""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""POOL""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""SDIC""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""SDOCU""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""SLDEF""PSAPSR3700X""PSAPSR3700X"

4 ETG011 "MOD TABART/Container old/container new""SLEXC""PSAPSR3700X""PSAPSR3700X"

4 ETG011 "MOD TABART/Container old/container new""SLOAD""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""SPROT""PSAPSR3""PSAPSR3"

4 ETG011 "MOD TABART/Container old/container new""SSDEF""PSAPSR3700X""PSAPSR3700X"

4 ETG011 "MOD TABART/Container old/container new""SSEXC""PSAPSR3700X""PSAPSR3700X"

4 ETG011 "MOD TABART/Container old/container new""SSRC""PSAPSR3""PSAPSR3"

3WETG011 "No usable container for tabart""TEMP""- keeping old value"

4 ETG011 "MOD TABART/Container old/container new""USER""PSAPSR3USR""PSAPSR3USR"

3WETG011 "No usable container for tabart""USER1""- keeping old value"

4 ETG011 "Adjust setting according to db-distribution""IAORA"

3WETG011 "No usable container for tabart""APPL0"

3WETG011 "No usable container for tabart""APPL1"

3WETG011 "No usable container for tabart""APPL2"

3WETG011 "No usable container for tabart""CLUST"

[Former Member]

This Problem is solved.

It was a different version between disp+work and the sapstartsrv.exe. So always use the a consistent kernel. Following of this inconstistency the Upgrade routine is writing a file .lck in user\sap\put\mig, that is the reason why the Upgrade`s stick in the mud.

Cheers Mario

[markus_doehr2]

> The shadow instance are running and i can logon.

> In the Transaction SM37 the Job RSUPDTEC are in status green : finished

anything in the joblog?

Markus

[Former Member]

Hi,

no only started and finished - no errors

[markus_doehr2]

I wouldn't ignore that phase.

The program corrects tablespace names in some tables... do you have some non-standard names?

Markus