EXPORT DATA FROM ORACLE STANDBY DATABASE

 

EXPORT DATA FROM ORACLE STANDBY DATABASE

EXPORT OBJECTS FROM ORACLE STANDBY DATABASE INSTEAD OF PRODUCTION DATABASE 

During peak business hours, firing export from production might impact the performance.

So if we have a physical standby database (ACTIVE DATAGUARD), we can export data using datapump from standby database.

IMPORTANT POINTS TO NOTE:

• Physical standby database (ACTIVE DATA GUARD) should be in READ-ONLY MODE.
• EXPDP can't be directly run on physical standby database. As datapump job/MASTER Table can be created only on a read-write database.
• So, we will use the NETWORK_LINK parameter and run the expdp job from PRODUCTION database.

STEPS:

1. CHECK THE STANDBY DATABASE OPEN STATUS.

2. CREATE A DATABASE LINK [DBLINK] FROM PROD TO STANDBY. 

3. CREATE A DIRECTORY FOR DATAPUMP AT PRODUCTION DATABASE.

create directory EXPDP_STANDBY as '/backup/export';

grant read,write on directory EXPDP_STANDBY to public;

4. RUN THE EXPDP COMMAND AT PROD DB.

expdp directory=EXPDP_STANDBY network_link=DB_LINK_TO_READ dumpfile=vmrltable.dmp logfile=vmrltabledmp.log tables=vmrl.PURODT_HT

We have successfully generated the export dump from standby database on production database.

5. EXPDP DUMPFILE and LOGFILE. 

6. FROM THE LONGOPS CHECK THE TIME REMAINING

7. FROM THE DATAPUMP_JOBS FIND THE RUNNING JOBS

8. SEE THE STATUS OF RUNNING EXPORT [ATTACH THAT JOB]

9. SEE THE STATUS OF ATTACHED JOB

10.HOW TO KILL THE JOB AFTER BEING ATTACHED





























































11.FOLLOWING COMMANDS CAN RUN ON DATAPUMP EXPORT PROMPT










































12. HOW TO EXECUTE EXPORT COMMAND IN BACKGROUND