My Oracle Support Banner

Pin_bill_acct Logging Wrong Thread Number (Doc ID 1317004.1)

Last updated on OCTOBER 14, 2019

Applies to:

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

Goal

While running pin_bill_acct in verbose mode its printing wrong thread numbers.

Thread (4145597328) begins ...
Thread (4135107472) begins ...
Thread (4124617616) begins ...
Thread (4114127760) begins ...
Thread (4103637904) begins ...
Total Fetched (0) units, err 0
Thread (4114127760) exits ...
Thread (4124617616) exits ...
Thread (4145597328) exits ...
Thread (4135107472) exits ...
Thread (4103637904) exits ...
Total number of records processed = 0.
Number of data errors encountered = 0.
Total number of errors encountered = 0.


Correct thread number should be displayed as below. 

Thread (4) begins ...

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.