IBM Support

SQL1224N error during restore even after dropping the old database

Troubleshooting


Problem

After dropping the old database, restoring a backup image might hit the following error:

SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032

Symptom

SQL1224N error during restore even after dropping the old database

Cause

Corrupt audit log files preventing the restore

Environment

Database being restored after dropping the previous one

Diagnosing The Problem

The following entries are written to db2diag.log during the restore attempt:

2025-07-22-17.39.07.396730-180 I18667A534 LEVEL: Error
PID : 19006704 TID : 1400512 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-23103 APPID: *LOCAL.db2inst1.250726220400
HOSTNAME: localhost
EDUID : 1400512 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, bsu security, sqlexAuditBufferManager::finalizeBuffer, probe:196
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
"Unexpected System Error"

2025-07-22-17.39.07.396988-180 I19202A942 LEVEL: Error
PID : 19006704 TID : 1400512 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-23103 APPID: *LOCAL.db2inst1.250726220400
HOSTNAME: localhost
EDUID : 1400512 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, bsu security, sqlexAuditData::logEvent, probe:1111
MESSAGE : ZRC=0x875C00CD=-2024013619=SQLEX_UNEXPECTED_SYSERR
"Unexpected System Error"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1042 sqlerrml: 3
sqlerrmc: 205
sqlerrp : SQLEXADT
sqlerrd : (1) 0x875C00CD (2) 0x000000CD (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

These messages indicates the audit logs are corrupted. Run db2audit describe to check whether the audit log paths exists and are valid, for instance:

DB2 AUDIT SETTINGS:

Audit active: "TRUE "

Log audit events: "BOTH"

Log checking events: "FAILURE"

Log object maintenance events: "BOTH"

Log security maintenance events: "BOTH"

Log system administrator events: "BOTH"

Log validate events: "BOTH"

Log context events: "NONE"

Return SQLCA on audit error: "TRUE "

Audit Data Path: "/db2/work/db2inst1/scripts/audit/data/"

Audit Archive Path: "/db2/work/db2inst1/scripts/audit/archive/"

Resolving The Problem

Delete the logs from the paths outlined on db2audit describe command related to the database being restored and try the restore again.

Related Information

db2audit command

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PmdAAE","label":"Recovery-\u003ERestore"}],"ARM Case Number":"TS019859117","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1.0;10.5.0;11.1.0;11.5.0;11.5.1;11.5.2;11.5.3;11.5.4;11.5.5;11.5.6;11.5.7;11.5.8;11.5.9;12.1.0;12.1.1;12.1.2;12.1.3;8.2.0;9.1.0;9.5.0;9.7.0;9.8.0"}]

Document Information

Modified date:
26 November 2025

UID

ibm17252507

Page Feedback