Quantcast
Channel: SCN : Popular Discussions - SAP MaxDB
Viewing all articles
Browse latest Browse all 1545

DB-Connect Failed, Return Code 008192

$
0
0

Hello,

 

I changed the hostname of our SAP System (not productiv). When I'm trying to start SAP the following message appears in the syslog:

 

SAP Basis System: Initialization           DB-Connect Failed, Return Code  008192

SAP Basis System: Initialization           DB-Connect Failed, Return Code  008192

 

The database is on the same host and running. Before I tried to start SAP I changed all the three profiles (start, default, etc.).

I "reregistered" the SAP Services and I also read SAPNote 8307.

 

Here is also a part of the dev_trace.

 

Mon Oct 19 13:51:48 2009

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( moritz47) [dpxxdisp.c   10467]

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

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

CCMS: Checking Downtime Configuration of Monitoring Segment.

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

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 247

Release check o.K.

 

Mon Oct 19 13:52:28 2009

      • ERROR => W0 (pid 1804) died [dpxxdisp.c   13050]

      • ERROR => W1 (pid 704) died [dpxxdisp.c   13050]

      • ERROR => W2 (pid 1752) died [dpxxdisp.c   13050]

      • ERROR => W3 (pid 492) died [dpxxdisp.c   13050]

      • ERROR => W4 (pid 624) died [dpxxdisp.c   13050]

      • ERROR => W5 (pid 1800) died [dpxxdisp.c   13050]

      • ERROR => W6 (pid 3472) died [dpxxdisp.c   13050]

      • ERROR => W7 (pid 4052) died [dpxxdisp.c   13050]

      • ERROR => W8 (pid 1860) died [dpxxdisp.c   13050]

      • ERROR => W9 (pid 3620) died [dpxxdisp.c   13050]

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

      • ERROR => W10 (pid 3240) died [dpxxdisp.c   13050]

      • ERROR => W11 (pid 1912) died [dpxxdisp.c   13050]

my types changed after wp death/restart 0xbe --> 0xbc

      • ERROR => W12 (pid 1904) died [dpxxdisp.c   13050]

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

      • ERROR => W13 (pid 1592) died [dpxxdisp.c   13050]

      • ERROR => W14 (pid 2692) died [dpxxdisp.c   13050]

      • ERROR => W15 (pid 1208) died [dpxxdisp.c   13050]

      • ERROR => W16 (pid 1588) died [dpxxdisp.c   13050]

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

      • ERROR => W17 (pid 2352) died [dpxxdisp.c   13050]

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

      • ERROR => W18 (pid 1664) died [dpxxdisp.c   13050]

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-1804 (SIGUSR2)

      • ERROR => DpWpKill(1804, SIGUSR2) failed [dpxxtool.c   2508]

killing W1-704 (SIGUSR2)

      • ERROR => DpWpKill(704, SIGUSR2) failed [dpxxtool.c   2508]

killing W2-1752 (SIGUSR2)

      • ERROR => DpWpKill(1752, SIGUSR2) failed [dpxxtool.c   2508]

killing W3-492 (SIGUSR2)

      • ERROR => DpWpKill(492, SIGUSR2) failed [dpxxtool.c   2508]

killing W4-624 (SIGUSR2)

      • ERROR => DpWpKill(624, SIGUSR2) failed [dpxxtool.c   2508]

killing W5-1800 (SIGUSR2)

      • ERROR => DpWpKill(1800, SIGUSR2) failed [dpxxtool.c   2508]

killing W6-3472 (SIGUSR2)

      • ERROR => DpWpKill(3472, SIGUSR2) failed [dpxxtool.c   2508]

killing W7-4052 (SIGUSR2)

      • ERROR => DpWpKill(4052, SIGUSR2) failed [dpxxtool.c   2508]

killing W8-1860 (SIGUSR2)

      • ERROR => DpWpKill(1860, SIGUSR2) failed [dpxxtool.c   2508]

killing W9-3620 (SIGUSR2)

      • ERROR => DpWpKill(3620, SIGUSR2) failed [dpxxtool.c   2508]

killing W10-3240 (SIGUSR2)

      • ERROR => DpWpKill(3240, SIGUSR2) failed [dpxxtool.c   2508]

killing W11-1912 (SIGUSR2)

      • ERROR => DpWpKill(1912, SIGUSR2) failed [dpxxtool.c   2508]

killing W12-1904 (SIGUSR2)

      • ERROR => DpWpKill(1904, SIGUSR2) failed [dpxxtool.c   2508]

killing W13-1592 (SIGUSR2)

      • ERROR => DpWpKill(1592, SIGUSR2) failed [dpxxtool.c   2508]

killing W14-2692 (SIGUSR2)

      • ERROR => DpWpKill(2692, SIGUSR2) failed [dpxxtool.c   2508]

killing W15-1208 (SIGUSR2)

      • ERROR => DpWpKill(1208, SIGUSR2) failed [dpxxtool.c   2508]

killing W16-1588 (SIGUSR2)

      • ERROR => DpWpKill(1588, SIGUSR2) failed [dpxxtool.c   2508]

killing W17-2352 (SIGUSR2)

      • ERROR => DpWpKill(2352, SIGUSR2) failed [dpxxtool.c   2508]

killing W18-1664 (SIGUSR2)

      • ERROR => DpWpKill(1664, SIGUSR2) failed [dpxxtool.c   2508]

NiWait: sleep (10000 msecs) ...

NiISelect: timeout 10000 ms

NiISelect: maximum fd=1549

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Mon Oct 19 13:52:38 2009

NiISelect: TIMEOUT occured (10000 ms)

dump system status

 

Thank you.

 

Regards

Stephan


Viewing all articles
Browse latest Browse all 1545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>