E2B Report Generation And Transmission Not Working For Active Enterprise (Doc ID 2016910.1)

Last updated on JUNE 19, 2015

Applies to:

Oracle Argus Interchange - Version 7.0.5 and later
Information in this document applies to any platform.

Symptoms

issue with E2B report generation and transmission. The Status of the transmitted E2B report is stuck in Transmit and the bulb was either green or yellow. 

The AG and ESM logs do not show entries for the enterprise from where the reports are scheduled.

Found Below Error in Bulk Report Transmit E2B and Batch Report generation  service logs when Verbose is enabled for AGProc.config  located in C:\Program Files (x86)\Oracle\Argus\Argus Safety\  folder.

Enter ADBObject::DirectSQL(SQL: BEGIN GSS_PERIODIC.LOAD_DLP_INFORMATION(:PO_DLP_DB_NAME, :PO_DLP_USER_NAME, :PO_DLP_USER_PASSWORD); END;;)
[EnterpiseID: GOLD SVT1 Formal] 19-May-2015, 08:36:21:237, [1], UserId: yage2b, Exit ADBObject::DirectSQL, Return Value: 1, Execution Time: 00:00:00:005
[EnterpiseID: GOLD SVT1 Formal] 19-May-2015, 08:36:21:257, [1], UserId: yage2b, Exception DetailsMessage
Error:1; Line: 7418: ERROR: Padding is invalid and cannot be removed.
Stack Trace

  

 

Changes

 Enabled  Data Lock Point  in Argus Console -> system configuration -> system management ( common profile switches) , Modify Data Lock point Section.

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