|
Problem IT34227
|
Status: Closed |
ADMIN_CMD and GET_DB_CONFIG cannot handle extended number range of LOGBUFSZ
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
If a value > 65535 gets used for ADMIN_CMD UPDATE DB CFG, the
following get returned:
CALL ADMIN_CMD('UPDATE DB CFG USING LOGBUFSZ 70000')
SQL0104N An unexpected token "70000" was found following
"LOGBUFSZ".
Expected tokens may include: "".
SQLSTATE=42601
If LOGBUFSZ is already set to a value > 65535 then GET_DB_CONFIG
returns the following error:
CALL SYSPROC.GET_DB_CONFIG()
Return Status = 0
SQL5066W The database configuration parameter value for token
"SQLF_DBTN_LOGBUFSZ" has been truncated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* LOGBUFSZ > 65535 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.6 or higher *
**************************************************************** |
| Local Fix: |
Use CLP to update db config parameter LOGBUFSZ with high values
and use GET_DB_CFG to retrieve config parameters. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* LOGBUFSZ > 65535 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.6 or higher *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.09.2020
07.10.2020
07.10.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
