Re: Dbexport

mbaumgartner@cardhealth.com wrote: > Last week there was a thread that asked how long it would take to dbexport a 28 > Gig db. Well this past weekend we were trying to dbexport a 68 Gig db only to > have it blow up when one of the .unl files reached 2 Gig. > <snip> Mark, I would recommend the use of a named pipe to which you can write the output and use the pipe to save into a file, even a compress and save. The compress could give you about 3 to 7 (depending on data type) times reduction in size. I wouldn't dare to use dbexport, mainly because of the problems that may occur during restore, in addition to long transactions, etc. I would prefer simple unload of schema and tables into named pipe, compress and save/tar into file(s)). For restoring create the database using the schema, disable triggers of all tables and cat/tar into pipe, uncompress and perform a dbload. Otherwise use ontape or some other utilities like that. -- Have a nice day Felix K. Mathews mailto:fmathews@systems.dhl.com