Oracle GoldenGate for Non-Audited Enscribe to Oracle

Transcription

1 Oracle GoldenGate for Non-Audited Enscribe to Oracle Oracle GoldenGate for Non-Audited Enscribe to Oracle Objective Upon completion of this lesson, you will be able to keep two heterogeneous databases synchronized, in this case NonStop non-audited Enscribe to Oracle. During this lesson, you will learn how to: Prepare your environment to configure the GoldenGate processes Configure and execute the initial data load Configure and start the change capture of database operations Configure and start the change delivery of database operations NonStop Enscribe to Oracle configuration The following diagram illustrates a configuration with the source data in a non-audited data base on the HP NonStop and the target in an Oracle database on a Windows or UNIX platform. NonStop <source> Source database Manager Windows server <target> Manager Logger Network Trails Extract Collector Trails Oracle Replicat Target <schema> Page 1

2 Oracle GoldenGate for Non-Audited Enscribe to Oracle Overview of Tasks Prepare the Environment In order to execute this lesson, the GoldenGate application must be installed on both the source and target systems. The installation includes a sample database and scripts to generate initial data as well as subsequent update operations. The source and target tables are created and loaded with initial data. The GoldenGate Manager processes are also started so that other processes may be configured and started. Initial Data Load To initially load data between heterogeneous databases, use the GoldenGate application to perform your initial data synchronization while the application remains active. This lesson demonstrates the direct method using Extract to pull data from the source files and sending the data directly to Replicat on the target system. <source> NonStop Windows or UNIX <target> server Network Oracle Source database Initial Extract Initial Replicat Target <schema> Configure Change Capture For non-audited files, you must identify all programs that perform database operations on the files to be captured. These programs are bound with the GoldenGate intercept library. The Logger process is configured and started to create the log trail of all captured operations. An Extract process distributes the trails to the remote system. Configure Change Delivery Once the tables have been initially loaded with data and the Extract process is capturing all operations, the Replicat process is configured to deliver the captured operations to the target database. Page 2

3 Prepare the Environment Exercise 1. Prepare the Environment Objective The goals of this exercise are to: Configure and start the Manager processes. Prepare the source and target sample databases. Prepare the source NSK environment 1. Configure a GLOBALS parameter file on the source A GLOBALS parameter can be used to uniquely identify each GoldenGate instance when multiple environments exist on single NSK node. Use the two-character <prefix> that was defined in the Lab Preparation. Execute the following commands on the <source> system unless neither a <prefix> nor <audcfg> is needed for your installation. TACL> VOLUME <install vol>.<install subvol> TACL> TEDIT GLOBALS ADD DEFINE =GGS_PREFIX, CLASS MAP, FILE $<prefix> ADD DEFINE =GGS_AUDCFG, CLASS MAP, FILE <audcfg> 2. Configure the Manager process on the source system The Manager process is responsible for starting and monitoring all of the other GoldenGate processes. You will always have one manager process per GoldenGate instance. TACL> VOLUME <install vol>.<install subvol> TACL> RUN GGSCI GGSCI> TEDIT PARAMS MGRPARM GoldenGate Manager Parameter file TCPIPPROCESSNAME <tcpip process> PORT <port> GGSCI> START MANAGER, CPU 1, PRI 180 3

4 Prepare the Environment Verify the results: GGSCI> INFO MANAGER 3. Create and load source files The installation includes scripts to create sample files and generate initial data. Note that your <prefix> may need to be substituted for the GG in subvolume GGSSOU used in this section. Move the script to the source data volume. TACL> VOLUME <install vol>.ggssou TACL> FUP DUP <install subvol>.demoldeo, GGSSOU.* Run the scripts. TACL> FUP /IN <install vol>.<install subvol>.demofups/ TACL> RUN <install vol>.<install subvol>.demoldeo Within DEMOLDEO the following prompts and replies are issued: To perform an initial load enter (I), to update the database enter (U) or to exit the program enter (E).?I To perform an initial load enter (I), to update the database enter (U) or to exit the program enter (E).?E Verify the results: TACL> FUP COPY ECUSTMER TACL> FUP COPY ECUSTORD 4. Generate source definitions The DEFGEN utility is an interactive program that generates a source definition file describing the layouts of the files/tables that are to be replicated. TACL> VOLUME <install vol>.<install subvol> TACL> RUN DEFGEN Within DEFGEN, the following prompts and replies are issued: Enter definitions filename (or Exit): <install vol>.ggsdef.ecustdef File/Table to create definition for (or Exit): <install vol>.ggssou.ecustmer Definition retrieved. File/Table to create definition for (or Exit): <install vol>.ggssou.ecustord Definition retrieved. File/Table to create definition for (or Exit): EXIT 4

