Cannot put online a restored database

Hi. We are probing a new machine (Sun E890) with IDS 9.40 FC7. One of the tests was perform an ontape to backup our data an then perform a restore. There's no abnormal messages in online.log, but when I tried to bring database to quiescent mode with oninit -sv I got the next: .......... Opening primary chunks...succeeded Opening mirror chunks...succeeded Initializing dbspaces...succeeded Validating chunks...succeeded Initialize Async Log Flusher...succeeded Initializing DBSPACETEMP list Checking database partition index...FAILED oninit: Fatal error in shared memory initialization Everything before this was successful. By the way, in online.log I got: 14:58:45 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized. 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp1' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp2' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp3' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp4' 14:58:45 Physical Recovery Started at Page (3:54774). 14:58:45 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 14:58:47 Logical Recovery Started. 14:58:47 10 recovery worker threads will be started. 14:58:50 Logical Recovery has reached the transaction cleanup phase. 14:58:50 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks But all links and permissions seems to be ok on temporary dbspaces. Why does it happened? Should I perform restore again? Thanks in advance. Omar Muñoz.

Omar I got caught with this a few days ago during a DR restore, bit exciting at the time !!. After the ontape -r restore the database is left in quiescent mode, you MUST issue onmode -m before doing anything else in order to bring it to full multi-user mode, only then can you shut down (onmode -yuck) and restart (oninit). You will have to undertake the restore again. Keith -----Original Message----- From: OMAR MUñOZ [mailto:omarmun@yahoo.com] Sent: Sunday, February 12, 2006 9:40 PM To: ids@iiug.org Subject: Cannot put online a restored database [6363] Hi. We are probing a new machine (Sun E890) with IDS 9.40 FC7. One of the tests was perform an ontape to backup our data an then perform a restore. There's no abnormal messages in online.log, but when I tried to bring database to quiescent mode with oninit -sv I got the next: ........... Opening primary chunks...succeeded Opening mirror chunks...succeeded Initializing dbspaces...succeeded Validating chunks...succeeded Initialize Async Log Flusher...succeeded Initializing DBSPACETEMP list Checking database partition index...FAILED oninit: Fatal error in shared memory initialization Everything before this was successful. By the way, in online.log I got: 14:58:45 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized. 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp1' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp2' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp3' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp4' 14:58:45 Physical Recovery Started at Page (3:54774). 14:58:45 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 14:58:47 Logical Recovery Started. 14:58:47 10 recovery worker threads will be started. 14:58:50 Logical Recovery has reached the transaction cleanup phase. 14:58:50 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks But all links and permissions seems to be ok on temporary dbspaces. Why does it happened? Should I perform restore again? Thanks in advance. Omar Muñoz. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************** ** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ******************************************************************************** **

Onmode -m and wait for the engine to come fully online completing the fast recovery before shutting down. Art S. Kagel ----- Original Message ----- From: Keith Simmons <ids@iiug.org> At: 2/13 16:34 Omar I got caught with this a few days ago during a DR restore, bit exciting at the time !!. After the ontape -r restore the database is left in quiescent mode, you MUST issue onmode -m before doing anything else in order to bring it to full multi-user mode, only then can you shut down (onmode -yuck) and restart (oninit). You will have to undertake the restore again. Keith -----Original Message----- From: OMAR MU•OZ [mailto:omarmun@yahoo.com] Sent: Sunday, February 12, 2006 9:40 PM To: ids@iiug.org Subject: Cannot put online a restored database [6363] Hi. We are probing a new machine (Sun E890) with IDS 9.40 FC7. One of the tests was perform an ontape to backup our data an then perform a restore. There's no abnormal messages in online.log, but when I tried to bring database to quiescent mode with oninit -sv I got the next: ........... Opening primary chunks...succeeded Opening mirror chunks...succeeded Initializing dbspaces...succeeded Validating chunks...succeeded Initialize Async Log Flusher...succeeded Initializing DBSPACETEMP list Checking database partition index...FAILED oninit: Fatal error in shared memory initialization Everything before this was successful. By the way, in online.log I got: 14:58:45 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized. 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp1' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp2' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp3' 14:58:45 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'dbstemp4' 14:58:45 Physical Recovery Started at Page (3:54774). 14:58:45 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 14:58:47 Logical Recovery Started. 14:58:47 10 recovery worker threads will be started. 14:58:50 Logical Recovery has reached the transaction cleanup phase. 14:58:50 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks But all links and permissions seems to be ok on temporary dbspaces. Why does it happened? Should I perform restore again? Thanks in advance. Omar Mu•oz. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************** ** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ******************************************************************************** ** ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.