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 IT32756 Status: Closed

DYNAMIC CHANGE OF LTAPEDEV TO NULL DEVICE MAY NOT MARK LOGS AS BACKED UP
ON SECONDARY SERVERS

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
The onmode -wm and onmode -wf commands may be used to
dynamically change the value of the LTAPEDEV onconfig paramter
to the null device, eg. /dev/null for Unix and Linux operating
systems. When this command is run on a secondary server not all
of the used log files may be marked as backed up. If the onmode
command is then run again to change the LTAPEDEV parameter to a
non-null value then a problem will occur when the logs cycle
round and encounter those logs that have not been marked as
backed up. The secondary server will become stuck trying to
switch into the log that is not backed up with the logrecover
thread spinning in a loop. A typical stack for this thread is:

yield_processor_svp
mt_yield
lgr_set_logf
dologrecvr
th_init_initgls

The thread will frequently be seen to be in a running state.

Furthermore the communications with the primary server may
become blocked. If the problem secondary server is an HDR then
the primary may hang on a checkpoint request until such time as
the timeout value set for the HDR communications is exceeded and
the connection will be dropped.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC6.  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC15 (when available) or    *
* 14.10.xC6 (when available).                                  *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC6.  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC15 (when available) or    *
* 14.10.xC6 (when available).                                  *
****************************************************************
Comment
Fixed in Informix Server 12.10.xC15 and 14.10.xC6.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.05.2020
12.05.2021
12.05.2021
Problem solved at the following versions (IBM BugInfos)
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