home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC68897 Status: Closed

DB2LOOK OR DROP MQT CAN RETURN AN SQL0901N ERROR OR TRAP IF THE DDL TEXT IN
SYSCAT.VIEWS DOES NOT BEGIN WITH 'CREATE' OR 'ALTER'

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An MQT that was created via a Windows utility may prepend extra 
characters (^M or <NL> characters) in the MQT DDL text. This can 
lead to an SQL0901N error or possible trap when trying to 
collect the DDL via db2look or when the DROP TABLE RECOVERY 
feature attempts to collect the DDL when the MQT is being 
dropped. This also applies to any MQT DDL statement that does 
not begin with 'CREATE' or 'ALTER' (case insensitive). 
 
You can verify the DDL text used to create the MQT with the 
below query: 
 
select text from syscat.views
Problem Summary:
Users affected: Any using a 3rd party client tool to create 
tables 
Problem Description: Extra characters in the table name can 
cause db2 to trap during DROP table or db2look. 
Problem Summary: See above.
Local Fix:
For the drop table case, you can temporarily turn off DROP TABLE 
RECOVERY for that tablespace (e.g. ALTER TABLESPACE <tbspname> 
DROPPED TABLE RECOVERY OFF) to allow the drop to complete and 
then re-enable it.
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
Problem was first fixed in Version 9.7 FixPak 3
Workaround
For the drop table case, you can temporarily turn off DROP TABLE 
 
RECOVERY for that tablespace (e.g. ALTER TABLESPACE <tbspname> 
DROPPED TABLE RECOVERY OFF) to allow the drop to complete and 
then re-enable it.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69731 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.05.2010
07.10.2010
07.10.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList