Oracle Data Guard _ tablespace for Master/Slave database transmission

8.3.3 Using Transportable Tablespaces with a Physical Standby Database

8.3.3 use of the transmitted tablespace in the physical standby Database

You can use the Oracle transportable tablespaces feature to move a subset of an Oracle database and plug it in to another Oracle database, essential tially moving tablespaces between the databases.

You can use oracle to transmit table space features from a subset of the oracle database to another oracle database, essentially moving Table space in the database.

To move or copy a set of tablespaces into a primary database when a physical standby is being used, perform the following steps:

When the standby database is in use, move or copy a group of tablespaces to the primary database, perform the following steps:

1.

Generate a transportable tablespace set that consists of datafiles for the set of tablespaces being transported and an export file containing structural information for the set of tablespaces.

1. Get the table space set that contains the data to be transmitted, and export the file that contains the framework information of the empty table set.

2. Transport the tablespace set:

2. Transfer the tablespace set

Copy the datafiles and the export file to the primary database.

1. copy the data file and export the file to the master database.

2. Copy the datafiles to the standby database.

2. copy the data file to the slave database.

The datafiles must be copied in a directory defined by the DB_FILE_NAME_CONVERT initialization parameter. if DB_FILE_NAME_CONVERT is not defined, then issue the alter database rename file statement to modify the standby control file after the redo data containing the transportable tablespace has been applied and has failed. the STANDBY_FILE_MANAGEMENT initialization parameter must be set to AUTO.

The data file must be copied to the specified directory for DB_FILE_NAME_CONVERT initialization. If DB_FILE_NAME_CONVERT is not defined, the system contains the redo data of the tablespace to be transferred after the failure, you can issue the alter database rename file statement to change the backup control FILE. The STANDBY_FILE_MANAGEMENT parameter must be set to AUTO.

3. Plug in the tablespace.

3. Insert tablespace

Invoke the Data Pump utility to plug the set of tablespaces into the primary database. Redo data will be generated and applied at the standby site to plug the tablespace into the standby database.

Call the Data Pump to insert the tablespace to the master database. Then, the slave database will obtain the redo data and apply the tablespace to the slave database.

References:

Important configuration parameters of Oracle Data Guard

Configure Oracle 11g Data Guard based on the same host

Explore Oracle 11g elastic uard

Oracle Data Guard (RAC + DG) archive deletion policies and scripts

Role conversion for Oracle Data Guard

FAL gap in Oracle Data Guard logs

Oracle 11g Data Guard Error 16143 Heartbeat failed to connect to standby