Question & Answer
This document addresses the following error that occurs when you attempt to start the DB2® UDB instance: The service has returned a service-specific error code.
This problem can occur if the %DB2PATH%\%DB2INSTANCE%\security\db2audit.cfg file does not exist. It does not matter whether you have enabled auditing or not.
An example of the message you will see when this problem occurs is as follows:
DB2-0 : The service has returned a service-specific error code.
05/31/2006 14:51:51 0 0 SQL1042C An unexpected system error occurred.
SQL1032N No start database manager command was issued. SQLSTATE=57019
The db2diag.log will contain a message similar to the following:
2006-05-31-220.127.116.118000-420 I2471H357 LEVEL: Error
PID : 5272 TID : 5956 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, bsu security, sqlex_read_aud_cfg, probe:20
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
The Windows Application Event log shows:
db2start : SQL1323N An error occurred when accessing the audit configuration file.
To address the problem, recreate db2audit.cfg file:
db2audit configure reset
If the problem still persists, call IBM support for further analysis.
16 June 2018