• Admin-Scout-small-Banner
           
    CURSOR Admin-Scout
    get the ultimate tool for Informix
    pfeil  
invispix 10x10
invispix 10x10
Latest versionsfixlist
14.10.xC5 FixList
12.10.xC14.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
Question in the chat LiveZilla Live Help

Informix - Problem description

Problem IT34246 Status: Closed

LOG RECOVERY ERRORS ON SECONDARIES IF RESTARTED TOO SOON AFTER
INSTATIATION FROM PHYSICALLY RESTORED NON-WHOLE-SYSTEM BACKUP

product:
INFORMIX SERVER / 5725A3900 / E10 - 
Problem description:
Physically restoring an instance from a non-whole-system backup
(no -w) will result in a system without any usable logical log
files, all existing log files will have a zero unique id and no
usable content, and the various dbspaces/sbspaces in the system
might represent states of vastly different checkpoints,
potentially many logical logs apart from each other.

When now using such physically restored system for instantiating
a secondary server (running 'onmode -d secondary/RSS
' on this), the list of required log files will be
determined from archive checkpoint information of all the spaces
in the system, with some spaces needing older logs, others only
later ones. Those logs will be retrieved from primary (or log.
log backup) and applied to the system, with log records from
older logs pertaining to spaces only requiring later logs being
skipped based on spaces' ds_logid/ds_logpos information.
This skipping, though, will only work as long as the server
remains online since that initial instantiation; should the
secondary be restarted before reaching the highest of those
ds_logid/ds_logpos LSNs, any log records older than that LSN of
the space they correspond to will no longer be skipped which, as
they're old and their actions long applied to the space, can
lead to all kinds of log recovery failures.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 14.10.xC5.                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to Informix Server 14.10.xC5.                         *
****************************************************************
Local Fix:
Avoid the problem by not shutting down a secondary before it
reached the latest archive checkpoint of all spaces in the
system.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2020
09.12.2020
09.12.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
invispix 10x10
invispix 10x10
invispix 10x10
Technical InfoTechnical Info

Technical Info

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

invispix 10x10
Service und SupportService und Support

Service and Support

Informix MonitoringInformix Monitoring

Informix Monitoring

Admin-Scout forInformixAdmin-Scout forInformix

Admin-Scout for Informix

Informix News & InfosInformix News & Infos

Informix News & Infos

This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.