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

A BRM 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 appendix can take a significant amount of time to complete.

The BRM Adapter can be installed with the Oracle Communications Data Model Add-ons type installation. The BRM 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 BRM Adapter Configuration

The following are prerequisites for installing the Billing and Revenue Management to Oracle Communication Data Model Adapter:

Confirming that Oracle Data Integrator Enterprise Edition is Installed

To verify your Oracle Data Integrator Enterprise Edition installation, perform the following steps:

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

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 Billing and Revenue Management to Oracle Communication Data Model Adapter (BRM Adapter), using, installing, and configuring Oracle GoldenGate is optional depending on whether you want to use Real-time staging with the BRM Adapter.

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

Installation Overview for BRM Adapter

To complete the installation of the Billing and Revenue Management to Oracle Communication Data Model Adapter, perform the tasks in this appendix sequentially.

To begin working, you need to set up the BRM Master Repository and Work Repository connection 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.

Notes:

  • Before following the steps in this appendix, you must have installed the Oracle Data Integrator software using the procedure outlined in "Oracle Data Integrator Enterprise Edition".

  • Before following the steps in this appendix, you must have installed the BRM Adapter software using the procedure outlined in "Installer Execution".

  • The installation and set up steps assume the following recommended ODI configuration:

    • The ODI Master Repository database schema is created in same database instance.

    • The ODI Work Repository database schema is created in same database instance.

    • The Data Warehouse database schema is hosted on the same database instance as the ODI Repository.

The following steps explains how to install Billing and Revenue Management (BRM) to Oracle Communication Data Model Adapter.

Oracle Communications Data Model Adapter Installation Steps:

Note:

If you do not use real-time ETL, then perform step 1 and skip step 2.
  1. Configuring Oracle Data Integrator for BRM Adapter (Non Oracle GoldenGate Option)

  2. Setting Up Oracle GoldenGate for BRM 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 BRM Adapter (Non Oracle GoldenGate Option)

Configuring Oracle Data Integrator for Oracle Communications Data Model use with the BRM Adapter includes the following steps:

Creating the ODI Connection for BRM Adapter Repository

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

  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. In the Start menu, select All Programs, select Oracle, select Oracle Data Integrator, and then select ODI Studio.

      Figure A-1 ODI Studio Data Server Start Menu

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

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

    Figure A-2 ODI Studio Data Server Designer Navigator

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

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

    Figure A-3 ODI Studio Data Server Login Dialog Box

    Description of Figure A-3 follows
    Description of "Figure A-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 A-1:

    Figure A-4 ODI Studio Data Server Repository Connection Information Dialog Box

    Description of Figure A-4 follows
    Description of "Figure A-4 ODI Studio Data Server Repository Connection Information Dialog Box"

    Table A-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, BRM 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 brm_odim

    Specify the default password brm_odim

    Specify the default 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 A-5 ODI Studio Data Server Repositories Tab

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

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

    Figure A-6 ODI Studio Data Server WORKREP1 Screen

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

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

    Figure A-7 ODI Studio Data Server Error Message

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

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

    Figure A-8 Work Repository Connection Information Tab

    Description of Figure A-8 follows
    Description of "Figure A-8 Work Repository Connection Information Tab"

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

    Figure A-9 ODI Studio Data Server Definitions Tab

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

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

    Field Description

    User

    Specify the default user name brm_odiw

    Password

    Specify the default password brm_odiw


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

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

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

    Table A-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 "BRM Adapter" from the ODI drop-down list.

    Figure A-11 Disconnect BRM Adapter Option in the ODI Studio Data Server Menu

    Description of Figure A-11 follows
    Description of "Figure A-11 Disconnect BRM Adapter Option in the ODI Studio Data Server Menu"

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

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

    Description of Figure A-12 follows
    Description of "Figure A-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 from the Work Repositories List. Click OK.

    Figure A-13 ODI Studio Data Server Work Repository Connection Fields and Values

    Description of Figure A-13 follows
    Description of "Figure A-13 ODI Studio Data Server Work Repository Connection Fields and Values"

  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, perform the following steps:

