Apply patch/upgrade to source and target
Supported databases
Oracle on all supported platforms
When to use this procedure
Use this procedure if the patch or upgrade makes DDL changes of a type not replicated by SharePlex. For a list of objects for which DDL is supported, see the SharePlex Release Notes.
Overview of the procedure
Use this procedure to apply an application patch or upgrade if it includes changes to the database that are not replicated by SharePlex and you can stop user access to the source database to deactivate and reactivate the configuration file. It requires deactivation of the configuration file so that SharePlex can rebuild its object information to incorporate the changes that the patch or upgrade applied. When you reactivate the configuration, SharePlex will re-analyze all of the objects again. You can allow users to access the source data while the patch or upgrade is applied to the target system.
Apply the patch/upgrade
- Stop user access to the instances involved in replication on the source and target systems, but do not shut down SharePlex.
-
On the source system, flush the data to the target system. This command stops Post and places a marker in the data stream that establishes a synchronization point between source and target data.
sp_ctrl> flush datasource
where: datasource is the datasource of the source instance, for example o.oraA.
-
On the source system, deactivate the configuration.
sp_ctrl> deactivate config filename
- On the source system, apply the patch or upgrade.
-
[If the patch/upgrade adds objects that must be replicated] On the source system, edit the configuration file, including making any changes to column partitions or column conditions if using partitioned replication. For more information, see Change an active configuration file.
sp_ctrl> edit config filename
-
On the source system, activate the configuration file.
sp_ctrl> activate config filename
- On the source system, restore user access to the source instance.
- On the target system, apply the patch or upgrade.
- On the target system, if the patch or upgrade installed triggers on the tables in replication, disable them or run the sp_add_trigger.sql utility script so that the triggers ignore the SharePlex user.
- On the target system, if the patch or upgrade added check constraints or scheduled jobs that perform DML, disable them.
- On the target system, perform any cleanup required by partitioned replication.
-
On the target system, start Post.
sp_ctrl> start post
The two instances are now in synchronization, and SharePlex resumes replication.
Apply patch to source and replicate it to the target
Supported databases
Oracle on all supported platforms
When to use this procedure
Use this procedure if all of the operations applied by a patch or upgrade are supported by SharePlex and can be replicated to the target. This includes DML changes and DDL that is supported by SharePlex. If you are not sure whether the patch or upgrade performs operations that are not supported by SharePlex, use the procedure Apply patch/upgrade to source then copy it to target.
Note: For a list of operations that SharePlex supports, see the SharePlex Release Notes.
Apply the patch/upgrade
- Stop user access to the Oracle instances on the source and target systems.
-
On the source system, flush the data to the target system. This command stops Post and places a marker in the data stream that establishes a synchronization point between source and target data.
sp_ctrl> flush datasource
where: datasource is the datasource of the source instance, for example o.oraA.
- On the source system, apply the patch or upgrade.
- On the source system, restore user access to the source instance.
- On the target system, if the patch or upgrade created or modified triggers, disable them or run the sp_add_trigger.sql utility script so that the triggers ignore the SharePlex user.
- On the target system, restore user access to the target instance.
Back up Oracle data on the source or target
Back up data on the source or target
This topic contains procedures for making backups of source and target data while replication is active.
Contents
Perform a partial backup of the source system
To perform a partial back up of a source system (for example, to extract data or populate a data warehouse) while data is being replicated, you can perform the partial backup on the target system instead and copy the same data as you would on the source system.
This procedure does not interrupt user access to the source data and does not deactivate or reactivate the configuration file.
Supported databases
Oracle
All targets
Procedure
- On the source system, start sp_ctrl.
-
On the source system, flush the data to the target system. This command stops the Post process and places a marker in the data stream that establishes a synchronization point between source and target data.
sp_ctrl> flush datasource
where: datasource is the datasource specification of the source database in the configuration file, for example o.ora1.
- On the target system, back up the data. Note: The data now matches the source data at the flush marker.
-
On the target system, start the Post process.
sp_ctrl> start post
