RE: need help - infformix is down - restart got index failed

OK Neil, I ran an experiment....... hsap10% oninit -v ........ Initializing 127 flushers...succeeded Initializing log/checkpoint information...succeeded Opening primary chunks...succeeded Opening mirror chunks...succeeded Initializing dbspaces...succeeded Validating chunks...succeeded Initialize Async Log Flusher...succeeded Forking btree cleaner...succeeded Initializing DBSPACETEMP list *******see below for online log ****** hsap10% Checking database partition index...succeeded Checking location of physical log...succeeded Initializing dataskip structure...succeeded Checking for temporary tables to drop Forking onmode_mon thread...succeeded Verbose output complete: mode = 5 hsap10% during the time the onint -v is processing, a tail of the online.log is also running. After the "DBSPACETEMP list" output of the oninit -v, the oninit "pauses" (going back to command line), then it goes on with remaining output above. During the "pause" time, the DB online.log appears to complete physical recovery and enter logical recovery: 11:37:18 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 11:37:18 Logical Recovery Started. 11:37:18 10 recovery worker threads will be started. 11:37:21 Logical Recovery has reached the transaction cleanup phase. 11:37:21 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks 11:37:25 Dataskip is now OFF for all dbspaces But the original post appeared to complete logical recovery. SO.... What happens internally in the DB engine between logical recovery completion and "on-line"? Maybe system catalog or sysmaster db corruption? Norma Jean Sebastian ERP Support Administration GIS- Enterprise Technical Services -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Neil Truby Sent: Thursday, November 23, 2006 10:59 AM To: informix-list@iiug.org Subject: Re: need help - infformix is down - restart got index failed "Sebastian, Norma J." <NormaJean.Sebastian@tellabs.com> wrote in message news:mailman.370.1164298908.29126.informix-list@iiug.org... >> The end of the oninit -v may give some clue. It says: Initializing DBSPACETEMP list Checking database partition index...FAILED oninit: Fatal error in shared memory initialization it does not say "initializing DBSPACETEMP....succeeded. what's DBSPACETEMP set to? Check your chunks..... maybe you lost a disk? Or maybe some of your chunk perms are set incorrectly (660 informix informix) I don't think the absence of temporary dbspaces causes Informix to fail. Could be wrong though. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================