DB2 FOR LUW / DB2FORLUW / A50 - DB2

If you have a database that meets the following conditions: 
 
- HADR setup with TSA 
- automation has been disabled by running "db2haicu -disable" 
 
Then under certain conditions you could see applications 
receiving SQL1224N errors: 
 
$ db2 connect to sample 
 
   Database Connection Information 
 
 Database server        = DB2/AIX64 10.5.3 
 SQL authorization ID   = DB2INST1 
 Local database alias   = SAMPLE 
 
$ db2 "select count(*) from syscat.tables" 
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 
 
This is caused by the HADR monitor script "hadrV105_monitor.ksh" 
which will under certain conditions look to force off database 
applications. 
 
This issue can be confirmed by checking the syslogs and looking 
for a call to this script: 
/usr/sbin/rsct/sapolicies/db2/forceAllApps. 
 
For example: 
Nov 20 13:07:44 host01 user:notice 
/usr/sbin/rsct/sapolicies/db2/forceAllApps[34603234]: Force 
applid 56722 connected to SAMPLE 
Nov 20 13:07:44 host01 user:notice 
/usr/sbin/rsct/sapolicies/db2/forceAllApps[34603234]: Force 
applid 56748 connected to SAMPLE 
Nov 20 13:07:44 host01 user:notice 
/usr/sbin/rsct/sapolicies/db2/forceAllApps[34603234]: Force 
applid 56761 connected to SAMPLE 
 
Can look to check for this by running the following: 
lsrsrc -s "Name like '%'" IBM.Test Name | grep -c Name 
 
Can then look to clean this up using the following: 
rmrsrc -s "Name like '%'" IBM.Test

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 7 or Later.                 * 
****************************************************************

Re-enable automation via the db2haicu command. If the issue 
persists, delete and re-create the cluster resources by running 
"db2haicu -delete" and re-creating the resources using db2haicu.

First Fixed in DB2 LUW v10.5 Fixpack 7.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.11.2014
20.01.2016
20.01.2016