5 Prepare the Environment 5. Move the source definitions to the target After exiting, FTP the file <install-vol>.ggsdef.ecustdef in ASCII format to the target <install location>/dirdef/source.def. 5

6 Initial Data Load: NonStop ENS to Oracle Exercise 2. Initial Data Load: NonStop ENS to Oracle Objective The goals of this exercise are to: Configure and execute the initial data load capture Configure and execute the initial data delivery Configure initial load 1. Add the initial load capture batch task group Execute the following commands on the <source> system to add an Extract named EINI<unique id>1. GGSCI> ADD EXTRACT EINI<unique id>, SOURCEISTABLE Verify the results: GGSCI> INFO EXTRACT *, TASKS 2. Configure the initial load capture parameter file GGSCI> EDIT PARAMS EINI<unique id> GoldenGate Initial Data Capture for ECUSTMER and ECUSTORD EXTRACT EINI<unique id> RMTHOST <target>, MGRPORT <port> RMTTASK REPLICAT, GROUP RINI<unique id> TABLE <install vol>.ggssou.ecustmer; TABLE <install vol>.ggssou.ecustord; 1 The process names used in lab exercises, for example EINIBD, are made up of 1) one character for the GoldenGate process (E for Extract, R for Replicat); 2) three or four to describe the process type (INI for initial data load, ORA for capture from or delivery to an Oracle database, etc.) and 3) two characters to create a unique identifier (usually your initials).. 6

7 Initial Data Load: NonStop ENS to Oracle 3. Add the initial load delivery batch task group Execute the following commands on the <target> system. GGSCI> ADD REPLICAT RINI<unique id>, SPECIALRUN Verify the results: GGSCI> INFO REPLICAT *, TASKS 4. Configure the initial load delivery parameter file Execute the following commands on the <target> system. GGSCI> EDIT PARAMS RINI<unique id> Change Delivery parameter file for TCUSTMER and TCUSTORD changes REPLICAT RINI<unique id> USERID <login>, PASSWORD <password> SOURCEDEFS./dirdef/source.def DISCARDFILE./dirrpt/RINI<unique id>.dsc, PURGE MAP <install vol>.ggssou.ecustmer, TARGET <owner/schema>.ecustmer; MAP <install vol>.ggssou.ecustord, TARGET <owner/schema>.ecustord; Note: Remember to use <db type>.def if you renamed the source.def when you transferred it to the <target>. 5. Execute the initial load process GGSCI> START EXTRACT EINI<unique id> Verify results: GGSCI> VIEW REPORT EINI<unique id> 7

8 Configure Change Capture Exercise 3. Configure Change Capture Objective The goals of this exercise are to: Configure and add the Logger process that will log changes. Bind in the GoldenGate intercept library. Configure and add the Extract process that will route the changes to the remote system. Start the capture process. Configure and start logging changes 1. Create the Logger parameter file Execute the following commands on the <source> system to define a Logger process to capture changes for the non-audited Enscribe files and store these changes in GoldenGate trails. GGSCI> TEDIT PARAMS LOGPARM LOGGER configuration for one logger process LOG <install vol>.ggslog.<log trail id>, MEGABYTES 2, NUMFILES 5, SECURE "NUUU" CPU 1, 0 FILE <install vol>.ggssou.ecustmer; FILE <install vol>.ggssou.ecustord; Note: Record the two characters selected for your <log trail id>:. You will need this for step Process the Logger configuration GGSCI> ADD LOGGER Start the Logger Process GGSCI> START LOGGER 8

9 Configure Change Capture Verify the results: GGSCI> INFO LOGGER Bind the intercept library 3. Bind GoldenGate intercept library to application programs Execute the following commands on the <source> system to bind in the routines that will route changes to Logger. GGSCI> INFO PROGRAM <install vol>.ggssou.demoldeo GGSCI> BIND PROGRAMS Enter the name of the program at the Program prompt. Program <install vol>.ggssou.demoldeo Adding program <install vol>.ggssou.demoldeo to change library list. After all programs have been entered, start the binding process by entering GO at the Program prompt. To abort the process, enter EXIT. Program: GO The program will interact as shown below. The following programs will include GGSLIB as a user library. <install vol>.ggssou.demoldeo It is strongly recommended that you make backup copies of all programs before continuing. Begin with BIND process (Y/N)? Y Beginning program linking to GGSLIB Changing user library for <install vol>.ggssou.demoldeo to <source>.<install vol>.<install subvol>.ggslib. BIND completed. Errors Detected: 0 Review report file <source>.<install vol>.ggsrpt.bind for complete results. Verify results: GGSCI> INFO PROGRAM <install vol>.ggssou.demoldeo GGSCI> VIEW REPORT BIND 9

10 Configure Change Capture Configure change capture 4. Create the Extract parameter file Execute the following commands on the <source> system to define an Extract process to route changes from the log trails (<log trail id>) to remote trails (<trail id>). GGSCI> TEDIT PARAM ELOG<unique id> EXTRACT parameter file to read log trail data and distribute the data to remote trail on the target system EXTRACT ELOG<unique id> DISCARDFILE <install vol>.ggsdisc.elog<unique id>, PURGE PASSTHRU TCPIPPROCESSNAME <tcpip process> RMTHOST <target>, MGRPORT <port> RMTTRAIL./dirdat/<trail id> FILE $*.*.*; Note: Use the target name or its IP address to identify the <target> system of RMTHOST parameter. Use the \node for the <target> of the fully qualified remote file name. Note: Record the two characters selected for your <trail id>:. You will need this for the Replicat. 5. Add the Extract group GGSCI> ADD EXTRACT ELOG<unique id>, LOGTRAILSOURCE <install vol>.ggslog.<log trail id> Verify the results: GGSCI> INFO EXTRACT ELOG<unique id> 6. Define the GoldenGate remote trails GGSCI> ADD RMTTRAIL./dirdat/<trail id>, EXTRACT ELOG<unique id>, MEGABYTES 5 7. Start the Extract process GGSCI> START EXTRACT ELOG<unique id> 10

11 Configure Change Capture Verify the results: GGSCI> INFO EXTRACT ELOG<unique id> Discussion points 1. Using Logger When is it necessary to use Logger? 2. Binding to the intercept library Why is it necessary to bind the application programs to the GoldenGate intercept libraries when using Logger? 3. Using BIND arguments In GGSCI, do a HELP BIND PROGRAMS. Go over the list of arguments to try to understand when you might use each of them. When would you use CHANGELIB? 4. Identifying a remote system What parameters are used to identify the remote target system? 5. Using PASSTHRU This parameter is used only when Extract is distributing data from what type of trail? Hint: Search in the GoldenGate for HP NonStop Reference Guide for PASSTHRU NOPASSTHRU 11

12 Configure Change Delivery Exercise 4. Configure Change Delivery Objective The goals of this exercise are to: Set up the checkpoint table on the target system. Create a named group that includes the Replicat process and the checkpoint tables. Configure the Replicat group by adding parameters. Start the Replicat group. Set up the checkpoint table 1. Create a GLOBALS file on the target system Execute the following commands on the <target> system. Create and edit the GLOBALS parameter file to add the checkpoint table. Shell> cd <install location> Shell> ggsci GGSCI> EDIT PARAMS./GLOBALS In the text editor, type: CHECKPOINTTABLE <owner/schema>.ggschkpt Record the checkpoint table owner and name, then save and close the file. Table owner name Note: You could name the table anything you want, but for training purposes we are using ggschkpt. Verify that the GLOBALS file was created in the root GoldenGate directory, and remove any file extension that was added. 2. Activate the GLOBALS parameters For the GLOBALS configuration to take effect, you must exit the session in which the changes were made. Execute the following command to exit GGSCI. GGSCI> EXIT 12

