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 (in this chapter referred to as the BRM Adapter).

This chapter includes the following sections:

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

For detailed information about the objects and extract, transform, and load (ETL) process associated with the BRM Adapter, see Chapter 3, "BRM Adapter Reference".

Populating Warehouse Using the BRM Adapter

You use the BRM Adapter 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 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, Oracle 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 Initial Load with the BRM Adapter

You can prepare your own load plans to move source data to Oracle Communications Data Model or use one of the ready-to-use loads provided by Oracle Communications Data Model.

When you prepare a load plan you can move data in any sequence into the staging layer, to do this, you must follow a load-execution sequence. The load- execution sequence number is attached to the package name.

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"

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

SRC_STG_LOAD

Running this scenario loads data into the staging layer.

Before starting the SRC_STG_LOAD scenario set appropriate parameters for process name and from and to date in the 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);

Where the parameters are:

  1. PROCESS_NAME - 'BRM-ADAPTER'

  2. FROM_DATE_ETL - Load start from date

  3. TO_DATE_ETL - Load up to date

  4. LOAD_DT - usually sysdate

Note:

If the TO_DATE_ETL date is null, then the system sets the date to the source system date. This is useful in an incremental load.

The BRM_ETL_PARAMETER table is added as a filter to the query that is passed to the source system as follows:

MOD_T >= FROM_DATE_ETL AND MOD_T < TO_DATE_ETL

When you run this scenario, no status should be in either in the state 'RUNNING' or 'COMPLETED':

SELECT * FROM BRM_EXEC_STAT where proc_typ = 'SRC_STG';

This condition prevents you from running multiple processes at the same time and also verifies that the process is complete. The RUNNING status is set when source-to-staging or staging-to-Oracle Communications Data Model load scenarios are running.

After the source-to-staging scenario is completed, the status changes to COMPLETED.

Note:

Every time source-to-staging scenarios are run, a staging table is truncated which ensures that data is not duplicated.

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

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

This query disables the history only for the ACCOUNT_T source table. If required, you can disable the moving of history data into all tables by removing the WHERE clause from the previous query.

If the BRM_MAPPING_TAB staging table lacks an entry for a history table, then you can make an entry.

Note:

The history table structure must be the same as the structure of the delta table.

STG_OCDM_LOAD

This scenario loads data into Oracle Communications Data Model tables. The SRC_STG process status must be COMPLETED before you run this scenario. This scenario sets the execution status to RUNNING and sets the SRC_STG and the STG_OCDM process status to CLOSED.

SELECT * FROM BRM_EXEC_STAT where proc_typ = 'STG_OCDM';

After the staging to load data (STG_OCDM_LOAD) has finished, the BRM_ETL_PARAMETER table is updated as follows:

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

Note:

You must examine E$_{OCDM Table} for any records rejected during staging. These tables are truncated after every load.

END_TO_END_LOAD_PLAN

This package runs SRC_STG_LOAD and STG_OCDM_LOAD. Running this package performs two steps: loading data in the staging layer and then to Oracle Communications Data Model.

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 the BRM_ETL_LOAD_PLAN BRM_STG table.

The BRM_ETL_LOAD_PLAN configuration is as follows:

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 in a table. Do not insert a value of CLOSED into the PROCESS_STATUS column because CLOSED is considered as processed.

Every time a schedule runs, the current entry from BRM_ETL_LOAD_PLAN table is copied into the BRM_ETL_PARAMETER table. The BRM Adapter uses BRM_ETL_PARAMETER parameter to filter data in the Oracle Billing and Revenue Management source system.

Performing a Data Refresh with the BRM Adapter

After you have performed an initial data load of an Oracle Communications Data Model warehouse and you need to refresh the data, use Oracle Data Integrator to refresh all 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

When using the BRM Adapter you refresh the foundation layer on a scheduled basis using Oracle Data Integrator (when you are not using the BRM Adapter with Oracle GoldenGate).

To refresh the data in the foundation layer using only Oracle Data Integrator, do the following:

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

    See Also:

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

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

    2. Review the BRM_ETL_PARAMETER table. If required, you can update the ETL parameter. Because the BRM_ETL_PARAMETER values are maintained by the BRM Adapter for incremental loading, if you manually change parameter dates by updating values in this table, the manual changes might lead to loss of data.

      Whenever the STG_OCDM_LOAD scenario runs, the BRM_ETL_PARAMETER table is updated as follows:

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

    1. SRC_STG_LOAD: Loads data into the staging layer. Next, start the STG_OCDM_LOAD scenario.

    2. STG_OCDM_LOAD: Runs after the SRC_STG_LOAD is completed. This scenario loads data into Oracle Communications Data Model.

    3. END_TO_END_LOAD_PLAN: This is the preferred scenario for incremental loading. This scenario runs both the SRC_STG_LOAD and the STG_OCDM_LOAD scenarios in sequence.

    Note:

    You can schedule periodic runs of these scenarios using Oracle Data Integrator.

Refreshing the Foundation Layer with Real-Time Data

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

Follow these steps to refresh the data in the foundation layer of an Oracle Communications Data Model warehouse:

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

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

  2. Oracle GoldenGate handles loading data from the source database into the staging database (as shown in step 1 in Figure 1-2). All you need to do is check whether the Oracle GoldenGate processes in the source and staging systems are in the RUNNING status. All Oracle 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, run info all commands to verify that the Oracle GoldenGate processes needed by the BRM Adapter 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 shows these commands and 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
    

    Tip:

    If you have two source systems, check the process status on both. For commands to manage Oracle GoldenGate processes, see Oracle Communications Data Model Adapters and Analytics Installation Guide.
  4. Reconfigure BRM_SRC physical data server to point to Oracle GoldenGate target tables.

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

  5. Run the scenarios in this order:

    1. SRC_STG_LOAD: Loads data into the staging layer. Next, start the STG_OCDM_LOAD scenario.

    2. STG_OCDM_LOAD: Runs after the SRC_STG_LOAD scenario completes. This scenario loads data into Oracle Communications Data Model.

    3. END_TO_END_LOAD_PLAN: This is the preferred option for incremental loading. Runs both the SRC_STG_LOAD scenario and the STG_OCDM_LOAD scenario in sequence.

Note:

You can schedule each of these scenarios to run periodically using Oracle Data Integrator.

Verifying That Oracle GoldenGate Processes Are Running

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

Source System Processes

  • Manager Process

  • Extract Process (EXTBRM)

  • Extract Pump Process (EXTPBRM)

For example, on the BRM_SRC source system, the source processes should look similar to the following:

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 System Processes

  • Manager Process

  • Replicate process (REPBRM)

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

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

Tip:

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

BRM Adapter Exception Handling

Exception handling is provided within the SRC_STG_LOAD and STG_OCDM_LOAD packages. All interfaces and procedures are provided with an exception handling procedure. If any exception occurs, then the exception handling procedure is executed. The 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 Operator Log

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

Exception Handler Configuration

Exception handling is configured for each step within the package, not for each interface or procedure. In most cases, interfaces and procedures can have the same name as the step name. Open the respective packages and click the particular step to 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 the exception handler log:

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 an exception means do not stop the execution and proceed with the next step. You can run the following insert query in the BRM_STG schema:

insert into brm_odi_exception_handle ( interface_name, execution_context, skip_exception ) values ( 'DWR_ACCT_MAP', 'GLOBAL', 'Y' )
  1. interface_name: The step name.

  2. execution_context: The execution context; default is GLOBAL.

  3. skip_exception: The recommended values are Y and N.

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

    2. N - No, do not skip the exception, raise an 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 the OCDM_SYS schema. If the OCDM_SYS schema table changes, then the load will fail. You can find and drop the E$_ tables. Review existing data in these tables before you drop them.

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