Database space problem, ontape restore, cannot open chunk.

I'm in the process of trying to do either a full, or partial restore from an ontape archive. I've had a ton of problems, but have made considerable progress trying various permutations of restore options. At this point I can do an ontape -p and restore my primary database spaces. However, when I startup informix (ie. oninit) I get this error: > oninit oninit: Cannot open chunk '/black/informix/dbspace/tempdbs1'. See online message log. oninit: Cannot open chunk '/black/informix/dbspace/tempdbs2'. See online message log. oninit: Cannot open chunk '/black/informix/dbspace/tempdbs3'. See online message log. > oninit: Fatal error in shared memory initialization From what I can tell, the temp database spaces were not included in the backup, and therefore not restored with the others. So, I tried to first create the database spaces listed above, and then perform the restore, but as I expected the restore itself pretty much whacks any existing information. I cannot get the database in a usable mode since it never initializes shared memory, etc...so I cannot use onmonitor to manually create the missing database spaces. Does anyone know what I can do to overcome this? I need to get the restored data back ASAP. Any assistance will be greatly appreciated. -db Dave Brookshire <david@NOSPAMmagnet.com> Magnet Interactive Group, Inc. "Everybody happy but Zathras...but Zathras never happy...Zathras happy once, had friend once, but wheels fell off, very sad..." - JMS

Dave Brookshire wrote: > > I'm in the process of trying to do either a full, or partial restore > from an ontape archive. I've had a ton of problems, but have made > considerable progress trying various permutations of restore options. > At this point I can do an ontape -p and restore my primary database > spaces. However, when I startup informix (ie. oninit) I get this error: This is your first problem. Ontape -p is for physical restore used to initiate a replicant (slave) server for HDR (Hierarchical Data Replication). To restore your server use "ontape -r". If you want to do a minimal cold restore (ie rootdbs only) use "ontape -r -D rootdbs". Then you can bring the engine online and do warm restores of the other dbspaces: "ontape -r -D dbspace1, dbspace2, dbspace3...". Before restoring you must make certain that all of the files/devices exist. In other words if the files mentioned below (the tempdbs? files) are cooked files (filesystem space) they must exist if it is a link to a raw device then the link must exist and if a softlink it must point to an actual device. The permissions of the files and/or devices must be owner: informix, group: informix, chmod: 0660. > > oninit > oninit: Cannot open chunk '/black/informix/dbspace/tempdbs1'. See online message log. > oninit: Cannot open chunk '/black/informix/dbspace/tempdbs2'. See online message log. > oninit: Cannot open chunk '/black/informix/dbspace/tempdbs3'. See online message log.> > oninit: Fatal error in shared memory initialization > > From what I can tell, the temp database spaces were not included in > the backup, and therefore not restored with the others. They are not, however, their existence is required at restore time. It is not necessary to restore the tempdbspaces since the engine startup will wipe them out anyway. > So, I tried to first create the database spaces listed above, and then > perform the restore, but as I expected the restore itself pretty much > whacks any existing information. You do not need to run onspaces/onmonitor to create the dbspaces, they will be restored, from the engine's perspective, by ontape. However, the files or devices must exist as stated above. > I cannot get the database in a usable mode since it never initializes > shared memory, etc...so I cannot use onmonitor to manually create the > missing database spaces. > Does anyone know what I can do to overcome this? I need to get the > restored data back ASAP. Any assistance will be greatly appreciated. Art S. Kagel

In article <78ik1a$f2e@lemur.magnet.com>, Dave Brookshire <david@NOSPAMmagnet.com> wrote: > I'm in the process of trying to do either a full, or partial restore > from an ontape archive. I've had a ton of problems, but have made > considerable progress trying various permutations of restore options. > > At this point I can do an ontape -p and restore my primary database > spaces. However, when I startup informix (ie. oninit) I get this error: > > > oninit > oninit: Cannot open chunk '/black/informix/dbspace/tempdbs1'. See onlinemessage log. > oninit: Cannot open chunk '/black/informix/dbspace/tempdbs2'. See online message log. > oninit: Cannot open chunk '/black/informix/dbspace/tempdbs3'. See online message log. > > oninit: Fatal error in shared memory initialization > > From what I can tell, the temp database spaces were not included in > the backup, and therefore not restored with the others. > > So, I tried to first create the database spaces listed above, and then > perform the restore, but as I expected the restore itself pretty much > whacks any existing information. > > I cannot get the database in a usable mode since it never initializes > shared memory, etc...so I cannot use onmonitor to manually create the > missing database spaces. > > Does anyone know what I can do to overcome this? I need to get the > restored data back ASAP. Any assistance will be greatly appreciated. > > -db > > Dave Brookshire <david@NOSPAMmagnet.com> > Magnet Interactive Group, Inc. > > "Everybody happy but Zathras...but Zathras never happy...Zathras happy > once, had friend once, but wheels fell off, very sad..." - JMS > > Don't use 'ontape -p' as it is for use with HDR only. Instead, try a full restore using 'ontape -r'. Also, make sure that /black/informix/dbspace/tempdbs1,2,3 exist. If not and they are cooked files 'touch' them and make sure permissions are informix:informix 660. If these are soft links to other devices, make sure the links still exist and that the devices have informix:informix 660 permissions. When the files and/or links exist with the correct permissions, the restore will take care of creating the dbspaces. Bob --------- -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own