Setting 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 A-14 ODI Studio Physical Data Servers

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

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

  5. Display the Definition tab and enter the appropriate information, as described in.

    Figure A-15 ODI Studio Data Server Definition Dialog

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

    Table A-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, brm_stg

    This is the warehouse database user name.

    Password

    Specify Password.

    This is the 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 A-5.

    Figure A-16 ODI Studio Data Server JDBC Tab

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

    Table A-5 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:orcl
    

  7. After entering the required values, click Test. This shows the dialog in Figure A-17.

    Figure A-17 ODI Studio Data Server Test Connection

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

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

    Figure A-18 Test Connection Information Dialog

    Description of Figure A-18 follows
    Description of "Figure A-18 Test Connection Information Dialog"

  9. Click the Save icon.

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 A-19 ODI Studio Physical Architecture Data Server Node

    Description of Figure A-19 follows
    Description of "Figure A-19 ODI Studio Physical Architecture Data Server Node"

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

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

    Figure A-20 ODI Studio Physical Schema Definition Tab

    Description of Figure A-20 follows
    Description of "Figure A-20 ODI Studio Physical Schema Definition Tab"

    Table A-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: BRM_STAGE)

    Schema (Work Schema)

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


    Note: Do not change the other field values.

  7. Click the Save icon.

Note:

Follow the same steps (1-7) to configure BRM_SRC 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 A-21 ODI Studio Logical Architecture for Logical Data Server

    Description of Figure A-21 follows
    Description of "Figure A-21 ODI Studio Logical Architecture for Logical Data Server"

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

  5. Display the Definition tab.

  6. Edit the BRM_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 BRM_STG_BRM_STG (Physical Schema created in Physical Data Server).

    Figure A-22 ODI Studio Logical Data Server Definition Tab for Logical Schema

    Description of Figure A-22 follows
    Description of "Figure A-22 ODI Studio Logical Data Server Definition Tab for Logical Schema"

  7. Click the Save icon.

  8. After checking whether the context is set properly, ensure that in the Topology->Physical Architecture tab that the context tab of physical schemas points to the right logical context.

    Figure A-23 ODI Studio Logical Data Server Context Tab

    Description of Figure A-23 follows
    Description of "Figure A-23 ODI Studio Logical Data Server Context Tab"

Note: Follow these steps (1-7) to configure the BRM_SRC_LS and OCDM_SYS_LS Logical Data Servers. When you finish these steps, the installation of ODI is complete.

Setting Up Oracle GoldenGate for BRM Adapter

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

Installing Oracle GoldenGate on Target for BRM Adapter

