Skip Headers
Oracle® Communications Data Model Adapters and Analytics User's Guide
Release 11.3.2

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

2 Using the BRM Adapter

This chapter provides information about populating an Oracle Communications Data Model warehouse using the Oracle Communications Billing and Revenue Management Adapter for Oracle Communications Data Model (BRM Adapter).

This chapter includes the following topics:

For information on installing and configuring the BRM Adapter for Oracle Communications Data Model, see Oracle Communications Data Model Installation Guide.

For detailed information about the objects and ETL associated with the BRM Adapter for Oracle Communications Data Model, see Oracle Communications Data Model Reference.

Populating a Warehouse Using the BRM Adapter for Oracle Communications Data Model

You use the BRM Adapter for Oracle Communications Data Model to populate or refresh the foundation layer of the Oracle Communications Data Model warehouse (that is, the base, reference, and lookup tables defined in the ocdm_sys schema). For more information, see:

After you use the BRM Adapter for Oracle Communications Data Model to populate the foundation layer, you populate or refresh the access layer of the Oracle Communications Data Model (that is, the derived tables, aggregate tables, OLAP cubes, and data mining models defined in the ocdm_sys schema) in the same manner as you would if you were not using an application adapter for Oracle Communications Data Model to populate the foundation layer. For more information, see Oracle Communications Data Model Implementation and Operations Guide.

Performing an Initial Load with the BRM Adapter for Oracle Communications Data Model

You can prepare your own load plans to move data from source to Oracle Communications Data Model but Oracle Communications Data Model provides different scenarios for out of the box to loads.

While preparing a load plan, you can move data in any sequence into staging but while preparing load plan for staging to Oracle Communications Data Model you must follow the load execution sequence. Execution sequence number is attached to package name.

To perform an initial load of the foundation layer of an Oracle Communications Data Model warehouse using the BRM Adapter for Oracle Communications Data Model with BRM adapter, run following scenarios as required:

Figure 2-1 Initial Load Scenario for BRM Adapter

Description of Figure 2-1 follows
Description of "Figure 2-1 Initial Load Scenario for BRM Adapter"

SRC_STG_LOAD

Running this scenario will load data into staging layer.

Before starting SRC_STG_LOAD scenario make sure to set BRM_ETL_PARAMETER table.

INSERT INTO BRM_ETL_PARAMETER (PROCESS_NAME, FROM_DATE_ETL, TO_DATE_ETL, LOAD_DT) VALUES ('BRM-ADAPTER', '01-JAN-1970', '31-DEC-2012', SYSDATE);
  1. PROCESS_NAME - 'BRM-ADAPTER'

  2. FROM_DATE_ETL - Load start from date

  3. TO_DATE_ETL - Load up to date

  4. LOAD_DT - mostly sysdate

Note:

In case TO_DATE_ETL date is null then system will set this as source system date. This is useful in incremental load.

BRM_ETL_PARAMETER added as filter to query passed to source system as shown:

MOD_T >= FROM_DATE_ETL AND MOD_T < TO_DATE_ETL

While running this scenario makes sure none of statuses are in 'RUNNING' and 'COMPLETED':

SELECT * FROM BRM_EXEC_STAT where proc_typ = 'SRC_STG';

This condition is added to avoid multiple processes at the same time and also to check process completeness. RUNNING status is set when source to staging or staging to Oracle Communications Data Model load scenarios are running.

Once source to stage scenario is completed, it changes status to COMPLETED.

Note:

Every time when source to staging scenarios are run, it truncates staging table. To ensure that data is not duplicated.

BRM Adapter is designed to move data into history tables. History table mapping is available in BRM_MAPPING_TAB staging table. By default BRM adapter moves data into history tables. If required you can disable moving data into history tables by passing below query:

UPDATE BRM_MAPPING_TAB SET DELTA_HIST_TAB_NAME = NULL WHERE NORMAL_TAB_NAME = 'ACCOUNT_T';

