cancel
Showing results for 
Search instead for 
Did you mean: 

NW04s Upgrade Error during Shadow Instance started

Former Member
0 Kudos

Hi @all,

i hope you can help me. During a NW04s Upgrade (with EP6.0 on Windows 32BIT 2003 Server SP1 DB= MS SQL2000 SP4) appears the error, that the shadow instance doesn't start. Following appears in dev_disp:

trc file: "dev_disp", trc level: 1, release: "700"

-


sysno 02

sid DEV

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 80

intno 20050900

make: multithreaded, ASCII, optimized

pid 4520

Sun Jan 14 20:02:05 2007

kernel runs with dp version 217(ext=109) (@(#) DPLIB-INT-VERSION-217)

length of sys_adm_ext is 360 bytes

      • SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (02 4520) [dpxxdisp.c 1239]

shared lib "dw_xml.dll" version 80 successfully loaded

shared lib "dw_xtc.dll" version 80 successfully loaded

shared lib "dw_stl.dll" version 80 successfully loaded

shared lib "dw_gui.dll" version 80 successfully loaded

shared lib "dw_mdm.dll" version 80 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

Sun Jan 14 20:02:10 2007

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

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

MtxInit: 30000 0 0

      • ERROR => DpSysAdmExtCreate: ShmCreate (CREATE) [dpxxtool2.c 607]

      • ERROR => dispatcher already running ???? [dpxxtool2.c 608]

      • ERROR => I better EXIT before I do any (more) damage [dpxxtool2.c 610]

I have change some parametes as ipc_memory, but it doesn't work. Have anyone a idea?

Thanks

Martin

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Martin,

as per the trace file, it talks about DNS of the Server. if you are using the concept of Clustering, i guess this problem arises.

please look into ‘STARTSFI.LOG’ & ‘DEVTRACE.LOG’ for the error details. and try remote log on, using the RFC connection,

"SAP_UPGRADE_SHADOW_SYSTEM". check whtr instance number is correctly mentioned &

check whtr the following actions are done already.

• You have to login as root and enter: the shadow dispatcher instance sapdp<shadow instance number> in /etc/services with number 32<insance number>

• Please create the user for the shadow instance by executing

SQL script crshdusr.sql. [which is available in “/DEPOT” directory].

try to create a copy of START_DVEBMGS<instance no>_<hostname> with name START_DVEBMGS<instance_no>.

and try starting it manually.

Stopping Shadow instance

cd /usr/sap/put

cd bin

R3up stopshd

Enter the path of your upgrade directory [/usr/sap/put]:

Upgrade directory = /usr/sap/put

Starting Shadow instance

R3up startshd

Enter the path of your upgrade directory [/usr/sap/put]:

Upgrade directory = /usr/sap/put

with br,

Raj.

please go thru this link.

<i>award suitable points</i>

Former Member
0 Kudos

Hi Rajesh,

and thanks for your reply. I think you doesn't understand my question. This error appears during the Upgradephase. Prepare runs without an error.

I start the shadow instance with SAPUp.exe startshd. But the dispatcher can be allokated enough memory.

(* ERROR => DpSysAdmExtCreate: ShmCreate (CREATE) [dpxxtool2.c 607])

I have looked if another dispatcher run on port 3602, but the is nothing (with netstat -na | find "3602"

Now I lose one's patience and I create a OSS Message

When I have a solution I will post that here.

Greets

Martin

Message was edited by:

Martin vom Bruch

Former Member
0 Kudos

HI,

I am upgrading BI 3.5 to 7.0 and i am facing error.

Where a bg job is not running. Bg job is scheduled but not executed.

I have oppened the connections to SAP.

and the reply from SAP is:

<b>Can you setup a remote connection to your shadow instance as there is

not enough information in your system.

BATCHJOB RSUPGCUAGEN111 is scheduled but is not released in your system

and the cause of this may be available in Shadow instance.</b>

!) how can i setup remote connection to your shadow instance?

2) Do i have to run any commands?

3) As i see MMC in the shadow Instance, Message server is running but dispatcher is stopped?

Regards,

Mag.

Former Member
0 Kudos

Hi,

I am facing the same issue, could you please help me on this topic?

Thanks

Former Member
0 Kudos

Hi Magham,

In MMC you can find the instance number of the shadow instance.

Update the same to SAP, and also don't forget to add the entries in SAP route tab file.

Regards,

Kiran Madhu