Informix - Problembeschreibung
Problem IT18331 | Status: Geschlossen |
CDR_MONITOR THREAD HANGS | |
Produkt: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problembeschreibung: | |
Some times CDR_Monitor thread can hang due to logical log corruption. The error message in the online log looks like this: 14:27:49 Log corruption detected or read error occurred while snooping logs. 14:27:49 AlarmStart:ccm_sjcvtg_092_ccm11_5_1_11950_61:EMERGENCY:39:Please notify IBM Informix Techical Support.:Log corruption detected or read error occurred while snooping logs.:AlarmEnd 14:27:49 Log corruption detected while snooping logs, logid=27, logpos=172216344. 14:27:49 Double rewound detected in ddrReadLog() 14:27:58 CDR GC: synchronization complete 14:27:58 CDR Grouper Fanout interface with the Dynamic Server has failed. 14:27:58 CDR Grouper FanOut thread is aborting. 14:27:58 14:27:58 DDR Log Snooping - Shutdown 14:27:58 CDR is shutting down due to internal error: Internal shutdown 14:27:58 ER Monitor received an error from the TSMachinery subcomponent. Disabling Monitoring of this subcomponent. And the stack of the thread looks like: # gstack 28380 #0 in grprLATimedWait () #1 in grprLAClean () #2 in cdrMonitorThread () #3 in cdrTrampolineThread () #4 in th_init_initgls () #5 in startup () #6 in ?? () | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC9 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.12.2016 10.07.2017 10.07.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
12.10.xC9 | |
Problem behoben lt. FixList in der Version |