This query only disables history for ACCOUNT_T source table. If required, you can disable history for all tables by removing WHERE clause from this query.

In case BRM_MAPPING_TAB does not have entry for history table then you can make an entry.

Note:

History table structure must be same as delta table (staging later tables).

STG_OCDM_LOAD

Running this scenario loads data into Oracle Communications Data Model tables. It is required to have SRC_STG process status as COMPLETED.

This scenario will only run when SRC_STG process type is set to COMPLETED. This scenario also sets the execution status to RUNNING and finally sets both SRC_STG and STG_OCDM process status to CLOSED.

SELECT * FROM BRM_EXEC_STAT where proc_typ = 'STG_OCDM';

After the staging to Oracle Communications Data Model load (STG_OCDM_LOAD) is finished, BRM_ETL_PARAMETER table is updated as shown:

UPDATE BRM_ETL_PARAMETER SET FROM_DATE_ETL = TO_DATE_ETL, TO_DATE_ETL = NULL where PROCESS_NAME = 'BRM-ADAPTER';

Note:

You must check E$_{OCDM Table}, for any rejected records during staging to Oracle Communications Data Model load. These tables are truncated every load.

END_TO_END_LOAD_PLAN

This package runs SRC_STG_LOAD and STG_OCDM_LOAD scenario. Running this package loads data in staging and then Oracle Communications Data Model. This scenario runs both SRC_STG_LOAD and STG_OCDM_LOAD.

END_TO_END_LOAD_PLAN__SCHEDULING

This package runs in iteration. Iterations are based on the user configuration. You configure multiple iterations by making entries into BRM_ETL_LOAD_PLAN BRM_STG table.

BRM_ETL_LOAD_PLAN configuration:

INSERT INTO BRM_ETL_LOAD_PLAN (LOAD_SEQUENCE, FROM_DATE_ETL, TO_DATE_ETL, PROCESS_STATUS) VALUES (10, '01-JAN-2001', '31-DEC-2012', NULL);

You can have multiple entries into table. Make sure not to insert CLOSED into PROCESS_STATUS column. CLOSED is considered as processed.

Every time when schedule is run, current entry from BRM_ETL_LOAD_PLAN table copied into BRM_ETL_PARAMETER table. BRM Adapter uses BRM_ETL_PARAMETER parameter to filter data at BRM source.

Performing Data Refresh with the BRM Adapter for Oracle Communications Data Model (Change Data Capture: CDC)

Once you have performed an initial data load of an Oracle Communications Data Model warehouse, when you must refresh the data, you use ODI to refresh all of the data in the staging area and in the foundation layer of the Oracle Communications Data Model warehouse.

Refreshing the Foundation Layer on a Scheduled Basis

If you are not using the BRM Adapter for Oracle Communications Data Model with Oracle GoldenGate to populate the foundation layer of an Oracle Communications Data Model warehouse, then you refresh the foundation layer on a scheduled basis using Oracle Data Integrator (ODI).

To refresh the data in the foundation layer using only ODI, take the following steps:

  1. Verify that the installation and configuration created the schema objects described in "Schema Definitions Added for the BRM Adapter for Oracle Communications Data Model".

    See:

    Oracle Communications Data Model Installation Guide for instructions on installing and configuring the BRM Adapter for Oracle Communications Data Model for use by ODI.
  2. Reset the BRM_ETL_PARAMETER table parameter values:

    1. Connect to the staging schema (for example: BRM_STG).

    2. Review BRM_ETL_PARAMETER table. If required you can update the ETL parameter. BRM_ETL_PARAMETER values are maintained by BRM Adapter for incremental load. Updating this table every time might lead to loss of data.

      Every time when STG_OCDM_LOAD scenario is run BRM_ETL_PARAMETER table being updated as below:

      UPDATE BRM_ETL_PARAMETER SET FROM_DATE_ETL = TO_DATE_ETL, TO_DATE_ETL = NULL where PROCESS_NAME = 'BRM-ADAPTER';
      
  3. Run scenarios accordingly. Recommended scenarios:

    1. SRC_STG_LOAD - loads data into staging layer. Start STG_OCDM_LOAD scenario after this.

    2. STG_OCDM_LOAD - Runs when SRC_STG_LOAD is completed. Load data into Oracle Communications Data Model.

    3. END_TO_END_LOAD_PLAN - Preferred option for incremental load as this scenario runs both SRC_STG_LOAD and STG_OCDM_LOAD scenarios in sequence.

    Note:

    You can make of ODI scenario scheduling to run scenario periodically.

Refreshing the Foundation Layer with Real-Time Data

After performing an initial load of the Oracle Communications Data Model warehouse as described in "Performing an Initial Load with the BRM Adapter for Oracle Communications Data Model", you can refresh the data in the foundation layer of an Oracle Communications Data Model warehouse on a real-time basis.

Take the followings steps to ensure that to the data in the foundation layer of an Oracle Communications Data Model warehouse in this manner:

  1. Install the BRM Adapter for Oracle Communications Data Model and configure it for use by both Oracle GoldenGate and Oracle Data Integrator (ODI) and as described in Oracle Communications Data Model Installation Guide.

    Verify that the installation and configuration created the schema objects described in "Schema Definitions Added for the BRM Adapter for Oracle Communications Data Model".

  2. Oracle GoldenGate handles step 1, as shown in Figure 1-2. All you need to do is check whether the Oracle GoldenGate processes in the source and staging systems are in RUNNING mode (all GoldenGate processes keep checkpoint information and restart from the point of failure without any loss of data, provided nobody alters the process to restart from a different position).

    From the GGSCI prompt, issue info all commands to verify that the Oracle GoldenGate processes needed by the BRM Adapter for Oracle Communications Data Model are running.

    Source System Processes Staging System Processes
    Manager process

    Extract process (EXTBRM)

    Extract Pump process (EXTPBRM)

    Manager process

    Replicate process (REPBRM)


  3. The following code shows the issuing of these commands with successful results.

    GGSCI>  (mypc1)  5> info all
    
    Program    Status   Group    Lag        Time Since Chkpt
    
    MANAGER    RUNNING
    EXTRACT    RUNNING  EXTBRM   47:29:00   00:00:20
    EXTRACT    RUNNING  EXTPBRM  00:00:00   47:29:06
    
    GGSCI>  (ocdm01)  2> info all
    
    Program    Status   Group    Lag        Time Since Chkpt
    
    MANAGER    RUNNING
    REPLICAT   RUNNING  REPBRM   00:00:00   00:03:09
    

    Tips:

    If you have two source systems, check process status on both source systems.

    For commands to manage Oracle GoldenGate processes, see Oracle Communications Data Model Installation Guide.

  4. Reconfigure BRM_SRC to point to OGG target.

    Reconfigure BRM_SRC physical data server to point to OGG target tables.

    The OGG target tables are maintained with BRM_STG schema. You can reconfigure BRM_SRC data server to point to OGG target tables (BRM_STG schema).

  5. To perform Step 2, 3, 4 as shown in Figure 1-2, run scenarios accordingly.

    Recommended Scenarios:

    1. SRC_STG_LOAD - loads data into staging layer. Start STG_OCDM_LOAD scenario after this.

    2. STG_OCDM_LOAD - Runs when SRC_STG_LOAD is completed. Loads data into Oracle Communications Data Model.

    3. END_TO_END_LOAD_PLAN - Preferred option for incremental load, as this scenario runs both SRC_STG_LOAD and STG_OCDM_LOAD scenarios in sequence.

    See:

    "Execution Flow Using BRM Adapter: with Oracle GoldenGate and ODI" for an explanation of the execution flow.

Note:

You can make of ODI scenario scheduling to run scenario periodically.

Checking Oracle GoldenGate Processes

