disp+work error after upgrade

[Former Member]

Hi all, while upgrading 4.6C to ECC 6.0 with MAXDB 7.6 build 35, SAPup tries to start SAP System but work processes fail with this error

C INFO : Connect to DB as 'SAPR3'

C *** ERROR => the connected shadow upgrade user (SAPR3) does not work with the right user/schema

[dbslsdb.cpp 4793]

C *** ERROR => application has to work with schema SAPR3SHD (dbs/ada/schema)

[dbslsdb.cpp 4795]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1440]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10468]

M

I've already tried to change default profile parameter dbs/ada/schema to SAPR3 and SAPR3SHD as I've changed windows profile dbs_ada_schema to SAPR3SHD but the error maintains, except it shows

C *** ERROR => application has to work with schema SAPR3SHDSHD (dbs/ada/schema)

kernel was already updated, someoneas any idea ??

Thanks in advance,

best regards,

Pedro Rodrigues

[Former Member · Accepted solution]

Hi,

check Note 39439 - XUSER entries for SAP DB 6.x and 7.x

regards,

kaushal

[Former Member · Accepted solution]

Hi kaushal,

I've checked that oss note, and changed DEFAULT Xuser to SAPR3 and SAPR3SHD, but no success, is that what mean, right?

if not, what's your idea?

thanks

Regards,

Pedro

[former_member229109 · Accepted solution]

Hello Pedro,

Please update with additional information to get clear on the reported issue:

-> Please update with output of the following commands, run them on the database server:

dbmcli db_enum

dbmcli inst_enum

xinstinfo <DB-name>

dbmcli -d <DB-name> -u <dbm-user>,<pwd> user_getall

-> Please run the SQL statement as SYSDBA user < default user/pwd: superdba/admin > & update with output:

select * from users

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

updated information:

dbmcli db_enum

SID C:\sapdb\SID\db 7.6.00.35 fast running

SID C:\sapdb\SID\db 7.6.00.35 quick offline

SID C:\sapdb\SID\db 7.6.00.35 slow offline

SID C:\sapdb\SID\db 7.6.00.35 test offline

dbmcli inst_enum

7.6.00.35 C:\sapdb\sid\db

xinstinfo <DB-name>

IndepData : c:\sapdb\data

IndepPrograms : c:\sapdb\programs

InstallationPath : C:\sapdb\SID\db

Kernelversion : KERNEL 7.6.00 BUILD 035-123-139-084

Rundirectory : c:\sapdb\data\wrk\SID

dbmcli -d <DB-name> -u <dbm-user>,<pwd> user_getall

SUPERDBA

CONTROL

DOMAIN

-> Please run the SQL statement as SYSDBA user < default user/pwd: superdba/admin > & update with output:

select * from users

'CONTROL';'';'CONTROL';'ADMIN';'MULTIPLE';(null);(null);(null);'DEFAULT';'200805

08';'00105554';'20080508';'00105554';'20080508';'00105554';'SID';'DESENV.customer.l

ocal';0;'NO';(null)

'SUPERDBA';'';'SUPERDBA';'SYSDBA';'MULTIPLE';(null);(null);(null);'DEFAULT';'200

80507';'00125533';'20080508';'00105627';'20080509';'00181419';'SID';'DESENV.amba

r.local';10;'NO';(null)

'SUPERDBA';'';'SAPR3';'DBA';'MULTIPLE';(null);(null);(null);'ASCII';'20080507';'

00125541';'20080507';'00125541';'20080507';'00125543';'SID';'DESENV.customer.local'

;14;'NO';(null)

'SUPERDBA';'';'SAPR3SHD';'DBA';'MULTIPLE';(null);(null);(null);'DEFAULT';'200805

10';'00152208';'20080510';'00152208';'20080510';'00152208';'SID';'DESENV.customer.l

ocal';33;'NO';(null)

I hope this helps you..

thanks and best regards,

Pedro

Edited by: Pedro Rodrigues on May 12, 2008 8:05 PM

[former_member229109 · Accepted solution]

Hello Pedro,

-> Did you create the SAP ticket, where this problem is reported?

-> It will be helpful in what upgrade phase you failed? What upgrade strategy you

selected? Also it will be helpful to review the upgrade logs.

Please post the R3upchk.log < please list the "Environment for R3up" >

&& TOOLOUT.LOG , shdinst.out.

Please post <DIR_PUT>\bin\DEFAULT.TPP

-> "I've already tried to change default profile parameter dbs/ada/schema to SAPR3 and SAPR3SHD as I've changed windows profile dbs_ada_schema to SAPR3SHD"

Why did you do so? Could you please give the reference to the document/SAP note, where it was recommended?

< Please also change the DEFAULT Xuser entry back to SAPR3, SAP note 39439 >

-> Please run & update with results::

<.>:\usr\sap\put\exe\tp.exe pf=<.>:\usr\sap\put\bin\DEFAULT.TPP getdbinfo SID

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

Thanks for help

-> Did you create the SAP ticket, where this problem is reported?

Yes, I did

