why not take the size of the tablespaces with data(not indexes, u do have your indexes in separate tablespaces right?), divide by 1.9G and put that many filenames on the command line, you can't have too many, oracle wont use the extra but if you're short, you lose.
 
joe


>>> [EMAIL PROTECTED] 09/19/01 02:10PM >>>

any idea on how to estimate the export dump file size without doing an actual export (not even to /dev/null)?
the idea is to use filesize option of export utility to export db to several files.
i am aware of using pipe/split to do large export.

thanks, bill

Reply via email to