Re: Datapump and read only database

Brian Peasland <dba_at_nospam.peasland.net> writes:

> Lothar Armbrüster wrote:

[...]
>> I could stick with exp/imp or set up a second small instance on the
>> standby server which will be read/write and just exist to do the
>> datapump remotely on the standby database. I also could do the
>> datapump remotely on the primary site but that would run over the
>> network and put some load on the primaray database which I want to
>> avoid.
>>

[...]
>
> You can still use exp/imp but there may be a future version of Oracle
> where these are not available.
>
> You can invoke the datapump utilities from a remote server, but the
> master table is still created on the target server, so that will not
> solve your problem.

Well, then I have to find another way. I might remember reading somewhere on google that datapumping a read only database remotely is possible though. I'll check that in the docs. Maybe there is some hidden option. ;-)

>
> Any reason why you cannot perform your export operation on the primary
> server and not the standby? What will this dump be used for?
>

As I wrote in answer to Steve's posting, the export is part of our backup strategy.
The main reason to export the standby and not the primary database is to keep some load away from the primary database. Another reason is that an export on the read only standby database is always consistent so I do not run into ORA-1555 (hope I'm remembering the number for "snapshot too old" coerrectly :-) when running a consistent export on a database with havy batch load on it.

[...]

Regards,
Lothar

-- 
Lothar Armbrüster  | lothar.armbruester_at_t-online.de
Hauptstr. 26       |
65346 Eltville     |