A BRM Adapter Post-Installation Tasks

This appendix describes the post-installation tasks for Oracle Communications Billing and Revenue Management Adapter for Oracle Communications Data Model (BRM Adapter).

You must install Oracle Communications Data Model Add-ons with the Oracle Communications BRM Adapter component before doing the post-installation tasks in this appendix. See "Installation of Oracle Communications Data Model Add-ons".

Overview of BRM Adapter Post-Installation Tasks

After installing Oracle Communications Data Model Add-ons with the Oracle Communications BRM Adapter component, you must install Oracle Data Integrator and configure the BRM master repository and work repository connections in Oracle Data Integrator. After you install Oracle Data Integrator and configure the repositories, you configure the BRM Adapter to create the required tables in the BRM staging schema.

Additionally, if you want to perform real-time feed of the BRM source data to the Oracle Communications Data Model staging layer, you must install and configure Oracle GoldenGate (in addition to Oracle Data Integrator) on the source and target database for Oracle GoldenGate replication. See Oracle Communications Data Model Adapters and Analytics User's Guide for information on using Oracle GoldenGate with BRM Adapter.

Note:

The post-installation procedures assume the Oracle Communications Data Model warehouse database schema is hosted on the same database instance as the Oracle Data Integrator Repository.

Note:

The post-installation procedures in this appendix can take a significant amount of time to complete.

Installing and Configuring Oracle Data Integrator for BRM Adapter

To use BRM Adapter, you must install and configure Oracle Data Integrator.

Installing Oracle Data Integrator for BRM Adapter

To use BRM Adapter, you must install Oracle Data Integrator Enterprise Edition.

To install Oracle Data Integrator Enterprise Edition:

  1. Download Oracle Data Integrator Enterprise Edition 11g (11.1.1.50) from the Oracle Technology Network at:

    http://www.oracle.com/technetwork/middleware/data-integrator/downloads/index.html

  2. Follow the installation instructions in Installation Guide for Oracle Data Integrator at:

    http://www.oracle.com/technetwork/middleware/data-integrator/documentation/index.html

Configuring Oracle Data Integrator for BRM Adapter

To configure Oracle Data Integrator for BRM Adapter, do the following steps:

  1. Creating the Oracle Data Integrator Connection for BRM Adapter Repository

  2. Setting up the Oracle Data Integrator Topology

Creating the Oracle Data Integrator Connection for BRM Adapter Repository

To create the Oracle Data Integrator connection for BRM Adapter Repository, perform the following steps:

  1. Start Oracle Data Integrator Studio:

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

    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''

  8. Right-click on the Work Repositories tab and click New Work Repository.

    Figure A-7 ODI Studio Data Server Work Repositories Tab

    Description of Figure A-7 follows
    Description of ''Figure A-7 ODI Studio Data Server Work Repositories Tab''

  9. Specify the ODI Work Repository connection properties, as described in Table A-2, then click Test Connection.

    Figure A-8 ODI Work Repository Connection Properties Screen

    Description of Figure A-8 follows
    Description of ''Figure A-8 ODI Work Repository Connection Properties Screen''

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

    User

    Specify the default user name brm_odiw.

    Password

    Specify the default password brm_odiw.


  10. Click Next after successful connection.

  11. Click Yes to reattch the work repository.

    Figure A-9 ODI Create Work Repository Confirmation Dialog Box

    Description of Figure A-9 follows
    Description of ''Figure A-9 ODI Create Work Repository Confirmation Dialog Box''

  12. Specify the password of the ODI work repository to attach, then click Next.

    Figure A-10 ODI Work Repository Password Field

    Description of Figure A-10 follows
    Description of ''Figure A-10 ODI Work Repository Password Field''

  13. Specify the name of the ODI work repository to attach and click Finish.

    Figure A-11 ODI Create Work Repository Name Field

    Description of Figure A-11 follows
    Description of ''Figure A-11 ODI Create Work Repository Name Field''

  14. Click Disconnect "BRM Adapter" from the ODI drop-down list.

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

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

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

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

    Description of Figure A-13 follows
    Description of ''Figure A-13 Edit Option in the ODI Studio Data Server Login Dialog Box''

  16. 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-14 ODI Studio Data Server Work Repository Connection Fields and Values

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

  17. 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 Oracle Data Integrator Topology

To set up the Oracle Data Integrator 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-15 Oracle Data Integrator Studio Physical Data Servers

    Description of Figure A-15 follows
    Description of ''Figure A-15 Oracle Data Integrator 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-16 Oracle Data Integrator Studio Data Server Definition Dialog

    Description of Figure A-16 follows
    Description of ''Figure A-16 Oracle Data Integrator Studio Data Server Definition Dialog''

    Table A-3 Oracle Data Integrator 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-4.

    Figure A-17 Oracle Data Integrator Studio Data Server JDBC Tab

    Description of Figure A-17 follows
    Description of ''Figure A-17 Oracle Data Integrator Studio Data Server JDBC Tab''

    Table A-4 Oracle Data Integrator 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-18.

    Figure A-18 Oracle Data Integrator Studio Data Server Test Connection

    Description of Figure A-18 follows
    Description of ''Figure A-18 Oracle Data Integrator Studio Data Server Test Connection''

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

    Figure A-19 Test Connection Information Dialog

    Description of Figure A-19 follows
    Description of ''Figure A-19 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-20 Oracle Data Integrator Studio Physical Architecture Data Server Node

    Description of Figure A-20 follows
    Description of ''Figure A-20 Oracle Data Integrator 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-5.

    Figure A-21 Oracle Data Integrator Studio Physical Schema Definition Tab

    Description of Figure A-21 follows
    Description of ''Figure A-21 Oracle Data Integrator Studio Physical Schema Definition Tab''

    Table A-5 Oracle Data Integrator 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-22 Oracle Data Integrator Studio Logical Architecture for Logical Data Server

    Description of Figure A-22 follows
    Description of ''Figure A-22 Oracle Data Integrator 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-23 Oracle Data Integrator Studio Logical Data Server Definition Tab for Logical Schema

    Description of Figure A-23 follows
    Description of ''Figure A-23 Oracle Data Integrator 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-24 ODI Studio Logical Data Server Context Tab

    Description of Figure A-24 follows
    Description of ''Figure A-24 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.

Note:

If you plan to real-time ETL, you must also install and configure Oracle GoldenGate. See "Installing and Configuring Oracle GoldenGate for BRM Adapter."

Setting Up the Topology for BRM Multischema Deployment

If your BRM system uses multischema architecture, set up the topology for a BRM multischema deployment.

The following are a guideline to set up the topology for a BRM multischema deployment and assumes that the BRM system has one primary schema and one secondary schema.

Using Oracle Data Integrator Studio, do the following:

  1. Navigate to the Topology navigator.

  2. Create the source and staging physical schemas for the BRM primary and secondary schemas.

    Figure A-25 shows the source physical schemas (brm_src and brm_src_schema2), and the staging physical schemas (brm_stg and brm_stg_schema2):

    Figure A-25 Physical Schema Architecture for BRM Multischema Deployment

    Description of Figure A-25 follows
    Description of ''Figure A-25 Physical Schema Architecture for BRM Multischema Deployment''

  3. Create the source and staging logical schemas for the BRM primary and secondary schemas.

    Figure A-26 shows the source logical schemas (brm_src_ls and brm_src_ls_schema2) and the staging logical schemas (brm_stg_ls and brm_stg_ls_schema2):

    Figure A-26 Logical Schema Architecture for BRM Multischema Deployment

    Description of Figure A-26 follows
    Description of ''Figure A-26 Logical Schema Architecture for BRM Multischema Deployment''

  4. Create the contexts for the BRM primary and secondary schemas and associate the logical schemas with the physical schemas in the contexts.

    Figure A-27 shows the Global Data context that associates the source logical schemas, brm_src_ls and brm_stg_ls, to the source physical schemas, brm_src and brm_stg:

    Figure A-27 Context for BRM Multischema Deployment

    Description of Figure A-27 follows
    Description of ''Figure A-27 Context for BRM Multischema Deployment''

    The following example shows the Subscriber Data context that associates the source logical schemas, brm_src_ls_schema2 and brm_stg_ls_schema2, to the source physical schemas, brm_src_schema2 and brm_stg_schema2:

    Figure A-28 Context for BRM Multischema Deployment

    Description of Figure A-28 follows
    Description of ''Figure A-28 Context for BRM Multischema Deployment''

For more information about setting up the topology in Oracle Data Integrator Studio, see Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

Configuring the BRM Adapter

Configuring the BRM Adapter involves creating the required BRM staging schema (BRM_STG) tables.

To configure the BRM staging schema tables:

  1. Using Oracle Data Integrator Studio, connect to the BRM Adapter work repository.

  2. In the Designer navigator, expand the BRM-OCDM project folder and then the CONFIG folder (as shown in Figure A-29).

    Figure A-29 BRM Adapter Files CONFIG Folder

    Description of Figure A-29 follows
    Description of ''Figure A-29 BRM Adapter Files CONFIG Folder''

    The CONFIG folder contains Oracle Communications Data Model 11.3.2.1 procedures and the Oracle Communications Data Model 11.3.2 packages.

  3. Select the 11.3.2 package, then right-click and select Run.

    Note:

    Do not run the procedure alone. Running the procedure will fail and might lead to configuration issues. If the package fails, do not run it again. Check the failures and then manually run the steps in the package from the failed step onwards.

Reviewing the BRM Adapter Configuration Steps

The BRM Adapter configuration includes multiple steps. Review the steps as follows.

  1. SERVICE_T_MAP_VW - create view

    This step creates mapping table in BRM_STG schema. You do not need to review this.

    Note:

    Refer to DWL_SRVC_TYP table. If a new service is added, then you need to add an entry into the DWR_SRVC_TYP table.
  2. BRM_DD_OBJECTS_MAP - create table

    This step creates table in BRM_STG schema for default mapping values. You do not need to review this step.

  3. brm_dd_objects_map - insert

    This step inserts mappings between BRM services. The BRM Adapter uses mappings. This step includes different insert statements as shown in Table A-6. Update these insert statements for your needs.

    Table A-6 BRM_DD_Object_Map Statements

    Mapping Description

    SERVICE_MAP

    This mapping is used to assign proper names to different BRM services. Using the BRM services name directly in the reports may not make any sense. In this mapping you assign proper, that is understandable names to each of the BRM services:

    insert into brm_dd_objects_map values (1868, '/service/email', 'EMAIL', 'SERVICE_MAP', sysdate, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/service/*).

    3. User understandable service name.

    4. Map type - do not change this column (key column used in adapter mapping).

    SERVICE_TYPE

    This mapping defines the type for BRM services. Values added services are tagged as 'VAS'

    insert into brm_dd_objects_map values (1868, '/service/email', 'REGULAR', 'SERVICE_TYPE', sysdate, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/service/*).

    3. Service type

    4. Map type - do not change this column (key column used in adapter mapping).

    PRICE_TYPE

    This mapping maps BRM price types to Oracle Communications Data Model price types. Oracle Communications Data Model has defined certain price type and these price types are used within IETL to generate derived and aggregated tables.

    Oracle Communications Data Model specification:

    1. 1% Recurring Fee

    2. 2% Onetime fee

    3. 3% Onetime usage

    4. 4% Duration based usage

    5. 5% Volume based usage

    6. 6% Free of charge

    7. 7% Usage discount

    8. 8% Other discounts

    9. -5000 unknown

    You can extend this list.

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (1696,'/item/cycle_arrear','1100', 'PRICE_TYPE',SYSDATE, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/item/*).

    3. Price type

    4. Map type - do not change this column (key column used in adapter mapping).

    Refer to DWL_PRICE_TYP Oracle Communications Data Model table. If a new price type is added, then make sure to add entry into DWL_PRICE_TYP table in Oracle Communications Data Model.

    Make sure to map '/item/adjustment' as 'ADJUSTMENT'. This is used in mapping to find adjustments items.

    INVC_ITEM_TYPE

    Define the item type for each of invoice items. It is similar to PRICE TYPE. Oracle Communications Data Model specification:

    1. 1% Recurring Fees

    2. 2% One Time Fees

    3. 3% Usage (any type)

    4. 4% Recharges (any type)

    5. 5% to be defined

    6. 6% Discounts

    7. 7% Carry Over

    8. 8% Penalty

    9. 9% Specials (adj, write off, redirection,...)

    Insert into brm_dd_objects_map values (1696,'/item/cycle_arrear','1000','INVC_ITEM_TYPE',SYSDATE, 'ADMIN');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/item/*).

    3. Invoice item type

    4. Map type - do not change this column (key column used in adapter mapping).

    Refer to DWL_INVC_ITEM_TYP Oracle Communications Data Model table. If a new invoice item is added, then make sure to add entry into DWL_INVC_ITEM_TYP table in Oracle Communications Data Model.

    DWL_INVC_DISC_TYP

    Maps BRM discount types to Oracle Communications Data Model mapping. BRM discount type can derived from event POID type.

    Oracle Communications Data Model specification:

    1. 1% Recurring Discount

    2. 2% Onetime Discount

    3. 3% Onetime usage discount

    4. 4% Usage Discount

    You can extend this list.

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (2214,'/event/delayed/session/telco/gsm','4000', 'DWL_INVC_DISC_TYP',SYSDATE, 'admin');
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/event/*).

    3. Discount Oracle Communications Data Model map

    4. Map type - do not change this column (key column used in adapter mapping).

    Refer to DWL_INVC_DISC_TYP Oracle Communications Data Model table. If a new discount type is added, then make sure to add entry into DWL_INVC_DISC_TYP table in Oracle Communications Data Model.

    EVENT_TYPE_MAP

    You can map different event POID type to some understandable names. This will help you for better reporting with meaningful names for event types.

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (2244,'/event/delayed/session/telco/gprs','USAGE','EVENT_TYPE_MAP', SYSDATE, NULL);
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/event/*).

    3. Event type map

    4. Map type - do not change this column (key column used in adapter mapping).

    Refer to DWL_EVT_TYP Oracle Communications Data Model table. If new event type is added,then make sure to add entry intoDWL_EVT_TYP table in Oracle Communications Data Model.

    ROAMING_TYPE_MAP

    This mapping is used to find roaming and non-roaming events. Configure this mapping to distinguish between roaming and non-roaming calls.

    Oracle Communications Data Model specification:

    1. NONROAM

    2. ROAM

    INSERT INTO BRM_DD_OBJECTS_MAP VALUES (2216,'/event/delayed/session/telco/gsm/roaming','ROAM','ROAMING_TYPE_MAP', SYSDATE, NULL);
    
    1. Obj_id0 column from dd_objects_t table.

    2. Name column from dd_objects_t table (/event/*).

    3. Roaming type map

    4. Map type - do not change this column (key column used in adapter mapping).

    Refer to DWL_RMNG_TYP Oracle Communications Data Model table.


  4. BRM_DD_OBJ_MAP_DEFAULT - create table

    This step creates default mapping table in BRM_STG schema. You do not need to review this step.

  5. BRM_DD_OBJ_MAP_DEFAULT - insert

    You can skip this step review, but it is recommended to review. Here you can define default values, in case mapping is not available for DD_OBJECT. If this step is not configured for any of mapping then it will return -5000 by default.

    INSERT INTO BRM_DD_OBJ_MAP_DEFAULT VALUES ('SERVICE_MAP', '-5000', SYSDATE, 'ADMIN')
    
    1. Map type (refer BRM_DD_OBJECTS_MAP table).

    2. Default value (make sure this value is available in respective lookup table).

  6. BRM_GET_DD_OBJ_MAP - create function

    This step creates BRM_GET_DD_OBJ_MAP function. You do not need to review this step.

  7. brm_odi_exception_handle - create table

    This step creates exception handling table. You do not need to review this step.

    See the discussion about exception handling in Oracle Communications Data Model Adapters and Analytics User's Guide.

  8. DWC_ETL_MATRIX_OCDMLKUP_MATCH - INSERT

    This step provides extensions to the existing DWC_ETL_MATRIX_OCDMLKUP_MATCH mapping. This mapping is extended as shown in Table A-7:

    Table A-7 ETL OCDM Lookup Extensions

    Table Mapping Description

    DWL_INVC_ADJ_TYP

    You can map BRM adjustment type to Oracle Communications Data Model for better reporting. BRM adjustments are defined in STRINGS_T table in BRM. It is recommended to consult BRM developer for detail regarding VERSION range used for adjustment type. Actual adjustments event are available in EVENT_T and EVENT_BILLING_MISC_T BRM table.

    Oracle Communications Data Model specification:

    1. 2% Credit reasons

    2. 8% Debit reasons

    3. 3% Bill settlements

    4. 4% Write off

    You can extend this list.

    Refer DWL_INVC_ADJ_TYP Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_INVC_ADJ_TYP Oracle Communications Data Model table.

    (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'STRINGS_T', 'VERSION', '21', 'DWL_INVC_ADJ_TYP', 'INVC_ADJ_TYP_CD', '221000');
    
    1. SRC_SYS_TAB_COL_VAL - BRM adjustment value. You need to configure this according to BRM system configuration.

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    Refer DWL_INVC_ADJ_TYP Oracle Communications Data Model table. If you add new adjustment type then make sure to make entry into DWL_INVC_ADJ_TYP table. If you do not want to make entry into DWL_INVC_ADJ_TYP table then recommended disabling respective constraints. If not done, it might lead to BRM adapter data load failure.

    DWL_INVC_ADJ_RSN

    You can map BRM adjustment reasons to Oracle Communications Data Model. BRM adjustments reasons are defined in STRINGS_T table in BRM. It is recommended to consult BRM developer for detail regarding VERSION and STRING_ID range used for adjustment reason.

    Actual adjustments event are available in EVENT_T and EVENT_BILLING_MISC_T BRM table.

    Oracle Communications Data Model specification:

    1. 2% Credit reasons

    2. 8% Debit reasons

    3. 3% Bill settlements

    4. 4% Write off

    You can extend this list.

    Refer DWL_INVC_ADJ_RSN Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_INVC_ADJ_RSN Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'STRINGS_T', 'STRING_ID', '21-1', 'DWL_INVC_ADJ_RSN', 'INVC_ADJ_RSN_CD', '221100');
    
    • SRC_SYS_TAB_COL_VAL - BRM adjustment reason. If you need to configure this according to BRM system configuration. This column value is combination of both VERSION and STRING_ID from STRINGS_T table (VERSION || '_' || STRING_ID). This helps in assigning reason codes to respective adjustment types.

    • OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_CUST_TYP

    You can map BRM customer residency type to Oracle Communications Data Model customer type. Different business types are defined CONFIG_BUSINESS_TYPE_T BRM table. BRM adapter moves this table data into DWL_CUST_TYP Oracle Communications Data Model table.

    Oracle Communications Data Model specification:

    1. IND - individual customers

    2. ORG - Business customers

    You can extend this list.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL, OCDM_TGT_TAB_COL_VAL_DEF_IND, EFF_FROM_DT, EFF_TO_DT) VALUES ('BRM', 'CONFIG_BUSINESS_TYPE_T', 'REC_ID', '0', 'DWL_CUST_TYP', 'CUST_TYP_CD', 'IND', NULL, NULL, NULL);
    
    1. SRC_SYS_TAB_COL_VAL - REC_ID from CONFIG_BUSINESS_TYPE_T BRM table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_BLLG_PRD

    You can map BRM "BILL WHEN" to Oracle Communications Data Model mapping. You do not need to change this mapping but still recommended to review.

    Oracle Communications Data Model specification:

    1. MONTHLY

    2. BI MONTHLY

    3. QUARTERLY

    4. ANNUALLY

    You can extend this list.

    Refer DWL_BLLG_PRD Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_BLLG_PRD Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'PIN_FLD_BILL_WHEN', 'PIN_FLD_BILL_WHEN', '12', 'DWL_BLLG_PRD', 'BLLG_PRD_CD', 'ANNUALLY');
    
    1. SRC_SYS_TAB_COL_VAL - "BILL WHEN" value from BRM

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value. Can set any value by following Oracle Communications Data Model specifications mentioned above.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_PYMT_MTHD_TYP

    You can configure different payment methods available in BRM system to Oracle Communications Data Model. BRM payment methods are configured in CONFIG_PAYMENT_PAY_TYPES_T BRM table. BRM adapter moves data from CONFIG_PAYMENT_PAY_TYPES_T table to DWL_PYMT_MTHD_TYP Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'CONFIG_PAYMENT_PAY_TYPES_T', 'REC_ID', '10003', 'DWL_PYMT_MTHD_TYP', 'PYMT_MTHD_TYP_CD', '3');
    
    1. SRC_SYS_TAB_COL_VAL - REC_ID from CONFIG_PAYMENT_PAY_TYPES_T BRM table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_CALL_TYP

    You can configure call type using this configuration option. Balance impact category can be used to configure different call types.

    Oracle Communications Data Model specification:

    1. NTNL - National calls

    2. LCL - Local calls

    3. INTL - International calls

    You can extend this list.

    Refer DWL_CALL_TYP Oracle Communications Data Model table. If you are adding new entry, then make sure to add same into DWL_CALL_TYP Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'CONFIG_IMPACT_CATEGORIES_T', 'REC_ID', 'NAT_FIX', 'DWL_CALL_TYP', 'CALL_TYP_CD', 'NTNL');
    
    1. SRC_SYS_TAB_COL_VAL - BRM balance impact category

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value for call type map.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_CALL_SUCC_FAIL_TYP

    You can configure call termination cause. Termination cause is available in EVENT_SESSION_TLCS_T table.

    Oracle Communications Data Model specification:

    1. SUCC - Successful call

    2. FAIL - Call failed

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'EVENT_SESSION_TLCS_T', 'TERMINATE_CAUSE', '0', 'DWL_CALL_SUCC_FAIL_TYP', 'CALL_SUCC_FAIL_TYP_CD', 'SUCC');
    
    1. SRC_SYS_TAB_COL_VAL - Call TERMINATE_CAUSE from EVENT_SESSION_TLCS_T BRM table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value for call termination.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.

    DWL_INVC_STAT

    This mapping is used configure invoice status. You do not need to make any changes to this mapping but still recommended to review. STATUS column from INVOICE_T is BRM source for invoice statues.

    Oracle Communications Data Model specification:

    1. 1% Invoice is open but pending (not yet physically or digitally created to dispatch)

    2. 2% Invoice is created but not yet dispatched

    3. 3% Invoice is created and has been sent or published for customer to see (sub-types allowed)

    4. 5% Invoice has been fully paid.

    5. 9% Invoice was sent but came back.

    You can extend this list.

    Refer DWL_INVC_STAT Oracle Communications Data Model table. If you are adding a new entry, then make sure to add same into DWL_INVC_STAT Oracle Communications Data Model table.

    Insert into DWC_ETL_MATRIX_OCDMLKUP_MATCH (SRC_SYS_KEY, SRC_SYS_TAB_NAME, SRC_SYS_TAB_COL_NAME, SRC_SYS_TAB_COL_VAL, OCDM_TGT_TAB_NAME, OCDM_TGT_TAB_COL_NAME, OCDM_TGT_TAB_COL_VAL) VALUES ('BRM', 'INVC_STAT', 'INVC_STAT_CD', '0', 'DWL_INVC_STAT', 'INVC_STAT_CD', '1000');
    
    1. SRC_SYS_TAB_COL_VAL - Invoice STATUS from INVOICE_T table

    2. OCDM_TGT_TAB_COL_VAL - Oracle Communications Data Model mapping value for invoice status.

    You are not allowed to change the rest of columns as these are used in adapter mapping to refer this mapping configuration.


  9. EVENT_BAL_IMPACT_COLL_VW - create view

    This step rebuilds the EVENT_BAL_IMPACT_CALL_VW view. You do not need to review this step.

  10. EVENT_BILLING_PAYMENT_T_MAP_VW - create view

    This step rebuilds the EVENT_BILLING_PAYMENT_T_MAP_VW view. You do not need to review this step.

  11. OCDM SYS - Disable Constraints

    This step disables few of OCDM constraint.You do not need to review this step.

  12. DWL_ADDR_TYP - insert

    You can configure different address type using CONTACT_TYPE column from ACCOUNT_NAMEINFO_T table. You need to configure it same as BRM value.

  13. DWL_BLLG_PRD - insert

    You do not need to makes changes to this step. Refer step 8 for more detail.

  14. DWL_BLLG_STAT_TYP - insert

    You do not need to make changes in this step but recommended to review. Source for this mapping is BILLING_STATUS column of BILLINFO_T BRM table and OCDM target is BLLG_STAT_CD column of DWR_ACCT table.

  15. DWL_INVC_ADJ_RSN - insert

    You need to review this mapping and also verify with step 8 (DWL_INVC_ADJ_RSN)

  16. DWL_INVC_ADJ_TYP - insert

    You need to review this mapping and verify with step 8 (DWL_INVC_ADJ_TYP)

  17. DWL_INVC_DISC_TYP - insert

    You need to review this mapping and verify with step 3 (DWL_INVC_DISC_TYP)

  18. DWL_INVC_DLVRY_TYP - insert

    You can configure different invoice delivery types. STATUS from INVOICE_STATUSES_T table is BRM source. BRM adapter uses this information to find delivery type and invoice dispatch date.

  19. BRM_ETL_PARAMETER - TO_DATE_ETL(null)

    This step alters BRM_ETL_PARAMETER table, makes TO_DATE_ETL as nullable. You do not need to review this step.

  20. BRM_ETL_LOAD_PLAN - create table

    Creates table for load scheduling.You do not need to review this step.

  21. GRANT ALL TO OCDM_SYS

  22. grant all to ocdm_sys

    Grants BRM_STG object access to OCDM_SYS schema. This is required in BRM adapter mapping. You do not need to review this step.

  23. DWL_SRVC_TYP - insert

    You do not need to review this mapping configuration.

  24. BRM_ETL_PARAMETER - insert

    Deletes existing BRM_ETL_PARAMETERS and makes dummy entry. You do not need to review this step.

  25. UPDATE DWL_ONOFF_NET

    Updates DWL_ONOFF_NET table with proper OCDM lookup values.

  26. dwl_rmng_typ - insert (NONROAM)

    Makes entry into DWL_RMNG_TYP table for NONROAM. You do not need to review this step.

  27. DWR_BLLG_CYCL - insert

    Makes entry into DWR_BLLG_CYCL table for billing cycle. You do not need to review this step.

  28. DWB_INVC - DUMMY INVOICE

    Makes dummy entry into DWB_INVC table.You do not need to review this step.

  29. DWL_CALL_DRCTN - CALL FORWARD

    BRM add new call direction type as call forwarding. This step adds the entry into DWL_CALL_DRCTN table. You do not need to review this step.

Installing and Configuring Oracle GoldenGate for BRM Adapter

Install and configure Oracle GoldenGate only if you want to perform real-time data feed of the BRM source data to the data warehouse.

To install and configure Oracle GoldenGate for BRM Adapter, do the following:

  1. Installing Oracle GoldenGate on Target for BRM Adapter

  2. Configuring Oracle GoldenGate on Target for BRM Adapter

  3. Installing Oracle GoldenGate on Source for BRM Adapter

  4. Configuring Oracle GoldenGate on Source System for BRM Adapter

  5. Starting Oracle GoldenGate Processes on Source System

  6. Starting Oracle GoldenGate Processes on Target System

Installing Oracle GoldenGate on Target for BRM Adapter

To install Oracle GoldenGate:

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

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

    Description of Figure A-30 follows
    Description of ''Figure A-30 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 gg folder 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. Download Oracle GoldenGate 11g (11.1.1.1.0) from Oracle Technology Network at: http://www.oracle.com/technetwork/middleware/goldengate/downloads/index.html

  4. Copy the downloaded software (for example: V22228-01.zip) into gg folder.

  5. Unzip the software in the folder. For example:

    [oracle@server gg]$ unzip V22228-01.zip
    
  6. Extract the Oracle GoldenGate .tar file using the following command:

    [oracle@server gg] tar -xf filename.tar
    
  7. Export the path to Oracle GoldenGate libraries to LD_LIBRARY_PATH using the command:

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

    GGSCI (server.oracle.com) 1>create subdirs
    GGSCI (server.oracle.com) 2>exit
    [oracle@server gg]$ mkdir $GGATE/diroby
    

After Oracle GoldenGate is installed, you must configure the source and target database for Oracle GoldenGate Replication.

Note:

The steps for installing Oracle GoldenGate on the target database and the steps for installing Oracle GoldenGate on the source database are same.

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-31 Changing Directory to the Oracle Database Installation Path

    Description of Figure A-31 follows
    Description of ''Figure A-31 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. Download Oracle GoldenGate 11g (11.1.1.1.0) from Oracle Technology Network at: http://www.oracle.com/technetwork/middleware/goldengate/downloads/index.html

  4. Copy the downloaded software (for example: V22228-01.zip) into gg folder.

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

    [oracle@server gg]$ unzip V22228-01.zip
    
  6. Extract the Oracle GoldenGate .tar file using the following command:

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

    export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$GGATE
    
  8. 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 gg:

    GGSCI (server.oracle.com) 1>create subdirs
    GGSCI (server.oracle.com) 2>exit
    [oracle@server gg]$ mkdir $GGATE/diroby
    

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

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-8 provides a summary of Oracle GoldenGate process commands. Note: Run these commands from GGSCI.

Table A-8 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-32).

    Figure A-32 ODI Studio Import Master Repository

    Description of Figure A-32 follows
    Description of ''Figure A-32 ODI Studio Import Master Repository''

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

    Figure A-33 Reimport: Import From a Folder

    Description of Figure A-33 follows
    Description of ''Figure A-33 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-34 ODI Studio Open and Import Master Repository

    Description of Figure A-34 follows
    Description of ''Figure A-34 ODI Studio Open and Import Master Repository''

    Figure A-35 ODI Studio Import Master Repository Progress

    Description of Figure A-35 follows
    Description of ''Figure A-35 ODI Studio Import Master Repository Progress''

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

    Figure A-36 Reimport: Import Report Listing

    Description of Figure A-36 follows
    Description of ''Figure A-36 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-37).

    Figure A-37 ODI Studio Import Work Repository

    Description of Figure A-37 follows
    Description of ''Figure A-37 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-38 ODI Studio Import Work Repository from Zip File

    Description of Figure A-38 follows
    Description of ''Figure A-38 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-39 ODI Studio Import Work Repository from Zip File

    Description of Figure A-39 follows
    Description of ''Figure A-39 ODI Studio Import Work Repository from Zip File''

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

    Description of Figure A-40 follows
    Description of ''Figure A-40 ODI Studio Open and Import Work Repository Progress''

    Figure A-41 Reimport: Work Repository Warning Message Dialog

    Description of Figure A-41 follows
    Description of ''Figure A-41 Reimport: Work Repository Warning Message Dialog''

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

    Figure A-42 Reimport: Work Repository Report

    Description of Figure A-42 follows
    Description of ''Figure A-42 Reimport: Work Repository Report''

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

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

Description of Figure A-43 follows
Description of ''Figure A-43 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-44 Troubleshooting BRM Adapter Problems

Description of Figure A-44 follows
Description of ''Figure A-44 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-45.

    Figure A-45 Renumber Master Repository

    Description of Figure A-45 follows
    Description of ''Figure A-45 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-46.

    Figure A-46 Renumber Repository Step 1

    Description of Figure A-46 follows
    Description of ''Figure A-46 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-47.

    Figure A-47 Renumber Repository Step 2

    Description of Figure A-47 follows
    Description of ''Figure A-47 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-48.

    Figure A-48 Check Repository ID

    Description of Figure A-48 follows
    Description of ''Figure A-48 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-49 Renumber Work Repository

    Description of Figure A-49 follows
    Description of ''Figure A-49 Renumber Work Repository''

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

    Figure A-50 Renumber Work Repository Step 1

    Description of Figure A-50 follows
    Description of ''Figure A-50 Renumber Work Repository Step 1''

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

    Figure A-51 Renumber Work Repository Step 2

    Description of Figure A-51 follows
    Description of ''Figure A-51 Renumber Work Repository Step 2''

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

    Figure A-52 Renumber Work Repository Step 3

    Description of Figure A-52 follows
    Description of ''Figure A-52 Renumber Work Repository Step 3''

  6. Click Yes to confirm the change.

    Figure A-53 Verify the Renumber Operation

    Description of Figure A-53 follows
    Description of ''Figure A-53 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-54 Verify the Changed Repository ID

    Description of Figure A-54 follows
    Description of ''Figure A-54 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.