start_shdi_first in upgrade - SAP Community

I have stucked with this step for days.

when I looked at the trace file, it looked like it can connect to the shadow instance, but failed to call function module.

But after this DDIC user is locked. after I unlocked DDIC and gave a new password, and used SAPUP set stdpar to change DDIC password to the new one.

Same thing happen.

I can login interactively with DDIC and call that funtion module, and also from other systems with RFC connection. Is there something I missed here?

Here is the log file.

Anybody can help?

Thanks,

Eric

-

1 ETQ201XEntering upgrade-phase "START_SHDI_FIRST" ("20060904015943")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ora_schema=SAPR3

4 ETQ399 auth_shadow_upgrade=0

4 ETQ399 Set environment for shadow connect:

4 ETQ399 ENV: dbs_ora_schema=SAPR3

4 ETQ399 ENV: auth_shadow_upgrade=1

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '01', GwService = 'sapgw01'

4 ETQ399 Set tool parameters for shadow connect:

4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"

4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ383 translates to path "exe"

4 ETQ383 translates to path "exe"

4 ETQ399 default TPPARAM: SHADOW.TPP

4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"

4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ383 translates to path "exe"

4 ETQ383 translates to path "exe"

2 ETQ399 Starting shadow instance

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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

2 ETQ353 Starting system

2 ETQ370 starting test RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="TST", Nr="01", GwHost="namsdatwn898", GwService="sapgw01"

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

4 ETQ399 Set environment for standard connect:

4 ETQ399 ENV: dbs_ora_schema=SAPR3

4 ETQ399 ENV: auth_shadow_upgrade=0

4 ETQ399 Set RFC variables for standard connect:

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Set tool parameters for standard connect:

4 ETQ399 default TPPARAM: DEFAULT.TPP

1EETQ204 Upgrade phase "START_SHDI_FIRST" aborted with severe errors ("20060904020540")

SAP Managed Tags:
Oracle Database,
SAP ERP

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (3)

Answers (3)

Hello

Thanks, I obtein unlock DDIC, but when we start shadow instance, password DDIC is not correct

000120 | 00000000 00000000 00000000 00000000 |................|

000130 | 00000000 00000000 00000000 00000000 |................|

000140 | 00060514 00104602 BF78BF69 2216E100 |......F.¿x¿i".á.|

000150 | 00000A01 00420514 0402003C 50617373 |.....B.....<Pass|

000160 | 776F7264 206C6F67 6F6E206E 6F206C6F |word logon no lo|

000170 | 6E676572 20706F73 7369626C 65202D20 |nger possible - |

000180 | 746F6F20 6D616E79 20666169 6C656420 |too many failed |

000190 | 61747465 6D707473 0402FFFF 0000FFFF |attempts..ÿÿ..ÿÿ|

>>>> < accepted > : INT <ac: 54> K jessica >>> FLUSH(WRITE) (94440551)

{4602BF78-BF69-2216-E100-00000A010042}-

>>>> < accepted > : INT <ac: 55> K jessica >>> FLUSH(WRITE) (94440551)

{4602BF78-BF69-2216-E100-00000A010042}-

>>>> < accepted > : INT <ac: 56> K jessica >>> ABORT absignon.c 2423 (94440551)

shadow instance start but you can´t logon.

We change password DDIC with SAPup set shdddicpwd, but I don´t known which password use SAPup

Please could you indicate us how make DDIC can logon in shadow instance??

Thanks

Best Regards

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

hello

We have same problem, but we don´t known how unlock user DDIC...please if you can help us ??

Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

search SDN with keywords: unlock DDIC

hi,

i don't remember clearly but is there any dev_rfc file under log dir?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Guys,

Finally I solved it.

The problem was due to the password saved by SAPUP was different from what was in SAP, instance 01.

I do not know the mechanism of SAPUP transmitting the password while the new Shadow instance becomes case sensitive. My experience is even when the password case is correct in SAPUP, it still would not work.

Finally I reset the password for DDIC, shadow instance 01, to a series of numbers, such as '19920706', then it worked just fine.

However, it took me a long time to try it out. I wish there was a warning for this if you used combination of letters/numbers for password you may have problem during upgrade, at the beginning of the upgrade guide or the note supplement to the guide.

The command to set new password on Windows is:

SAPup set shdddicpwd

choose instance 01 to go on next.

Then one has to make sure you can log in to client 000, instance 01, with that password before you can restart SAPUP.

Thanks,

Eric

very well.

enjoy your activity

Hi Eric,

We are facing the same issue, and stuck in the upgrade (4.6C to ECC6), could you please help us, how you sloved, that would be great help,

Tried changing the password for DDIC using "SAPup set shdddicpwd", eventhough we are not able to login to the Shadow system using DDIC,

Please help us, Thanks in advance,

--Nag

Ask a Question

Top Q&A Solution Author

User

Count

85

10

10

9

6

6

6

5

4

3