DB2 - Problembeschreibung
Problem IT02957 | Status: Geschlossen |
DB2SUPPORT WITH CL1 OPTION DOES NOT COLLECT INFORMATION FOR THE CDE COLUMNS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
db2support using cl1 option but does not collect all the information for column oriented tables. In the optimizer log you have seen that the column keyword (CO) was not included in the undercover commands it runs to collect statistics information For example:- db2support output_directory -d database_name -sf sql_file -cl 1 In optimizer.log the statement should look like select distinct o.object_name from explain_object o where (o.object_type in ('TA','NK','TF','DP') or o.object_type like '+%') . and explain_time >'2014-06-22-08.35.53.675807'!/db2recovery/db2dqa10/sqllib/bin/d b2look -d PMQABLU -a -e -m -l-t S_USER_BUS_AREA_AUTH S_USER_COMP_AUTH S_USER_VERSION_AUTH V_C_D_ TIME V_C_F_TITLE_ACTUALV_C_F_TITLE_ACTUAL_POCV_C_H_CONS_HIERARCHY_POC V_C_H_FRCH_SEG_HIERARCHY -o/home/dba/prd/info/DB2S o.object_type in ('TA','NK','TF','DP') ------------------------> It does not have any keyword CO for column oriented tables. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to V105FP4+ * **************************************************************** | |
Local-Fix: | |
Collect data using cl0 option with db2support i.e:- db2support output_directory -d database_name -cl 0 | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
V105FP4 contains the fix. COL table will be included in db2look output. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.07.2014 21.10.2014 21.10.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |