Skip Headers
Oracle® Communications Data Model Adapters and Analytics Installation Guide
Release 11.3.2

E37744-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

C NCC Adapter Installation and Configuration

This appendix shows how to install and set up the following:

This appendix includes the following sections:

Note:

The steps in this section can take a significant amount of time to complete.

The NCC Adapter that is installed with the Add-ons type installation feeds pre-paid billing data from the Oracle Communications Network Charging and Control application to the Oracle Communications Data Model. The NCC Adapter includes an option to feed data in real-time using Oracle GoldenGate to the Oracle Communications Data Model staging layer, or to extract, load and transform the data in batch mode using Oracle Data Integrator.

Prerequisites for NCC Adapter Configuration

The following are prerequisites for installing the Oracle Communications Network Charging and Control Adapter for Oracle Communications Data Model (NCC Adapter):

Confirming that Oracle Data Integrator Enterprise Edition is Installed

To verify your Oracle Data Integrator Enterprise Edition installation:

  1. Start ODI Studio:

    • On UNIX operating systems: ODI_HOME/oracledi/client/odi.sh

    • On Windows you can launch ODI Studio from the Start menu. On the Start menu, select All Programs, select Oracle, select Oracle Data Integrator , and then select ODI Studio.

  2. In Designer Navigator, click Connect To Repository...

    The Oracle Data Integrator Login dialog is displayed.

If Oracle Data Integrator Enterprise Edition is not installed, see "Oracle Data Integrator Enterprise Edition".

Confirming that Oracle GoldenGate is Installed

If you install the Oracle Communications Network Charging and Control Adapter for Oracle Communications Data Model (NCC Adapter), using, installing, and configuring Oracle GoldenGate is optional depending on whether you want to use Real-time staging with the NCC Adapter.

If Oracle GoldenGate is not installed, see "Oracle GoldenGate".

Oracle Communications Data Model NCC Adapter Installation Overview

To begin working, you need to set up ODI Master Repository and Work Repository and use Oracle Data Integrator (ODI) and optionally if you are using Oracle GoldenGate, you need to install and configure Oracle GoldenGate to perform real-time ETL.

  1. Configuring Oracle Data Integrator for Oracle Communications Data Model NCC Adapter

  2. Setting Up Oracle GoldenGate for Oracle Communications Data Model NCC Adapter

Note:

If you need real-time ETL optionally, install and configure ODI and Oracle GoldenGate together, that is for real-time ETL, you must first perform step 1 and then step 2.

Configuring Oracle Data Integrator for Oracle Communications Data Model NCC Adapter

Configuring Oracle Data Integrator for Oracle Communications Data Model includes the following steps:

Creating the ODI Connection for NCC Adapter Repository

To create the ODI connection for NCC Adapter Repository, perform the following steps:

  1. Start ODI Studio:

    • On UNIX operating systems: ODI_INSTALLATION_LOC/oracledi/client /odi.sh

    • On Windows you can launch ODI Studio from the Start menu. In the Start menu, select All Programs, select Oracle, select Oracle Data Integrator , and then select ODI Studio.

      Figure C-1 ODI Studio Data Server Start Menu

      Description of Figure C-1 follows
      Description of "Figure C-1 ODI Studio Data Server Start Menu"

  2. In the Designer Navigator, click Connect To Repository...

    Figure C-2 ODI Studio Data Server Designer Navigator

    Description of Figure C-2 follows
    Description of "Figure C-2 ODI Studio Data Server Designer Navigator"

  3. In the ODI Studio Data Server Login dialog box, click New.

    Figure C-3 ODI Studio Data Server Login Dialog Box

    Description of Figure C-3 follows
    Description of "Figure C-3 ODI Studio Data Server Login Dialog Box"

  4. The Repository Connection Information dialog box is displayed. Enter the appropriate information, as described in Table C-1:

    Figure C-4 ODI Studio Repository Connection Information Dialog Box

    Description of Figure C-4 follows
    Description of "Figure C-4 ODI Studio Repository Connection Information Dialog Box"

    Table C-1 ODI Studio Data Server Repository Connection Information Tab Fields

    Section Field Description

    Oracle Data Integrator Connection

    Login Name

    User

    Password

    Specify the Login Name. For example, NCC Adapter

    Specify the default user name SUPERVISOR

    Specify the default password sunopsis

    Database connection (Master Repository)

    User

    Password

    Driver List

    DriverName

    URL

    Specify the default user name ncc_odim

    Specify the default password ncc_odim

    Specify Oracle JDBC Driver

    Specify oracle.jdbc.OracleDriver

    Specify in the format

    jdbc:oracle:thin:@HOST:PORT:SID
    

    For example:

    @localhost:1521:orcl11203
    

    Work Repository

     

    Select Master Repository Only


    Click OK.

  5. In the ODI Studio Data Server Login dialog box, click OK.

  6. In the Topology Navigator, expand the Repositories tab. Next, expand the Work Repositories tab to select the WORKREP1 tab.

    Figure C-5 ODI Studio Data Server Repositories Tab

    Description of Figure C-5 follows
    Description of "Figure C-5 ODI Studio Data Server Repositories Tab"

  7. Right-click the WORKREP1 tab and click Open.

    Figure C-6 ODI Studio Data Server WORKREP1 Screen

    Description of Figure C-6 follows
    Description of "Figure C-6 ODI Studio Data Server WORKREP1 Screen"

    If you see an error message, ignore it and click OK.

    Figure C-7 ODI Studio Data Server Error Message

    Description of Figure C-7 follows
    Description of "Figure C-7 ODI Studio Data Server Error Message"

  8. In the Work Repository Connection Information tab, click the Connection icon.

    Figure C-8 ODI Studio Work Repository Connection Information Tab

    Description of Figure C-8 follows
    Description of "Figure C-8 ODI Studio Work Repository Connection Information Tab"

  9. In the Definitions tab, enter the appropriate information, as described in Table C-2:

    Figure C-9 ODI Studio Data Server Definitions Tab

    Description of Figure C-9 follows
    Description of "Figure C-9 ODI Studio Data Server Definitions Tab"

    Table C-2 ODI Studio Data Server Connection Field and Values

    Field Description

    User

    Specify the default user name ncc_odiw

    Password

    Specify the default password ncc_odiw


  10. In the JDBC tab, enter the appropriate information, as described in Table C-3:

    Figure C-10 ODI Studio Data Server JDBC Tab Fields and Values

    Description of Figure C-10 follows
    Description of "Figure C-10 ODI Studio Data Server JDBC Tab Fields and Values "

    Table C-3 ODI Studio Data Server JDBC Tab Fields and Values

    Field Description

    JDBC Driver

    Specify oracle.jdbc.OracleDriver

    JDBC URL

    Specify in the format jdbc:oracle:thin:@host:port:SID.

    Replace host, port and SID with the values for the database hosting the ODI Repositories.

    For example:

    jdbc:oracle:thin:@localhost:1521:orcl11203
    

    Click Save.

  11. Click Disconnect "NCC Adapter" from the ODI drop-down list.

    Figure C-11 Disconnect NCC Adapter Option in ODI Studio Data Server Menu

    Description of Figure C-11 follows
    Description of "Figure C-11 Disconnect NCC Adapter Option in ODI Studio Data Server Menu"

  12. Click Edit in the ODI Studio Data Server Login dialog box.

    Figure C-12 Edit Option in the ODI Studio Data Server Login Dialog Box

    Description of Figure C-12 follows
    Description of "Figure C-12 Edit Option in the ODI Studio Data Server Login Dialog Box"

  13. The Repository Connection Information dialog box is displayed. In the Work Repository section, click Browse and select WORKREP1 in the text field. Click OK.

    Figure C-13 ODI Studio Data Server Work Repository Connection Fields

    Description of Figure C-13 follows
    Description of "Figure C-13 ODI Studio Data Server Work Repository Connection Fields"

  14. Go to the ODI Studio Data Server Login dialog box and click OK.

    The ODI Studio Data Server Master and Work Repository is successfully imported.

