Using Data Replication with Merge Apply and Audit Apply in a Single Configuration

Transcription

1 Using Data Replication with Merge Apply and Audit Apply in a Single Configuration 2016 Informatica LLC. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. All other company and product names may be trade names or trademarks of their respective owners and/or copyrighted materials of such owners.

2 Abstract This article describes how to configure Data Replication to replicate a set of source tables using both Merge Apply mode and Audit Apply mode. Supported Versions Data Replication Table of Contents Overview Task Flow Creating Source and Target Database Connections Generating Target Tables and Audit Log Tables Creating a Configuration with Merge Apply Mappings Adding the Secondary Target to the Configuration for Audit Log Tables That Use Audit Apply Setting Sync SCN Values for the Secondary Target with Audit Apply Mappings Overview Data Replication can replicate change data from the same set of source tables to both regular target tables by using Merge Apply and audit log tables by using Audit Apply, while maintaining the audit history. To implement this scenario, you generate one set of target tables for Merge Apply and two sets of audit log tables under different schemas: one for Merge Apply and the other for Audit Apply. Then create a replication configuration that maps the source tables to the primary target tables in Merge Apply mode. Then you add a secondary target to the configuration that uses Audit Apply mode for the audit log tables. The primary and secondary targets must use different schema and different target connections. Also, the regular target tables that use Merge Apply and audit log tables that use Audit Apply must have the same table names so that you can use the same mapping for both apply modes. Do not include the default _LOG suffix in the audit log table names for Audit Apply mappings. Audit log tables for Merge Apply can use the default _LOG suffix. Task Flow To replicate change data from the same set of source tables to both regular target tables in Merge Apply mode and audit log tables, perform the following tasks: 1. Create a named connection to the source database, and create two named connections to the target database. The target connections must have different connection names. This scenario uses oracle_target1 and oracle_target2. 2. Generate the target tables and audit log tables for Merge Apply mappings. Also, generate audit log tables for Audit Apply mappings. This scenario uses TARGET1 as the schema name for the regular target tables and audit log tables for Merge Apply mappings and uses TARGET2 as the schema name for the audit log tables for Audit Apply mappings. 3. Create a replication configuration that maps the source tables to the target tables in Merge Apply mode. 4. Add a secondary target to the configuration for the audit log tables. 5. Set the Sync SCN values for the audit log tables in the secondary target for which you use Audit Apply. 2

3 Creating Source and Target Database Connections Connect to the Server Manager Main server and create one connection to the source database and one target connection for each Apply type. 1. Start the Data Replication Console on a Windows system by running the idr_console.cmd script file in the top-level Data Replication installation directory. 2. To connect to the Server Manager Main server, perform the following substeps: a. Click the Server Manager tab > Configs view. b. Enter connection details in the Host, Port, Login, and Password fields. c. Click Connect. 3. On the Server Manager tab > Connections view, click New on the Connections toolbar. 4. Enter database connection details for the source database. 5. To test that the connection information is valid, click Test Connection. If the test is successful, a message displays "Connected." Click OK. 6. Click OK. 7. Repeat steps 3-6 to add two connections for the target database. This scenario uses the following connection names: oracle_target1 for Merge Apply mappings. oracle_target2 for Audit Apply mappings. Important: The target connection names must be different but all of the other connection information, including the user name and password, can be the same. In this case, ensure that the target database user has access to both schemas where you plan to generate regular target tables and audit log tables. Generating Target Tables and Audit Log Tables In the Data Replication Console, when you create the configuration, you can generate target tables and audit log tables for Merge Apply mappings and a separate set of audit log tables for Audit Apply mappings in the target database. 1. To create a new replication configuration, click the New button or select File > New. 2. In the New dialog box, perform the following substeps: a. Enter a configuration name. b. Select the configuration owner. c. Select the source and target Server Manager servers. d. Select the source and target environment variables lists. e. Click OK. 3. On the Source Database tab, in the Database Connection list, select the connection that you defined for the source database. Then click Connect to connect to the database. 4. On the Target Database tab, in the Database Connection list, select the connection that you defined for replicating data in Merge Apply mode. Then click Connect to connect to the database. 3

