|
Problem IC71435
|
Status: Closed |
TRAP IN SQLEINTERRUPTAPPLICATION DURING DATABASE DEACTIVATION AFTER DB MARKED BAD |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* Users on DPF 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: *
* Please upgrade to 9.7 FP4 or later *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in Version 9.7 Fixpack 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71554 IC72773
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.09.2010
02.05.2011
02.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