Setting up the ODI Topology

To set up the ODI Topology, do the following:

Setting up the Physical Data Servers

To set up the Physical Data Servers:

  1. From the Topology Navigator, display the Physical Architecture tab.

  2. Expand the Technologies node.

  3. Expand the Oracle node to display the Physical Data Servers.

    Figure C-14 ODI Studio Physical Data Servers

    Description of Figure C-14 follows
    Description of "Figure C-14 ODI Studio Physical Data Servers"

  4. Double-click the NCC_STG node to display the Data Server: Name dialog.

  5. Display the Definition tab and enter the appropriate information, as described in Table C-4.

    Figure C-15 ODI Studio Data Server Definition Dialog

    Description of Figure C-15 follows
    Description of "Figure C-15 ODI Studio Data Server Definition Dialog"

    Table C-4 ODI Studio Data Server Definition Fields and Values

    Field Description

    Name

    Do not change name of the Data Server.

    Technology

    Do not change the default value Oracle.

    Instance/dblink (Data Server)

    Specify a database instance name.

    Use the Oracle SID name. For example, ORCL

    User

    Specify User Name. For example, ncc_stg

    This is the warehouse database user name.

    Password

    Specify Password. For example, ncc_stg

    This is default password for the warehouse database user name.

    Array Fetch Size

    Specify a value suitable to your environment

    (Do not change the default value).

    Batch Update Size

    Specify a value suitable to your environment

    (Do not change the default value).


  6. Display the JDBC tab and enter the appropriate information, as described in Table C-5.

    Figure C-16 ODI Studio Data Server JDBC Tab

    Description of Figure C-16 follows
    Description of "Figure C-16 ODI Studio Data Server JDBC Tab"

    Table C-5 ODI Studio Data Server JDBC Tab Fields and Values

    Field Description

    JDBC Driver

    Specify oracle.jdbc.driver.OracleDriver

    JDBC Url

    Specify in the format jdbc:oracle:thin:@host:port:SID.

    Replace host, port and SID with the values for the database hosting the ODI Repositories.

    For example:

    jdbc:oracle:thin:@localhost:1521:orcl
    

  7. Click Test to display the Test Connection for: Connection dialog.

    Figure C-17 ODI Studio Data Server Test Connection

    Description of Figure C-17 follows
    Description of "Figure C-17 ODI Studio Data Server Test Connection"

  8. Click the Save icon.

Note:

Follow the same steps (1-8) to configure NCC_BE, NCC_CCS and OCDM_SYS Physical Data Servers.

Setting up the Physical Schema

To set up the Physical Schema for a Data Server:

  1. From the Topology Navigator, display the Physical Architecture tab.

  2. Expand the Technologies node.

  3. Expand the Oracle node to display the Physical Data Servers.

  4. Expand the Data Server node.

    Figure C-18 ODI Studio Physical Architecture Data Server Node

    Description of Figure C-18 follows
    Description of "Figure C-18 ODI Studio Physical Architecture Data Server Node"

  5. Double-click NCC_STG.NCC_STG to display the Physical Schema: Name dialog.

  6. Display the Definition tab and enter the appropriate information, as described in Table C-6.

    Figure C-19 ODI Studio Physical Schema Definition Tab

    Description of Figure C-19 follows
    Description of "Figure C-19 ODI Studio Physical Schema Definition Tab"

    Table C-6 ODI Studio Physical Schema Definition Tab Properties and Values

    Field Description

    Schema (Schema)

    Make sure that Physical Schema is selected from the drop down list.(For example: NCC_STG)

    Schema (Work Schema)

    Make sure that Physical Schema is selected from the drop down list.(For example: NCC_STG)


    Note:

    Ensure that you do not change the other field values.
  7. Click to save the details.

Note:

Follow the same steps (1-7) to configure NCC_BE, NCC_CCS and OCDM_SYS Physical Schemas.

Setting up the Logical Data Servers

To set up the Logical Data Servers:

  1. From the Topology Navigator, display the Logical Architecture tab.

  2. Expand the Technologies node.

  3. Expand the Oracle node to display the Logical Data Servers.

    Figure C-20 ODI Studio Logical Architecture for Logical Data Server

    Description of Figure C-20 follows
    Description of "Figure C-20 ODI Studio Logical Architecture for Logical Data Server"

  4. Double-click the NCC_STG_LS node to display the Logical Data Server: Name dialog.

  5. Display the Definition tab.

  6. Edit the NCC_STG_LS Logical Data Server and ensure that for the appropriate Context (for example, Global, Development...), the value in the Physical Schemas column is set to NCC_STG.NCC_STG (Physical Schema created in Physical Data Server).

    Figure C-21 ODI Studio Logical Data Server Definition Tab

    Description of Figure C-21 follows
    Description of "Figure C-21 ODI Studio Logical Data Server Definition Tab"

  7. Click the Save icon.

    Note: Follow the same steps (1-7) to configure NCC_BE_LS, NCC_CCS_LS and OCDM_SYS_LS Logical Data Server.

Setting Up Oracle GoldenGate for Oracle Communications Data Model NCC Adapter

To set up Oracle GoldenGate for Oracle Communications Data Model, perform the following steps:

Installing Oracle GoldenGate on Target for NCC Adapter

To use NCC Adapter real-time capturing, installing, and configuring Oracle GoldenGate (GG), perform the following steps:

  1. Change directory to the database installation path.

    For example: /u02/app/oracle/product

  2. Create a directory (gg) for installing Oracle GoldenGate under the product folder:

    [oracle@server product]$ mkdir /u02/app/oracle/product/gg
    

    Or, manually create the folder (gg) by going directly in the product folder:

    [oracle@server product]$ export GGATE=/biaora/home/db11gR2/product/gg
    Or setenv GGATE /biaora/home/db11gR2/product/gg
    [oracle@server product]$ cd $GGATE
    [oracle@server gg]$
    
  3. Copy the downloaded Oracle GoldenGate software (for example: V22228-01.zip) into gg folder (for information on downloading Oracle GoldenGate, see "Oracle GoldenGate").

  4. Unzip the software in the folder using following command:

    [oracle@server gg]$ unzip V22228-01.zip
    
  5. After you unzip the file, use the .tar extension file to extract Oracle GoldenGate.

  6. Extract the Oracle GoldenGate .tar file using the following command:

    [oracle@server gg] tar -xf filename.tar
    
  7. Now export the path to GG libraries to LD_LIBRARY_PATH using the command:

    export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/u02/app/oracle/product/gg
    

    or,

    setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:$GGATE
    
  8. Now start the GG command line utility (ggsci):

    [oracle@server gg]$. /ggsci
    

    This command connects you to the Oracle GoldenGate server.

    For example:

    Oracle GoldenGate Command Interpreter for Oracle Version 11.1.1.0.0 Build 078 Linux, x86, 32bit (optimized), Oracle 11 on Jul 28 2010 13:22:25 Copyright (C) 1995, 2010, Oracle and/or its affiliates. All rights reserved.
    
  9. Create the necessary working directories for Oracle GoldenGate:

    GGSCI (server.oracle.com) 1> create subdirs
    GGSCI (server.oracle.com) 2> exit
    [oracle@server gg]$ mkdir $GGATE/diroby
    
  10. After these steps Oracle GoldenGate is installed.

    After you install Oracle GoldenGate, you prepare and configure the source and target database for Oracle GoldenGate Replication.

    Note:

    Steps 1 to 10 in "Installing Oracle GoldenGate on Target for NCC Adapter" are common for both source (CCS_ADMIN and E2BE_ADMIN) and target systems.

Configuring Oracle GoldenGate on Target for NCC Adapters

