OC/RDC 5.4: Patient Data Report / Blank Casebook and CRF Report are failing with RS_FAILURE
(Doc ID 2988955.1)
Last updated on NOVEMBER 23, 2023
Applies to:
Oracle Clinical - Version 5.4.0 and laterOracle Clinical Remote Data Capture Option - Version 5.4.0 and later
Microsoft Windows x64 (64-bit)
Symptoms
CRF Report and Patient Data Report ( and Blank Casebook Rport) are failing with RS_FAILURE .
In the rwEng-0_diagnostic.log we could see the generic error "REP-1825: The Before Report trigger returned FALSE."
rwEng-0_diagnostic.log contains for both CRF Report and Patient Data Report the following generic error:
| Path: <ORACLE_HOME>\user_projects\domains\FRDomain\servers\<REPORT SERVER NAME>\logs |
rwEng-0_diagnostic.log
[DATE] [reports] [ERROR] [] [oracle.reports.engine] [tid: 14] [ecid: ecid] [EngineName: rwEng-0] C Engine Job ID = <JOB_ID> ERR REP-1825: The Before Report trigger returned FALSE.
[DATE] [reports] [ERROR] [] [oracle.reports.engine] [tid: 14] [ecid: ecid] [EngineName: rwEng-0] rwfdt:rwfdtprint Job ID = <JOB_ID ERR Error occurred sending Job output to cache
[DATE] [reports] [INCIDENT_ERROR] [REP-1825] [oracle.reports.engine] [tid: 14] [ecid: ecid] [EngineName: rwEng-0] REP-1825 : MSG-00010: 328900: SRW.RUN_REPORT failed. Updating faiulre text.[[
REP-1825: The Before Report trigger returned FALSE.
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
at oracle.reports.engine.EngineImpl.run(EngineImpl.java:553)
at oracle.reports.engine.EngineClassPOA._invoke(EngineClassPOA.java:104)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:654)
at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:205)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1700)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1558)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:940)
at com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:198)
at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:712)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:474)
at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1237)
at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:490)
at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:519)
The temporary folder i.e [DRIVE]:\opapps54\temp did not had any files created during job execution.
In the Graphic Blank Casebook Report log we could see the following message:
Graphic Blank Casebook Report ends with error : Blank Casebook Report contains no data. Please see the java log file for details: [DRIVE]:\<user_path>
FYI:
In this particular scenario it was observed that all the DCIs from the dci_form_versions are having the Length = 0, even for new DCIs created and regenerated DCIs .
This can be verified by using the below query:
select dbms_lob.getlength(xmlp_pdf) from dci_form_versions table;
Changes
No changes. This was a fresh installation of the OC/RDC 5.4 environment.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |