View previous topic :: View next topic
|
Author |
Message |
pkmurali Warnings : 1 Active User
Joined: 15 Dec 2005 Posts: 271
|
|
|
|
Hi All,
In my project, we are upgrading DB2V10 from V8. We found some difference like 'TIMESTAMP EXTERNAL' occupies X(26) in V8 and in X(19)v10. Also from google i got the following link
www-05.ibm.com/fr/events/db2.../DB2V10_Migration_Gareth_Jones.pdf
Where the Char data type has some incompatible changes,
Quote: |
Incompatible changes
– CHAR() scalar function – solution for compatibility is coming
SQL scalar function CHAR() for COL1 DEC(4,0)
SELECT COL1
,CHAR(COL1)
,HEX(CHAR(COL1))
,SUBSTR(CHAR(COL1), 2, 4) APPL_SUBSTR
FROM DB2_TABLE;
+------------------------------------------------+ +-------------------------------------------------+
! COL1 ! CHAR_V9 ! HEX_CHAR_V9 ! APPL_SUBSTR ! ! COL1 ! CHAR_V10 ! HEX_CHAR_V10 ! APPL_SUBSTR !
+------------------------------------------------+ +-------------------------------------------------+
! 9 ! 0009, ! 40F0F0F0F96B ! 0009 ! ! 9 ! 9 ! F94040404040 ! !
! 99 ! 0099, ! 40F0F0F9F96B ! 0099 ! ! 99 ! 99 ! F9F940404040 ! 9 !
! 999 ! 0999, ! 40F0F9F9F96B ! 0999 ! ! 999 ! 999 ! F9F9F9404040 ! 99 !
! 9999 ! 9999, ! 40F9F9F9F96B ! 9999 ! ! 9999 ! 9999 ! F9F9F9F94040 ! 999 !
+------------------------------------------------+ +-------------------------------------------------+
|
But i can't find the difference of 'TIMESTAMP EXTERNAL' in that link. The 'TIMESTAMP EXTERNAL' detail is obtained from our DBA. Please let me know what are all the difference that need to be verified before upgrading V10.
Thanks,
Murali. |
|
Back to top |
|
|
gylbharat
Active Member
Joined: 31 Jul 2009 Posts: 565 Location: Bangalore
|
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
Back to top |
|
|
gylbharat
Active Member
Joined: 31 Jul 2009 Posts: 565 Location: Bangalore
|
|
|
|
From - DB2 10 for z/OS Technical Overview
With DB2 10 for z/OS new-function mode, timestamp data type can provide precision up to a
picosecond (10-12 of a second). You can control the number of digits for the fractional second
using the optional timestamp precision attribute. The precision attribute range is 0 to 12, and
the default value is 6 because only six digits for the fractional second were supported in prior
releases. Example6-25 illustrates various timestamp precisions that could be declared.
Example 6-25 Examples of timestamp precision
Code: |
CREATE TABLE TRYTMSPREC(
ID INT
,TMS_DFLT TIMESTAMP -- precision 6 (default )
,TMS_0 TIMESTAMP(0) -- precision 0 (minimum supported)
,TMS_6 TIMESTAMP(6) -- precision 6 (same as default)
,TMS_9 TIMESTAMP(9) -- precision 9
,TMS_12 TIMESTAMP(12) -- precision 12 (maximum supported)
); |
The external representation of a timestamp is a string representation of the form
yyyy-mm-dd-hh.mm.ss (19 bytes, when precision is 0) or yyyy-mm-dd-hh.mm.ss.nnnnnnnnnnnn
(where the number of digits n for the fractional second can vary from 1 to 12, resulting in
external length of 21 to 32 accordingly). |
|
Back to top |
|
|
|