Re: Datapump export, incremential only?
Date: Wed, 10 Aug 2011 20:40:29 -0300
Message-ID: <CAJ2dSGSndkBhyzoXhMy5tTa+2NR++U26qxuC1SoBz-_72eFcnw_at_mail.gmail.com>
I have only one question: do you expect this dapump dumps to be your database backup? if so, please think again.
If you are using DP Exports to have "snapshots" of the database, might I suggest taking a look at flashback?
Also, if you are actually worried that this will come back and bite you, why not attempting to recover the database from this "backup" (and I use the term loosely), that way you can have a documentation of what will be required and you won't have to struggle with parameters and stuff during an actual recovery situation. We call this a DRE (Disaster Recovery Excercise).
hth
Alan.-
On Wed, Aug 10, 2011 at 8:06 PM, Gus Spier <gus.spier_at_gmail.com> wrote:
> Chris, is there some way to use the datapump WHERE clause to set your
> defined criteria for an incremental datapump export? Of course, if the
> tables don't have a TIMESTAMP compatible column, that might be problematic.
>
> I suspect that big Oracle advocates RMAN solutions over datapump
> incremental backups. That might account for the absence of your datapump
> solution.
>
> Regards,
> Gus
>
>
> On Wed, Aug 10, 2011 at 5:44 PM, Grabowy, Chris <chris.grabowy_at_lmco.com>wrote:
>
>> We have been struggling with having Datapump exports complete every
>> night. Sometimes with execution times. Other cases with dump file sizes.
>> ****
>>
>> ** **
>>
>> We added the compress option and that helped with generating smaller dump
>> files with no obvious impact to the execution time, but that hasn’t really
>> helped with the overall execution time. ****
>>
>> ** **
>>
>> We have played with the parallel option with some success.****
>>
>> ** **
>>
>> Anyway one of the DBAs updated the script to generate a datapump parm file
>> that contains a list of the tables that changed in the last two days. Even
>> though we execute datapump every night he felt it would be safer to generate
>> a list of changed tables for the last two days. He generates the list of
>> changed tables by querying dba_tab_modifications. With this change, the
>> datapump exports are obviously faster and the dump files much smaller.***
>> *
>>
>> ** **
>>
>> We still do a weekly full datapump export on Sundays.****
>>
>> ** **
>>
>> Anyway, were kind of scratching our heads and trying to figure out if this
>> could come back and bite us somehow. Paranoia is a required DBA trait…**
>> **
>>
>> ** **
>>
>> We do understand that when importing we might have to go back to the
>> Sunday save to import a table since it might have not been saved in any of
>> the incrementals. We are saving/organizing the log files to easily grep for
>> the desired table.****
>>
>> ** **
>>
>> I know that incremental was not a stable/valid option in the old export
>> tool, but you would think that Oracle would have figured out how to do
>> incremental datapump exports by now…using some sort of defined criteria. At
>> least, looking thru the doc I did not find such an option. Am I just being
>> naïve here and missing the bigger picture on the viability of a
>> datapump/export incremental feature?****
>>
>> ** **
>>
>> Thoughts? Suggestions? Insults?****
>>
>> ** **
>>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 10 2011 - 18:40:29 CDT