Enhancement to pin_rel to Exclude Path in Duplicate File Detection

(Doc ID 2389467.1)

Last updated on MAY 07, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Goal

In all versions of Oracle Communications Billing and Revenue Management (BRM), the pin_rel (Rated Event Loader) utility is used to load post-Pipeline processed events into the database.

This can be automated through the batch_controller or by manually invoking pin_rel and passing in an event filename to it.

Currently, all versions of pin_rel perform duplicate file detection based on the full path of the argument.

This can be tested as follows:

1. Run pin_rel against an input file

> pin_rel -f /pinhome/pin3009/opt/ifw/data/out/gsm/telephony/test_TEL_20180330151020_cdr.out
The process completed successfully.

2. Move the input file to a new directory and call pin_rel against the same file

> mv /pinhome/pin3009/opt/ifw/data/out/gsm/telephony/test_TEL_20180330151020_cdr.out /pinhome/pin3009/opt/ifw/data/out/gsm/telephony1/test_TEL_20180330151020_cdr.out

3. Run pin_rel against the same file in the new location

> pin_rel -f /pinhome/pin3009/opt/ifw/data/out/gsm/telephony1/test_TEL_20180330151020_cdr.out
The process completed successfully.

As a result, duplicated events are loaded into the database.

Is it possible to have pin_rel only consider the file name (or any other unique attribute of the input file) for the duplicate detection logic?

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