The following are instructions for starting SharePlex and the sp_ctrl command-line interface on Unix and Linux. Start SharePlex on the source and target systems.
To start SharePlex on Unix and Linux systems:
From the bin sub-directory of the SharePlex product directory ( productdir in the following syntax), run sp_cop and sp_ctrl.
$cd /productdir/bin
$./sp_cop &
$. /sp_ctrl
SharePlex gets its replication instructions from a configuration file, which defines the objects that are to be replicated. The file specifies following:
Note: This demonstration demonstrates replication from one database to another. It does not cover replication to a file or a messaging container.
Perform these steps on the source system. The demonstration objects are assumed to be in the schema named splex.
Perform the following steps to create a configuration file:
Run sp_ctrl.
Issue the following command to create a configuration file named sample_config in the default text editor.
sp_ctrl(source)>create config sample_config
In the text editor, build your configuration file based on the appropriate template, as shown in the Configuration templates. Allow no spaces between the characters in a component (source specification, target specification, routing map), and place at least one space between each component.
In sp_ctrl, verify that the configuration file will activate successfully.
sp_ctrl(source)>verify config sample_config
datasource:r.source_DB | ||
"qarun"."basic_c127" |
"splex"."basic_c127" |
10.250.14.105@r.sp_ad |
where:
Perform these steps on the source system. When you activate a configuration, SharePlex is ready to capture transactional changes that are made to the specified source data.
Perform the following steps to activate a configuration file:
Activate the configuration.
sp_ctrl(source)>activate config sample_config
Note: Configuration names are case-sensitive.
Confirm that the configuration activated successfully. The name sample_config should appear under File Name, and the word Active should appear under State.
sp_ctrl(source)>list config
If your configuration activation fails, isue the view config sample_config command to view the file. Compare it to the template and make sure all of the information you entered is correct. Make certain you specified the correct database identifier. Check your syntax for extra spaces or missing components.
Because the configuration file is not active, you can edit it directly with the following command:
sp_ctrl(source)>edit config sample_config
Save the changes, then re-try the activation.
Note: To change an active configuration, you must copy it to a new file first, and then edit and activate the copy. For more information, see Add or Change Table Specifications in an Active Configuration in the SharePlex Installation and Setup Guide.
This section demonstrates the speed and accuracy of SharePlex replication. It can also be used to verify that SharePlex was installed and configured correctly. For detailed information, see Demonstration of replication.
This demonstration shows you how to use named post queues to process different tables through different, parallel Post processes to improve performance.
NOTE: The demonstration objects are assumed to be in the schema named splex.
Perform the following steps to clean up the replication environment:
If you ran previous demonstrations, do the following:
On the source and target, run sp_ctrl and issue the following command to shut down sp_cop.
sp_ctrl(source)shutdown
sp_ctrl(target)shutdown
On the source, TRUNCATE the splex.demo_src. SharePlex replicates the TRUNCATE to the target.
truncate table splex.demo_src;
Perform these steps on the source system. The demonstration objects are assumed to be in the schema named splex.
You will configure the following:
Run sp_ctrl.
Issue the following command to create a configuration file named postq_config in the default text editor.
sp_ctrl(source)>create config postq_config
In the text editor, build your configuration file based on the appropriate template, as shown in the Configuration templates. Allow no spaces between the characters in a component (source specification, target specification, routing map), and place at least one space between each component.
In sp_ctrl, verify that the configuration file will activate successfully.
sp_ctrl(source)>verify config postq_config
datasource:r.dbname | ||
splex.demo_src |
splex.demo_dest |
target_system:q1@r.database_name |
splex.demo_dest |
splex.demo_src |
target_system:q2@r.database_name |
where:
splex is the database user of the target database
Important!Make certain you created the scripts described in Prework for the demonstrations.
Perform these steps on the source system. When you activate a configuration, SharePlex is ready to capture transactional changes that are made to the specified source data.
Perform the following steps to activate the configuration:
Activate the configuration.
sp_ctrl(source)>activate config postq_config
Note: Configuration names are case-sensitive.
Confirm that the configuration activated successfully. The name postq_config should appear under File Name, and the word Active should appear under State.
sp_ctrl(source)>list config
On the source, run the following scripts to insert data into the two local demonstration tables (in this demonstration, the demo_dest table is used as a source):
Perform the following steps to view the post queues:
On the target, issue the show post command with the detail option. This command shows statistics about the number of messages processed and the queues that were used.
sp_ctrl(target)>show post detail
In the output, the Queue field shows the name of each post queue, in this case q1 and q2, and the Operations Posted field shows the number of operations that were posted. Each queue should show 500 operations posted.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center