RDC Onsite PDR fails with ORA-39565: Message 39565 not found error (Doc ID 601732.1)

Last updated on APRIL 13, 2011

Applies to:

Oracle Clinical Remote Data Capture Option - Version: 4.5.3 and later   [Release: 4.5 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to run PDR reports from RDC Onsite, the following error occurs:

ERROR
LOG :
Report: d:\opapps45\oc\RXCDMLPD.rep
Logged onto server: RDC02
Username: OPS$JFERREIRA


ERR REP-1401: 'beforereport': Fatal PL/SQL error occurred.
ORA-39565: Message 39565 not found; product=RDBMS; facility=ORA

ERR Error occurred sending Job output to cache.


The log file might also have the following information:

MSG MSG-00005: Entering Before Report Trigger
MSG MSG-00005: Before calling rxc_reporting.ReportMetadataPDF................
MSG MSG-00005: After calling rxc_reporting.ReportMetadataPDF ...............
MSG MSG-00005: Patient Specific Case Blnk PDR................................
ERR REP-1401: 'beforereport': Fatal PL/SQL error occurred.
ORA-39565: Message 39565 not found; product=RDBMS; facility=ORA

Compare this to the following excerpt from a log file where the process ran to completion:



MSG MSG-00005: Patient Specific Case Blnk PDR................................
MSG MSG-00005: Start Calling PATIENTDATAREPORT Setter Methods.......................
MSG MSG-00005: End calling PATIENTDATAREPORT setter Methods..........................
MSG MSG-00005: Start of Java code ................
MSG MSG-00005: Finish of Java code ................
MSG MSG-00005: End of Before Report Trigger: PDF report finished successfully



Notice the process dies after indicating the ‘Patient Specific Case Blnk PDR’ but does not get to ‘Start Calling PATIENTDATAREPORT Setter Methods’.

Examination of the code shows that the subsequent function call fails to complete. Testing the individual queries which feed the function calls which are used as parameters in the call to the java object one can determine that all of the internal calls should have been successful. The problem is in attempting to access the java object (.jar file).

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