Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Netweaver ehp2 upgrade failed at START_SHDI_FIRST phase

Hello experts,

I'm having an issue with the START_SHDI_FIRST phase of my Netweaver ehp2 upgrade. I'm upgrading from 7.01 SP5, Windows 32bit, with MaxDB 7.7.

Basically when trying to start the shadow instance the disp_work dies and the following is what pops out at me from the dev_w0 log:

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

[dbslsdb.cpp 5357]

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

[dbslsdb.cpp 5359]

The contents of the system profiles can be found below.

I checked OSS notes about changing the schema name in the profiles to SAPR3 but I continue to get the same error..........

Anyone have any ideas on what the problem could be?

Thanks,

James

DEV_DVEBMGS03_sapsys:

  1. Instance profile for shadow system 702

rdisp/mshost = sapsys

  1. *** CHANGE for the shadow instance ***"

#rdisp/wp_no_dia = 5

rdisp/wp_no_dia = 5

  1. *** CHANGE for the shadow instance ***"

#rdisp/wp_no_vb = 1

rdisp/wp_no_vb = 1

  1. *** CHANGE for the shadow instance ***"

#rdisp/wp_no_vb2 = 0

rdisp/wp_no_vb2 = 0

  1. *** CHANGE for the shadow instance ***"

#rdisp/wp_no_enq = 1

rdisp/wp_no_enq = 1

  1. *** CHANGE for the shadow instance ***"

#rdisp/wp_no_btc = 4

rdisp/wp_no_btc = 4

  1. *** CHANGE for the shadow instance ***"

#rdisp/wp_no_spo = 1

rdisp/wp_no_spo = 1

PHYS_MEMSIZE = 25%

  1. *** CHANGE for the shadow instance ***"

#rdisp/autoabaptime = 0

rdisp/autoabaptime = 0

zcsa/system_language = E

dbs/ada/schema = SAPDEV

ddic/masact/memopt = true

  1. *** CHANGE for the shadow instance ***"

dbs/ada/sqlopt = -u SAPDEVSHD,rl30QzQZ

em/initial_size_MB = 2048

ipc/shm_psize_10 = 128000000

ipc/shm_psize_40 = 112000000

rdisp/accept_remote_trace_level = 0

transport/during_upgrade = ON

rdisp/system_needs_spool = false

snc/enable = 0

rdisp/j2ee_start = 0

rdisp/start_icman = false

vmcj/enable = off

abap/package_check = off

rdisp/dynamic_wp_check = false

  1. Adaptions for shadow system 702

SAPSYSTEMNAME = DEV

SAPSYSTEM = 03

INSTANCE_NAME = DVEBMGS03

SAPGLOBALHOST = sapsys

SAPLOCALHOST = sapsys

SAPLOCALHOSTFULL = sapsys

DIR_INSTANCE = C:\Upgrade702\EHPI\abap$(DIR_SEP)DEV$(DIR_SEP)$(INSTANCE_NAME)

DIR_PROFILE = C:\Upgrade702\EHPI\abap$(DIR_SEP)DEV$(DIR_SEP)SYS$(DIR_SEP)profile

DIR_EXECUTABLE = C:\Upgrade702\EHPI\abap\exe

DIR_CT_RUN = C:\Upgrade702\EHPI\abap\exe

DIR_GLOBAL = C:\Upgrade702\EHPI\abap$(DIR_SEP)DEV$(DIR_SEP)SYS$(DIR_SEP)global#

auth/shadow_upgrade = 1

DEFAULT.PFL:

  1. Default profile for shadow system 702

dbms/type = ada

SAPSYSTEMNAME = DEV

SAPDBHOST = sapsys

rdisp/mshost = sapsys

rdisp/vbname = sapsys_DEV_03

rdisp/enqname = sapsys_DEV_03

rdisp/btcname = sapsys_DEV_03

rdisp/bufrefmode = sendon,exeauto

ZTTA/DEFTITLE = SAP Web Application Server

rdisp/msserv = 3603

DIR_TRANS = C:\Upgrade702\EHPI\abap

DIR_PUT = C:\Upgrade702\EHPI\abap

rdisp/myname = sapsys_DEV_03

  1. *** CHANGE for the shadow instance Default Profile ***"

rsdb/dbid = DEV

abap/package_check = off

auth/shadow_upgrade = 1

Not what you were looking for? View more on this topic or Ask a question