To set up Oracle GoldenGate Schema, perform the following steps:

  1. Create Oracle GoldenGate schema:

    SQL>sqlplus / as sysdba;
    SQL> create user ggate identified by ggate default tablespace users temporary tablespace temp;
    

    Note:

    For Oracle GoldenGate schema, the default password is set during the setup phase. For example, ggate. To change the password, change the default password in the related prm and oby files. For more information, see "Edit Oracle GoldenGate schema and password."
  2. Grant privileges to Oracle GoldenGate schema:

    SQL> grant connect, resource, unlimited tablespace to ggate;
    SQL> grant select any dictionary to ggate;
    SQL> grant execute on utl_file to ggate;
    SQL> grant alter any table to ggate;
    SQL> grant create table to ggate;
    SQL> grant select any table, insert any table, update any table, delete
    any table to ggate;
    SQL>exit;
    
  3. Copy the target configuration file to the $GGATE directory. The files for the target are generated at the following location:

    $ORACLE_HOME/ocdm/addon/adapter/ncc/goldengate_param/stg
    

    Copy the files to $GGATEE using the same directory structure.

    • Copy file in $ORACLE_HOME/ocdm/addon/adapter/ncc/goldengate_param/stg

    • Copy file in $ORACLE_HOME/ocdm/addon/adapter/ncc/goldengate_param/stg

  4. Edit Oracle GoldenGate schema and password.

    The default schema and password are ggate.

    • Edit file $GGATE/diroby/ ncc_ogg_stg.oby according to the environment. Use the correct value in the following command:

      DBLOGIN USERID userid, PASSWORD passwd
      
    • Edit the file $GGATE/dirprm/ globals.prm according to the environment. Change the value in the following command:

      GGSCHEMA ggate
      CHECKPOINTTABLE ggate.ggschkpt
      
  5. Config the manager port. The default manager port at the target is 7809. If required , edit the port in the file:

    $GGATEE/dirprm/mgr.prm
    
  6. Edit schema E2BE_ADMIN, CCS_ADMIN and NCC_STG at REPLICAT:

    The default NCC_SRC schema is ncc_src_demo,the default NCC_STG schema is ncc_stg. Edit the file $GGATEE/dirprm/ rep1.prm and $GGATEE/dirprm/ rep2.prm , change schema names according to the environment. For example:

    Change file in rep1.prm

    map ncc_src_demo.BE_BALANCE, TARGET ggstg.BE_BALANCE, REPERROR (1403, DISCARD), KEYCOLS (WALLET, BALANCE_TYPE), colmap ( usedefaults, OPTYPE=@GETENV("GGHEADER","OPTYPE"), last_update_time = @GETENV ("GGHEADER", "COMMITTIMESTAMP") );
    

    to

    map e2be_admin.BE_BALANCE, TARGET ncc_stg.BE_BALANCE, REPERROR (1403, DISCARD), KEYCOLS (WALLET, BALANCE_TYPE), colmap ( usedefaults, OPTYPE=@GETENV("GGHEADER","OPTYPE"), last_update_time = @GETENV ("GGHEADER", "COMMITTIMESTAMP") );
    
  7. Add the Replicat group.

    Execute the following command on the target system to add a delivery group named repncc and repbe.

    [oracle@server gg]$ $GGATE/./ggsci paramfile $GGATE/diroby/ ncc_ogg_stg_cdc_cmd.oby
    

    You can run the batch commands in ncc_ogg_stg_cdc_cmd.oby to see the result of each single command. For example,

    1. Log in to Oracle GoldenGate schema:

      ./ggsci
      
    2. Execute the following:

      GGSCI (slc00tcw)>DBLOGIN USERID ggate, PASSWORD ggate
      GGSCI (slc00tcw)>ADD CHECKPOINTTABLE ggate.ggschkpt
      GGSCI (slc00tcw)> ADD REPLICAT rep2, EXTTRAIL ./dirdat/rb, checkpointtable ggate.ggschkpt
      GGSCI (slc00tcw)> ADD REPLICAT rep1, EXTTRAIL ./dirdat/rc, checkpointtable ggate.ggschkpt
      

