|
Problem IC70364
|
Status: Closed |
JOURNAL DISPLAYS SQL1014W WARNING MESSAGE FOR A PARTICULAR DATABASE EVEN WHEN THE HISTORY FILE IS NOT EMPTY |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Journal displays SQL1014W Warning Message under certain
circumstances for a particular database even when the
history file is not empty.
For example, if a command like the one below was used to create
a tablespace with 'DROPPED TABLE RECOVERY ON', and the record
corresponding to this is in the history file, the issue occurs.
CREATE REGULAR TABLESPACE <tablespace name> PAGESIZE 8 K
MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 8 OVERHEAD 10.5
PREFETCHSIZE 8 TRANSFERRATE 0.14 BUFFERPOOL BP_SG8K
DROPPED TABLE RECOVERY ON
where <tablespace name> is the name of the tablespace
This in itself is fine but when an actual DROP TABLE event hits
the history file the problem presents in the journal GUI. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* Journal displays SQL1014W Warning Message trying to see the *
* history for a database even when the history file is not *
* empty. This does not occur for all databases nor always. It *
* occurs under certain circumstances for a particular database *
* *
* *
* *
* For example, if a command like the one below was used to *
* create a tablespace with 'DROPPED TABLE RECOVERY ON', and *
* the record corresponding to this is in the history file, the *
* issue occurs. *
* *
* *
* *
* *
* CREATE REGULAR TABLESPACE <tablespace name> PAGESIZE 8 K *
* *
* MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 8 OVERHEAD 10.5 *
* PREFETCHSIZE 8 TRANSFERRATE 0.14 BUFFERPOOL BP_SG8K *
* DROPPED TABLE RECOVERY ON *
* *
* *
* where <tablespace name> is the name of the tablespace *
* *
* *
* *
* This in itself is fine but when an actual DROP TABLE event *
* hits the history file the problem presents in the journal *
* GUI. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.5 Fix Pack 7 or later *
**************************************************************** |
| Local Fix: |
Use the db2 prune history command to prune the history file. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 version 9.5 Fix Pack 7 |
| Workaround |
Use the db2 prune history command to prune the history file. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC90555
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.08.2010
07.10.2010
07.10.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