If you are using Oracle GoldenGate, verify that Oracle GoldenGate is working so that the Adapter can load data into the staging system. The processes listed should be running on both the source systems and the staging system as shown:

Source Processes

  • Manager Process

  • Extract Process (EXTBRM)

  • Extract Pump Process (EXTPBRM)

For example, on the BRM_SRC Source System, the source processes should look as follows:

GGSCI>  (mypc1)  5> info all

Program    Status   Group    Lag        Time Since Chkpt

MANAGER    RUNNING
EXTRACT    RUNNING  EXTBRM   47:29:00   00:00:20
EXTRACT    RUNNING  EXTPBRM  00:00:00   47:29:06

Staging Processes

GGSCI>  (ocdm01)  2> info all
Program    Status   Group    Lag        Time Since Chkpt

MANAGER    RUNNING
REPLICAT   RUNNING  REPBRM   00:00:00   00:03:09

Tips:

If you have two source systems, check process status on both source systems. For commands to manage Oracle GoldenGate processes, see Oracle Communications Data Model Installation Guide.

BRM Adapter Exception Handling

Exception handling is provided within SRC_STG_LOAD and STG_OCDM_LOAD packages. All interfaces and procedures are provided with exception handling procedure. In case any exception occurs, exception handling procedure gets executed. Exception handling procedure checks the exception handling configuration and proceeds accordingly.

Figure 2-2 shows the exception handler operator log.

Figure 2-2 BRM Adapter Exception Handler Operation Log

Description of Figure 2-2 follows
Description of "Figure 2-2 BRM Adapter Exception Handler Operation Log"

Exception Handler Configuration

Exception handling is configured for each step within the package, not for each interface or procedure. In most of the cases, interfaces and procedures can have the same name as the step name. You need to open respective packages and then click the particular step and then look for the step name, as shown in Figure 2-3.

Figure 2-3 Finding Step Names for Exception Handling

Description of Figure 2-3 follows
Description of "Figure 2-3 Finding Step Names for Exception Handling"

Alternatively you can find the step name in exception handler log also, as highlighted:

ODI-1228: Task PROCESS_ERROR_HANDLING (Procedure) fails on the target ORACLE connection BRM_STG
Caused By: java.sql.SQLException: ORA-20001:
Error occurred while processing DWR_ACCT_MAP, fix the error in interface or make entry into brm_stg (brm_odi_exception_handle) table, if you wish to skip this error

To skip exception means do not stop the execution and proceed with next step. You can run the following insert query accordingly in BRM_STG schema.

insert into brm_odi_exception_handle ( interface_name, execution_context, skip_exception ) values ( 'DWR_ACCT_MAP', 'GLOBAL', 'Y' )
  1. INTERFACE_NAME - step name as mentioned

  2. EXECUTION_CONTEXT - execution context, default GLOBAL

  3. SKIP_EXCEPTION - recommended values are Y and N.

    1. Y - Yes, skip exception, continue with next step.

    2. N - No, do not skip exception, raise error.

Package and Step Name Mapping

Table 2-1 Package and Step Name Mapping

Package Folder Step Name

100 - LOOKUP

STG_OCDM

DWB_CRNCY_EXCHNG_RATE_MAP

100 - LOOKUP

STG_OCDM

DWL_ACCT_BAL_TYP_MAP

100 - LOOKUP

STG_OCDM

DWL_CALL_SRVC_TYP_MAP

100 - LOOKUP

STG_OCDM

DWL_COLLCTN_TYP_MAP

100 - LOOKUP

STG_OCDM

DWL_CRNCY_MAP

100 - LOOKUP

STG_OCDM

DWL_CUST_TYP_MAP

100 - LOOKUP

STG_OCDM

DWL_PK_OFPK_TIME_MAP

100 - LOOKUP

STG_OCDM

DWL_PROD_SPEC_TYP_MAP

10000 - BROADBAND_USAGE_EVENT_PKG

STG_OCDM