4 5. To generate the target tables for Merge Apply mode in the target database, perform the following substeps: a. Click Schema > Generating Schema for the Target. The Generating Schema for the Target dialog box appears. b. Under Source/Target, ensure that the Source option is selected. c. In the Schema/owner list, select the source schema that contains the tables that you want to replicate to the target. d. Select the Convert check box next to each source table that you want to use to generate a corresponding target table in the target database. e. Under Target, in the Schema field, enter the name of the schema under which you want to generate the target tables for Merge Apply mode. This scenario uses TARGET1. f. In the Database type list, select the target database type. 4

5 The following image shows the completed fields for this scenario: g. Click Run. Alternatively, click Save to the save the DDL to a script file if you do not have the authority to run it. You can then give the file to your DBA to run. 6. To generate audit log tables for Merge Apply mappings in the target database, perform the following substeps: a. Under Source/Target, select the Target option. b. In the Schema/owner field, enter the name of the target schema that you specified in step 5d to generate the target tables for Merge Apply mode. c. Select the Convert check box next to each target table that you want to use to generate a corresponding audit log table. 5

6 d. Select Generate audit log tables. e. Under Target, in the Schema field, enter the name of the schema under which you want to generate the audit log tables for Merge Apply mode. f. In the Audit tables suffix field, keep the default suffix _LOG or enter another suffix. g. Click Run. h. Click Close. 7. To generate audit log tables for Audit Apply mappings in the target database, perform the following substeps: a. Under Source/Target, select the Source option. b. In the Schema/owner list, select the source schema that contains the tables that you want to replicate to the target. c. Select the Convert check box next to each source table that you want to use to generate a corresponding audit log table. d. Under Target, in the Schema field, enter the name of the schema that you want to use for the audit log tables. This scenario uses TARGET2. Note: This schema name must be different from the schema name for the regular target tables that you specified in step 5d. e. Select Generate audit log tables. 6

7 f. Clear the Audit tables suffix field. Important: To replicate data from one source to multiple targets, all of the mapped target tables must have identical names. g. Click Run. Important: If the database user that the named connection uses to connect to the primary target does not have access to the schema that you want to use for the audit log tables, click Save to save the SQL CREATE TABLE statements to a script file. Then run the script under a database user name that has permissions to create tables in this schema. h. Click Close. Creating a Configuration with Merge Apply Mappings In the Data Replication Console, create a configuration that uses Merge Apply mode to replicate data from the source tables to the target tables. 1. To create a new replication configuration, click the New button or select File > New. 2. In the New dialog box, perform the following substeps: a. Enter a configuration name. b. Select the configuration owner. c. Select the source and target Server Manager servers. 7

8 d. Select the source and target environment variables lists. e. Click OK. 3. On the Source Database tab, in the Database Connection list, select the connection that you defined for the source database. Then click Connect to connect to the database. 4. On the Target Database tab, in the Database Connection list, select the connection that you defined for replicating data in Merge Apply mode. Then click Connect to connect to the database. This scenario uses oracle_target1. 5. To map the source tables to the target tables in Merge Apply mode, perform the following substeps: a. In the Source schema field, enter the source schema name. b. Select a source table. c. In the Target schema field, enter the schema name of the target tables. d. Select the target table that corresponds to the source table. e. Click Merge Map. 6. Repeat step 5 for each pair of the source and target tables that you want to map. 7. To save the configuration, perform the following substeps: a. Click File > Save on the menu bar, or click the Save icon button on the main toolbar. b. For Oracle sources, if all of the tables in the new configuration have a primary key definition or unique index, the Data Replication Console, by default, displays a prompt that asks if you want to run supplemental logging. Click Yes to enable supplemental logging for the tables in the configuration. c. For DB2 and Oracle sources, if any source table in the new configuration does not have a primary key or unique index definition, the Data Replication Console prompts you to select an option for replicating these tables. d. For DB2 sources, the Data Replication Console displays a prompt that asks if you want to manage the DB2 DATA CAPTURE settings for the mapped source tables. Click Yes to manage these settings for the tables in the configuration. After you save the configuration, you can edit the DATA CAPTURE settings in the Manage DB2 DATA CAPTURE Settings dialog box, which is accessed from the Map Tables tab. e. For targets that use a recovery table, the Data Replication Console displays the Enter Recovery Table Name and Schema dialog box. Accept the default schema and table name for the recovery table that will be on the primary target or enter another schema or table name. For some targets, you might need to specify a database or owner name. Then click Yes. Adding the Secondary Target to the Configuration for Audit Log Tables That Use Audit Apply After you create a replication configuration with Merge Apply mappings, add a secondary target that uses the second target database connection. The secondary target is used to replicate data to the audit log tables in Audit Apply mode. 1. Open the configuration in Edit mode. 2. On the Routing tab, click New. 8

