Upgraded Stopped: START_SHDI_FIRST

[Former Member]

Hi all!

This is our infrastructure:

SAP R/3 4.6B Kernel Version 46D

Oracle 9.2.0.7 (migrated from 0racle 8.1.7)

We are upgrading our QA system to SAP R/3 Enterprise 4.7 Ext. 200 SR1

The upgraded Stopped in the phase: <b>START_SHDI_FIRST</b>

Starting shadow system ...

R3up error message

R3up> SEVERE ERROR: Starting system failed, rc=-1

To analyse errors during start of shadow instance,

View files 'STARTFI.LOG' and 'DEVTRACE.LOG'

in directory 'D:\usr\sap\put\log'

Repeat phase until shadow instance is started

and you can log on instance number '56'

In the prepare decided to assign the number <b>56</b> to the shadow instance.

Here is the STARTFI.LOG:

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

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 = '56', GwService = 'sapgw56'

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="TVK", Nr="56", GwHost="vensapk", GwService="sapgw56"

2 ETQ231 RFC Login failed

4 ETQ359 RFC Login to: System="TVK", Nr="56", GwHost="vensapk", GwService="sapgw56"

2 ETQ231 RFC Login failed

2 ETQ353 Starting system

2EETQ399 Starting shadow instance failed

2EETQ399 Dialogue: SEVERE ERROR

2EETQ399 Starting system failed, rc=-1

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 ("20071105123831")

This is our dev_rfc file:

>TS> Mon Nov 05 16:34:34 2007

T:2388 ======> Connect to SAP gateway failed

Connect_PM DEST=TVK, GWHOST=vensapk, GWSERV=sapgw56, ASHOST=vensapk, SYSNR=56

LOCATION CPIC (TCP/IP) on local host

ERROR partner not reached (host vensapk, service 3356)

TIME Mon Nov 05 16:34:34 2007

RELEASE 620

COMPONENT NI (network interface)

VERSION 36

RC -10

MODULE ninti.c

LINE 976

DETAIL NiPConnect2

SYSTEM CALL SO_ERROR

ERRNO 10061

ERRNO TEXT WSAECONNREFUSED: Connection refused

COUNTER 6

This is part of our C:\WINNT\system32\drivers\etc\services file:

sapmsSHDTVK 3656/tcp #Upgrade shadow instance

sapdp56 3256/tcp #Upgrade shadow instance

sapgw56 3356/tcp #Upgrade shadow instance

We search for the DEVTRACE.LOG file, but it doesn't exists!!

Please some tips.

Best Regards,

Ivonne Villegas

[former_member59864 · Accepted solution]

Check the listener status and R3trans -d, to see if you have a problem with the database connection

[Former Member · Accepted solution]

Hi!

