nstance PWP/DVEBMGS00 [ABAP: STARTING] did not start after 10:00 minutes. G

[Former Member]

Hi,

Iam getting error during solution manager 4.0 CI instance at the stage of START ABAP instance. I have try to restart the server even then it could not work . My memory is 4GB and swap 8GB. I have pasted the the log

<b>ERROR 2006-09-19 18:56:09

CJS-30149 ABAP processes of instance PWE/DVEBMGS00 [ABAP: STARTING] did not start after 10:00 minutes. Giving up.

ERROR 2006-09-19 18:56:09

FCO-00011 The step start with step key |NW_Doublestack_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|10|0|NW_CI_Instance_Start|ind|ind|ind|ind|0|0|start was executed with status ERROR .</b>

Please suggest asap.

- Lisa

[former_member75185]

Hi All,

I also have the same problem with the problem above, what about the error below in 2 log files,

Starting SID/DVEBMGS00 reached state SHUTDOWN after having state STARTING ABAP processes of instance BWD/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:10 minutes. Giving up) It basically means the system failed to start. You should check the logs (dev_w0 and dev_disp) present in the instance "work" directory. /usr/sap/BWD/DVEBMGS00/work

dev_w0 :

Sat Jul 13 02:52:12 2019 M pfinit_clock o.k. max_pfclock_val = 4294967295 Y *** ERROR => MtxOpen PbufAll, using semaphore [dypbuf.c 385] B *** BZ9 LOG => SVERS table does not exist in nametab [dbcrtab 7330] A *** ERROR => Could not read db table SVERS, rc = 32 [sapicc.c 1686] M *** ERROR => ThShMInit: ThrtReadDBVersion [thxxhead.c 3097] M *** ERROR => ThIPCInit: ThShMInit failed, shutdown server [thxxhead.c 2242]

dev_disp :

Sat Jul 13 02:52:04 2019 *** ERROR => DpHdlDeadWp: W3 (pid 33968) edited (severity = 0, status = 65280) [dpxxwp.c 1746] DpTraceWpStatus: child (pid = 33968) exited with exit code 255 *** ERROR => *** *** DpRqNoWpHandle: SHUTDOWN request from wp_id 1 received (reason =?) *** *** [dpxxdisp.c 6085] DpHalt: shutdown server> appbwdev_BWD_00 <(normal) DpModState: change server state from STARTING to SHUTDOWN DPHalt: stop work processes.

what should I do, thank you

S.P

[Former Member]

I have this problem too.

This is my sapinst.log:

INFO 2007-11-29 11:19:19

Connection request to guiengine backend by host 194.29.138.215 .

INFO 2007-11-29 11:19:35

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:19:35

Working directory changed to /db2/sapinst/1.

INFO 2007-11-29 11:19:35

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:19:35

Working directory changed to /db2/sapinst/1.

INFO 2007-11-29 11:19:39

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:19:39

Working directory changed to /db2/sapinst/1.

INFO 2007-11-29 11:19:40

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:19:40

Working directory changed to /db2/sapinst/1.

INFO 2007-11-29 11:19:41

Copied file '/db2/sapinst/1/inifile.xml' to '/db2/sapinst/1/inifile.24.xml'.

INFO 2007-11-29 11:19:41

Copied file '/db2/sapinst/1/inifile.xml' to '/db2/sapinst/1/inifile.25.xml'.

INFO 2007-11-29 11:20:00

Copied file '/db2/sapinst/1/keydb.xml' to '/db2/sapinst/1/keydb.13.xml'.

INFO 2007-11-29 11:20:01

Execute step start of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|1|0.

INFO 2007-11-29 11:20:27

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:20:27

Working directory changed to /db2/sapinst/1.

INFO 2007-11-29 11:20:27

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:20:27

Working directory changed to /db2/sapinst/1.

INFO 2007-11-29 11:20:28

Starting instance QAS/DVEBMGS21...

INFO 2007-11-29 11:20:28

Working directory changed to /tmp/sapinst_exe.26311.1196331543.

INFO 2007-11-29 11:20:28

Working directory changed to /db2/sapinst/1.

WARNING 2007-11-29 11:20:28

Connect to message server (sapqas/3921) failed: NIECONN_REFUSED.

INFO 2007-11-29 11:20:30

Account qasadm already exists.

INFO 2007-11-29 11:20:30

Account 0 already exists.

INFO 2007-11-29 11:20:30

Account 103 already exists.

INFO 2007-11-29 11:20:30

Account 102 already exists.

INFO 2007-11-29 11:20:30

Account 0 already exists.

INFO 2007-11-29 11:20:30

Account 103 already exists.

INFO 2007-11-29 11:20:32

Creating file /db2/sapinst/1/start_QAS_DVEBMGS21.log.

INFO 2007-11-29 11:20:32

Output of /usr/sap/QAS/SYS/exe/run/startsap all DVEBMGS21 sapqas is written to the logfile start_QAS_DVEBMGS21.log.

INFO 2007-11-29 11:21:49

Execution of the command "/usr/sap/QAS/SYS/exe/run/startsap all DVEBMGS21 sapqas" finished with return code 0. Output:

Checking db6 db Database

-

---

ABAP Database is not available via R3trans

Starting SAP-Collector Daemon

-

---

11:20:33 29.11.2007 LOG: Effective User Id is root

***********************************************************************

• This is Saposcol Version COLL 20.90 700 - V3.72 64Bit

• Usage: saposcol -l: Start OS Collector

• saposcol -k: Stop OS Collector

• saposcol -d: OS Collector Dialog Mode

• saposcol -s: OS Collector Status

• The OS Collector (PID 23558) is already running .....

************************************************************************

saposcol already running

Running /usr/sap/QAS/SYS/exe/run/startdb

11/29/2007 11:20:37 0 0 SQL1063N DB2START processing was successful.

SQL1063N DB2START processing was successful.

Database activated

• WARNING Logretain mode is disabled

You will be unable to fully recover your database in case

of a media failure

/usr/sap/QAS/SYS/exe/run/startdb completed successfully

Starting SAP Instance DVEBMGS21

-

---

Startup-Log is written to /home/qasadm/startsap_DVEBMGS21.log

Instance Service on host sapqas started

Instance on host sapqas started

INFO 2007-11-29 11:21:52

Connect to message server (sapqas/3921) succeeded.

INFO 2007-11-29 11:21:52

Disconnect from message server (sapqas/3921) succeeded.

...

...

...

...

...

INFO 2007-11-29 11:30:55

Connect to message server (sapqas/3921) succeeded.

INFO 2007-11-29 11:30:55

Disconnect from message server (sapqas/3921) succeeded.

ERROR 2007-11-29 11:30:58

CJS-30149 ABAP processes of instance QAS/DVEBMGS21 [ABAP: UNKNOWN] did not start after 10:00 minutes. Giving up.

ERROR 2007-11-29 11:31:00

FCO-00011 The step start with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Start|ind|ind|ind|ind|1|0|start was executed with status ERROR .

[former_member185954]

I ran a search for the warning message displayed in the post and found this note:

Although the note is for UNIX,

you can try the changes it suggests and see if that change can fix the issue.

Note 809306 - DB6: startdb fails with DB2 UDB V8.2 on UNIX

Regards,

Siddhesh

[Former Member]

any help

[Former Member]

Hi Lisa,

Please post the sapinst.log (or other relevant logs). All these logs are available in the SAPINST Temp directory.

Regards,

Mike

[Former Member]

hi..

Any solution to this issue, I am getting simillar issue. I thought it is with the message server (internal) port. but still has the same issue.