Any assistance appreciated: Dynamic Server Initialisation Failure

Hi All, I have a situation where the IDS-731UD4 instance I run on HP-UX 11 is failing after a cold restore. I do not have time to perform another restore without serious business ramifications. The output from the log file is: the last lines: 09:47:30 Could not create single shared memory segment with resident andnon-re sident partitions. Proceeding to create 2 shared memory segments instead. 09:47:32 Segment locked: addr=0xc1841000, size=683679744 Sat Jan 22 09:47:32 2005 09:47:32 Event alarms enabled. ALARMPROG = '/apps/informix_ids/etc/ifx_alert.sh' 09:47:38 DR: DRAUTO is 0 (Off) 09:47:39 Dynamically allocated new message shared memory segment (size 1104KB) 09:47:39 Informix Dynamic Server Version 7.31.UD1 Software Serial NumberAAD #J216570 09:47:39 Informix Dynamic Server Initialized -- Shared Memory Initialized. 09:47:39 Physical Recovery Started. 09:47:39 Physical Recovery Complete: 0 Pages Restored. 09:47:39 Logical Recovery Started. 09:47:42 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks However: informix@machinename$ onstat -shared memory not initialized for INFORMIXSERVER 'newworld' The results of the oninit -v are: Checking group membership to determine server run modesucceeded Reading configuration file '/apps/informix_ids/etc/onconfig.newworld'...succeeded Creating /INFORMIXTMP/.infxdirs ... succeeded Creating infos file "/apps/informix_ids/etc/.infos.newworld" ... "/apps/informix_ids/etc/.conf.newworld" ... succeeded Writing to infos file ... succeeded Checking config parameters...succeeded Allocating and attaching to shared memory...succeeded Creating resident pool 143252 kbytes...succeeded Creating buffer pool 524290 kbytes...succeeded Initializing rhead structure...succeeded Initializing ASF ...succeeded Initializing Dictionary Cache and Stored Procedure Cache...succeeded Bringing up ADM VP...succeeded Creating VP classes...succeeded Onlining 4 additional cpu vps...succeeded Onlining 18 IO vps...succeeded Forking main_loop thread...succeeded Initialzing DR structures...succeeded Forking 1 'ipcshm' listener threads...succeeded Forking 2 'soctcp' listener threads...succeeded Forking 1 'ipcshm' listener threads...succeeded Forking 0 'soctcp' listener threads...succeeded Forking 0 'soctcp' listener threads...succeeded Starting tracing...succeeded Initializing 32 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 Checking database partition index...FAILED oninit: Fatal error in shared memory initialization I realise that it is unlikely that too many people are out there right at this moment, however, I have been working on this issue so long now that I am loosing track of time, Does anyone have any ideas as to how to get this online, I do have a vague recollection of an issue like this in the past that was resolved quite simply. I am attempting to contact IBM Support on the issue although it is a moderately complex task out of hours when I cannot locate the support contracts etc... Clifford Burton Senior Database Administrator SIMplus Mobile Pty Ltd [ www.SIMplus.com.au <http://www.simplus.com.au/>; ] Ph: (02) 9028 1716 Fx: (02) 9030 6284 Em: Clifford_Burton@SIMplus.com.au <mailto:Clifford_Burton@SIMplus.com.au> SIMplus Mobile Pty Ltd ABN 37 098 145 218. SIMplus is the trademark of SingTel Optus Ltd trading as Optus Communications. ---------------------------------------------------- This message is for the named person's use only. Privileged/confidential information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message, and notify us immediately. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. ---------------------------------------------------- sending to informix-list

