on 12-21-2010 3:41 PM
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:
Instance profile for shadow system 702
rdisp/mshost = sapsys
*** CHANGE for the shadow instance ***"
#rdisp/wp_no_dia = 5
rdisp/wp_no_dia = 5
*** CHANGE for the shadow instance ***"
#rdisp/wp_no_vb = 1
rdisp/wp_no_vb = 1
*** CHANGE for the shadow instance ***"
#rdisp/wp_no_vb2 = 0
rdisp/wp_no_vb2 = 0
*** CHANGE for the shadow instance ***"
#rdisp/wp_no_enq = 1
rdisp/wp_no_enq = 1
*** CHANGE for the shadow instance ***"
#rdisp/wp_no_btc = 4
rdisp/wp_no_btc = 4
*** CHANGE for the shadow instance ***"
#rdisp/wp_no_spo = 1
rdisp/wp_no_spo = 1
PHYS_MEMSIZE = 25%
*** CHANGE for the shadow instance ***"
#rdisp/autoabaptime = 0
rdisp/autoabaptime = 0
zcsa/system_language = E
dbs/ada/schema = SAPDEV
ddic/masact/memopt = true
*** 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
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:
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
*** CHANGE for the shadow instance Default Profile ***"
rsdb/dbid = DEV
abap/package_check = off
auth/shadow_upgrade = 1
check if the parameter value dbs/ada/schema is correct as per point d of note # 129352
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Niraj,
I changed the following line in the instance profile:
from - bs/ada/sqlopt = -u SAPDEVSHD
to - bs/ada/sqlopt = -u SAPDEV
And then I was able to get through that phase and startup the shadow instance.
But now I'm stuck on the MAIN_SHDPREPUT/SUBMOD_EHPPREPUT/ALTNTAB_FILL_PRE phase with the following messages:
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFIPRE.ELG".
And inside the referenced file:
2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
2EETG011 "No shadow system""DB-connect not against shadow tables !"
so the auth/shadow_upgrade parameter in the instance profile seems to be working fine, but where is this environment parameter set? Or maybe changing the line in the instance profile above was the wrong thing to do.............
Any ideas?
Cheers,
James
Hi guys,
This whole problem was caused by the environment variable in the System settings for auth_shadow_upgrade. It was set to "0" for someone reason when at this point it was expected to be set to "1".
So I did that and reset that entry in the instance profile to use SAPDEVSHD and it looks like its working properly now.
Thanks for the help!
Cheers,
James
User | Count |
---|---|
73 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.