Recovering a single dbspace.

Hi group! Due to a bug in a program of ours, I must recover a backup from a week ago. The problem is that I am only interested in one table, the rest of the db must remain as it is. I read in a previous message here that there are special tools for recovering single tables. But isn't there a way to recover a dbspace to a new, temporary, database? Then it would be easy for us to select what we want from the new database into the production-database. I have read the Archive and Backup Guide, which describes how to do a partial recovery, but it doesn't mention creating a new db out of a backup. We're running Informix 7.22 on Solaris 2.6, using ontape to dump to filesystem, then taping the dumps on an NT-box. Any help much appreciated, Johan Wikstr'm -- Johan Wikstr'm Commentor AB Tel: 08-744 10 00 Mail: johan.wikstrom@commentor.se

Johan Wikström wrote: > > Hi group! > > Due to a bug in a program of ours, I must recover a backup from > a week ago. The problem is that I am only interested in one table, > the rest of the db must remain as it is. I read in a previous message > here > that there are special tools for recovering single tables. > But isn't there a way to recover a dbspace to a new, temporary, > database? > Then it would be easy for us to select what we want from the new > database > into the production-database. I have read the Archive and Backup Guide, > which describes how to do a partial recovery, but it doesn't mention > creating > a new db out of a backup. > > We're running Informix 7.22 on Solaris 2.6, using ontape to dump to > filesystem, > then taping the dumps on an NT-box. You can create a new instance, on a different machine since all of the file/device names must be identical to those on source machine of the archive, and restore just the rootdbs and the dbspace you need. Then bring the engine online and extract the data. If you do not have a machine where the chunknames are not already being used for something you have no recourse but to download June's arcunload program (and possibly also my on_to_unload.ec program) from the Special Software section of the IIUG Software Repository and extract just the one table from the archive files. You can then use onload to reload the table from the arcunload output or post-process the output with my on_to_unload.ec creating a delmited file you can edit and select data from to reload with dbload or dbaccess->load. Art S. Kagel

Johan Wikström wrote: > Due to a bug in a program of ours, I must recover a backup from > a week ago. The problem is that I am only interested in one table, > the rest of the db must remain as it is. I read in a previous message > here > that there are special tools for recovering single tables. > But isn't there a way to recover a dbspace to a new, temporary, > database? No, there isn't. There is dbspace-level recovery *only back into the original instance*, and it then requires logical recovery to sync it back up with the rest of the system, which would effectively re-play your bug. Only the entire instance can be recovered to a new, temporary instance. Now you know why I had to write the "special tool" ;-) June -- june_t@hotmail.com Grounded in Palo Alto, living on M&M's (plain)