DB2 - Problem description
| Problem IT03728 | Status: Closed |
MAX_COORDAGENTS CANNOT BE SET TO 0 VALUE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
When we activate the database, the DB2 system need to start up couples of system applications. If MAX_COORDAGENTS is set to 0,the database will not able to activate and it will hung. The code that automatically adjust the MAX_COORDAGENTS will not able to execute because the database system have not come up and running. Hence we should not allow this MAX_COORDAGENTS to set to 0 and it should throw an error in case it is tried to be set to 0 via some user or any defect inadvertently. However due to APAR IC97753 is inadvertently set to 0,which made the DB unusable and hung state. | |
| Problem Summary: | |
If MAX_COORDAGENTS is set to 0,the database will not able to activate and it will hung. | |
| Local Fix: | |
db2 update dbm cfg using MAX_CORDAGENTS to any non zero value. | |
| Solution | |
| Workaround | |
db2 update dbm cfg using MAX_CORDAGENTS to any non zero value. | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.08.2014 04.12.2014 04.12.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.5 |
|