Re: Datapump and read only database

Brian Peasland <dba_at_nospam.peasland.net> writes:

[...]
>
> I forgot about the network link option and it looks like it will solve
> your problem. To me, running DP remotely involves using invoking as
> follows:
>
> expdp system/manager_at_remote_db .....
>
> The above will still create the master table in the "remote" database,
> which if it is read-only, will result in an error. But the
> NETWORK_LINK parameter runs DP on a different server, places the
> master table a database there, but lets you run this dumping from a
> read-only database. Please see the docs on that link here:
>
> http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_import.htm#sthref319
>

It's good to read that my memory still works, mostly ;-)

>>> 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.
>>
>
> Since you are on 10g, if someone accidentally drops a table, then the
> FLASHBACK TABLE TO BEFORE DROP is preferable to importing from a dump
> file. And if someone accidentally deleted rows from a table, then a
> Flashback Query might be better to restore those rows. There are many,
> many more options in 10g for recovering these sorts of things than a
> dump file. They might bear investigation to determine if they will fit
> your needs and how they work in your specific environment.

You are surely right pointing me to flashback. This is what I'm using if someone accidently deleted some rows. But there are cases when someone realizes that days or months later and undo_retention is 3 hours. In these cases the only chance is to import the table from backup into another schema and fix the deletes.

[...]

Regards,
Lothar

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