Procedure Generation (RXCPDGEN) Job stays in 'Started' status (scenario: Windows DB Server running on 19c database).
(Doc ID 2816466.1)
Last updated on FEBRUARY 21, 2023
Applies to:Oracle Clinical - Version 5.2.2 and later
Information in this document applies to any platform.
Procedure Generation job stays at STARTED status (Windows DB server running on 19c database) i.e.
Procedure Generation job consumes more then 96% of the processor when running.
Procedure Generation log files contains below (with RXC_DEBUG enabled):
l<batch_job_id>.log: Connecting as [VxxxM]/@[db] Connected to database. pslaunch_pc_stmt_06 executed successfully. pslaunch_pc_stmt_02 executed successfully. Job started. Starting 3GL command... 3GL/PLSQL Command started. PID saved. Connecting... OS User=opapps proclogn_pc_stmt_01. 19c proclogn_pc_stmt_03. nErrMsgNum=0, nIndErrMsgNum=0, vSeqNames=, nIndSeqNames=-1 Connected. Generating procedure... rxcpdggd_pc_stmt_03 executed successfully. rxcpdggd_pc_stmt_02 executed successfully.
rxcpdgen.log: Connect prvl user. Connected to ORACLE as user [VxxxM]/@[db]. Connected to ORACLE as user RXC_PD. After setting role RXCLIN_MOD
V$SESSION information shows below sessions for RXC_PD and the user that is running the Procedure Generation job:
USERNAME STATUS MODULE SQL_ID STATE SECONDS_IN_WAIT -------- -------- ------------ ------ ------- --------------- RXC_PD INACTIVE rxcpdgen.exe WAITING 6986 VxxxM INACTIVE pslaunch.exe WAITING 6991 VxxxM ACTIVE RXCPSMSG WAITING 10
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