SAP Upgrade - BW 3.0B to NW2004s SR2 (BI 7)

[Former Member]

Hi,

I have hit a problem in the START_SHDI_FIRST phase. The UA gives the following message...

ERROR: Starting system failed, rc=0

The log file STARTSFI.LOG contains the following...

2 ETQ370 starting test RFC

4 ETQ359 RFC Login to: System="XGU", Nr="02", GwHost="emalonsbx001", GwService="sapgw02"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ359 RFC Login to: System="XGU", Nr="02", GwHost="emalonsbx001", GwService="sapgw02"

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

The shadow instance is started. I can log in to client 000 as DDIC. Form the UA I ran "Start SAPup with options" and set the DDIC password to the correct password. Here is the interesting bit... when I repeat the START_SHDI_FIRST phase it fails and DDIC is locked out of the system (uflag value of 128 in usr02).

Any help on this one would be much appreciated!

Cheers,

Greg.

[Former Member · Accepted solution]

Greg,

Can you see any additional information in the system? ST22, SM20, etc? I'm curious as to what exactly went wrong with the call of FM UPG_IS_SHADOW_SYSTEM.

Thanks.

Tim

[Former Member · Accepted solution]

Hi Tim,

There are no runtime errors in ST22 and no entries in the Security Audut Log (SM20). I can display and execute the function module in SE37.

Cheers,

Greg.

[former_member204746 · Accepted solution]

change back password to 19920706 for DDIC in client 000, in your working client, and with SAPUP and try again.

[Former Member · Accepted solution]

Greg,

This probably relates to Eric's comments.

In past upgrades, I've seen an issue where the xml file can cause some issues - for instance having fewer characters than the password itself - i.e. your password is the WAS620 max of 8 characters, and the XML is only recording 7 (mismatch equals a password lock) or the XML obseves case sensitivty (which is observed now in WAS700/NW04S. Maybe a solution here is to enter DDICs password in UPPERCASE to match the WAS620 backend (remember everything gets converted UP) and the UA is attempting to pass as lowercase or mixed.

I know on the surface this should NOT be, but I've seen these types of issues. If the all CAPS password entry does not work, you may need to check the control.xml file or others to see if there are any mismatches.

Hope this helps.

Tim

[Former Member · Accepted solution]

Hi Eric and Tim,

Thanks very much for your interest in my question/post.

I have fixed the problem and it seems I caused it myself in the first place.

When I ran PREPARE I entered 'greg' as the DDIC password. I subsequently changed the password to 'niceday'. So that SAPup would know the password was 'niceday' I ran Aministrator -> Start SAPup with options and changed the DDIC password to 'niceday' here as well. This does NOT work! SAPup was using the passworg 'greg' every time and thats why DDIC ended up getting locked. As soon as I changed the password of DDIC back to 'greg' in SU01 SAPup finished this phase with no problem! No more changing passwords mid upgrade for me!

Thanks again for responding,

Greg.

4 ETQ359 RFC Login to: System="XGU", Nr="02", GwHost="emalonsbx001", GwService="sapgw02"

4 ETQ232 RFC Login succeeded

4 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

4 ETQ234 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC succeeded

4 ETQ239 Logging off from SAP system

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 = '01', GwService = 'sapgw01'

4 ETQ399 Set tool parameters for standard connect:

4 ETQ399 default TPPARAM: DEFAULT.TPP

1 ETQ202 Upgrade phase "START_SHDI_FIRST" completed sucessfully ("20070316183230")

[Former Member · Accepted solution]

Greg,

Nice. Thanks for the resolution information. The same will go for installations too - these values become 'hardcoded' into respone files that SAPUP/SAPINST will re-read every time. IF you change something, you'd have to start it all from the beginning - a 'reset'.

Remember this 'hardcoding' after the upgrade is complete too. You may want to remove/lockdown the log directories since the password is essentially in plain sight.

Best of luck with your upgrade!

Cheers,

Tim