BIPublisher : Database Connection Error While Trying To Schedule Jobs Using pin_invoice_doc_gen (Doc ID 1477525.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Microsoft Windows (32-bit)
Linux x86-64
***Checked for relevance on 29-Jul-2016***

Symptoms

Running pin_inv_doc_gen fails with the following set of error messages.

Error 04/20/12 2:50:19:0564 PM ( 1334901019564 )  T:pool-1-thread-2 JavaLog isConnectionObtained 1:devbrm:UnknownProgramName:0:pool-1-thread-2:0:1334900975:0
Connection is not yet obtained. Load either THIN or OCI connection.
Error 04/20/12 2:50:19:0564 PM ( 1334901019564 )  T:pool-1-thread-2 JavaLog PortalException 1:devbrm:UnknownProgramName:0:pool-1-thread-2:0:1334900975:0
Scheduler DB insert Invoice JOb mapping - Resultset Error : Connection is not yet obtained. Load either THIN or OCI connection.
Message 04/20/12 2:50:19:0564 PM ( 1334901019564 )  T:pool-1-thread-2 JavaLog Exception 1:devbrm:UnknownProgramName:0:pool-1-thread-2:0:1334900975:0
java.lang.Exception
Message 04/20/12 2:50:19:0564 PM ( 1334901019564 )  T:pool-1-thread-2 JavaLog Exception 1:devbrm:UnknownProgramName:0:pool-1-thread-2:0:1334900975:0
Unable to Schedule Report Request
Scheduler DB insert Invoice JOb mapping - SQL Error
Message 04/20/12 2:50:19:0564 PM ( 1334901019564 )  T:pool-1-thread-2 JavaLog Exception 1:devbrm:UnknownProgramName:0:pool-1-thread-2:0:1334900975:0
Thread Execution Failed . Scheduler DB insert Invoice JOb mapping - SQL Error
Error 04/20/12 2:50:19:0565 PM ( 1334901019565 )  T:pool-1-thread-2 JavaLog InvThreadException thrownSchedule Report thread failed for 2843068 1:devbrm:UnknownProgramName:0:pool-1-thread-2:0:1334900975:0
Schedule Report thread failed for 2843068
Schedule Report thread failed for 2843068


Failing to connect to the BI Publisher DB prevents the invoices to be recorded into Publisher, therefore breaking the invoicing handling chain. It is expected that these errors are cleared and the JDBC connection between BRM and BI Publisher established when running the pin_inv_doc_gen application.

Changes

 

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