13 Configure Change Delivery 3. Add a Replicat checkpoint table On the <target> system, execute the following commands in GGSCI: Shell> cd <install location> Shell> ggsci GGSCI> DBLOGIN USERID <login>, PASSWORD <password> GGSCI> ADD CHECKPOINTTABLE Configure Change Delivery 4. Add the Replicat group Execute the following command on the <target> system to add a delivery group named RORA<unique id>. GGSCI> ADD REPLICAT RORA<unique id>, EXTTRAIL./dirdat/<trail id> Note: Refer to your Extract set up for the correct two-character <trail id>. 5. Create Replicat parameter file Execute the following commands on the <target> system to bring up the parameter file in the editor. GGSCI> EDIT PARAM RORA<unique id> Type in the following parameters Change Delivery parameter file to apply TCUSTMER and TCUSTORD Changes REPLICAT RORA<unique id> USERID <login>, PASSWORD <password> HANDLECOLLISIONS SOURCEDEFS./dirdef/source.def DISCARDFILE./dirrpt/RORA<unique id>.dsc, PURGE MAP <source vol>.ggssou.tcustmer, TARGET <owner/schema>.tcustmer; MAP <source vol>.ggssou.tcustord, TARGET <owner/schema>.tcustord; 6. Start the Replicat process GGSCI> START REPLICAT RORA<unique id> Verify the results: GGSCI> INFO REPLICAT RORA<unique id> 13

14 Configure Change Delivery Discussion points Search in the Windows/UNIX Reference Guide for the information on the following questions. 1. When to use HANDLECOLLISIONS For which stage of GoldenGate processing change capture, initial data load, or change delivery would you use HANDLECOLLISIONS? What does it do? 2. What information is supplied by SOURCEDEFS 3. What is the purpose of the DISCARDFILE? 14

15 Generate Activity and Verify Results Exercise 5. Generate Activity and Verify Results Objective The goals of this exercise are to: Execute miscellaneous update, insert, and delete operations on the source system. Verify the delivery of the changes to the target Generate database operations 1. Execute miscellaneous update, insert, and delete operations Set up the define for AUDCFG at the TACL prompt. TACL> ADD DEFINE =GGS_AUDCFG, CLASS MAP, FILE $<audcfg> Execute update operations. TACL> VOLUME <install vol>.ggssou TACL> RUN DEMOLDEO Within DEMOLDEO the following prompts and replies are issued: To perform an initial load enter (I), to update the database enter (U) or to exit the program enter (E).?U To perform an initial load enter (I), to update the database enter (U) or to exit the program enter (E).?E Verify change capture and delivery 2. Verify the results on your source system Execute the following commands on the <source> system to view the contents of the source Enscribe files. TACL> FUP COPY <install vol>.ggssou.ecustmer TACL> FUP COPY <install vol>.ggssou.ecustord Page 15

16 Generate Activity and Verify Results 3. Verify your results on the target system Execute the following commands on the <target> system to verify the target data. Shell> cd <install location> Shell> sqlplus <userid>/<password> SQL> select * from ecustmer; SQL> select * from ecustord; SQL> exit Shell> ggsci GGSCI> SEND REPLICAT RORA<unique id>, REPORT GGSCI> VIEW REPORT RORA<unique id> Turn off error handling 4. Turn off initial load error handling for the running delivery process GGSCI> SEND REPLICAT RORA<unique id>, NOHANDLECOLLISIONS 5. Remove initial load error handling from the parameter file GGSCI> EDIT PARAMS RORA<unique id> Remove the HANDLECOLLISIONS parameter. Page 16

17 Exercise Name Page 17