|
Problem IT28628
|
Status: Closed |
FAILED CONNECTIONS COULD LEAD TO INCORRECT VALUE FOR SHMEM->SH_RSNACTIVE WHICH COULD CAUSE PHYSICAL LOG OVERFLOW ASSERTIONS
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
Under specific failed connections, it's possible that
shmem->sh_rsnactive will be decremented prior to it having been
incremented. If this happens often enough
shmem->sh_rsnactive can go to a negative value. This can lead
to physical log overflow because this value is used in the code
to determine if a non-blocking checkpoint needs to be switched
to a blocking checkpoint, to prevent the physical log from
filling.
The most likely cause of failed connections would be servers
that have SHMTOTAL set to a non-zero value, and the server has
allocated SHMTOTAL amount of memory.
Fixed in 12.10.UC11 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All operating systems. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Under specific failed connections, it's possible that *
* shmem->sh_rsnactive will be decremented prior to it having *
* been *
* incremented. If this happens often enough *
* shmem->sh_rsnactive can go to a negative value. This can *
* lead *
* to physical log overflow because this value is used in the *
* code *
* to determine if a non-blocking checkpoint needs to be *
* switched *
* to a blocking checkpoint, to prevent the physical log from *
* filling. *
* *
* The most likely cause of failed connections would be servers *
* that have SHMTOTAL set to a non-zero value, and the server *
* has *
* allocated SHMTOTAL amount of memory. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to version 12.10.XC11 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.04.2019
08.10.2019
08.10.2019 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC11
|
| Problem solved according to the fixlist(s) of the following version(s) |
