Re: Unloading a live database

Agreed, but what about replication? It's a more difficult solution requiring a solid network, more work, and pretty much the same configuration in dbspaces as the full or selected dbspace restore from backup. A simple solution on any Informix database is dbexport, but this locks the database, whereas a backup, at least with Dynamic Server gives you the database as of the last checkpoint. Yours, Nick On Thu, 5 Aug 1999, Doug Agnew wrote: > Since the second instance may not be similar enough, I gather that you would > be planning to restore tables to different dbspaces than their original > locations. If so, then you would need a table level backup and restore, > true?? In that case, I think the solution offered is probably about the > best you're going to get. BUT, the tables will NOT be synchronized to the > beginning of the unloads. > > Or, if all the tables you want are in a set of dbspaces that do not exist in > the second instance, could you do define the dbspaces in the second instance > and then do a dbspace-level restore of an ontape backup (think this would > work with ontape, but don't quote me)?? > > Just my humble, and often wrong (which is why no one wants them), opinion > > Doug > > Alanoly Andrews wrote in message <7oc4hi$ib$1@news.xmission.com>... > > > > > >Thanks. But it does not actually solve my problem. What I need to > >unload is an entire "database" containing about 100 tables. Your > >answer is for unloading single tables. Is there a way to unload the > >database without interrupting updates to tables in the database? > >What I need is a "snapshot" of the database at the time the unload > >command is issued. "dbexport" takes an exclusive lock on the DB > >and "onunload" takes a shared lock. So, neither of these is suitable. > >The "load" is not a problem because it will be on a different instance. > >"ontape" seems to be out because the second instance is not > >guaranteed to have the same DBspace configurations as the first. > > > >Informix Dynamic Server 7.31 > >AIX 4.3 > > > >Thanks. > > > >Alanoly J. Andrews > > > >> -----Original Message----- > >> From: Pons Roca, Isidre [SMTP:ipons@dtgna.altanet.org] > >> Sent: Thursday, August 05, 1999 3:00 AM > >> To: informix-list@iiug.org > >> Subject: Re: Unloading a live database > >> > >> En Alanoly Andrews va escriure el dia 4 Aug 99, a les 9:23: > >> > >> Option 1: > >> from dbaccess do: > >> unload to "file" select * from <table name> --> this in> >> instance 1 > >> load from "file" insert into <table_name> --> this in instance> >> 2 > >> > >> Option 2: > >> from dbaccess in instance 1 do: > >> insert into databasename@informixservername:table select * > >> from <table name>> >> > >> Suggestion: > >> Put the database in the second instace WITH NO LOG. > >> To do that use ontape. > >> > >> Be fun. > >> > >> > >> > > >> > Hi, > >> > > >> > I need to unload a "database" while the instance is running > >> > and accepting updates on the database. I see that the "onunload" > >> > utility of Informix takes a lock on the database and does not allow > >> > users to modify the Database during the unload process. > >> > The unloaded database is to be loaded into another instance > >> > which need not have the same DBspace configurations as the > >> > first instance. This seems to rule out the use of archiving utilities > >> like > >> > "ontape" which require identical DBspace configurations for a restore. > >> > > >> > I'd appreciate your input into solving this problem. > >> > > >> > Thanks. > >> > > >> > Alanoly J. Andrews > >> > > >> > >> > >> > >> --------------------------------------- > >> Isidre PONS ROCA > >> BASE - Gesti' d'Ingressos Locals > >> (Diputacio de Tarragona) > >> Servei de Sistemes de Informacio > >> Av President Lluis Companys 12-C > >> 43005 - Tarragona > >> SPAIN > >> Tel # +34 977 236731 > >> Fax # +34 977 227302 > >> http://www.altanet.org > >> ipons@dtgna.altanet.org > >> --------------------------------------- > > >