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 IC92250 Status: Closed

YOU MAY MEET SQL1227N ERROR WHEN HIGH2KEY AND LOW2KEY IS TIMESTAMP TYPE IN
ORACLE MODE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Here is the reproducing scripts: 
 
1. Remote data source 
create table t1(c1 int, C2 TIMESTAMP); 
insert into t1 values(1,NULL); 
insert into t1 values(2,current timestamp); 
insert into t1 values(3,current timestamp +1 DAY); 
insert into t1 values(4,current timestamp +2 DAY); 
insert into t1 values(5,current timestamp +3 DAY); 
RUNSTATS ON TABLE ADMINISTRATOR.t1 ON ALL COLUMNS AND INDEXES 
ALL ALLOW WRITE ACCESS; 
 
 
db2 => SELECT COLCARD, HIGH2KEY, LOW2KEY FROM SYSSTAT.COLUMNS 
where TABNAME='T1' and COLNAME = 'C2' 
 
COLCARD              HIGH2KEY 
 
LOW2KEY 
 
 
-------------------- 
---------------------------------------------------------------- 
---------------------------------------------------------------- 
------ 
---------------------------------------------------------------- 
--------------------------------------------------- 
--------------------------------------- 
---------------------------------------------------------------- 
---------------------------------------------------------------- 
--------------------------- 
-------------------------------------------------- 
                   5 '2013-05-03-23.25.14.832000' 
 
'2013-05-01-23.25.14.829000' 
 
 
 
 
2. Federated database in oracle mode: 
 
connect to ora; 
drop wrapper drda; 
create wrapper drda; 
create server v97db type db2/udb  version 9.7 wrapper drda 
authorization "ADMINISTRATOR" password "xxxxxx" 
options(dbname'TEST'); 
create user mapping for administrator server v97db 
options(remote_authid 'ADMINISTRATOR',remote_password 'xxxxxx'); 
create nickname n1 for  v97db."ADMINISTRATOR"."T1"; 
call 
sysproc.nnstat('V97DB','ADMINISTRATOR','N1',NULL,NULL,0,'<your_p 
ath>\nnstat.txt::DIAG',?); 
 
Session.NNSTAT_Columns 
----schema----nickname----colname----card----high2key----low2key 
---overflow---- 
ADMINISTRATOR        | N1                   | C1 
|          5 | 4                                        | 2 
 
ADMINISTRATOR        | N1                   | C2 
|          5 | '2013-05-03-23.25.14.832000'             | 
'2013-05-01-23.25.14.829000' 
 
 
Session.NNSTAT_Indexes 
----tabschema----tabname----indschema----indname----nleaf----nle 
vels---clusterratio----clusterfactor---firstkeycard---fullkeycar 
d--- 
 
 
Done writing global temporary tables to log. 
 
 
An attempt to select all the nicknames failed. An error was 
returned when opening a cursor on syscat.taboptions. 
nnstat.SQC, Line 1917 : SQL1227N  The catalog statistic 
"'2013-05-03-23.25.14.832000'" for column "HIGH2KEY" is out of 
range for its target column, has an invalid format, or is 
inconsistent in relation to some other statistic. Reason Code = 
"3".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use NNSTAT in oracle mode                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fix V9.7fp9                                       * 
****************************************************************
Local Fix:
available fix packs:
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
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96754 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.05.2013
16.12.2013
16.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList