Re: Oninit from cron leaves engine in permanent fast recovery

When IDS starts up the first oninit process starts the others. When it exists the oninit command returns to the command line and the first VP loses it's parent process. init notices this and the OS should assign init (PID 1) as it's new parent. I suspect that the first oninit process that is creating is not completing hence it never exits. This means the next one will not get a parent PID of 1 and the oninit command appears to hang. The theads that exist in IDS include fastrec (fast recovery) bld_logrecs ( I assume collects log records for application) log_redo (i assume applies the log records) The "Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored." means no active transactions that I can see. It is in the Logical Recovery phase. There make still be logical log records to be applied since some events are always logged even if no transaction logging is on any database.(e.g. allocating a new extent to a table, adding a chunk) so IDS can keep it's space allocation information consistent. Also things like changes to stuff stored on the reserved pages e.g. checkpoint records, level 0 archive information, changing onconfig parameters are logged.so Informix can keep reserved pages consistent. . What does onstat -g stk all give? You could try running onstat -l and the get the logical log with a C against it (current). Run onlog against it. onlog -n <logical log id number, I think or justonlog and dump the output to a file as that dumps everything. See if this changes as IDS applies logical log records. onstat -g stk all should be interesting.