RE: Export datapump is INCONSISTENT

Brandon,

Thanks for bringing this to our attention. Legacy mode is actually a new 
feature in 11gR2 data pump:

http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/dp_legacy.htm

"If you use original Export (exp) and Import (imp), then you may have
scripts you have been using for many years. To ease the transition...
Oracle strongly recommends that you view the new syntax and make script 
changes as time permits
...
CONSISTENT
Data Pump Export determines the current time and uses FLASHBACK_TIME."

The Help for the expdp and impdp hasn't caught up.

Legacy mode parameters may have some minor bugs, as in case of indexes 
(Bug 9208389), touser (Bug 9444023). Because of the word "legacy" and 
Oracle's recommendation, I think it's good practice to not use them. 
Oracle apparently added this support to make old scripts work without 
change (I wish it had come earlier), not, unfortunately, as your 
enhancement request would like. But I agree permanently supporting 
"consistent=y" would be ideal.

Yong Huang


--- On Fri, 6/17/11, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote:

> All,
> 
> I just found that Oracle has quietly added support for the
> old CONSISTENT parameter back in data pump.  I'm not
> sure exactly when they added it and I couldn't find any
> documentation of it in the online docs or on MOS, other than
> a mention of it in bug 9243068.  I filed an enhancement
> request for this (bug 12360744) and they accepted it, but
> they never told me they already made the enhancement in
> 11g.  However, I tested it on an 11.2.0.1 database on
> Windows, with patch bundle 6 installed, and it definitely
> works as you can see below - notice it says it's in "Legacy
> Mode" so I'm not sure what all the implication of that
> are.  It works with both "consistent=y" and
> "consistent=true".  I also found that setting
> flashback_time=systimestamp works in 11.2.0.1 and it doesn't
> give the "Legacy Mode" message, so maybe that's a better
> option.  Neither of these parameters worked in another
> 10.2.0.4 database that I tested.  I haven't tried any
> other versions yet.
> 
> E:\xyzdevDBExports>expdp system/pwd@xyzdev
> tables=tridata.T_CLASSIFICATION,tridata.t_tristatus
> consistent=y dumpfile
> =xyzdev_tst logfile=xyzdev_tst
> 
> Export: Release 11.2.0.1.0 - Production on Fri Jun 17
> 10:15:30 2011
> 
> <snip>
> 
> Legacy Mode Active due to the following parameters:
> Legacy Mode Parameter: "consistent=TRUE" Location: Command
> Line, Replaced with:
> "flashback_time=TO_TIMESTAMP('2011-06-17
>  10:15:30', 'YYYY-MM-DD HH24:MI:SS')"
> Legacy Mode has set reuse_dumpfiles=true parameter.
> 
> <snip>
> Job "SYSTEM"."SYS_EXPORT_TABLE_01" successfully completed
> at 10:15:36
> 
> 
> E:\xyzdevDBExports>expdp system/pwd@xyzdev
> tables=tridata.T_CLASSIFICATION,tridata.t_tristatus
> flashback_time=systimestamp dumpfile=xyzdev_tst
> logfile=xyzdev_tst
> 
> Export: Release 11.2.0.1.0 - Production on Fri Jun 17
> 10:37:46 2011
> 
> <snip>
> 
> Starting "SYSTEM"."SYS_EXPORT_TABLE_01": 
> system/********@xyzdev
> tables=tridata.T_CLASSIFICATION,tridata.t_tristatus fla
> shback_time=systimestamp dumpfile=xyzdev_tst
> logfile=xyzdev_tst
> 
> <snip>
> 
> Job "SYSTEM"."SYS_EXPORT_TABLE_01" successfully completed
> at 10:37:52
> 
> Regards,
> Brandon
> 
> -----Original Message-----
> From: Allen, Brandon
> Sent: Thursday, February 10, 2011 12:13 PM
> To: Yong Huang; Oracle-l Digest Users; Jcmiranda
> Subject: Re: Export datapump is INCONSISTENT
> 
> Thanks Yong and Juan for the helpful info.  I had also
> been under the misconception that data pump was consistent
> by default.  I just wanted to add that MOS Doc ID
> 377218.1 also provides some detail on this topic.  The
> Oracle documentation and expdp output is very misleading on
> this so I wouldn't be surprised if there are many more
> people out there that are also confused and unaware that
> their data pump exports are inconsistent.  I think
> Oracle should either bring back the consistent=y parameter
> for data pump, or add an option for flashback_time=now or
> flashback_scn=current or something like that instead of this
> ridiculously long string that you have to use instead to get
> the same functionality:
> 
>        
> flashback_time="to_timestamp(to_char(sysdate,'yyyy-mm-dd
> hh24:mi:ss'),'yyyy-mm-dd hh24:mi:ss')"
> 
> Maybe I'll file an enhancement request for it.
> 
> Regards,
> Brandon
> 
> 
> 
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Yong Huang
> 
> I did some research on data pump export flashback_time and
> flashback_scn at
> 
> http://yong321.freeshell.org/oranotes/DataPump.txt
--
http://www.freelists.org/webpage/oracle-l


Other related posts: