Pin_rel.Get_service_tables_str Fails If The Length Of Service_table_names Is Greater Than 255 (Doc ID 1361338.1)

Last updated on OCTOBER 31, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.4.0.0.0 and later   [Release: 7.4.0 and later ]
Information in this document applies to any platform.

Symptoms


Recently a new *service* table, named event_dlyd_sess_tlco_chr_t, had been defined for loading some custom information via pin_rel;
but the pin_rel failed with the following error:


ORA-20011: An unexpected error occurred in the preupdate procedure
ORA-06512: at "BTO_PIN17.PIN_REL", line 4330
ORA-06502: PL/SQL: numeric or value error: character string buffer too small


 When  renamed the new service table to evt_dlyd_chr_t (12 chars less) , the pin_rel works properly.

 The issue is caused by a variable of pin_rel.get_service_tables_str function, wrongly defined as varchar(255) instead of rel_sub_processes_t.tables%type.

  The string usually stored in rel_sub_processes_t.tables is:

event_t;event_bal_impacts_t;event_essentials_t;event_dlay_sess_tlcs_t;event_dlay_sess_tlcs_svc_cds_t;event_dlyd_sess_tlco_gprs_t;bi_event_t;bi_event_balance_impact_t;roaming_event_summary_t;bi_consumed_units_t;volume_summary_t;consumed_units_t;event_rrt_data_t;item_sub_aggregation_t;evt_dlyd_chr_t

the length is 299 but the length of service tables (not considering "event_t;event_bal_impacts_t;event_essentials_t;") is 252, less than 255.

Cause

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