home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

Informix - Problembeschreibung

Problem IT06253 Status: Geschlossen

RUNNING ONMODE -M FOLLOWING A PHYSICAL ONLY WHOLE SYSTEM RESTORE DOES NOT
TRIGGER SCHEDULER STARTUP

Produkt:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problembeschreibung:
You run a physical only whole system restore (like onbar -r -w 
-p), 
and choose not to do a logical restore afterwards but bring the 
instance just online with 'onmode -m'. 
While this succeeds, the scheduler is not being started and 
required tasks are not ready to run. 
 
For example, you might observe errors like -9799 when running 
BTS dependent queries, 
because the scheduler 'autoregvp' task is not ready to create 
the bts vp.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB Users                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10                          * 
****************************************************************
Local-Fix:
A restart of the instance resolves any issues. 
Alternatively, consider starting the scheduler manually 
("execute function task('scheduler start')" against sysadmin 
database).
Lösung
Problem Fixed In IBM Informix Server 12.10
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.12.2014
16.10.2015
16.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
12.10.0
Problem behoben lt. FixList in der Version
12.10.xC5 FixList
12.10.xC5.W1 FixList