Installing Oracle GoldenGate on Source CCS_ADMIN for NCC Adapter

Follow the same steps in "Installing Oracle GoldenGate on Target for NCC Adapter" to install Oracle GoldenGate in source system where CCS_ADMIN schema is located.

Configuring Oracle GoldenGate on Source CCS_ADMIN for NCC Adapter

To set up Oracle GoldenGate Schema, perform the following steps:

  1. Switch the database server to archive log mode.

    Connect to sqlplus from oracle user:

    [oracle@server dbhome_1]$ sqlplus / as sysdba
    SQL> shutdown immediate
    SQL> startup mount
    SQL> alter database archivelog;
    SQL> alter database open;
    
  2. Enable minimal supplemental logging:

    SQL> alter database add supplemental log data;
    

    Switch log to start supplemental logging:

    SQL> ALTER SYSTEM SWITCH LOGFILE;
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    

    Verify supplemental logging is enabled (with the following command showing a result: 'YES').

    SQL> SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
    
  3. Prepare the database to support database replication. Turn off recyclebin for the database:

    SQL> alter system set recyclebin=off scope=spfile;
    
  4. Create Oracle GoldenGate schema:

    SQL> create user ggate identified by ggate default tablespace users temporary tablespace temp;
    

    Note:

    For Oracle GoldenGate schema, the default password is set during the setup phase. For example, ggate. To change the password, change the default password in the related prm and oby files. For more information, see Edit Oracle GoldenGate schema and password. "Edit ggate default schema and password".
  5. Grant necessary privileges to Oracle GoldenGate schema:

    SQL> grant connect, resource, unlimited tablespace to ggate;
    SQL> grant select any dictionary to ggate;
    SQL> grant select any table to ggate;
    SQL> grant alter any table to ggate;
    SQL> grant flashback any table to ggate;
    SQL> grant execute on dbms_flashback to ggate;
    SQL> Grant alter any table to ggate; 
    SQL> grant execute on utl_file to ggate;
    SQL> exit;
    

    To do Trandata, you need to enable supplemental logging on the source. To enable Supplemental logging, use the following command:

    alter database add supplemental log data;
    
  6. Copy source config file to $GGATE directory. The files for the source system are generated at the following location:

    $ORACLE_HOME/ocdm/addon/adapter/ncc/goldengate_param/src/src_ccs
    

    Note:

    Files in $ORACLE_HOME/ocdm/addon/adapter/ncc/goldengate_param/src/src_be are configuration files for source where e2be_admin schema located.

    These files must be copied on the source to the following location $GGATEE using the same directory structure:

    • Copy files in goldengate_param/src/src_ccs/dirprm to $GGATEE/dirprm

    • Copy files in goldengate_param/src/src_ccs/diroby to $GGATEE/diroby

  7. Config manager port. The default manager port at source is 7890. As required, edit this port in the file:

    $GGATEE/dirprm/mgr.prm
    
  8. Config RMTHOST. Change the RMTHOST and MGRPORT in dpump.prm files in the $GGATEE/dirprm directory as required for your working environment:

    RMTHOST Remote Host Name, MGRPORT Port
    

    For example:

    rmthost slc00tcw, mgrport 7809
    
  9. Config CCS_ADMIN schema at EXTRACT. The default CCS_ADMIN schema for the NCC Adapter is NCC_SRC_DEMO. Change the source schema name according to your source schemas. For example, change schema NCC_SRC_ DEMO to CCS_ADMIN.

    • Change NCC_CCS schema at $GGATE/dirprm/ext1.prm. For example, change Table ncc_src_demo.CCS_BALANCE_TYPE; to Table CCS_ADMIN. CCS_BALANCE_TYPE;

    • Change CCS_ADMIN schema at $GGATE/dirprm/dpump.prm. For example, change Table ncc_src_demo.CCS_BALANCE_TYPE; to Table CCS_ADMIN.CCS_BALANCE_TYPE;

    • Change CCS_ADMIN schema at $GGATE/diroby/ ncc_ogg_src_cdc_cmd_101_sms.oby. For example, change ADD TRANDATA ncc_src_demo.* to ADD TRANDATA CCS_ADMIN.*

  10. Configure Change Capture using a Data Pump. The goals of this method are to:

    • Configure and add the Extract process that will capture changes

    • Add the local trail that will store these changes.

    • Configure and add a data pump Extract to read the local trail and create a remote trail on the target.

    • Add the remote trail.

    Execute the following command on the source CCS_ADMIN system to define an extract group named ext1 and to define a data pump extract named dpump to pull data from the local Oracle GoldenGate trail and route these changes to Oracle GoldenGate on the target.

    [oracle@server gg]$ $GGATE/./ggsci paramfile $GGATE/diroby/ ncc_ogg_src_cdc_cmd_101_sms.oby
    

    Note:

    In most cases, run the batch commands in the oby file one by one manually in the Oracle GoldenGate command line util ggsci.

