AHD50050:DB confirmation failed. Reason: AHD50060:Database check FAILED

[Jordan Reich]

Situation:

CA SDM Production (Advanced Availability)

CA SDM Test Environment (Conventional)

 

Wanted to update the test environment with an updated version of the production MDB database. We did a backup of MDB on production and transferred that database over to test and restored. This process completed without any issue.

 

Ran pdm_configure on an administrative launch of command prompt. The process completed ALL steps successfully with the exception of restarting the CA Service Desk Manager service. This resulted in a failure. 

 

Log (STDLOG):

02/23 15:18:29.24 WTDHSWEBL18 key_prov_nxd 4384 SIGNIFICANT key_prov.c 193 STARTUP of key_prov_nxd
02/23 15:18:29.25 WTDHSWEBL18 sql_prov_nxd 400 SIGNIFICANT sql_prov.c 213 Started up SQL Server provider NAME=_prov DATABASE=mdb
02/23 15:18:29.26 WTDHSWEBL18 proctor_WTDHSWEBL 10896 SIGNIFICANT pdm_process.c 927 Process stopped (C:/PROGRA~2/CA/SERVIC~1/bin/ddict_rd -t return: 0
02/23 15:18:29.26 WTDHSWEBL18 proctor_WTDHSWEBL 10896 SIGNIFICANT pdm_process.c 936 Stopped: C:/PROGRA~2/CA/SERVIC~1/bin/ddict_rd -t
02/23 15:18:29.41 WTDHSWEBL18 sqlagt:Default 8776 SIGNIFICANT sql_agent.c 245 STARTUP of sql_agent:mdb:key_prov_nxd:Default
02/23 15:18:29.52 WTDHSWEBL18 confirm_db 8664 SIGNIFICANT ntservice.c 311 Command return non-zero exit code. Command: redirect -m "C:\Windows\TEMP\tmp290" "C:\Windows\TEMP\tmp291" "C:/PROGRA~2/CA/SERVIC~1/bin/sql_check_db" -c -s WTDHSWEBL18 >"C:\Windows\TEMP\tmp290" 2> "C:\Windows\TEMP\tmp291" . Exit Code: 10
02/23 15:18:29.60 WTDHSWEBL18 pdm_proctor_nxd 8696 SIGNIFICANT STDIO 0 AHD50050:DB confirmation failed. Reason: AHD50060:Database check FAILED.
02/23 15:18:29.60 WTDHSWEBL18 pdm_proctor_nxd 8696 SIGNIFICANT STDIO 0 AHD50051:Server shutdown requested.
02/23 15:18:29.60 WTDHSWEBL18 confirm_db 8664 SIGNIFICANT api_misc.c 585 Requesting shutdown of system. Reason (AHD50060:Database check FAILED. )
02/23 15:18:29.61 WTDHSWEBL18 slump_nxd 10296 EXIT server.c 2844 Slump_nxd was requested to shutdown. Check Prior log information.
02/23 15:18:29.61 WTDHSWEBL18 sql_prov_nxd 400 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.61 WTDHSWEBL18 spelsrvr:hw 5388 EXIT spel_srvr.c 219 Slump died detected
02/23 15:18:29.61 WTDHSWEBL18 bopauth_nxd 8772 EXIT bopauth.c 158 Slump died detected
02/23 15:18:29.61 WTDHSWEBL18 pdm_mail_nxd 10444 SIGNIFICANT pdm_mail_nxd.c 745 Detected disconnect from slump server. Shutting down...
02/23 15:18:29.61 WTDHSWEBL18 sqlagt:Default 8776 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.61 WTDHSWEBL18 web:wsp 10716 EXIT webengine.c 1170 Slump died detected
02/23 15:18:29.61 WTDHSWEBL18 key_prov_nxd 4384 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.61 WTDHSWEBL18 boplgin 10152 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.61 WTDHSWEBL18 lexagt 9636 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.62 WTDHSWEBL18 pdm_export_mgr 10736 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.62 WTDHSWEBL18 pdm_ver_nxd 10408 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.62 WTDHSWEBL18 web:local 9364 EXIT webengine.c 1170 Slump died detected
02/23 15:18:29.62 WTDHSWEBL18 mdb_registration_ 10652 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.62 WTDHSWEBL18 spelsrvr 10332 EXIT spel_srvr.c 219 Slump died detected
02/23 15:18:29.62 WTDHSWEBL18 pcrpt_nxd 9828 EXIT pcreport.c 1236 Slump died detected
02/23 15:18:29.62 WTDHSWEBL18 sql_prov_nxd 400 SIGNIFICANT sql_prov.c 165 Exiting provider
02/23 15:18:29.61 WTDHSWEBL18 pdm_d_mgr 8696 EXIT api.c 1760 Exiting because slump server terminated!
02/23 15:18:29.62 WTDHSWEBL18 spelsrvr:hw 5388 SIGNIFICANT miscos.c 189 Exiting normally
02/23 15:18:29.63 WTDHSWEBL18 pdm_mail_nxd 10444 SIGNIFICANT pdm_mail_nxd.c 758 Shutdown of pdm_mail_nxd successful
02/23 15:18:29.67 WTDHSWEBL18 spelsrvr 10332 SIGNIFICANT miscos.c 189 Exiting normally
02/23 15:18:29.68 WTDHSWEBL18 sql_prov_nxd 400 SIGNIFICANT key_stuff.c 1389 Shutting down key agent
02/23 15:18:29.77 WTDHSWEBL18 proctor_WTDHSWEBL 10896 SIGNIFICANT api.c 1748 Slump server terminated!

 

Log (JSTD):

02/23 03:26:32.826[Thread-4] ERROR SLUMP 547 Can't logon to slump - check server daemons: java.io.IOException: java.net.ConnectException: Connection refused: connect 

 

Appreciate your help!

[Gordon Preston]

Hi Jordan,

 

If you run 'sql_check_db -c -s WTDHSWEBL18' on the Service Desk server, what does it return ?

 

Regards,

Gordon 

[Jordan Reich]

Command ran. Output:

[Gordon Preston]

Check the dlgtsrv table in the mdb and make sure that the entry matches your current (test) server. You may need to manually update the row in the table to reflect the test server name.

 

Regards,

Gordon 

[Jordan Reich]

The following was found in dlgtsrv:

id         del        sym      nx_desc server   metafile transport           default_assignee            appl_addr         password            default_userid    anon_userid

1          0          WPDHSAPPL28   Local System (WPDHSAPPL28)     WPDHSWEBL35  NULL    9100     NULL    NULL    NULL            NULL    NULL

Edited the following:

Adjusted WPDHSWEBL35 to the test server value of WTDHSWEBL18

 

Outcome:

Task status still failed ...

 

Logs:

02/23 04:26:47.859[Thread-4] ERROR SLUMP 547 Can't logon to slump - check server daemons: java.io.IOException: java.net.ConnectException: Connection refused: connect

 

02/23 16:22:38.88 WTDHSWEBL18 confirm_db 1812 SIGNIFICANT api_misc.c 585 Requesting shutdown of system. Reason (AHD50060:Database check FAILED. )

02/23 16:22:38.88 WTDHSWEBL18 slump_nxd 10336 EXIT server.c 2844 Slump_nxd was requested to shutdown. Check Prior log information.

[Gordon Preston]

You may also need to check and update the entry in the usp_servers table for the primary/BG server.

 

Regards,

Gordon.

[Jordan Reich]

Solution update:

1. Restored the production database

2. Restored the usp_servers and dlgtsrv tables from the old test environment onto the new production database restore.

3. Ran pdm_configure

This resolved the problem. The test environment on the updated database is now functioning correctly. 

 

Thanks!