Informix - Problem description
Problem IT19351 | Status: Closed |
AFTER ONMODE -KY, ONCLEAN -KY THROWS ERROR MESSAGES THE SEMCTL()FUNCTION ON ID = ?????? FAILED WITH ERROR NUMBER = 22 | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
After onmode -ky, if user types onclean -ky it throws error messages The semctl() function on ID = 21397552 failed with error number = 22. - Looking for the shmem key: 52d34801 - Looking for the shmem key: 52d34802 - Looking for semaphore ID: 21430321 The semctl() function on ID = 21430321 failed with error number = 22. - Looking for semaphore ID: 21463090 The semctl() function on ID = 21463090 failed with error number = 22. - Looking for semaphore ID: 21495859 The semctl() function on ID = 21495859 failed with error number = 22. - Looking for the shmem key: 52d34804 - Looking for semaphore ID: 21528628 The semctl() function on ID = 21528628 failed with error number = 22. - Looking for semaphore ID: 21561397 The semctl() function on ID = 21561397 failed with error number = 22. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users running onclean -ky with the server off-line * **************************************************************** * PROBLEM DESCRIPTION: * * The error being reported by onclean is benign and expected * * if the server is already down. The user should focus on the * * return code from onclean (0), and its final message, "IBM * * Informix Dynamic Server seems to have shutdown cleanly." * * Because the semctl() error message was causing concern, * * however, it has been removed in the fixed version. * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC9 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.02.2017 10.07.2017 10.07.2017 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC9 | |
Problem solved according to the fixlist(s) of the following version(s) |