This topic helps you make common changes to the Oracle environment while replication is active.
Oracle on Linux and UNIX
If you change the ORACLE_HOME, you need to relink SharePlex to the Oracle libraries.
Shut down SharePlex.
sp_ctrl> shutdown
On the source system, copy the active configuration file to a new name, but do not deactivate it.
sp_ctrl> copy config filename to newname
On the source system, open the new configuration file.
sp_ctrl> edit config filename
On the source system, flush the data in the queues to the target. This stops the Post process and establishes a synchronization point between the source and target databases.
sp_ctrl> flush datasource
where: datasource is the database indicator of the source instance, for example o.oraA.
On the source system, activate the new configuration file. This will deactivate the original configuration file.
sp_ctrl> activate config filename
Note: The activation will be brief because SharePlex does not need to analyze the tables.
On the target system, verify that Post stopped. If Post is not stopped, continue to issue the command until it shows that Post stopped.
sp_ctrl> status
On the target system, start Post.
sp_ctrl> start post
You can change the user name (schema or database), the password, or both in the SharePlex database account. The database account was established during the installation of SharePlex. These procedures guide you through the process in the correct order to maintain an active replication configuration.
All SharePlex-supported databases
This procedure changes the user account name and/or password of the SharePlex user account in a database. This user account is the one that the SharePlex processes use to connect to the database when performing replication tasks.
Important! If using multiple variable-data directories, you must run this procedure for each one that you want to change.
(Unix and Linux only) If you are using multiple variable-data directories, export the environment variable that points to the variable-data directory for the SharePlex instance for which you are changing the account name or password.
ksh shell:
export SP_SYS_VARDIR=/full_path_of_variable-data_directory
csh shell:
setenv SP_SYS_VARDIR=/full_path_of_variable-data_directory
Stop the SharePlex processes on the system where you are changing the account information. For example, if you are changing the SharePlex account in the source database, stop Capture and Read. If you are changing the account in the target database, stop Post.
sp_ctrl> stop service
Verify that all SharePlex replication processes for this instance of SharePlex are stopped.
sp_ctrl> status
If you changed the account name, copy all of the SharePlex database objects from the old account to the new one.
Note: Keep the old account and SharePlex objects as backup until you are certain replication resumes properly.
In sp_crtl, issue the following command to change the account name and/or password in the SharePlex internal records.
To change the user account:
sp_ctrl> connection {o.SID | r.database} set user=username
To change the password:
sp_ctrl> connection {o.SID | r.database} set password=password
where:
password is the new password.
Start the SharePlex processes.
sp_ctrl> start service
Use the provision utility to change a host name or IP address in the SharePlex configuration.
The SharePlex processes rely on the host names or IP addresses of the source and target machines to route data properly. The provision utility enables you to change host names or IP addresses within an active SharePlex instance, without reactivating a new configuration.
Note: The provision utility does not change anything in the database. It only affects SharePlex internal objects.
All databases supported by SharePlex on all supported platforms
(SharePlex 7.0.2 only) Add the following parameter to the param-defaults file before you run provision:
SP_CFP_DEBUG I live int() 0x00000000
If running SharePlex on an AIX machine, set EXTSHM before running provision.
export EXTSHM=ON
Run provision on all of the machines in the SharePlex configuration. Each machine can reference the IP addresses of all the other machines.
Using the command line of the operating system, run provision from the SharePlex variable-data directory with the following syntax:
provision -f old_name[:old_ipaddress] -t new_name[:new_ipaddress] [-p port] [-n]
Argument | Input |
---|---|
-f old_hostname[:old_ipaddress] |
|
-t new_hostname[:new_ipaddress] |
|
-p port | For Windows systems, specifies the port of the SharePlex instance for which provision is being run. |
-n |
Runs provision without actually making any changes. Generates a report on the changes that provision will make. Important! The best practice is to run provision with -n first, to make certain you agree with the potential changes, then run it without -n to make the changes. |
provision -f oldname -t newname -n
The provision utility creates an undo_provision script that can be used to restore the host names and IP addresses to their previous state. Run the undo_provision script from the util subdirectory of the SharePlex product directory. There are no input arguments to this script.
The following may occur but do not affect the integrity of the replication environment:
The SharePlex processes use TCP and UDP ports to communicate with each other on different systems. The default TCP and UDP port numbers for SharePlex are both set to 2100 at the time of installation. For some deployments of SharePlex you may need to change the port number or add additional ones.
Before selecting a port number, review the following points:
All databases supported by SharePlex on all supported platforms
To set the port number on Unix and Linux systems, a SharePlex Administrator must set both the TCP and UDP port parameters in the SharePlex environment. If there is an active configuration, you will be instructed to stop access to the source objects and shut down sp_cop.
(If using multiple variable-data directories] Export the SP_SYS_VARDIR environment variable to point to the correct variable-data directory for the port you are setting.
ksh shell:
export SP_SYS_VARDIR=/full_path_of_variable-data_directory
csh shell:
setenv SP_SYS_VARDIR=/full_path_of_variable-data_directory
Export the following environment variables.
ksh shell:
export SP_COP_TPORT=port
export SP_COP_UPORT=port
csh shell:
setenv SP_COP_TPORT port
setenv SP_COP_UPORT port
where: port is the new port number
Start sp_cop and sp_ctrl. Note:If you are using multiple variable-data directories, start sp_cop with the -uport option, where port is the port number that you have chosen for the variable-data directory that you exported.
./sp_cop [-uport] &
Run sp_ctrl.
./sp_ctrl
In sp_ctrl, set the following SharePlex parameters.
sp_ctrl> set param SP_COP_TPORT port
sp_ctrl> set param SP_COP_UPORT port
Do one of two things:
If there is not an active configuration, use the shutdown command in sp_ctrl to stop sp_cop. The next time you start sp_cop, the new port number takes effect.
NOTE: If you do not have an active configuration, you are finished setting the port number.
If there is an active configuration, continue to the next step.
To finish setting the port in an active configuration
Stop access to the replicating objects on the source system, then issue the flush command in sp_ctrl on the source system to clear the queues.
sp_ctrl> flush o.database_identifier
where: database_identifier is o. followed by the Oracle SID, TNS alias, or PDB name that SharePlex uses to connect to the source database (depends on whether the database is a regular Oracle instance, RAC, or PDB in a container database).
On the source system, issue the qstatus command to verify that all of the messages reached the target system.
sp_ctrl> qstatus
Continue to issue the command until the export queue is empty.
On the target system, issue the status command to verify that Post stopped.
sp_ctrl> status
Shut down SharePlex on the source and target systems.
sp_ctrl> shutdown
Start sp_cop on the source and target systems. Note:If you are using multiple variable-data directories, start sp_cop with the -uport option, where port is the port number that you have chosen for the variable-data directory that you exported.
./sp_cop [-uport] &
Start the Post process.
sp_ctrl> start post
Use the status command on the source and target systems to verify that all SharePlex processes are running.
sp_ctrl> status
On Windows systems, SharePlex port numbers are stored in the Windows Registry. If it becomes necessary to change a port number, this is the SharePlex entry location:
\HKEY_LOCAL_MACHINE\Software\Wow6432node\Quest Software\SharePlex.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center