APAR status
Closed as program error.
Error description
If you have a MACH11 cluster with an RS secondary instance and the RSS is configured with a delayed application of log files (DELAY_APPLY parameter in $ONCONFIG file set to non-zero value) and the filesystem defined by the LOG_STAGING_DIR parameter gets full, the DelayedApply thread (which creates the files in LOG_STAGING_DIR directory) ends. All the other replication-related threads on RSS are working properly, their stacks just show the threads are waiting for something to be sent from the primary. Moreover, the log pages sent by the primary are acknowledged by the RSS, so the net effect of this defect is the RSS gets out-of-sync with the primary without any obvious error message. If the logical logs on the primary wrap while the secondary is still applying staged logs, the secondary will add a message that it needs failure recovery from disk, but will need a restore to be able to apply that.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of RSS nodes configured with the DELAY_APPLY or * * STOP_APPLY parameter. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IDS-11.70.xC8 * ****************************************************************
Problem conclusion
Problem fixed in IDS-11.70.xC8. Instead of exiting on write errors, the delay or stop apply subsystem will retry. Upon encountering a write error, the RSS server will raise an alarm of severity 3 (attention) class 40 and event id 40007. While retrying the writes, the RSS will periodically write messages to the message log. onstat -g rss verbose will also print additional information about the delay or stop apply status.
Temporary fix
Comments
APAR Information
APAR number
IC95680
Reported component name
INFORMIX SERVER
Reported component ID
5725A3900
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-03
Closed date
2014-02-26
Last modified date
2014-02-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INFORMIX SERVER
Fixed component ID
5725A3900
Applicable component levels
RB70 PSY
UP
RC10 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 February 2014