Installing Oracle GoldenGate on Source E2BE_ADMIN for NCC Adapter

Follow the same steps in "Installing Oracle GoldenGate on Target for NCC Adapter" to install Oracle GoldenGate in source system where E2BE_ADMIN schema is located.

Configuring Oracle GoldenGate on Source E2BE_ADMIN for NCC Adapter

Follow the same steps in "Configuring Oracle GoldenGate on Source CCS_ADMIN for NCC Adapter" to configure Oracle GoldenGate in source system where E2BE_ADMIN schema is located.

Starting Oracle GoldenGate Processes on Source CCS_ADMIN for NCC Adapter

To start Oracle GoldenGate schema on source, perform the following steps:

  1. Log in to Oracle GoldenGate schema:

    ./ggsci
    
  2. Start running the Manager:

    GGSCI (gbr40193) 1> star mgr
    
  3. Start all extract processes:

    GGSCI (gbr40193) 2> star er *
    
  4. Check the processes status:

    GGSCI (gbr40193) 3> info all
    

    Figure C-22 The Processes Status for NCC Adapter on Source

    Description of Figure C-22 follows
    Description of "Figure C-22 The Processes Status for NCC Adapter on Source"

Starting Oracle GoldenGate Processes on Source E2BE_ADMIN for NCC Adapter

Follow the same steps in "Starting Oracle GoldenGate Processes on Source CCS_ADMIN for NCC Adapter" to start processes in the source server where E2BE_ADMIN schema is located.

Starting Oracle GoldenGate on Target for NCC Adapter

To start Oracle GoldenGate schema on source, perform the following steps:

  1. Start running the Manager:

    GGSCI (slc00tcw) 17>start mgr
    
  2. Start all replicat processes:

    GGSCI (slc00tcw) 18>start er *
    
  3. Check the processes status:

    GGSCI (slc00tcw) 19> info all
    

    Figure C-23 The Processes Status for NCC Adapter on Target

    Description of Figure C-23 follows
    Description of "Figure C-23 The Processes Status for NCC Adapter on Target"

Oracle GoldenGate Process Checking Command Reference

Table C-7 provides a summary of Oracle GoldenGate process commands. Note: Run these commands from GGSCI.

Table C-7 Oracle GoldenGate Process Commands Summary

Process Area Commands

To Start All Services

Manager: Start Manager

Extract: Start Extract Extract Group

Replicate: Start Replicat Replicat Group

Extract & Replicat: Start ER *

To Stop All Services

Manager: Stop Manager

Extract: Stop Extract Extract Group

Replicate: Stop Replicat Replicat Group

Extract & Replicat: Stop ER *

To Check Services Status

All Services: Info All

Manager: Info Mgr

Extract: Info Extract Extract Group

Replicate: Info Replicat Replicat Group

To View Report

Extract: View Report Extract Group

Replicate: View Report Replicat Group