DB2 - Problem description
Problem IC90391 | Status: Closed |
FOR A NONE PURESCALE INSTANCE, DB2 SHOUD NOT DISPLAY THE VALUE FOR RSTRT_LIGHT_MEM. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
According to the DB2 V10 Info Center, the value of RSTRT_LIGHT_MEM is set to AUTOMATIC and the calculated value will be between 1 and 10 percent of the instance memory limit. For a manual setting the values can be between 1 and 50. However, on a none Pursecale instance, when conducting the following test a value of zero was used to duplicate the problem: $ db2 get dbm cfg | grep restart Instance memory for restart light (%) (RSTRT_LIGHT_MEM) = AUTOMATIC(10) Then attach to the instance and the value of RSTRT_LIGHT_MEM will be changed from 10% which is the default to zero. In this case the value of Zero makes sense as DB2 will not use any memory for restart light. However, this behavior is not documented. $ db2 attach to rodeh Instance Attachment Information Instance server = DB2/AIX64 10.1.1 Authorization ID = RODEH Local instance alias = RODEH (rodeh@p6db2serv) /home/rodeh $ db2 get dbm cfg | grep restart Instance memory for restart light (%) (RSTRT_LIGHT_MEM) = 0 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgraded to DB2 Version 10.1 FP3 * **************************************************************** | |
Local Fix: | |
The RSTRT_LIGHT_MEM is only supported on a Purescale instance and doesn't have any effect on a none Purescale instance. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version DB2 V10.1 FP3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.02.2013 26.11.2013 26.11.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |