|
Problem IC72497
|
Status: Closed |
WHEN CONVERTING DATE TO ANOTHER TYPE, USING VARCHAR_FORMAT OR MO NTHNAME , OR OTHER FUNCTIONS, MAY CAUSE EXTRA MEMORY CALLS IN 97 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Extra memory calls during processing of monthname, or varchar_fo
rmat, or other such functions to convert the date to a specific
type. For example:
.
select varchar_format(ctime,'DDD') from sysibm.systables where
tid = 0 and fid = 5
.
In the db2 perfcount traces, one could see many calls
to sqlnls_gmblk_callback_U500R1 function. Similarly in
sqlnls_fmblk_callback_U500R1 function.
. |
| Problem Summary: |
Extra memory calls during processing of monthname, or varchar_fo
rmat, or other such functions to convert the date to a specific
type. For example:
.
select varchar_format(ctime,'DDD') from sysibm.systables where
tid = 0 and fid = 5
In the db2 perfcount traces, one could see many calls
to sqlnls_gmblk_callback_U500R1 function. Similarly in
sqlnls_fmblk_callback_U500R1 function. |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 |
First Fixed in DB2 Version 9.7 Fix Pack 5 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72994
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.11.2010
18.01.2012
28.02.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5,
9.7.FPk4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
