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

ASSERT FAILED: YIELD_PROCESSOR: CONDITIONAL LATCH COUNT NON-ZEROPOSSIBLE
WHEN ALRM_ALL_EVENTS SET TO 1

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
Server can abort with the following assertion:

08:18:37  Assert Failed: yield_processor: Conditional latch
count non-zero in thread 66

08:18:37   Who: Session(32, user@host, 29636, 0x46649cd8)
        Thread(66, sqlexec, 46606388, 8)
        File: mt_fn.c Line: 17634

Stack of the assertion thread:

afhandler
afcrash_interface
yield_processor_mvp
mt_lock_wait
mt_lock_helper
mt_lock
ph_wakeup
ph_submit_task
ph_alarm_post
invoke_alarmf
mt_sysmsg_body
mt_sysmsg
mt_logprintf
adjust_lru_flushing
bffindfree
buffget
find_page
rsread
rsdbopen
isdbopen
ddopen
dbopen
find_db
qopendb
excommand
sq_execute
sqmain
spawn_thread
th_init_initgls
startup

The critical portion of the stack is the
buffget/bffindfree/adjust_lru_flushing.  If the server gets into
that code path, and ALRM_ALL_EVENTS is set to 1, it's possible
that the assertion could happen once it gets down to the
ph_wakeup level.  It won't always happen, but it's possible.

The adjust_lru_flushing function would place something like the
following message into the MSGPATH file:

08:02:01  Adjusting LRU for bufferpool - id 0 size 2k
08:02:03    Old max 60.0 min 50.0    New max 59.4 min 49.5
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC7.  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when     *
* available).                                                  *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC7.  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when     *
* available).                                                  *
****************************************************************
Comment
Fixed in Informix Server 12.10.xC15 and 14.10.xC7.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.06.2020
26.08.2021
26.08.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