DWB_BRDBND_USG_EVT_MAP

10000 - DATA_SERVICE_EVENT_PKG

STG_OCDM

DWB_DATA_SRVC_EVT_MAP (DIALUP)

10000 - DATA_SERVICE_EVENT_PKG

STG_OCDM

DWB_DATA_SRVC_EVT_MAP (GSM POSTPAID)

10000 - DATA_SERVICE_EVENT_PKG

STG_OCDM

DWB_DATA_SRVC_EVT_MAP (GSM PREPAID)

10000 - GPRS_USAGE_EVENT_PKG

STG_OCDM

DWB_GPRS_USG_EVT_MAP (PostPaid)

10000 - GPRS_USAGE_EVENT_PKG

STG_OCDM

DWB_GPRS_USG_EVT_MAP (PrePaid)

10000 - SMS_EVENT_PKG

STG_OCDM

DWB_SMS_EVT_MAP (PostPaid)

10000 - SMS_EVENT_PKG

STG_OCDM

DWB_SMS_EVT_MAP (PrePaid)

10000 - VOICE_CALL_EVENT_PKG

STG_OCDM

DWB_WRLS_CALL_EVT_MAP(PostPaid)

10000 - VOICE_CALL_EVENT_PKG

STG_OCDM

DWB_WRLS_CALL_EVT_MAP (PrePaid)

200 - CUSTOMER_PKG

 

exec_geo_map

200 - CUSTOMER_PKG

STG_OCDM

DWR_PRTY_MAP

200 - CUSTOMER_PKG

STG_OCDM

DWR_CUST_MAP

200 - CUSTOMER_PKG

STG_OCDM

DWR_CUST_ADDR_MAP

200 - CUSTOMER_PKG

STG_OCDM

DWR_PRTY_CNCT_INFO_MAP

200 - CUSTOMER_PKG

STG_OCDM

DWR_PRTY_MAP (Payinfo_CC)

200 - CUSTOMER_PKG

STG_OCDM

DWR_PRTY_MAP (Payinfo_DD)

200 - CUSTOMER_PKG

STG_OCDM

DWR_PRTY_MAP (Payinfo_INV)

200 - CUSTOMER_PKG

 

UPDATE_DWR_PRTY.CUST_KEY

300 - ACCOUNT_PKG

STG_OCDM

DWR_ACCT_SGMNT

300 - ACCOUNT_PKG

STG_OCDM

DWR_ACCT_MAP

300 - ACCOUNT_PKG

STG_OCDM

DWR_ACCT_BAL_GRP_MAP

300 - ACCOUNT_PKG

STG_OCDM

DWR_ACCT_PREF_INVC_DLVRY_MAP

300 - ACCOUNT_PKG

STG_OCDM

DWR_ACCT_PYMT_MTHD_MAP

400 - SERVICE_PKG

STG_OCDM

DWR_SRVC_MAP

400 - SERVICE_PKG

STG_OCDM

DWR_SRVC_SPEC_MAP

400 - SERVICE_PKG

STG_OCDM

DWR_CUST_FCNG_SRVC_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_SPEC_MAP (PRODUCT_T)

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_OFR_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_SBRP_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_OFR_PROD_SPEC_ASGN_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_CTLG_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_CTLG_PROD_OFR_ASGN_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_SRVC_SPEC_PROD_SPEC_RLTN_MAP

500 - PRODUCT_PKG

 

UPDATE_PROD_OFR_PLN_TYP

500 - PRODUCT_PKG

STG_OCDM

DWR_AGRMNT_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_VAL_ADD_SRVC_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_AGRMNT_ITEM_MAP

500 - PRODUCT_PKG

STG_OCDM

DWR_PROD_OFR_PRICE_MAP

600 - ACCOUNT_BALANCE_PKG

STG_OCDM

DWB_ACCT_BAL_MAP

600 - ACCOUNT_BALANCE_PKG

STG_OCDM

DWB_ACCT_BAL_IMPC_MAP

700 - INVOICE_PKG

STG_OCDM

DWB_INVC_MAP

700 - INVOICE_PKG

STG_OCDM

DWB_INVC_ITEM_MAP

700 - INVOICE_PKG

STG_OCDM

DWB_INVC_ADJ_MAP

700 - INVOICE_PKG

STG_OCDM

DWB_INVC_DISC_MAP

700 - INVOICE_PKG

 

exec_update_invc

800 - COLLECTIONS

STG_OCDM

DWB_ACCT_DEBT_MAP

800 - PAYMENT_PKG

STG_OCDM

DWB_ACCT_PYMT_MAP

800 - PAYMENT_PKG

 

payment assign view

800 - PAYMENT_PKG

STG_OCDM

DWB_INVC_PYMT_ASGN_MAP

800 - PAYMENT_PKG

 

update dwb_invc.FULL_PAY_RCVD_IND

ACCOUNT_PKG

SRC_STG_NONGG

ACCOUNT_T_NONGG_IU

ACCOUNT_PKG

SRC_STG_NONGG

ACCOUNT_NAMEINFO_T_NONGG_IU

ACCOUNT_PKG

SRC_STG_NONGG

BILLINFO_T_NONGG_IU

BAL_GRP_PKG

SRC_STG_NONGG

BAL_GRP_T_NONGG_IU

BAL_GRP_PKG

SRC_STG_NONGG

BAL_GRP_BALS_T_NONOGG_IU

BAL_GRP_PKG

SRC_STG_NONGG

BAL_GRP_SUB_BALS_T_NONOGG_IU

COLLECTION_PKG

SRC_STG_NONGG

COLLECTIONS_SCENARIO_T_NONOGG_IU

COLLECTION_PKG

SRC_STG_NONGG

COLLECTIONS_ACTION_T_NONOGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_BEID_BALANCES_T_NONGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_BUSINESS_TYPE_T_NONGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_CUR_CONV_RATES_T_NONGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_PAYMENT_PAY_TYPES_T_NONGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_T_NONGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_COLLECTIONS_SCENARIO_T_NONOGG_IU

CONFIG_PKG

SRC_STG_NONGG

CONFIG_BILLING_SEGMENT_T_NOOGG_IU

DD_OBJECTS_PKG

SRC_STG_NONGG

DD_OBJECTS_T_NONGG_IU

EVENT_ACTIVITY_TLCS_PKG

SRC_STG_NONGG

EVENT_ACTIVITY_TLCS_T_NONGG_IU

EVENT_ACTIVITY_TLCS_PKG

SRC_STG_NONGG

EVENT_ACTV_TLCS_SVC_CODES_T_NONGG_IU

EVENT_BAL_IMPACT_PKG

SRC_STG_NONGG

EVENT_BAL_IMPACTS_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_MISC_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_CASH_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_CC_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_CHECK_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_DD_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_FAILED_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_PAYORD_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_POST_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_T_NONGG_IU

EVENT_BILLING_PKG

SRC_STG_NONGG

EVENT_BILLING_PAYMENT_WTRAN_T_NONGG_IU

EVENT_BROADBAND_USAGE_PKG

SRC_STG_NONGG

EVENT_BROADBAND_USAGE_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG

SRC_STG_NONGG

EVENT_DLAY_ACTV_TLCS_SVC_CDS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG

SRC_STG_NONGG

EVENT_DLAY_ACTV_TLCS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG

SRC_STG_NONGG

EVENT_DLAY_SESS_TLCS_SVC_CDS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG

SRC_STG_NONGG

EVENT_DLAY_SESS_TLCS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG

SRC_STG_NONGG

EVENT_DLYD_SESSION_TLCO_GPRS_T_NONGG_IU

EVENT_DLAY_ACTV_SESSION_TLCO_PKG

SRC_STG_NONGG

EVENT_DLYD_SESSION_TLCO_GSM_T_NONGG_IU

EVENT_PKG

SRC_STG_NONGG

EVENT_T_NONGG_IU

EVENT_RUM_MAP_PKG

SRC_STG_NONGG

EVENT_RUM_MAP_T_NONGG_IU

EVENT_SESSION_PKG

SRC_STG_NONGG

EVENT_SESSION_DIALUP_T_NONGG_IU

EVENT_SESSION_PKG

SRC_STG_NONGG

EVENT_SESSION_TELCO_GPRS_T_NONGG_IU

EVENT_SESSION_PKG

SRC_STG_NONGG

EVENT_SESSION_TLCO_GSM_T_NONGG_IU

EVENT_SESSION_PKG

SRC_STG_NONGG

EVENT_SESSION_TLCS_T_NONGG_IU

EVENT_SESSION_PKG

SRC_STG_NONGG

EVENT_SESS_TLCS_SVC_CODES_T_NONGG_IU

EVENT_TAX_JURISDICTIONS_PKG

SRC_STG_NONGG

EVENT_TAX_JURISDICTIONS_T_NONGG_IU

IFW_CURR_TIMEZOZE_USAGETYPE_PKG

SRC_STG_NONGG

IFW_CURRENCY_NONGG_IU

IFW_CURR_TIMEZOZE_USAGETYPE_PKG

SRC_STG_NONGG

IFW_TIMEZONE_NONGG_IU

IFW_CURR_TIMEZOZE_USAGETYPE_PKG

SRC_STG_NONGG

IFW_USAGETYPE_NONGG_IU

INVOICE_ITEM_PKG

SRC_STG_NONGG

EVENT_ITEM_TRANSFER_T_NONGG_IU

INVOICE_ITEM_PKG

SRC_STG_NONGG

ITEM_T_NONGG_IU

INVOICE_ITEM_PKG

SRC_STG_NONGG

BILL_T_NONGG_IU

INVOICE_ITEM_PKG

SRC_STG_NONGG

INVOICE_T_NONGG_IU

INVOICE_ITEM_PKG

SRC_STG_NONGG

INVOICE_STATUSES_T_NONGG_IU

PAYINFO_PKG

SRC_STG_NONGG

PAYINFO_T_NONGG_IU

PAYINFO_PKG

SRC_STG_NONGG

PAYINFO_INV_T_NONGG_IU

PAYINFO_PKG

SRC_STG_NONGG

PAYINFO_DD_T_NONGG_IU

PAYINFO_PKG

SRC_STG_NONGG

PAYINFO_CC_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

PRODUCT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

DEAL_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

DEAL_PRODUCTS_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

PLAN_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

PLAN_SERVICES_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

RATE_PLAN_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

DISCOUNT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

PURCHASED_PRODUCT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

PURCHASED_DISCOUNT_T_NONGG_IU

PRODUCT_DEAL_PLAN_PKG

SRC_STG_NONGG

DEAL_DISCOUNTS_T_D_NONGG_IU

SERVICE_PKG

SRC_STG_NONGG

SERVICE_T_NONGG_IU

SERVICE_PKG

SRC_STG_NONGG

SERVICE_EMAIL_T_NONGG_IU

SERVICE_PKG

SRC_STG_NONGG

SERVICE_TELCO_FEATURES_T_NONGG_IU

SERVICE_PKG

SRC_STG_NONGG

SERVICE_TELCO_GPRS_T_NONGG_IU

SERVICE_PKG

SRC_STG_NONGG

SERVICE_TELCO_GSM_T_NONGG_IU


Drop Error Tables (E$_)

You should drop the E$_{OCDM_SYS} tables from OCDM_SYS schema. In case OCDM_SYS schema table changes, then load will fail. You can find the E$_ tables and then drop manually. Make sure to review existing data in these tables before dropping.

SELECT * FROM USER_OBJECTS WHERE OBJECT_NAME LIKE 'E$_%' AND OBJECT_TYPE = 'TABLE'