Use this procedure to use the Oracle transportable tablespaces feature to establish a target Oracle instance and activate replication. It enables you to synchronize and resynchronize numerous objects quickly and with minimal downtime. It allows you to export just the metadata (data dictionary) and then copy the data files. This method also moves indexes so that there is no need to rebuild them in the target database, and you can move multiple tablespaces at one time.
Note: This document does not provide instructions for how to use transportable tablespaces. This procedure should be performed by someone who has a solid understanding of database copy methods.
Read these points before you proceed.
Oracle source and Oracle target
All replication strategies. This procedure may not appropriate for a high-availability strategy if the source database cannot be quieted even briefly.
In this procedure, the "source" system is one of the following:
In this procedure, the "intermediary" system only needs to be part of this procedure if SharePlex will be posting to, and capturing from, an intermediary system in a cascading configuration.
In this procedure, the "target" system is one of the following:
In this procedure, the SharePlex commands in the procedure apply to all sp_cop instances that apply to the replication strategy you are using (for example, all sp_cop processes on a target in consolidated replication).
On the source system, set the source tablespaces that you want to copy to READ ONLY.
svrmgr1> alter tablespace name read only;
On the source system, activate the configuration file.
sp_ctrl> activate config filename
On the source system, verify that sp_cop and sp_ctrl are running.
sp_ctrl> status
On the intermediary and target systems, stop Post. Stopping Post allows replicated data to accumulate in the post queue until the databases have been recovered.
sp_ctrl> stop post
Set the source tablespaces back to read/write mode.
svrmgr1> alter Tablespace name read write;
On the intermediary and target systems, disable triggers on the tables, or run the sp_add_trigger.sql utility script so that the triggers ignore the SharePlex user.
[Intermediary system only] Set the SP_OCT_REPLICATE_POSTER parameter to 1. This directs SharePlex to capture posted changes on that system and replicate them to the target system.
sp_ctrl> set param SP_OCT_REPLICATE_POSTER 1
[Intermediary system only] Activate the configuration file.
sp_ctrl> activate config filename
[High availability] On the target system, stop the Export process.
sp_ctrl> stop export
[High availability and peer-to-peer replication] Activate the configuration on the target system(s).
sp_ctrl> activate config filename
Start Post on the intermediary and target systems. SharePlex begins executing the SQL statements that have been collecting in the post queue, keeping the source and target data in sync.
sp_ctrl> start post
Use this procedure to synchronize the source and target data with the following utilities:
Note: This document does not provide instructions for how to perform the chosen copy method. This procedure should be performed by someone who has a solid understanding of database copy methods.
Read these points before you proceed.
Oracle source and Oracle target
All but high-availability. This procedure is not appropriate for a high-availability strategy because it requires the source database to be quieted while the configuration file is being activated.
In this procedure, the "source" system is one of the following:
In this procedure, the "intermediary" system only needs to be part of this procedure if SharePlex will be posting to, and capturing from, an intermediary system in a cascading configuration.
In this procedure, the "target" system is one of the following:
In this procedure, the SharePlex commands in the procedure apply to all sp_cop instances that apply to the replication strategy you are using (for example, all sp_cop processes on a target in consolidated replication).
On the source system, stop user access to the objects that are in the replication configuration.
On the source system, activate the configuration file (all files if using consolidated replication).
sp_ctrl> activate config filename
On the intermediary and target systems, stop Post. Stopping Post allows any data that gets replicated before the target data is established to collect in the post queue.
sp_ctrl> stop post
On the source system, verify that the sp_cop, Capture, and Read processes are running.
sp_ctrl> status
On the intermediary and target systems, disable triggers on the tables, or run the sp_add_trigger.sql utility script so that the triggers ignore the SharePlex user.
[Intermediary system only] Set the SP_OCT_REPLICATE_POSTER parameter to 1. This directs SharePlex to capture posted changes on that system and replicate them to the target system.
sp_ctrl> set param SP_OCT_REPLICATE_POSTER 1
[Intermediary system only] Activate the configuration file.
sp_ctrl> activate config filename
Start Post on:
Note: SharePlex will start executing SQL statements that accumulated in the post queue.
Use this procedure to synchronize an Oracle source database with an Open Target database. SharePlex replicates the Oracle data changes and maintains them in the Post queue until the target is established with the copy. When the target is ready, you run the SharePlex reconcile feature, which ensures that Post only applies the operations that occurred after the copy and discards operations that were committed to the source before the copy.
Read these points before you proceed.
Oracle source and any supported target
All
You can use your Oracle RMAN backup system to take a hot backup of your primary instance and recover to an SCN or sequence number in a staging instance.
On source and target systems, verify that the SharePlex processes are running.
sp_ctrl> status
On the target system, stop the Post process. This allows replicated data to accumulate in the post queue until the target database is instantiated and reconciled.
sp_ctrl> stop post
Activate the configuration on the source system.
sp_ctrl> activate config filename
On the source system, monitor activation status.
Note: The command retains control of sp_ctrl until activation is finished.
When the hot backup is finished, switch log files on the primary source system twice.
On-premises database:
svrmgr1> alter system switch logfile;
svrmgr1> alter system switch logfile;
Amazon RDS database:
Run the Amazon RDS procedure rdsadmin.rdsadmin_util.switch_logfile twice.
Do one of the following:
If the source is not RAC, recover to the sequence number of the last archive log that was copied to the staging server.
Note: The next steps apply the replicated changes that occurred after the backup point.
Do one of the following:
If source is non-RAC, make a note of the log sequence number that you recovered to on the staging server.
[Optional] If you are using named post queues and are unsure of the queue names, issue the qstatus command and make a note of them.
sp_ctrl> qstatus
On the target system, run sp_ctrl, then issue one of the following reconcile commands. If you are using named post queues, issue the command for each one.
If the source is non-RAC, reconcile to the log sequence number of the log that you noted previously.
sp_ctrl> reconcile queue queuename for datasource-datadest seq sequence_number
Example: reconcile queue SysA for o.prod1-r.rep1 seq 1234
If the source is RAC, reconcile to the SCN that you noted previously.
sp_ctrl> reconcile queue queuename for datasource-datadest scn scn_number
Example: reconcile queue SysA for o.prod1-r.rep1 scn 0123456789
Note: The command retains control of sp_ctrl until the reconcile process is finished.
On the target system, start the Post process. The two instances are now in synchronization, and SharePlex will continue replicating to maintain synchronization.
sp_ctrl> start post
This chapter contains an overview of the tools that SharePlex provides to detect errors and monitor the replication processes. Like any mission-critical software, SharePlex should be monitored regularly for situations or events that could interfere with processing, especially those that could result in loss of data synchronization.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
