peter, July 03, 2016 - 11:50 am UTC
I want to know will that offload the expdp from the primary node during the backup process
Note : I try 1st solution but I want to confirm that the expdp will run from primary node as I run on standby node and get the error I mentioned above
July 04, 2016 - 1:38 am UTC
that is correct - you are running 'expdp' on *any* read/write node.
Detailed steps on using Snapshot Standby
Gary, September 26, 2016 - 5:42 pm UTC
Connor
Can you please point me to any detailed instructions on how to convert a Physical Standby to a Snapshot Standby and back agian?
I have two (2) databases (11.2.0.4 EE), I can perform the above perfectly on one of them but not the other and am trying to see what differences there are in the DB setup between the two.
It has something to do with the Flashback setup as I always get the error message about the 'Flashback logs not available' or something like that on the one that doesn't work.
I follow the same steps on both so I'm assuming there's something different in the DB params or something.
Any help is greatly appreciated!!!
September 27, 2016 - 1:34 am UTC
The restore point / flashback is all handled for you. So it should just be case of:
snapshot
========
shutdown immediate;
startup mount;
alter database convert to snapshot standby;
shutdown immediate;
startup;
back to physical
================
shutdown immediate
startup mount exclusive
alter database convert to physical standby;
shutdown immediate
startup mount exclusive
alter database recover managed standby database using archived logfile delay 60 disconnect;
expdp on Physical standby - Measuring Performance impact
Dave, August 28, 2019 - 6:00 pm UTC
Hi Connor/Team - you mentioned that expdp on physical standby can be performed with reference to MOS note 1356592.1
I tested it on my production database-Primary (A) issuing expdp and pointing to physical standby (B) with network_link .
ours is an OLTP environment and we want to offload the expdp to our dataguard databases to reduce the load on our Primary databases.
1) where is the memory,cpu,I/o resource consumption caused ?
will it be on the Primary or in standby ?
2) how can i check if the primary or dataguard resources (I/O,cpu,memory) are being hit ? Are there any helpfull queries to run on both Primary & Dataguard and validate the output ?
Thank you in advance !
September 03, 2019 - 5:26 am UTC
You'll be able to see "worker" sessions running for the export, which do the vast bulk of the work (ie, reading the database data).
But the easiest way to ensure that production node is not involved, is to not use it, ie, use any other server as a the originating node and connect to the standby from that.
How To Use DataPump Export (EXPDP) To Export From Physical Standby Database (Doc ID 1356592.1)
Antonysamy, August 06, 2020 - 11:24 am UTC
I have tried this method on multitenant database.
I have created the DB link on non-standby PDB and DB link works.
SQL>create database link expdp_primary connect to mig_ora identified by XXXX using '(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = exacc1-scan.us2.ocm.s7036075.oraclecloudatcustomer.com)(PORT = 1521)) (CONNECT_DATA = (UR=A) (SERVER = DEDICATED) (SERVICE_NAME = HRPSPP_DR.us2.ocm.s7036075.oraclecloudatcustomer.com) (FAILOVER_MODE = (TYPE = select) (METHOD = basic))))';
SQL> select db_unique_name from v$database;
DB_UNIQUE_NAME
------------------------------
XEPS1Q
SQL> select db_unique_name from v$database@expdp_primary;
DB_UNIQUE_NAME
------------------------------
XEPS1R
SQL>
SQL> create directory exp_user_dir as '/oraexport/HRP4Q';
SQL> grant connect,dba to EXP_USER;
expdp EXP_USER/XXX@hrpspq_rw directory=exp_user_dir network_link=expdp_primary full=y dumpfile=standby_database.dmp logfile=standby_database.log
i am getting the below error.
please help me to fix this issue.
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-04054: database link EXPDP_PRIMARY does not exist
ORA-06512: at "SYS.KUPM$MCP", line 2305
ORA-39097: Data Pump job encountered unexpected error -4054
Regards,
Antony A
August 06, 2020 - 4:20 pm UTC
Uh-oh
ORA-39006: internal error => contact support
That said, look closely at this:
ORA-04054: database link EXPDP_PRIMARY does not exist
Verify that you can use the database link when connected as EXP_USER