PH10325: TIMESTAMP COLUMNS DECLARED WITH A NON-DEFAULT SIZE DISPLAY INCORRECT MILLISECOND VALUES

APAR status

• Closed as fixed if next.

Error description

• If a timestamp column is declared using the default precision
  of 9, through the syntax TIMESTAMP(9) or TIMESTAMP, the values
  are displayed correctly.  However, if a column is declared
  using a smaller precision such as TIMESTAMP(6) or TIMESTAMP(2),
  then the values displayed in the milliseconds field are
  incorrect.  Compare the following sample query results:
  $ db2 "create hadoop table ts(c1 timestamp, c3 timestamp(9))"
  DB20000I  The SQL command completed successfully.
  $ db2 "insert into ts values ('1999-09-09-09.09.09.5',
  '1999-09-09-09.09.09.5')"
  DB20000I  The SQL command completed successfully.
  $ db2 "select * from ts"
  C1                            C3
  ----------------------------- -----------------------------
  1999-09-09-09.09.09.500000000 1999-09-09-09.09.09.500000000
    1 record(s) selected.
  DB20000I  The SQL command completed successfully.
  $ db2 "create hadoop table ts(c1 timestamp, c3 timestamp(6))"
  DB20000I  The SQL command completed successfully.
  $ db2 "insert into ts values ('1999-09-09-09.09.09.5',
  '1999-09-09-09.09.09.5')"
  DB20000I  The SQL command completed successfully.
  $ db2 "select * from ts"
  C1                            C3
  ----------------------------- --------------------------
  1999-09-09-09.09.09.500000000 1999-09-09-09.09.09.000500
    1 record(s) selected.
  $ db2 "create hadoop table ts2 (c1 timestamp, c3 timestamp(2))"
  DB20000I  The SQL command completed successfully.
  $ db2 "insert into ts2 values ('1999-09-09-09.09.09.5',
  '1999-09-09-09.09.09.5')"
  DB20000I  The SQL command completed successfully.
  $ db2 "select * from ts2"
  C1                            C3
  ----------------------------- ----------------------
  1999-09-09-09.09.09.500000000 1999-09-09-09.09.09.00
    1 record(s) selected.
  

Local fix

Problem summary

•  Problem is fixed in IBM Db2 Big SQL version
  6.0.0.0
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels