Oracle EM -> Export DP Options

[peterx]

hi Tim,

If I use EM to Export Data like:

EM -> Data Movement -> Export to Export Files -> Schemas ->

When step 2 -> Export: Options -> Show Advanced Options, it can select:

Code: Select all

Flashback
1. As the specified System Change Number (SCN)
     it show a SCN, i think it is the most current SCN of my DB.

2. As the SCN which most closely matches the specified time
     it show current time.



The question i want to ask is:

For command backup, i can use option like "flashback_time=systimestamp" but inside the EM,
it always give me a SCN number or a time.

If I scheduled this EM task as a scheduled jobs, do you think this SCN will be
updated (every day backup should have different SCN, right?) when each run ?


thanks.

[Tim...]

Hi.

I'm not exactly sure why you would want to use a flashback as part of your export every day anyway. An export isn't a real backup. It's just a logical backup. You would not use it (except as a last resort) for a recovery, so an up to date export would be fine in my opinion.

As for deciding on a specific SCN, you can use the TIMESTAMP_TO_SCN function to work out the SCN each day. For example, midnight each day would be,

Code: Select all

TIMESTAMP_TO_SCN(TRUNC(SYSTIMESTAMP))

I don't know if that will work in EM. I never use this option there.

http://www.oracle-base.com/articles/10g ... _functions

Cheers

Tim...

[peterx]

hi Tim,

Application team request for a exports(from RAC) and import (to UAT ENV.) to another machine for testing.

But, i found that, always exports from RAC and import to UAT will have "sequence duplication error" when
their application run again in the UAT environment.

If I export manually and add options : flashback_time=systimestamp in my command,
this will fix the problem of "sequence duplication error", so I think this option will make the export in a good (in-syn) status.


Then, I do want to have a EM Export job with this option.

As you said before, if i do need to use this

Code: Select all

    TIMESTAMP_TO_SCN(TRUNC(SYSTIMESTAMP))


then, i think EM never have is options for schedule task.

thanks.

[Tim...]

Hi.

OK. I see why now.

Maybe you should schedule this using CRON or the DBMS_SCHEDULER then...

Cheers

Tim...