Skip to Content
author's profile photo Former Member
Former Member

Disp+Work was stopped immediately after startsap

Hi,

I have a problem about start sap. I have doing system copy by Backup/Restore on different SID and used old schema ID now in step import and startsap then disp+work was stopped automatically after start sap.

My environment:

Solaris 10

SAP netweaver 6.40 ECC 5.0

Oracle 9

Please you help me to solve this problem.

logs dev_disp

---------------------------------------------------

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

---------------------------------------------------

Tue Sep 30 13:51:16 2014

kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)

length of sys_adm_ext is 312 bytes

systemid 370 (SUN on SPARC CPU with Solaris 2.2)

relno 6400

patchlevel 0

patchno 43

intno 20020600

make: single threaded, ASCII, 64 bit

pid 27744

***LOG Q00=> DpSapEnvInit, DPStart (10 27744) [dpxxdisp.c 1100]

shared lib "dw_xml.so" version 43 successfully loaded

shared lib "dw_xtc.so" version 43 successfully loaded

shared lib "dw_stl.so" version 43 successfully loaded

shared lib "dw_gui.so" version 43 successfully loaded

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: JAVA is not active

DpShMCreate: sizeof(wp_adm) 6848 (856)

DpShMCreate: sizeof(tm_adm) 2852592 (14192)

DpShMCreate: sizeof(wp_ca_adm) 26400 (88)

DpShMCreate: sizeof(appc_ca_adm) 8800 (88)

DpShMCreate: sizeof(comm_adm) 216000 (432)

DpShMCreate: sizeof(vmc_adm) 0 (432)

DpShMCreate: sizeof(wall_adm) (22440/36712/80/104)

DpShMCreate: SHM_DP_ADM_KEY (addr: ffffffff73800000, size: 3176280)

DpShMCreate: allocated sys_adm at ffffffff73800000

DpShMCreate: allocated wp_adm at ffffffff73801898

DpShMCreate: allocated tm_adm_list at ffffffff73803358

DpShMCreate: allocated tm_adm at ffffffff73803380

DpShMCreate: allocated wp_ca_adm at ffffffff73abba70

DpShMCreate: allocated appc_ca_adm at ffffffff73ac2190

DpShMCreate: allocated comm_adm_list at ffffffff73ac43f0

DpShMCreate: allocated comm_adm at ffffffff73ac4408

DpShMCreate: allocated vmc_adm_list at ffffffff73af8fc8

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at ffffffff73af8ff0

DpShMCreate: allocated wall_adm at ffffffff73af8ff8

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation std

EsIUnamFileMapInit: ES base = 0xfffffffe70000000

EsStdInit: Extended Memory 4092 MB allocated

<ES> 1022 blocks reserved for free list.

ES initialized.

Tue Sep 30 13:51:55 2014

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( hristmp) [dpxxdisp.c 9736]

Tue Sep 30 13:51:56 2014

*** ERROR => W0 (pid 27749) died [dpxxdisp.c 12187]

DpMsgAdmin: Set release to 6400, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]

DpMsgAdmin: Set patchno for this platform to 43

Release check o.K.

*** ERROR => W0 (pid 27749) died [dpxxdisp.c 12187]

*** ERROR => W2 (pid 27751) died [dpxxdisp.c 12187]

my types changed after wp death/restart 0xbf --> 0xbd

*** ERROR => W3 (pid 27752) died [dpxxdisp.c 12187]

my types changed after wp death/restart 0xbd --> 0xb9

*** ERROR => W4 (pid 27753) died [dpxxdisp.c 12187]

Tue Sep 30 13:52:15 2014

*** ERROR => W1 (pid 27750) died [dpxxdisp.c 12187]

my types changed after wp death/restart 0xb9 --> 0xb8

*** ERROR => W5 (pid 27756) died [dpxxdisp.c 12187]

my types changed after wp death/restart 0xb8 --> 0xb0

*** ERROR => W6 (pid 27757) died [dpxxdisp.c 12187]

my types changed after wp death/restart 0xb0 --> 0xa0

*** ERROR => W7 (pid 27808) died [dpxxdisp.c 12187]

my types changed after wp death/restart 0xa0 --> 0x80

*** DP_FATAL_ERROR => DpWPCheck: no more work processes

*** DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

killing W0-27749 (SIGUSR2)

*** ERROR => DpWpKill(27749, SIGUSR2) failed [dpxxtool.c 2468]

killing W1-27750 (SIGUSR2)

*** ERROR => DpWpKill(27750, SIGUSR2) failed [dpxxtool.c 2468]

killing W2-27751 (SIGUSR2)

*** ERROR => DpWpKill(27751, SIGUSR2) failed [dpxxtool.c 2468]

killing W3-27752 (SIGUSR2)

*** ERROR => DpWpKill(27752, SIGUSR2) failed [dpxxtool.c 2468]

killing W4-27753 (SIGUSR2)

*** ERROR => DpWpKill(27753, SIGUSR2) failed [dpxxtool.c 2468]

killing W5-27756 (SIGUSR2)

*** ERROR => DpWpKill(27756, SIGUSR2) failed [dpxxtool.c 2468]

killing W6-27757 (SIGUSR2)

*** ERROR => DpWpKill(27757, SIGUSR2) failed [dpxxtool.c 2468]

killing W7-27808 (SIGUSR2)

*** ERROR => DpWpKill(27808, SIGUSR2) failed [dpxxtool.c 2468]

NiWait: sleep (10000 msecs) ...

NiISelect: timeout 10000 ms

NiISelect: maximum fd=14

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Regards,

P.Pholvises

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    Posted on Sep 30, 2014 at 11:01 AM

    Hi Peeravat,

    Is the source system kernel and the target system kernel are same?

    if not , then try to replace the target system kernel with the source system kernel.

    As the patch level of your kernel is only 43 for 640 which is lower itself.

    Also do paste the trans.log after running R3trans -d

    With Regards

    Ashutosh Chaturvedi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 30, 2014 at 10:13 AM

    Hello,

    typical reason of immediate death of work processes could be full file system or not enough memory. Have a look on this thread please: http://scn.sap.com/thread/1369854

    Maybe can you add here the content (last 100-200 rows should be enough) of dev_w0 file?

    Kind regards

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 30, 2014 at 10:18 AM

    Hi,

    Please upload dev_w0 logs and share r3trans -d trans.log.

    Regards,

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 30, 2014 at 10:41 AM

    Hi

    I thing your kernel & DBSL patch level are low you can upgrade the kernel and then check the same.

    (Your source & target kernel not same)

    BR

    SS

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 30, 2014 at 11:18 AM

    If possible attach the complete dev_w0 trace file.

    Run sappfpar against the instant profile and check for errors and if there are correct them and restart the SAP system.

    Also provide the SAP kernel version and patch level.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.