DB2 - Problem description
Problem IC71554 | Status: Closed |
TRAP IN SQLEINTERRUPTAPPLICATION DURING DATABASE DEACTIVATION AFTER DB MARKED BAD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
In a DPF environment, if a database is marked bad due to some issue, DB2 will drive a force application to deactivate the database. This database deactivation may result in crashing the instance by trapping in the function SQLEINTERRUPTAPPLICATION. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users in a Partitioned Database Environment * **************************************************************** * PROBLEM DESCRIPTION: * * In a DPF environment, if a database is marked bad due to * * some issue, DB2 will drive a force application to deactivate * * the database. This database deactivation may result in * * crashing the instance by trapping in the function * * SQLEINTERRUPTAPPLICATION. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.5 Fixpack 7 or later * **************************************************************** | |
Local Fix: | |
Solution | |
Problem is First Fixed in Version 9.5 Fixpack 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.09.2010 21.12.2010 21.12.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) |