|
Problem IC65063
|
Status: Closed |
TRAP IN SETUETABLECOLUMNS DURING RESTORE DB WHEN AN UOW EVENT MONITOR EXISTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A trap can occur in DB2 when (1) a UNIT OF WORK event monitor is
active (either because it is AUTOSTART or because it is
MANUALSTART and was explicitly activated), (2) UNIT OF WORK
collection has been turned on in the database configuration (for
example "db2 update db cfg for sample using mon_uow_data base"),
and (3) a restore is run following a backup. DB2 can trap with
the following call stack:
-- callstack --
setUETableColumns__19sqmFastWriterRecordFUlN218sqlo_gmtPcP9sqeBs
uEdu
generateUOWEvent__12sqmUOWEventsFP8sqeAgent
sqlmRequestEnd__FP8sqeAgentCbN22
sqljsCleanup__FP8sqeAgentP14db2UCconHandle
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T
RunEDU__8sqeAgentFv
EDUDriver__9sqzEDUObjFv
sqlzRunEDU__FPcUi
sqloEDUEntry |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW users that use the UNIT OF WORK event monitor *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 can trap with *
* the following call stack: *
* *
* *
* *
* -- callstack -- *
* *
* setUETableColumns__19sqmFastWriterRecordFUlN218sqlo_gmtPcP9sqe
* uEdu *
* *
* generateUOWEvent__12sqmUOWEventsFP8sqeAgent *
* *
* sqlmRequestEnd__FP8sqeAgentCbN22 *
* *
* sqljsCleanup__FP8sqeAgentP14db2UCconHandle *
* *
* sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb *
* *
* sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T *
* *
* RunEDU__8sqeAgentFv *
* *
* EDUDriver__9sqzEDUObjFv *
* *
* sqlzRunEDU__FPcUi *
* *
* sqloEDUEntry *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 9.7 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
After the backup either (1) recycle the db2 instance, or (2)
turn off UNIT OF WORK collection in the database configuration
(for example "db2 update db cfg for sample using mon_uow_data
none") |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
The problem will be fixed in DB2 LUW Version 9.7 Fix Pack 2,
and no workaround will be required after the backup, and before
the restore (the restore should not trap). |
| Workaround |
After the backup either (1) recycle the db2 instance, or (2)
turn off UNIT OF WORK collection in the database configuration
(for example "db2 update db cfg for sample using mon_uow_data
none") |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.12.2009
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
