Question Re: Dispatcher does not start after Refresh database in Technology Q&A

Dispatcher does not start after Refresh database

Maryam_95 — Sat, 20 Jul 2024 12:39:11 GMT

Hi all,

We are currently carrying out System Refresh from Production System to Test system using hana backup and recovery method.

We are currently able to restore & recover the Production backup on Test System. We have tried to restart the database & application .But we are unable to start the SAP application and disp+work is gray.

dev_w0 shows the below logs:

Sat Jul 20 12:39:55:886 2024
*** ERROR => Connect to database failed, rc=1, rcSQL=-10709
[dbhdbsql.cpp 620]
SQLCODE : -10709
SQLERRTEXT : Connection failed (RTE:[89009] Socket connect timeout (60000 ms) (192.168.212.250:21026 -> sappcopy:\
30515))
***LOG R19=> ThDbConnect, db_connect () [thxxtool.c 6114]
ThIErrHandle: in_ThErrHandle: 1
*** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2851]

Info for wp 0

pid = 459367
severity = 0
status = 0
stat = WP_NEW
waiting_for = NO_WAITING
workerType = DP_WORKER_DIAWP
act_cs_count = 0
csTrack = 0
csTrackRwExcl = 0
csTrackRwShrd = 0
mode_cleaned_counter = 0
control_flag = 0x1200000
report = > <
action = 0
tab_name = > <

ThIErrHandle: no current incoming request

Entering TH_CALLHOOKS
ThCallHooks: call hooks for event BEFORE_DUMP
ThIErrHandle: entering PfStatReset
ThIErrHandle: Entering DpRecoverMtxAfterProcessCrash
DpRecoverMtxAfterProcessCrash: recover mutex after crash of W0
ThIErrHandle: DpRecoverMtxAfterProcessCrash o.k.
ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

***
*** work process W0 died => ThInit: db_connect
call ThrShutDown (1)...
SigISetIgnoreAction : SIG_IGN for signal SIGUSR1
SigISetIgnoreAction : SIG_IGN for signal SIGUSR2
EnqWorkProcess: Initializing enqueue client
***LOG Q02=> wp_halt2, halt wp () [dpuxtool.c 335]

Can you please help us on how to resolve this error?

I must add that after system rename(Changes the SAP system ID), the problem is solved and the application server starts. But we want to solve the problem without changing the system sid.

Your help in this regard will be highly appreciated.

With regards,

Maryam

Re: Dispatcher does not start after Refresh database

HakanHaslaman — Tue, 23 Jul 2024 10:27:31 GMT

The dispatcher can't connect to the database due to possible network issues, wrong database parameters, or a non-running database service.

To troubleshoot, please check below:
1. Verify network connectivity between application and database servers.
2. Confirm the database service is running.
3. Check the SAP profile's database parameters for accuracy.
4. Review database logs for errors.
5. Examine SAP startup logs for errors.

Re: Dispatcher does not start after Refresh database

qwertie — Tue, 23 Jul 2024 12:34:18 GMT

check your hdbuserstore keys. like Hakan mentioned, you can not connect to your database (shows up in your logfile)

Re: Dispatcher does not start after Refresh database

Maryam_95 — Wed, 24 Jul 2024 06:17:41 GMT

Thank you for your answer. The database and application server are on the same host and we checked with Hana Studio and all the database services are running.

We added the details of the host of the reproduction system that we backed up here, to etc/hosts file, and the following error was generated in dev_w0:

*** ERROR => Connect to database failed, rc=1, rcSQL=-10709 [dbhdbsql.cpp 620]

SQLCODE: -10709 S

QLERRTEXT : Connection failed (RTE:[89009] Socket connect timeout (60000 ms) (192.168.212.250:60650 -> sappcopy:\ 30515))

M ***LOG R19=> ThDbConnect, db_connect () [thxxtool.c 6114] M ThIErrHandle: in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2851]

Our test and production machines are not connect to each other and are not in the same network. Could this be the problem?

Re: Dispatcher does not start after Refresh database

HakanHaslaman — Wed, 24 Jul 2024 06:31:57 GMT

Yes, possible issue: test and production machines aren't on the same network, causing a database connection timeout. This could be due to network issues, firewall settings, or incorrect configuration.

For Troubleshooting, please check below:
1. Verify network connectivity by pinging the database server from the application server.
2. Check firewall settings on both servers to ensure necessary port communication.
3. Confirm database is configured to accept connections from the application server, including database listener configuration and SAP profile parameters.
4. Ensure the database service is running and listening on the correct port.
5. Verify the SAP profile on the application server is correctly configured.

Re: Dispatcher does not start after Refresh database

Maryam_95 — Wed, 24 Jul 2024 07:56:08 GMT

Thank you rsnit; I'll check hdbuserstore keys.

Re: Dispatcher does not start after Refresh database

qwertie — Wed, 24 Jul 2024 10:50:41 GMT

furthermore maybe you can check and post the output of the following (sidadm user)

hdbsql -U DEFAULT

and

R3trans -d