SharePlex 10.2 - Installation and Setup for Oracle Source

Demonstration of data compare and repair

This demonstration shows you how to use the SharePlex compare command to compare the source and target data, and then repair rows that are out of synchronization.

1. On the source, TRUNCATE splex.demo_src to make certain it is empty. SharePlex replicates the TRUNCATE to the target.

   truncate table splex.demo_src;

2. On the source, use the insert_demo_src script to insert rows into splex.demo_src.

3. On the target, verify that all of the data posted to splex.demo_dest. If the command shows that data is still in the queue, issue the command again.

   sp_ctrl(target)>qstatus

4. On the source, issue the compare command in sp_ctrl.

   sp_ctrl (source)>compare splex.demo_src

   Note: The command determines the correct target table from the configuration file.

5. On the source, view the results of the comparison. There should be no rows out of synchronization.

   sp_ctrl(source)>compare status

6. On the target, UPDATE splex.demo_dest to change the values of the NAME column in two or more rows. The UPDATE causes the source and target tables to be out of synchronization.

7. On the source, issue the compare command again. It should show that the rows you updated in splex.demo_dest are out of synchronization.

   sp_ctrl(source)>compare splex.demo_src

8. On the source, issue the repair command to repair the rows that are out of synchronization.

   sp_ctrl(source)> repair splex.demo_src

9. On the source, verify that the repair was performed.

   sp_ctrl(source)>repair status

10. On the target, you can manually verify that the repair was accurate by using a SELECT statement to view all rows in both tables.

    select * from splex.demo_src;

    select * from splex.demo_dest;

Demonstration of named post queues

This demonstration shows you how to use named post queues to process different tables through different, parallel Post processes to improve performance.

Clean up the replication environment

NOTE: The demonstration objects are assumed to be in the schema named splex.

1. If you ran previous demonstrations, do the following:

   1. 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

   2. On the source and target, run the ora_cleansp or mss_cleansp utility according to the instructions in SharePlex utilities. This removes the queues from the previous demonstrations and deactivates the previous configuration.

2. On the source, TRUNCATE the splex.demo_src. SharePlex replicates the TRUNCATE to the target.

   truncate table splex.demo_src;

Create a configuration file

Perform these steps on the source system. The demonstration objects are assumed to be in the schema named splex.

You will configure the following:

• demo_src on the source replicates through a post queue named q1 to target demo_dest.
• demo_dest on the source replicates through a post queue named q2 to target demo_src.

1. Run sp_ctrl.

2. Issue the following command to create a configuration file named postq_config in the default text editor.

   sp_ctrl(source)>create config postq_config

3. 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.

4. Save the file, then exit the editor. SharePlex automatically saves the file in the config sub-directory of the variable-data directory.

5. In sp_ctrl, verify that the configuration file will activate successfully.

   sp_ctrl(source)>verify config postq_config

Configuration templates

Oracle source to Oracle target

where:

• source_SID is the ORACLE_SID of the source database.
• target_system is the name or IP address of the target system.
• target_SID is the ORACLE_SID of the target database.

Oracle source to Open Target

where:

• source_SID is the ORACLE_SID of the source database.
• target_system is the name or IP address of the target system.
• database_name is the name of the Open Target database.

Activate the configuration

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.

1. Activate the configuration.

   sp_ctrl(source)>activate config postq_config

   Note: Configuration names are case-sensitive.

2. 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

Generate data

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):

• Run the insert_demo_src script to insert 500 rows into the splex.demo_src table.
• Run the insert_demo_dest script to insert 500 rows into the splex.demo_dest table.

View the post queues

1. On the target, run sp_ctrl.

2. 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.

Advanced SharePlex demonstrations for Oracle

Contents

This chapter demonstrates selected features of SharePlex. These exercises can be run on Unix and Linux and Windows systems to demonstrate:

• How to build and verify a replication configuration
• How to use the compare command to verify synchronization
• How to use partitioned replication to replicate subsets of data
• How to use transformation to manipulate replicated data
• How to use generic conflict resolution in peer-to-peer replication

Prework for the demonstrations

Perform these tasks before you start the demonstrations.

Verify that DDL replication is enabled

On the source, verify that the SP_OCT_REPLICATE_DDL parameter is set to the default of 3. This parameter controls basic DDL replication, including the TRUNCATE command.

sp_ctrl(source)>list param modified capture

The SP_OCT_REPLICATE_DDL parameter should not be listed in the output. If it is, issue the following command:

sp_ctrl(source)>reset param SP_OCT_REPLICATE_DDL

Install the demonstration objects

The p2p.sql and od.sql scripts install the demonstration objects that you will use during these demonstrations. These scripts are stored in the util sub-directory of the SharePlex product directory.

To run the scripts

• Run od.sql first, then run p2p.sql.
• Run the scripts on the source and target systems that you will be using for the demonstrations.
• Run them in SQL*Plus as an existing user with the DBA role and SELECT ANY TABLE privileges.

The scripts prompt for the following items:

• The schema where you want the demonstration objects to be installed.
• The tablespace for the demonstration objects.
• Whether or not you want old demonstration objects from a previous version of SharePlex to be removed. To remove the old objects, supply the name of their schema.

Description of the demonstration objects