9 The New dialog box appears: 3. In the Target connection list, select the target database connection that you created for Audit Apply. 4. Click OK. The Enter Recovery Table Name and Schema dialog box appears. 5. In the Schema field, select the name of the target schema that contains the audit log tables for Audit Apply processing. 6. Click Yes to generate the IDR_RECOVERY table in the selected target schema. 9

10 7. To override the apply mode and schema name for the audit log tables for the secondary target, click the Routing tab > Override Apply subtab. 8. In the Replication Type list, select Audit Apply. 9. Click Save. 10. Click the Schema Name subtab, and then click New. The New dialog box appears. 11. In the Renamed To field, enter the name of the target schema that contains the audit log tables for Audit Apply processing: This scenario uses TARGET Click OK. 13. Save the configuration. The Data Replication Console prompts you to run InitialSync. In the Select Targets dialog box, select all targets for which to perform InitialSync processing and click OK. Note: With Audit Apply mode, you do not need to perform an initial synchronization of targets prior to starting change data replication. You can now create a replication schedule to run the replication tasks. 10

11 Setting Sync SCN Values for the Secondary Target with Audit Apply Mappings If you do not set Sync SCN values for the audit log tables in the secondary target when defining the Audit Apply mappings, the Applier applies all of the change data that was processed from the source transaction logs to these tables. To start applying change data to the audit log tables from the point of the initial synchronization of the source and target tables, set the Sync SCN values for the audit log tables to the Sync SCN values for the target tables in the primary target. 1. To switch to Edit mode, click the Switch to Edit Mode icon button on the main toolbar. 2. To export Sync SCN values to a.csv file, perform the following substeps: a. On the Map Tables tab, click Configure Start Point. The Configure Start Point dialog box appears. b. Under Applier start point, click the Export icon. c. Select the system to which to export the list of Sync SCN values. Options are: Main server. Export Sync SCN values to a.csv file on the system where the Server Manager Main server runs. Local. Export Sync SCN values to a.csv file on the system where the Data Replication Console runs. d. In the Save dialog box, enter a file name and location. e. Click Save. The Data Replication Console exports Sync SCN values to the specified.csv file. f. Click OK. 3. To specify the Sync SCN values for the secondary target in the.csv file, perform the following substeps: a. Open the.csv file in a plain text editor. 11

12 b. Copy the lines that contain Sync SCN values for the primary target and paste them in the secondary target section, overwriting the existing values. c. Save the.csv file. 4. To import the Sync SCN values from the.csv file, perform the following substeps: a. In the Configure Start Point dialog box, under Applier start point, click the Import icon. b. Select the system that contains the.csv file to which you exported Sync SCN values. Options are: Main server. Import Sync SCN values from a.csv file on the system where the Server Manager Main server runs. Local. Import Sync SCN values from a.csv file on the system where the Data Replication Console runs. c. In the Open dialog box, enter the.csv file name and location. d. Click Open. The Data Replication Console imports Sync SCN values from the specified.csv file. e. Click OK. f. Click Save. 5. Save the configuration. Author Anton Bobkov Principal Technical Writer 12