Am I missing something here? Wouldn't you expect, at the end of the restore, the database to be sitting in quiescent mode expecting you to bring it onlone with an onmode -m? What then was the necessity to do the oninit? Or am I very old and confused? "Burton, Clifford" <clifford_burton@simplus.com.au> wrote in message news:1106381417.1c1a8c8b9eef6b87f2adabdb982013d7@teranews... > > > Hi All, > > I have a situation where the IDS-731UD4 instance I run on HP-UX 11 is > failing after a cold restore. > > I do not have time to perform another restore without serious business > ramifications. > > The output from the log file is: the last lines: > 09:47:30 Could not create single shared memory segment with resident and> non-re sident partitions. Proceeding to create 2 shared memory segments > instead. > 09:47:32 Segment locked: addr=0xc1841000, size=683679744> > Sat Jan 22 09:47:32 2005 > > 09:47:32 Event alarms enabled. ALARMPROG = > '/apps/informix_ids/etc/ifx_alert.sh' > 09:47:38 DR: DRAUTO is 0 (Off) > 09:47:39 Dynamically allocated new message shared memory segment (size > 1104KB) > > 09:47:39 Informix Dynamic Server Version 7.31.UD1 Software Serial> Number > AAD > #J216570 > 09:47:39 Informix Dynamic Server Initialized -- Shared Memory> Initialized. > 09:47:39 Physical Recovery Started. > 09:47:39 Physical Recovery Complete: 0 Pages Restored. > 09:47:39 Logical Recovery Started. > 09:47:42 Logical Recovery Complete.> 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks > > However: > > informix@machinename$ onstat -> shared memory not initialized for INFORMIXSERVER 'newworld' > > The results of the oninit -v are: > > Checking group membership to determine server run modesucceeded Reading > configuration file '/apps/informix_ids/etc/onconfig.newworld'...succeeded > Creating /INFORMIXTMP/.infxdirs ... succeeded Creating infos file > "/apps/informix_ids/etc/.infos.newworld" ... > "/apps/informix_ids/etc/.conf.newworld" ... succeeded Writing to infos > file > ... succeeded Checking config parameters...succeeded Allocating and > attaching to shared memory...succeeded Creating resident pool 143252 > kbytes...succeeded Creating buffer pool 524290 kbytes...succeeded > Initializing rhead structure...succeeded Initializing ASF ...succeeded > Initializing Dictionary Cache and Stored Procedure Cache...succeeded > Bringing up ADM VP...succeeded Creating VP classes...succeeded Onlining 4 > additional cpu vps...succeeded Onlining 18 IO vps...succeeded Forking > main_loop thread...succeeded Initialzing DR structures...succeeded Forking > 1 > 'ipcshm' listener threads...succeeded Forking 2 'soctcp' listener > threads...succeeded Forking 1 'ipcshm' listener threads...succeeded > Forking > 0 'soctcp' listener threads...succeeded Forking 0 'soctcp' listener > threads...succeeded Starting tracing...succeeded Initializing 32 > 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 Checking database partition index...FAILED > oninit: Fatal error in shared memory initialization > > > I realise that it is unlikely that too many people are out there right at > this moment, however, I have been working on this issue so long now that I > am loosing track of time, Does anyone have any ideas as to how to get this > online, I do have a vague recollection of an issue like this in the past > that was resolved quite simply. I am attempting to contact IBM Support on > the issue although it is a moderately complex task out of hours when I > cannot locate the support contracts etc... > > Clifford Burton > Senior Database Administrator > SIMplus Mobile Pty Ltd [ www.SIMplus.com.au > http://www.simplus.com.au/>; ] > Ph: (02) 9028 1716 > Fx: (02) 9030 6284 > > Em: Clifford_Burton@SIMplus.com.au <mailto:Clifford_Burton@SIMplus.com.au> > > SIMplus Mobile Pty Ltd ABN 37 098 145 218. > SIMplus is the trademark of SingTel Optus Ltd trading as Optus > Communications. > > ---------------------------------------------------- > > This message is for the named person's use only. > > Privileged/confidential information may be contained in > this message. If you are not the addressee indicated in > this message (or responsible for delivery of the message > to such person), you may not copy or deliver this > message to anyone. In such case, you should destroy > this message, and notify us immediately. > > Any views expressed in this message are those of the > individual sender, except where the message states > otherwise and the sender is authorised to state them to > be the views of any such entity. > ---------------------------------------------------- > sending to informix-list

