Use the provision utility to change a host name or IP address in the SharePlex configuration. For more information on changing the name or IP address of a replication host, see the Provision utility section in the SharePlex Reference Guide.
Use the provision utility to change a host name or IP address in the SharePlex configuration. For more information on changing the name or IP address of a replication host, see the Provision utility section in the SharePlex Reference Guide.
The SharePlex processes use TCP to communicate with each other between different systems and uses UDP to communicate within a system. 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 TCP or UDP port numbers.
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.
To finish setting the port in an active configuration:
(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.
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
This section provides information about how initial synchronization of the database is performed when replicating data from PostgreSQL to PostgreSQL (cloud target databases).
You can set up an active replication between the following source and target platform combinations:
On-Prem Logical Source to Aurora Target
On-Prem Physical Source to Aurora Target
Azure Flexi Server Source to Aurora Target
Aurora Source to Azure Flexi Target
Aurora Source to On-Prem Target
To set up an active replication:
Run the pg_setup utility on both the source and target servers to prepare the environment.
Start SharePlex and execute the stop post command on the target server:
sp_ctrl (pslrhel7linux01:4073)> stop post
It ensures that even if a configuration file is not activated on the source, the Poster queue will be created but remain stopped.
Close access to the source database for users.
Activate the configuration file on the source.
sp_ctrl> activate config <config_file_name>
This creates the necessary replication slot as defined in pg_setup.
In the source database, create a snapshot while keeping the session open:
begin transaction isolation level REPEATABLE READ;
select pg_export_snapshot();
Use the following snapshot to run pg_dump on the source:
pg_dump --snapshot=00000003-000001BC-1 -d <database_name> -Fc -b -v -f dump04172024.sql -n <schemas>
For example:
pg_dump --snapshot=00000003-000001BC-1 -d testdb -Fc -b -v -f dump04172024.sql -n splex --username=splex
Resume user access to the source database while pg_dump is in progress.
Use the dump file to execute pg_restore on the target database after pg_dump is completed:
pg_restore -v -h pslaurorapgdb01.cihp157rpcvu.us-west-1.rds.amazonaws.com -U splex -d auroratest -j2 dump04172024.sql -n splex
Once pg_restore is executed, log in to the target database and check the tables.
After successful restoration, start the post queue on the target server using start post in sp_ctrl:
sp_ctrl> start post
Validate replication to ensure everything is working correctly.
This chapter contains procedures to follow when you need to apply an application patch or upgrade and there is an active replication configuration. These procedures apply to Oracle databases.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center