-> It will be helpful in what upgrade phase you failed? What upgrade strategy you

selected?

Upgrade failed in phase STARTSAP_NBAS and I've selected the Resource Minimized strategie, anyway I think this is just a problem with communiation between SAP and DB, because I was able to configure xuser in order to connect to DB but then SAPR3SHD does not found table SVERS (witch is normal because it is in SAPR3 schema), but then, if I changed profile parameter dbs/ada/schema did not solved it. I've used homogeneous copy oss notes to try to connect to DB, i know that xuser as something to do with it becaus when I clean it, then it fail the connection. with xuser = SAPR3SHD it didn't found SVERS and with SAPR3 it gave the error above about the schema issue.

TOOLOUT.LOG

SAPup> Starting subprocess tp.exe with id 1572 at 20080512022037

EXECUTING d:\usr\sap\put\exe\tp.exe pf=d:\usr\sap\put\bin\DEFAULT.TPP getdbinfo AT2

Environment: dbs_ada_schema=SAPR3SHD

Environment: Path=c:\sapdb\programs\bin;c:\sapdb\programs\pgm;c:\programs\sdb\programs\bin;c:\programs\sdb\programs\pgm;C:\Program Files\EMC\PowerPath\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbe5233";;D:\usr\sap\AT2\sys\exe\run;C:\sapdb\programs\pgm;D:\usr\sap\AT2
exe;
DESENV\SAPMNT\AT2\sys\exe\run;c:\sapdb\programs\pgm

Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

KERNVER=700

SAPVERS=700

DOKVERS=700

COMPVERS=EA-APPL 600 0006

COMPVERS=EA-DFPS 600 0006

COMPVERS=EA-FINSERV 600 0006

COMPVERS=EA-GLTRADE 600 0006

COMPVERS=EA-HR 600 0007

COMPVERS=EA-IPPE 400 0006

COMPVERS=EA-PS 600 0006

COMPVERS=EA-RETAIL 600 0006

COMPVERS=ECC-DIMP 600 0006

COMPVERS=ERECRUIT 600 0006

COMPVERS=FI-CA 600 0006

COMPVERS=FI-CAX 600 0006

COMPVERS=FINBASIS 600 0006

COMPVERS=INSURANCE 600 0006

COMPVERS=IS-CWM 600 0006

COMPVERS=IS-H 600 0006

COMPVERS=IS-M 600 0006

COMPVERS=IS-OIL 600 0006

COMPVERS=IS-PS-CA 600 0006

COMPVERS=IS-UT 600 0006

COMPVERS=LSOFE 600 0006

COMPVERS=PI_BASIS 2005_1_7000009

COMPVERS=SAP_ABA 700 0009

COMPVERS=SAP_AP 700 0006

COMPVERS=SAP_APPL 600 0006

COMPVERS=SAP_BASIS 700 0009

COMPVERS=SAP_BW 700 0009

COMPVERS=SAP_HR 600 0007

COMPVERS=SEM-BW 600 0006

COMPVERS=ST-PI 2005_1_7000002

DBAVERS=7.6.00.035

DBASUBTYPE=STANDARD

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

DEFAULT.TPP

transdir = d:\usr\sap\put\

r3transpath = D:\usr\sap\AT2\SYS\exe\run\R3trans.exe

#

alllog = ALOG700

syslog = SLOG700

#

fromdir = d:\usr\sap\put\exe\

todir = D:\usr\sap\AT2\SYS\exe\run\

exelist = "d:\usr\sap\put\exe\instance.lst d:\usr\sap\put\exe\instancedb.lst"

#

interrupt = no

#

mainimp_proc = 6

#

MVNTAB_LIST_FAILED = 0

#

daylight_shutdown = yes

clientcascade = true

with_tacob = no

lock_eu = yes

impdp_by_event = yes

repeatonerror = 8

stoponerror = 9

kernelmove = false

buffreset = no

reset_timestamps = yes

nbufform = 1

tp_version = 264

1. specific system parameters

AT2/dbtype = ada

AT2/dbname = AT2

AT2/dbhost = DESENV

sapevtpath = D:\usr\sap\AT2\SYS\exe\run\sapevt.exe

#

AT2/system_nr = 00

#

AT2/startsap = d:\usr\sap\put\exe\startsap.exe name=AT2 nr=00 SAPDIAHOST=DESENV

AT2/stopsap = d:\usr\sap\put\exe\stopsap.exe name=AT2 nr=00 SAPDIAHOST=DESENV

AT2/bufreftime = 120

AT2/batch_proc = 6

Regards,

Pedro

[former_member229109 · Accepted solution]

Hello Pedro,

-> What is the OSS SAP ticket number for the reported issue?

-> Phase STARTSAP_NBAS is the beginning of the

"Upgrade Phase Group: Downtime phases II: Conversion, Main Import, XPRAs".

Why did you change the Environment dbs_ada_schema to SAPR3SHD?

Please connect to the database as SAPR3 user & run the SQL statement:

select * from "SAPR3"."SVERS"

&& update with results.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

OSS message is 0000395076

