What about using the filesize parameter and the file wildcard (numeric
numbering) to have the export written to a series of datafiles. You should
then be able to pick up the closed export files and compress them while the
export is still generating additional export files.
-- Mark D Powell --
Phone (313) 592-5148
------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Leng Kaing
*Sent:* Tuesday, January 09, 2007 5:22 PM
*To:* rjamya
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* RE: Data Pump and compress on the fly in Unix
So how are you guys dealing with this problem then? The mknod allowed us
to export huge databases without needing the space up-front. Is there anyone
using DATA PUMP for real backups of large datababases? Or just experimenting
with it?
I realise that there's a COMPRESS=METADATA_ONLY option but this is just
the METADATA, not the huge amounts of application data that we have in the
database.
Oracle has told us to use datapump in 10g rather than exports. Now I have
a problem – BAM uses floating data types that is not supported with exp but
is supported with expdp. However, expdp does not allow compression on the
fly. I'm stuck. I can't possibly convert to data pump given the lack of
space available to perform the expdp.
------------------------------
*From:* rjamya [mailto:rjamya@xxxxxxxxx]
*Sent:* Tuesday, 9 January 2007 10:50 PM
*To:* Leng Kaing
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: Data Pump and compress on the fly in Unix
no, and it is not supported even in 10203, Larry knows that would happen
in 11.
rjamya
On 1/9/07, *Leng Kaing* < Leng.Kaing@xxxxxxxxxxx> wrote:
I think the question has been asked before but I'm hoping that 10.2.0.3has changed
things – can we do a compress on the fly with expdb now? Ie.
using mknod. Has anyone managed to get this to work?
