home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 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 IT06253 Status: Closed

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

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
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 Summary:
**************************************************************** 
* 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).
Solution
Problem Fixed In IBM Informix Server 12.10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.12.2014
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
12.10.0
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC5 FixList
12.10.xC5.W1 FixList