I've changed ads_dba_schema in order to figure it out what was the issue that cause this problem, but I could not found any solution.

I'm completely stucked since yesterday!!

Thanks

Pedro

[Former Member · Accepted solution]

select * from SAPR3.svers returs "700" witch is the correct one

SAPR3 owns all tables in db

SAPR3SHD owns none!!

[Former Member · Accepted solution]

up

this issue persists ..

regards,

Pedro

[former_member229109 · Accepted solution]

Hello,

You already passed KX_SWITCH phase.

Please set dbs_ada_schema to SAPR3.

Please set dbs/ada/schema to SAPR3 < see 129352 >.

Please also change the DEFAULT Xuser entry back to SAPR3, SAP note 39439.

< check the users <sid>adm and SAPservice<SID> >

-> Please run & update with results::

d:\usr\sap\put\exe\tp.exe pf=d:\usr\sap\put\bin\DEFAULT.TPP getdbinfo AT2

disp+work -V

R3trans -d

-> What else did you change manually?

-> The SAP ticket 395076 is processed by upgrade colleagues < component BC-UPG > & if you have additional questions please update the ticket.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia, I didn't change anything more.

after done as you said, result was:

C Attach to SAP DB : Kernel 7.6.00 Build 035-123-139-084

C Database release is SAP DB 7.6.00.035

C INFO : Database 'AT2' instance is running on 'DESENV'

C INFO : SAP DB Packet_Size = 65536

C INFO : SAP DB Min_Reply_Size = 4096

C INFO : SAP DB Comm_Size = 61440

C INFO : DBSL buffer size = 61440

C INFO : SAP DB MaxLocks = 800000

C INFO : Connect to DB as 'SAPR3'

C *** ERROR => the connected shadow upgrade user (SAPR3) does not work with the right user/schema

[dbslsdb.cpp 4793]

C *** ERROR => application has to work with schema SAPR3SHD (dbs/ada/schema)

[dbslsdb.cpp 4795]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1440]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10468]

M

getdbinfo

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

KERNVER=700

SAPVERS=700

DOKVERS=700

COMPVERS=EA-APPL 600 0006

COMPVERS=EA-DFPS 600 0006

COMPVERS=EA-FINSERV 600 0006

COMPVERS=EA-GLTRADE 600 0006

COMPVERS=EA-HR 600 0007

COMPVERS=EA-IPPE 400 0006

COMPVERS=EA-PS 600 0006

COMPVERS=EA-RETAIL 600 0006

COMPVERS=ECC-DIMP 600 0006

COMPVERS=ERECRUIT 600 0006

COMPVERS=FI-CA 600 0006

COMPVERS=FI-CAX 600 0006

COMPVERS=FINBASIS 600 0006

COMPVERS=INSURANCE 600 0006

COMPVERS=IS-CWM 600 0006

COMPVERS=IS-H 600 0006

COMPVERS=IS-M 600 0006

COMPVERS=IS-OIL 600 0006

COMPVERS=IS-PS-CA 600 0006

COMPVERS=IS-UT 600 0006

COMPVERS=LSOFE 600 0006

COMPVERS=PI_BASIS 2005_1_7000009

COMPVERS=SAP_ABA 700 0009

COMPVERS=SAP_AP 700 0006

COMPVERS=SAP_APPL 600 0006

COMPVERS=SAP_BASIS 700 0009

COMPVERS=SAP_BW 700 0009

COMPVERS=SAP_HR 600 0007

COMPVERS=SEM-BW 600 0006

COMPVERS=ST-PI 2005_1_7000002

DBAVERS=7.6.00.035

DBASUBTYPE=STANDARD

disp+work version 133 on put, and 146 on kernel

R3trans: version 6.14 (release 700 - 14

.02.08 - 14:55:00).

Thanks and best Regards,

Pedro

[Former Member · Accepted solution]

Hi again,

Support has not answered the oss message yet. no one has any idea to solve this issue or how can I trace it?

Thanks

Pedro

[former_member229109 · Accepted solution]

Please check SAP Note No. 398100.

Please check variable or profile parameter switches the connect to the shadow

user, schema or database ::

auth_shadow_upgrade = 1 ??

Did you set/change this parameter manually?

[Former Member · Accepted solution]

Hi Natalia,

I just be able to passed this, i've checked the oss note mensioned by you and tried to change thauth_shadow_upgrade = 1

to another name, and SAP starts, now upgrade is running again. I hope it did not stop because of this profile change.

I didn't changed this parameter by hand, perhaps, some step in the upgrade didn't made his job!!!

If I've another issue, I will return to this thread.

Thanks for everything.

Regards,

Pedro Rodrigues

PS: I've reward your deserved points

[former_member229109 · Accepted solution]

Hello Pedro,

As I already wrote you, the SAP ticket 395076 is processed by upgrade colleagues

< component BC-UPG > & if you have additional questions please update the ticket.

In case, if you urgent to get solution => update the SAP ticket Or increase the priority of the ticket, please.

Thank you and best regards, Natalia Khlopina