To use BRM Adapter real-time capturing, install and configure Oracle GoldenGate (GG) as follows:

  1. Change directory to the database installation path (For example: /u02/app/oracle/product).

    Figure A-24 Changing Directory to the Oracle Database Installation Path

    Description of Figure A-24 follows
    Description of "Figure A-24 Changing Directory to the Oracle Database Installation Path"

  2. Create a directory named (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=/u02/app/oracle/product/gg
    [oracle@server product]$ cd $GGATE
    [oracle@server gg]$
    
  3. Copy the downloaded 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 with the tar command to extract Oracle GoldenGate:

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

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

    export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$GGATE
    
  7. 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
    
  8. Create the necessary working directories for gg:

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

After Oracle GoldenGate is installed you prepare the source and target database for Oracle GoldenGate Replication.

Note: Steps 1 to 9 in "Installing Oracle GoldenGate on Target for BRM Adapter" are common for both the source and target databases. These same steps are shown in the section, "Installing Oracle GoldenGate on Source for BRM Adapter".

Configuring Oracle GoldenGate on Target for BRM Adapter

To set up the Oracle GoldenGate schema, do the following:

  1. Create Oracle GoldenGate schema:

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

    Note: For the Oracle Goldengate schema, a default password is provided during the setup phase. You can change the default password, but then you need to change the default password in the related prm and oby files; for more details see step 4, "Edit ggate default 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 target config file to $GGATE directory:

    The files for the target system have been generated in:

    $ORACL_HOME\ocdm\addon\adapter\brm\goldengate_param\stg

    These files must be copied on the target system, to the following location $GGATEE using the same directory structure.

    • Copy files contained in $ORACL_HOME\ocdm\addon\adapter\brm\goldengate_param\stg

    • Copy files contained in $ORACL_HOME\ocdm\addon\adapter\brm\goldengate_param\stg

  4. Edit the default schema and password. For the Oracle Goldengate schema, a default password is provided during the setup phase. You can the default password, but you also need to change the default password in the related prm and oby files:

    • Edit file $GGATE\diroby\ brm_ogg_stg_cdc_cmd.oby according the environment; use the correct value in the following command:

    DBLOGIN USERID userid, PASSWORD passwd
    
    • Edit the file $GGATE\dirprm\globals.prm according the environment, change the value in the following commands:

    GGSCHEMA ggate
    CHECKPOINTTABLE ggate.ggschkpt
    
  5. Config 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 BRM_SRC and BRM_STG at REPLICAT:

    The default BRM_SRC and BRM_STG schema are brm_src,and brm_stg, edit the file $GGATEE\dirprm\repbrm.prm, and change the two schema names according the environment. For example, change the following:

    map brm_src.ACCOUNT_NAMEINFO_T, TARGET brm_stg.ACCOUNT_NAMEINFO_T, KEYCOLS (OBJ_ID0,REC_ID), REPERROR (1403, DISCARD)
    

    to

    map pin5003.ACCOUNT_NAMEINFO_T, TARGET brm_stg_ogg.ACCOUNT_NAMEINFO_T, KEYCOLS (OBJ_ID0,REC_ID), REPERROR (1403, DISCARD)
    
  7. Add the Replicat group:

    Execute the following command on the target system to add a delivery groups named repbrm.

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

    Note: you can run the batch commands in brm_ogg_stg_cdc_cmd.oby manually to see the result of each single command. For example:

    First login to ggsci and execute the following:

    ./ggsci

    GGSCI (slc00tcw) 1> ADD REPLICAT repbrm, EXTTRAIL ./dirdat/rt, checkpointtable ggate.ggschkpt
    

Installing Oracle GoldenGate on Source for BRM Adapter

To use BRM Adapter real-time capturing, install and configure Oracle GoldenGate (GG) as follows:

  1. Change directory to the database installation path (For example: /u02/app/oracle/product).

    Figure A-25 Changing Directory to the Oracle Database Installation Path

    Description of Figure A-25 follows
    Description of "Figure A-25 Changing Directory to the Oracle Database Installation Path"

  2. Create a directory named (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=/u02/app/oracle/product/gg
    [oracle@server product]$ cd $GGATE
    [oracle@server gg]$
    
  3. Copy the downloaded 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 with the tar command to extract Oracle GoldenGate:

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

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

    export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$GGATE
    
  7. 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
    
  8. Create the necessary working directories for gg:

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

Configuring Oracle GoldenGate on Source System for BRM Adapter

  1. Switch the database to archive log mode as follows:

    [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 a result of 'YES')

    SQL> SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
    
  3. 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 the Oracle Goldengate schema, a default password is provided during the setup phase. You can the default password, but you also need to change the default password in the related prm and oby files.

  5. Grant 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 execute on utl_file to ggate;
    SQL> exit;
    

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

    alter database add supplemental log data;
    
  6. Copy source config file to $GGATE directory

    The files for the source systems have been generated in $ORACL_HOME\ocdm\addon\adapter\brm\goldengate_param\stg

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

    • copy files in $ORACL_HOME\ocdm\addon\adapter\brm\goldengate_param\stg

    • copy files in $ORACL_HOME\ocdm\addon\adapter\brm\goldengate_param\stg

  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 extpbrm.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 BRM_SRC schema at EXTRACT

    The default source schema for the BRM Adapter is BRM_SRC. Change the source schema name through your source system schemas. For example (brm_src ->pin5003)

    Change BRM_SRC schema at $GGATE\dirprm\extpbrm.prm.

    For example:

    Table pin5003.ACCOUNT_NAMEINFO_T, KEYCOLS (OBJ_ID0,REC_ID)
    

    Change BRM_SRC schema at $GGATE\dirprm\extpbrm.prm

    For example:

    Table pin5003.ACCOUNT_NAMEINFO_T;
    

    Change BRM_SRC schema at $GGATE\diroby\ brm_ogg_src_cdc_cmd.oby. For example:

    add TRANDATA pin5003.ACCOUNT_NAMEINFO_T COLS(OBJ_ID0,REC_ID), NOKEY
    

    Note:

    1. In the file brm_ogg_src_cdc_cmd.oby, use the following command for all current mapping tables except table ACCOUNT_T:

      ADD TRANDATA Source Schema Name.Table Name COLS(col1, col2,…), NOKEY
      
    2. If the TRANDATA of each table has been done, use the following command to delete it:

      DELETE TRANDATA Source Schema Name.*
      
  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 system to define an Extract group named extbrm and to define a data pump Extract named extpbrm 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/brm_ogg_src_cdc_cmd.oby
    

    Note: In most of the cases, run the batch commands mentioned in the oby file one by one manually in the Oracle GoldenGate command line util (ggsci).

Note:

For more information on the *.prm files, see the

$ORACLE_HOME\ocdm\addon\adapter\brm\goldengate_param\src\dirprm

Starting Oracle GoldenGate Processes on Source System

To start the primary Extract process and data pump Extract process, run the following command on the source systems.

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

Starting Oracle GoldenGate Processes on Target System

To start the Oracle GoldenGate processes on the target system, run the following command on the target system:

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

Oracle GoldenGate Process Checking Command Reference

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

Table A-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


Troubleshooting the Installation of the BRM Adapter

To deinstall the existing repositories, do the following:

Drop user (Master_Repo_user) cascade;
create user (Master_Repo_user) identified by (pswd) default tablespace users temporary tablespace temp;
grant connect, resource to (Master_Repo_user);
grant execute on dbms_lock to (Master_Repo_user);

This section includes the following topics:

Master and Work Repository Import Errors

Error Message:

Error: /…./…./…./….xml (No such file or directory)

This error could occur when you import repositories using the "Import from a Zip File" option.

Workaround:

To resolve this error "unzip" the Master and Work Repository zip files and start the import again using the "Import from a Folder" option.

Error Recovery: Reimporting Master Repository

To import a master repository (in an existing master repository):

  1. From the Topology Navigator toolbar menu select Import > Master Repository... (as shown in Figure A-26).

    Figure A-26 ODI Studio Import Master Repository

    Description of Figure A-26 follows
    Description of "Figure A-26 ODI Studio Import Master Repository"

  2. Select the Import Mode, the "Import from a Folder" and click OK (Figure A-27).

    Figure A-27 Reimport: Import From a Folder

    Description of Figure A-27 follows
    Description of "Figure A-27 Reimport: Import From a Folder"

    The specified file(s) are imported into the current master repository.

  3. Browse the Master Repository from the specified location:

    Repository Location: $BRM_OCDM_HOME/odi_repository/brm_ocdm_adapter_master

    Figure A-28 ODI Studio Open and Import Master Repository

    Description of Figure A-28 follows
    Description of "Figure A-28 ODI Studio Open and Import Master Repository"

    Figure A-29 ODI Studio Import Master Repository Progress

    Description of Figure A-29 follows
    Description of "Figure A-29 ODI Studio Import Master Repository Progress"

  4. You can check the Import Report and you can save this report by clicking Save.

    Figure A-30 Reimport: Import Report Listing

    Description of Figure A-30 follows
    Description of "Figure A-30 Reimport: Import Report Listing"

Error Recovery: Reimporting Work Repository

To import a work repository:

  1. From the Designer Navigator toolbar menu select Import > Work Repository... (as shown in Figure A-31).

    Figure A-31 ODI Studio Import Work Repository

    Description of Figure A-31 follows
    Description of "Figure A-31 ODI Studio Import Work Repository"

  2. Select the Import Mode: Import From a Folder or Import From a Zip file, and click OK.

    Figure A-32 ODI Studio Import Work Repository from Zip File

    Description of Figure A-32 follows
    Description of "Figure A-32 ODI Studio Import Work Repository from Zip File"

    The specified file(s) are imported into the work repository.

  3. Browse the Work Repository from the specified location.

    Repository Location:

    $BRM_OCDM_HOME/odi_repository/brm_ocdm_adapter_work.zip

    Figure A-33 ODI Studio Import Work Repository from Zip File

    Description of Figure A-33 follows
    Description of "Figure A-33 ODI Studio Import Work Repository from Zip File"

    Figure A-34 ODI Studio Open and Import Work Repository Progress

    Description of Figure A-34 follows
    Description of "Figure A-34 ODI Studio Open and Import Work Repository Progress"

    Figure A-35 Reimport: Work Repository Warning Message Dialog

    Description of Figure A-35 follows
    Description of "Figure A-35 Reimport: Work Repository Warning Message Dialog"

    You can check the Import Report and to save report, click Save.

    Figure A-36 Reimport: Work Repository Report

    Description of Figure A-36 follows
    Description of "Figure A-36 Reimport: Work Repository Report"

View the Designer tab Projects and Models areas to see the contents of the work repository.

Figure A-37 Shows the ODI Designer Navigator with Projects and Models

Description of Figure A-37 follows
Description of "Figure A-37 Shows the ODI Designer Navigator with Projects and Models"

Error ODI-26005: Importing an Object from Another Repository

Error Message:

ODI-26005: You are importing an object from another repository with the same identifier...

Possible cause: An object in the import file has an identifier which already exists in the repository.

Figure A-38 Troubleshooting BRM Adapter Problems

Description of Figure A-38 follows
Description of "Figure A-38 Troubleshooting BRM Adapter Problems"

Workaround:

Consider manually changing the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.

To resolve this error (ODI-26005), make changes depending on the repository:

Resolve ODI Error on Master Repository

Master Repository: To change the ID of ODI master repository, you can "Renumber.." the repository ID with these steps:

  1. From the Topology Navigator, expand Repositories tab.

  2. Right click Master Repository and click "Renumber", as shown in Figure A-39.

    Figure A-39 Renumber Master Repository

    Description of Figure A-39 follows
    Description of "Figure A-39 Renumber Master Repository"

  3. This opens the dialog, "Renumbering the repository - Step 1". Click Yes to renumber the repository ID, as shown in Figure A-40.

    Figure A-40 Renumber Repository Step 1

    Description of Figure A-40 follows
    Description of "Figure A-40 Renumber Repository Step 1"

  4. Provide the New ID for the Master repository and click OK. This displays the Renumbering the repository - Step 2 dialog, as shown in Figure A-41.

    Figure A-41 Renumber Repository Step 2

    Description of Figure A-41 follows
    Description of "Figure A-41 Renumber Repository Step 2"

  5. To check the changed ID, double click master repository and open version tab and check if the new ID is assigned, as shown in Figure A-42.

    Figure A-42 Check Repository ID

    Description of Figure A-42 follows
    Description of "Figure A-42 Check Repository ID"

Resolve ODI Error on Work Repository

To change the ID of ODI work repository, you can "Renumber.." the repository ID as follows:

  1. From the Topology Navigator, expand Repositories tab.

  2. Expand the "Work Repositories", Right click Work Repository and then click "Renumber".

    Figure A-43 Renumber Work Repository

    Description of Figure A-43 follows
    Description of "Figure A-43 Renumber Work Repository"

  3. This opens the dialog, "Renumbering the repository - Step 1". Click Yes to renumber the repository ID.

    Figure A-44 Renumber Work Repository Step 1

    Description of Figure A-44 follows
    Description of "Figure A-44 Renumber Work Repository Step 1"

  4. Click OK in the Renumbering the repository - Step 2 dialog.

    Figure A-45 Renumber Work Repository Step 2

    Description of Figure A-45 follows
    Description of "Figure A-45 Renumber Work Repository Step 2"

  5. Provide the New ID for the Work repository and click OK.

    Figure A-46 Renumber Work Repository Step 3

    Description of Figure A-46 follows
    Description of "Figure A-46 Renumber Work Repository Step 3"

  6. Click Yes to confirm the change.

    Figure A-47 Verify the Renumber Operation

    Description of Figure A-47 follows
    Description of "Figure A-47 Verify the Renumber Operation"

  7. To check the changed ID, double click work repository and open version tab and check that the new ID is assigned.

    Figure A-48 Verify the Changed Repository ID

    Description of Figure A-48 follows
    Description of "Figure A-48 Verify the Changed Repository ID"

Troubleshooting Error: An internal error occurred while opening the diagram...

The following error may happen and is related to an issue with ODI version 11.1.1.7.1:

ERROR: An internal error occurred while opening the diagram

Workaround:

From ODI Studio, open the corrupted Integration Interface, go to the "Version" tab, and get the internal ID. Connect to the database that hosts the ODI Work Repository tables, run the following SQL commands, and apply the changes:

delete from SNP_TXT
where I_TXT in (
select I_TXT_XMI_DATA
from SNP_DIAGRAM
where I_POP = <your internal ID>);
delete from SNP_DIAGRAM
where I_POP = <your internal ID>;
commit;

When you open the Integration Interface the next time, it creates a new Mapping and Flow map, and hence the issue should be resolved.