|
Problem IC79664
|
Status: Closed |
DB2 DOES NOT SUPPORT DDMONYYYY TIMESTAMP FORMAT NATIVELY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 9.7 does not support ddMonYYYY natively as part of the
Oracle compatibility issue.
The intent of this APAR is to allow users to use this timestamp
starting on DB2 Version 9.7 Fix Pack 6. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* COMPATIBILTIY_VECTOR set *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Install fix *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
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 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 |
Install fix |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84129
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.11.2011
06.06.2012
06.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
