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

REVERSION OF SYSHA DATABASE MAY SILENTLY FAIL LEADING TO ASSERT FAILURE
DURING STARTUP OF REVERTED VERSION

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
When using the onmode -b command to revert IDS to an earlier
version and if there are RSS server definitions contained within
the sysha database then it may occur that the database is in use
during the onmode command which prevents any update of its
schema to the earlier version. The online log will contain
messages suggesting a successful reversion of the database yet
on startup in the earlier version Assert Failures may occur and
the sysha database will be unusable.

Although the online log reports that the sysha database was
successfully reverted it does provide a clue to the impending
problem. For example:

17:04:56  processing sysha
17:05:56  *** entity_ver=0  targetVersion=33  indexVersion= 10
***
17:05:56  *** FromVersion=35  ToVersion=35 entity_ver=0
targetVersion=33 indexVersion=10 ***
17:05:56  *** FromVersion=35  ToVersion=36 entity_ver=0
targetVersion=33 indexVersion=9 ***
...
17:05:56  Database sysha SUCCESSFULLY reverted ...

The value of 0 for enity_ver is incorrect.

An example of an Assert Failure during startup in the earlier
version:

17:08:30  Found during mt_shm_free 1, error seen 1 times since
last print to the log
17:08:30  Pool 'iplrestart' (0x477cd040)
17:08:30  Bad block header 0x478a8d60
17:08:30  Assert Warning: Memory block header corruption
detected in mt_shm_free 1
17:08:30  IBM Informix Dynamic Server Version 11.70.FC9
17:08:30   Who: Session(14, informix@svr1, 0, 0x456956e0)
                Thread(40, iplrestart, 45656f10, 1)
                File: mtshpool.c Line: 2742
17:08:30   Results: Pool repaired
17:08:30   Action: Please notify IBM Informix Technical Support.
17:08:30  stack trace for pid 28704 written to
/opt/informix/IBM/11.70.FC9/tmp/af.41069fe
17:08:30   See Also: /opt/informix/IBM/11.70.FC9/tmp/af.41069fe

Other types of memory block header corruption AF are also
possible.

Running oncheck -cc on the sysha database will find various
problems.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 14.10.xC7.                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 14.10.xC7.                        *
****************************************************************
Local Fix:
This specific problem relating to the sysha database may be
avoided during reversion by ensuring that all RSS server
definitions are dropped prior to the start of reversion.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 14.10.xC7.                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 14.10.xC7.                        *
****************************************************************
Comment
Fixed in Informix Server 14.10.xC7.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.03.2020
02.11.2021
02.11.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