Re: Onarchive, logging, and dbspace restores

Mark Christmas <mchristmas@crosskeys.com> wrote: >We would like to create a very large table (20Gb) that is fragemented. >The database that this table would be in does not log transactions. This >means that there are no issues with large loads or purges. >One of the features we would like to use, is the ablility archive and >restore a single DBspace at a time. >Using the archiving a single DBspace ability would allow us to create a >new table with a new DBspace, load it, archive it, then attach the new >table to the very large table. At some point, we could then purge that >data and be able to restore it. >My question is - can we actually archive and restore these tables, that >get attached to a large fragemented table, without requiring the logs. >When transaction logging is off, there is still log activity when we >perform an attach, which leads me to believe that the logs might be >required. Mark, In order to restore an individual dbspace, you must use transaction logging and back up your logical log files. If you restore a noncritical dbspace using the last 0 level archive, the chunk(s) for that dbspace will come up in 'PI' status until you do a roll forward of the logical logs also. -- Melvin Mariney, Informix DBA e-mail: melvin.mariney2@bridge.bellsouth.com