Neil Truby wrote: > Am I missing something here? Wouldn't you expect, at the end of the > restore, the database to be sitting in quiescent mode expecting you to bring > it onlone with an onmode -m? What then was the necessity to do the oninit? > > Or am I very old and confused? > > "Burton, Clifford" <clifford_burton@simplus.com.au> wrote in message > news:1106381417.1c1a8c8b9eef6b87f2adabdb982013d7@teranews... > >> >>Hi All, >> >>I have a situation where the IDS-731UD4 instance I run on HP-UX 11 is >>failing after a cold restore. >> >>I do not have time to perform another restore without serious business >>ramifications. >> >>The output from the log file is: the last lines: >>09:47:30 Could not create single shared memory segment with resident and>>non-re sident partitions. Proceeding to create 2 shared memory segments >>instead. >>09:47:32 Segment locked: addr=0xc1841000, size=683679744>> >>Sat Jan 22 09:47:32 2005 >> >>09:47:32 Event alarms enabled. ALARMPROG = >>'/apps/informix_ids/etc/ifx_alert.sh' >>09:47:38 DR: DRAUTO is 0 (Off) >>09:47:39 Dynamically allocated new message shared memory segment (size >>1104KB) >> >>09:47:39 Informix Dynamic Server Version 7.31.UD1 Software Serial>>Number >>AAD >>#J216570 >>09:47:39 Informix Dynamic Server Initialized -- Shared Memory>>Initialized. >>09:47:39 Physical Recovery Started. >>09:47:39 Physical Recovery Complete: 0 Pages Restored. >>09:47:39 Logical Recovery Started. >>09:47:42 Logical Recovery Complete.>> 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks >> >>However: >> >>informix@machinename$ onstat ->>shared memory not initialized for INFORMIXSERVER 'newworld' >> >>The results of the oninit -v are: >> >>Checking group membership to determine server run modesucceeded Reading >>configuration file '/apps/informix_ids/etc/onconfig.newworld'...succeeded >>Creating /INFORMIXTMP/.infxdirs ... succeeded Creating infos file >>"/apps/informix_ids/etc/.infos.newworld" ... >>"/apps/informix_ids/etc/.conf.newworld" ... succeeded Writing to infos >>file >>... succeeded Checking config parameters...succeeded Allocating and >>attaching to shared memory...succeeded Creating resident pool 143252 >>kbytes...succeeded Creating buffer pool 524290 kbytes...succeeded >>Initializing rhead structure...succeeded Initializing ASF ...succeeded >>Initializing Dictionary Cache and Stored Procedure Cache...succeeded >>Bringing up ADM VP...succeeded Creating VP classes...succeeded Onlining 4 >>additional cpu vps...succeeded Onlining 18 IO vps...succeeded Forking >>main_loop thread...succeeded Initialzing DR structures...succeeded Forking >>1 >>'ipcshm' listener threads...succeeded Forking 2 'soctcp' listener >>threads...succeeded Forking 1 'ipcshm' listener threads...succeeded >>Forking >>0 'soctcp' listener threads...succeeded Forking 0 'soctcp' listener >>threads...succeeded Starting tracing...succeeded Initializing 32 >>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 Checking database partition index...FAILED >>oninit: Fatal error in shared memory initialization >> >> ... Well, the engine was shutdown at the end of the restore as opposed to finishing off answering the final questions. You can either ... do the restore completely, and monitor the window where the restore was run from ... DO NOT CLOSE IT. Or you could try running oninit -r and then onmode -m when the engine gets into fast recovery. This MAY work depending on what has happened to the instance after the "prematurely ended" restore.