on 09-01-2006 9:32 AM
Hello guys
Hello
We are doing upgrade from R/3 4.6C to ECC 6.0 SR1, platform iseries
In phase START_SHDI_FIRST we get error at starting shadow instance.
It seems the problem is caused by a bad call, the user is DESadm (!!??)
*****************************************************************+
*USRSPC.
Deleting spooled files of instance user
DES03...
0 archivos suprimidos. 0 archivos no
suprimidos.
Starting instance 03 of system
DES...
El subsistema R3_03 ya está
activo.
Command for starting system Job is SBMJOB CMD(CALL PGM
(R3INLPGM)
PARM
('/usr/sap/put/exe/sapstartsrv'
'pf=/usr/sap/put/DES/SYS/profile/START_DVEBMGS03_IBM550' '-
D'))
JOB(SAPSTRSRV) JOBD(R3DES400/R3_03) JOBQ(QSYS/QUSRNOMAX) USER
(DESadm)
SYSLIBL(SYSVAL) CURLIB(CRTDFT) INLLIBL( R3DES400 QTEMP
QGPL)
SRTSEQ(HEX) CCSID(500) CPYENVVAR(YES) ALWMLTTHD
(*YES)
No se ha encontrado el perfil de usuario
DESADM.
Errores producidos en el mandato
SBMJOB.
StartInstance: Error submitting sapstartsrv
job.
***************************************************************+
So, as the user DESadm doesn't exist, the process cancels.
We have applied patch for STARTSAP, but we get same error
Afterwards we have tried to apply patch for R3INLPGM unsuccessfully,
because we got a unknown error during APYR3FIX
Then, we have used a workaround: We have created user DESADM, copied
from DESOFR, and adding additionnal authorizations. With this solution
we don't get anymore this error, of course, and Instance Shadows
starts, but after 2 o 3 mins all workprocess die. Looking the trace
file we don't see the cause ...
So, I think the main problem is a bad call at time of starting shadow
instance.
Any idea???
Thanks and regards
Javier
Hello
I'm doing upgrade with user DESOFR
So, I think, the user DDIC in isntance shadow is locked because SAPup made mistakes
Anyone could tell me how can unlock user DDIC in shadow instance?
Thanks and Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Javier,
I don't see any mistakes of SAPup, but ...
How to enable a locked user ?
UPDATE R3DESSHD/USR02 SET UFLAG = 0
WHERE mandt = '000' and bname = 'DDIC'
If this doesn't work after 2 minutes, I would restart the shadow ...
As follows, you could reset the password to "19920706" which I always use for upgrades:
UPDATE R3DESSHD/USR02 SET BCODE = x'61D26428640DBAB5'
WHERE mandt = '000' and bname = 'DDIC'
(but in your case this is not easy as well, because you might have used a different password before)
btw: I do see a big problem with uppercase and lowercase here in this phase ... this is different as of 7.00 !
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
Hello
OK, I changed password of DDIC sucessfully. Now I can log into Shadow Instance via saplogon but...
.. I have restarted SAPup and... says the same message:
"waiting 20 seconds for system come up"
"testing if system is available""waiting 20 seconds for system come up"
"testing if system is available""waiting 20 seconds for system come up"
"testing if system is available""waiting 20 seconds for system come up"
"testing if system is available"
It seems SAPup doesn't know how to connect ..(!?)
Any idea?
Thanks and regards
file STARTSFI.LOG:
***********************
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2 ETQ370 starting test RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC
4 ETQ359 RFC Login to: System="DES", Nr="03", GwHost="IBM550", GwService="sapgw03"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC failed (error-status "-3")
4 ETQ239 Logging off from SAP system
2WETQ372 test RFC failed, rc="-3"
2EETQ399 Starting shadow instance failed
2EETQ399 Test RFC failed finally
2EETQ399 Dialogue: ERROR
2EETQ399 Starting system failed, rc=0
Hi again
Let's see... i'm going to be crazy...
looking the dev_rfc file I see error about the same " many logon attempts.."
So, I tried connect againg to shadow instance via saplogon, and ... surprise! now I can't!!
After this I reset pssword of DDIC using:
UPDATE R3DESSHD/USR02 SET BCODE = x'61D26428640DBAB5'
WHERE mandt = '000' and bname = 'DDIC'
Now I can't connect with "19920706"... (!?)
I don't understand nothing...
Thanks and regards
Javier
OK Volker,
but when I try to logon in shadow instance , client 000, user DDIC, systems say:
"Password logon no longer possible - too many failed attempts"
What can I do now?
Thanks and regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
now you know your problem !
That's what SAPup does as well and fails as well ...
first question would be:
what password did you tell SAPup for DDIC ?
Then you could check usr02 in the shadow and change the state from locked to unlocked.
but now, it becomes really consulting. I can help you but this is not via this forum and not for free ... sorry.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
Hi again
I can assure that password I told to SAPup for DDIC was right. In fact, SAPup does a verification at first steps of Upgrade
So, I don't understand why I can't log on into shadow instance with this password..
Could you tell me in which library is stored Shadow instance data?
Thanks and Regards
Thanks Volker
I have made this change in file you mentioned, and now it seems Shadow instance starts ok, but.. the process SAPup hangs in a loop
" waiting 20 seconds for system come up, testing if system is available...
...waiting 20 seconds for system come up, testing if system is available......
..waiting 20 seconds for system come up, testing if system is available...
"
How can I continue ???
Thanks and regards
Javier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Javier,
I forgot one thing:
start the shadow instance and wait until it is in SEMW AND log on with DDIC. During the logon process you might run into issues. As soon as they are solved the "20s waiting" will disappear. It could even be that it just needs time as it needs to compile all ABAPs.
=> you should try to logon to the shadow. As soon as this works fine this phase will work fine as well.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
Hi Javier,
I don't remember the exact "look&feel" of this error. But at least every of my upgrades crashed in this phase:
You could have a look at Note 821875 for details:
I always used:
edtf '/usr/sap/put/D01/SYS/global/ms_acl_info' changed as follows:
HOST = *
(as ONLY line => you have to overwrite the one line in there)
Then I stopped the shadow instance and restarted it again. After that it is active, I repeat the upgrade and this phase will run in seconds, because it sees it is active already.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
btw: DESadm is correct as of Basis 7.00 !
All platforms moved to the SAP-Standard of sidadm.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.