|
Problem IC70674
|
Status: Closed |
If you have set the BLOCKNONLOGGED parameter to YES, then you will encounter error SQL20054N while creating EXPLAIN tables. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the database configuration parameter BLOCKNONLOGGED is set to
YES, then some of the DDLs used within EXPLAIN.DDL file and the
SQL statement calling the stored procedure
SYSPROC.SYSINSTALLOBJECTS to create EXPLAIN tables will fail
with error SQL20054N.
For example: "CALL
SYSPROC.SYSINSTALLOBJECTS('EXPLAIN','C',NULL,CURRENT SCHEMA)". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users below V9.7 FP4 version are affected. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If you have set the BLOCKNONLOGGED parameter to YES, then *
* you will encounter error SQL20054N while creating EXPLAIN *
* tables. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to version V9.7 FP4 to resolve the problem. *
**************************************************************** |
| Local Fix: |
Edit the EXPLAIN.DDL file and remove the NOT LOGGED clause. |
| 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 fixed in V9.7 FP4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC75116 IC75171
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.08.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
|
 |