It appears that our Windows Register is corrupted, probably for a disk failure in C. (We have SAP Files usr/sap/* in 😧 and Oracle Datafile in E:)

Did you know how to regenerate the Windows Register? What are the HKey that i have to add. Like - registry keys (for SAP + Oracle)

We can used Windows registers from our Development System (That was upgraded to 4.7) or From our Production System that is still running with SAP 4.6 B / Kernel Release 46D.

In fact if you campare DEV - QA - PRD registers, you can see that in our QA system SAP entry only have a reference to the <SID>

For example:

Development System (Upgraded to 4.7 Etx. 200 SR1):

HKEY_LOCAL_MACHINE -> Software -> SAP ->

Converter

General

ITSConverter

NwSAPSetup

OfficeIntegrator

<SID>

Quality System (the one that we are upgrading to 4.7)

Only have this:

HKEY_LOCAL_MACHINE -> Software -> SAP ->

<SID>

Please some tips about how to recover our windows register only for the SAP / ORACLE parts.

R3trans -d Don't works. So we Started the oracle database (in this moment the oracle service OracleService<SID> is set to manual.. so probably when we do the restart it affect oracle start) We probe again and it works. But the Upgrade fails again in the START_SHDI_FIRST phase.

As a plus... when we so the dev_rfc log. And it gives this:

Connect to SAP gateway failed

Error partner not reached (host vensapk, service 3366 <- 56 is the shadow instance)

Best Regards,

Ivonne Villegas

Message was edited by:

IVONNE VILLEGAS

[former_member204746 · Accepted solution]

for Oracle, it is easier to re-install ORacle software and all patches.

or SAP, it is better to re-install SAP from CD/DVD, do NOT do the DB load. then upgrade your kernel.

[markus_doehr2 · Accepted solution]

> R3trans -d Don't works. So we Started the oracle

> database (in this moment the oracle service

> OracleService<SID> is set to manual.. so probably

> when we do the restart it affect oracle start) We

> probe again and it works. But the Upgrade fails again

> in the START_SHDI_FIRST phase.

so you started the DATABASE.

> As a plus... when we so the dev_rfc log. And it gives

> this:

>

> Connect to SAP gateway failed

> Error partner not reached (host vensapk, service

> 3366 <- 56 is the shadow instance)

Yes - if you only started the database, the system can't connect to the SAP system.

--

Markus

[markus_doehr2]

The developer traces are in

/usr/sap/put/<SID>/homeshd/work

Check dev_disp, dev_w0

--

Markus

[Former Member]

Hi!

This is our <b>dev_disp</b>

-

---

trc file: "dev_disp", trc level: 1, release: "46D"

-

---

Mon Nov 05 14:13:46 2007

relno 4640

patchlevel 0

patchno 2307

intno 0

pid 1652

***LOG Q00=> DpSapEnvInit, DPStart (00 1652) [dpxxdisp.c 921]

Mon Nov 05 14:13:52 2007

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust your DNS settings [dpxxtool2.c 3171]

MtxInit: -2 0 0

DpIPCInit: start server >vensapk_TVK_00 <

MBUF state OFF

MBUF opmode USE

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation std

<ES> Memory Reset enabled as NT default

<EsNT> EsIUnamFileMapInit: Initialize the memory 2952 MB

<ES> 2951 blocks reserved for free list.

ES initialized.

***LOG Q0K=> DpMsAttach, mscon ( vensapk) [dpxxdisp.c 8372]

MBUF set hwid_state to HWID_PENDING

DpStartStopMsg: send start message (myname is >vensapk_TVK_00 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 10000000 for monitoring segment.

CCMS: start to initalize 3.X shared alert area (first segment).

DpMsgAdmin: Set release to 4640, patchlevel 0

MBUF state PREPARED

MBUF component UP

MBUF set hwid_state to SAP_O_K (W0717415045 )

DpMsgAdmin: Set patchno for this platform to 2307

Release check o.K.

Mon Nov 05 14:14:14 2007

MBUF state ACTIVE

Mon Nov 05 16:29:02 2007

DpSigInt: caught signal 2

DpHalt: shutdown server >vensapk_TVK_00 <

Mon Nov 05 16:29:04 2007

DpStartStopMsg: send stop message (myname is >vensapk_TVK_00 <)

DpStartStopMsg: stop msg sent

Mon Nov 05 16:29:05 2007

DpHalt: sync with message server o.k.

detach from message server

***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 8577]

MBUF state OFF

MBUF component DOWN

***LOG Q05=> DpHalt, DPStop ( 1652) [dpxxdisp.c 7255]

<b>And this is our dev_w0</b>

-

---

trc file: "dev_w0", trc level: 1, release: "46D"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, M

*

B

B Mon Nov 05 14:08:45 2007

B create_con (con_name=R/3)

B Loading DB library 'D:\usr\sap\TVK\SYS\exe\run\dboraslib.dll' ...

B Library 'D:\usr\sap\TVK\SYS\exe\run\dboraslib.dll' loaded

B Version of library 'D:\usr\sap\TVK\SYS\exe\run\dboraslib.dll' is "46D.00", patchlevel (0.2238)

B New connection 0 created

M relno 4640

M patchlevel 0

M patchno 2307

M intno 0

M pid 688

M

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 688) [dpxxdisp.c 976]

I MtxInit: -2 0 0

X EmInit: MmSetImplementation( 2 ).

X <ES> client 0 initializing ....

X Using implementation std

M <ES> Memory Reset enabled

X ES initialized.

M ThSysUsrCheck: clear T0

M calling db_connect ...

C Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment

C Logon as OPS$-user to get SAPR3's password

C Connecting as /@TVK on connection 0 ...

C

C Mon Nov 05 14:08:48 2007

C *** ERROR => OCI-call 'olog' failed: rc = 12500

[dboci.c 2460]

C *** ERROR => CONNECT failed with sql error '12500'

[dboci.c 7025]

C Try to connect with default password

C Connecting as SAPR3/<pwd>@TVK on connection 0 ...

C

C Mon Nov 05 14:08:50 2007

C *** ERROR => OCI-call 'olog' failed: rc = 12500

[dboci.c 2460]

C *** ERROR => CONNECT failed with sql error '12500'

[dboci.c 7025]

C Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment

C Logon as OPS$-user to get SAPR3's password

C Connecting as /@TVK on connection 0 ...

C *** ERROR => OCI-call 'olog' failed: rc = 12500

[dboci.c 2460]

C *** ERROR => CONNECT failed with sql error '12500'

[dboci.c 7025]

C Try to connect with default password

C Connecting as SAPR3/<pwd>@TVK on connection 0 ...

C

C Mon Nov 05 14:08:51 2007

C *** ERROR => OCI-call 'olog' failed: rc = 12500

[dboci.c 2460]

C *** ERROR => CONNECT failed with sql error '12500'

[dboci.c 7025]

B ***LOG BY2=> sql error 12500 performing CON [dbsh 0707 ]

B ***LOG BY0=> [dbsh 0707 ]

B ***LOG BY2=> sql error 12500 performing CON [dblink 0627 ]

B ***LOG BY0=> [dblink 0627 ]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1188]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3) [thxxhead.c 8491]

M

M Info for wp 0

M

M stat = 4

M reqtype = 1

M act_reqtype = -1

M tid = -1

M mode = 255

M len = -1

M rq_id = -1

M rq_source = 255

M rq_info = 0

M last_tid = 0

M last_mode = 0

M int_checked_resource = 0

M ext_checked_resource = 0

M report = > <

M action = 0

M tab_name = > <

M

M *****************************************************************************

M *

M * LOCATION SAP-Server vensapk_TVK_00 on host vensapk (wp 0)

M * ERROR tskh_init: db_connect

M *

M * TIME Mon Nov 05 14:08:51 2007

M * RELEASE 46D

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 8602

M * COUNTER 1

M *

M *****************************************************************************

M

M Entering ThSetStatError

M call ThrShutDown (1) ...

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 688) [dpnttool.c 310]

Best Regards,

Ivonne Villegas