suche 36x36
  • Admin-Scout-small-Banner
           

    CURSOR Admin-Scout

    get the ultimate tool for Informix

    pfeil  
Latest versionsfixlist
14.10.xC10 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT10689 Status: Closed

STOP_APPLY = 1 IS NOT ALWAYS AFFECTIVE AND THE STAGING_DIR CAN REMAIN EMPTY

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
In a testing environment it is clear that STOP_APPLY does not 
always work consistently. 
 
In a testing environment that has a single RS server, it was 
observed that if there is a backlog on the RS and you set 
STOP_APPLY to ?1?, replication breaks.  It appears that the two 
instances stop talking to each other. When one sets STOP_APPLY 
to ?1? one expects to see logs being created in the 
LOG_STAGING_DIR.  This is not happening.  If one sets STOP_APPLY 
to ?0?, the RS does nothing.  It requires a bounce of the RS to 
get the server back in-sync with the Primary. When there is no 
backlog (according to onstat ?g rss verbose) and STOP_APPLY is 
set to ?1? the behavior is as expected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* MACH11 users with RSS nodes utilizing DELAY_APPLY or         * 
* STOP_APPLY                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.FC5.                     * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IBM Informix Server 12.10.FC5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.08.2015
28.06.2016
28.06.2016
Problem solved at the following versions (IBM BugInfos)
12.10.FC5
Problem solved according to the fixlist(s) of the following version(s)
Informix EditionsInformix Editions
Informix Editions
DocumentationDocumentation
Documentation
IBM NewsletterIBM Newsletter
IBM Newsletter
Current BugsCurrent Bugs
Current Bugs
Bug ResearchBug Research
Bug Research
Bug FixlistsBug Fixlists
Bug Fixlists
Release NotesRelease Notes
Release Notes
Machine NotesMachine Notes
Machine Notes
Release NewsRelease News
Release News
Product LifecycleProduct Lifecycle
Lifecycle
Media DownloadMedia Download
Media Download