My Oracle Support Banner

OC 5.4: Character Patient Data Report job ends with 'RS_FAILURE' (Doc ID 2909983.1)

Last updated on NOVEMBER 17, 2022

Applies to:

Oracle Clinical - Version 5.4.0 and later
Oracle Clinical Remote Data Capture Option - Version 5.4.0 and later
Information in this document applies to any platform.

Symptoms

OC 5.4

While submitting patient data report the Job status is displayed as RS_FAILURE.

Steps:

Notes:

- Issue occurring against all users
- Admin Reports are working fine ( i.e OC > Admin > Admin Reports) where log and outputs are stored in the <Report Server Path> specified for the user.
- <folderAccess> is setup correctly as per Doc ID 2559005.1



Errors :

- Reports Server Queue Status shows for the module RXCDMLPD the following error:

The report terminated with error:
REP-1825:MSG-00010: 328900: SRW.RUN_REPORT failed. Updating failure text. REP-1825: The Before Report trigger returned FALSE.


- rwEng-0_diagnostic.log


[<DATE>] [reports] [INCIDENT_ERROR] [REP-1825] [oracle.reports.engine] [tid: 13] [ecid: <ID>] [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)

 

Changes

 

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
References


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