PIN_REL Inconsistency While Updating "rel_sub_processes_t" (Doc ID 1425643.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.1 to 7.3.1.0.1 [Release 7.3.1]
Information in this document applies to any platform.

Goal

The pin_rel process does not upload to REL_SUB_PROCESS_T, the information of each record of BATCH_T and BATCH_REL_T.

Scenario:

"/portal/pin21/7.3.1/ifw/data/HOME/rel/processing/RAT_GSMGSM_Rollover_10.out". 
The batch_t and batch_rel_t tables were populated (POID: 9723045), and so was the rel_sub_processes_t.

  • Then, a second file was rated and loaded into DB through the pin_rel process:
"/portal/pin21/7.3.1/ifw/data/HOME/rel/processing/RAT_GSMGSM_Rollover_11.out".
Again, batch_t and batch_rel_t were populated (this time with POID: 9720212).

The rel_sub_processes_t was populated again, but the previous rows were not present in the table anymore. Only the new rows remained in that table.

The rel.pinlog files only had message: "The process completed successfully.". There was no data in cm.pinlog or dm_oracle.pinlog for that specific date.

This is the result of "select * from rel_sub_processes_t " after the second test:

OBJ_ID0|REC_ID|START_POID_ID0|END_POID_ID0|TOTAL_RECORDS|NUM_PROCESSED|NUM_SUB_BAL_PROCESSED|STATUS|CREATION_PROCESS|TABLES|NAME|BATCH_SIZE|PARAMETERS|STATUS_MSG

9720212|3|1426163338259461226|1426163338259461226||1|0|100|RATING_PIPELINE|event_t;event_bal_impacts_t;event_essentials_t;event_dlay_sess_tlcs_t;event_dlay_sess_tlcs_svc_cds_t;event_dlyd_session_tlco_gsm_t;event_tax_jurisdictions_t;event_rum_map_t;tmp_profile_event_ordering_t;event_dlyd_ses_tel_gsm_per_t|pin_rel.pin_rel_updater_sp|5|21|
9720212|4|1426163338259461227|1426163338259461230||4|0|100|RATING_PIPELINE|event_t;event_bal_impacts_t;event_essentials_t;event_dlay_sess_tlcs_t;event_dlay_sess_tlcs_svc_cds_t;event_dlyd_session_tlco_gsm_t;event_tax_jurisdictions_t;event_rum_map_t;tmp_profile_event_ordering_t;event_dlyd_ses_tel_gsm_per_t|pin_rel.pin_rel_updater_sp|5|21|
9720212|1|1426163338259461224|1426163338259461224||1|0|100|RATING_PIPELINE|event_t;event_bal_impacts_t;event_essentials_t;event_dlay_sess_tlcs_t;event_dlay_sess_tlcs_svc_cds_t;event_dlyd_session_tlco_gsm_t;event_tax_jurisdictions_t;event_rum_map_t;tmp_profile_event_ordering_t;event_dlyd_ses_tel_gsm_per_t|pin_rel.pin_rel_updater_sp|5|21|
9720212|2|1426163338259461225|1426163338259461225||1|0|100|RATING_PIPELINE|event_t;event_bal_impacts_t;event_essentials_t;event_dlay_sess_tlcs_t;event_dlay_sess_tlcs_svc_cds_t;event_dlyd_session_tlco_gsm_t;event_tax_jurisdictions_t;event_rum_map_t;tmp_profile_event_ordering_t;event_dlyd_ses_tel_gsm_per_t|pin_rel.pin_rel_updater_sp|5|21|


 Only rows for the latest processed file (POID: 9720212) remained on that table.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms