cancel
Showing results for 
Search instead for 
Did you mean: 

INSTANCE NOT STARTING AFTER SHUTDOWN

shoyab9135
Participant
0 Kudos
840

Hello Team,

i have an issue of my sap IDS when i stop the application from OS level it stop the application but when i trying to start the Application from OS level it was starting but it not connecting to application.

when i run :- sapcontrol -nr 00 -function GetProcessList

the output:- GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid disp+work, Dispatcher, GRAY, Stopped, , , 9744 igswd_mt, IGS Watchdog, GREEN, Running, 2019 10 12 11:21:14, 0:42:40, 9745

Does someone know whats happening please? I copy dev_w0 and dev_disp files below.

dev_disp

DpHalt: waiting for termination of 12 work processes (e.g. W0) ... Sat Oct 12 11:22:56:401 2019 *** ERROR => DpHalt: W0 (pid 9765) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W1 (pid 9766) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W3 (pid 9768) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W4 (pid 9769) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W6 (pid 9771) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W7 (pid 9772) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W8 (pid 9773) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W9 (pid 9774) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W10 (pid 9775) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W11 (pid 9776) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W12 (pid 9777) still alive ... [dpInit.c 3399] *** ERROR => DpHalt: W16 (pid 9781) still alive ... [dpInit.c 3399] DpHalt: waiting for termination of 12 work processes (e.g. W0) ...

dev_w0

*** ERROR => ThrInitServInfo: MtxOpen failed (7) [thxxrun1.c 298] M *** ERROR => ThrExclusiveInitRunTime: ThrInitServInfo failed (-1) [thxxrun1.c 234] M *** ERROR => ThrExclusiveInitRunTime failed (-1) [thxxext.c 686] M *** ERROR => ThShMInit: ThExclusiveStartUp failed (-1) [thxxhead.c 1844] M *** ERROosR => ThIPCInit: ThShMInit failed, shutdown server [thxxhead.c 1621] M si_code = -6 M Sending process ID = 9765 M Real user ID of sending process = 1001

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Hi Shoyab,

Upon checking the logs so shared, I came across with the below peice.

C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 6181]
C  (30294) [HY000] [SAP][ASE ODBC Driver]There is no server listening at IDES:4901.
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 6181]
C  (30012) [08001] [SAP][ASE ODBC Driver]Client unable to establish a connection
C  syb_glob.dbsl_ca.errclass set to DBSL_EC_RESTART
C  Connection 0 failed using DRIVER={Adaptive Server Enterprise};server=IDES;port=4901;uid=SAPSR3;db=IDS;pwd=xxxxxxxxxxx;TextSize=2147483647;CRC=0;FetchArraySize=1000;ReleaseLocksOnCursorClose=1;DynamicPrepare=1;QuotedIdentifier=1;UseCursor=2;homogeneousbatch=1;charset=utf8;EncryptPassword=1;EnableLOBLocator=0;app=R3D000 00 comm rd ODBC;logintimeout=3;ProtocolCapture=cap_w0_comm_rd;supresstdscontroltokens=1;SuppressRowFormat=1;SuppressParamFormat=1;
C  
B  ***LOG BV3=> severe db error 30012; work process is stopped [dbsh         1258]
B  ***LOG BY2=> sql error 30012  performing CON [dblink       644]
B  ***LOG BY0=> [ASE Error SQL30294:HY000][SAP][ASE ODBC Driver]There is no server listening at IDES:4901. [dblink       644]
M  ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 86]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c   2609]

It mainly indicates that the SAP Application is unable to connect with the ASE DB. This can happen due to some issues with the DB Client so installed. Can you please check 2768106 - Setup of remote db monitoring for SAP Sybase ASE (SAP Note 1532253) getting errors - ASE BS

Regards,

Prateek

S_Sriram
Active Contributor
0 Kudos

Hi Shoyab.

From the dev_w01 log all the workporcess are not connecting to DB error message " ASE ODBC Driver]There is no server listening at IDES:4901."

1. At OS level you have to check the DB status is it started or not? refer the SAP note link

https://launchpad.support.sap.com/#/notes/2511564

2. Check the DNS resolutions,

Regards

0 Kudos

Hi Shoyab,

Ensure that all the SAP services are stopped on the host including sapstartsrv and you clean the shared memory as well using "cleanipc $$ remove" [$$ being the instance number].

Even after doing this if you are still unable to restart the services properly. Check if the following works.

Logon to the host as <sid>adm

1. stop the SAP services using the regular stopsap r3 commands.

2. stop the sapstartsrv services of the SID using stopsap sapstartsrv. If this still does not work, kill the service (kill -9 <process id>)

3. perform cleanipc $$ remove [$$ being the instance number]. Crosscheck the same by doing "cleanipc $$ show" or "ipcs | grep <sid>adm". this command should not return any output, if it does you should clean the same by "ipcrm -s <semaphore ID from the above output>". Repeat the same till you get rid of all the stale semaphores.

4. get rid of all the socket files so created by the SAP Services.

cd /tmp

ls -ltr | sort -k 3 | grep <sid>adm

rm -rf "all the .sapstream files"

5. start the SAP services using the regular sapstart r3 commands.

Hope this thorough cleanup helps you solve the issue.

Regards

Prateek

shoyab9135
Participant
0 Kudos

Hi Prateek.

yes i have tried but same as before noting happens.

please have a look of previous comment of S Sriram. i have attached txt files dev_w0 and dev_disp hope that will help me.

S_Sriram
Active Contributor
0 Kudos

Hi Shoyab.

Could you attach the both logs as test format?

Regards

SS

shoyab9135
Participant
0 Kudos

Hello S Sriram.

yes i will attach the both logs here it is.dev-w01.txtdev-disp01.txt