On FMW 11.1.1.6 or 11.1.2.1 Reports Server Fails to start When jobStatusRepository is Enabled
(Doc ID 1448928.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Reports Developer - Version 11.1.1.6.0 to 11.1.2.2.0 [Release 11g]Information in this document applies to any platform.
Symptoms
After applying the FMW 11gR1 version 11.1.1.6.0 patchset or the FMW 11gR2 version 11.1.2.1.0 or 11.1.2.2.0 patchset.
The Report server fail to start with below errors.
In OPMN
$INSTANCE_HOME/bin> ./opmnctl startproc ias-component=repservername
opmnctl startproc: starting opmn managed processes...
================================================================================
opmn id=<host>:<port>
Response: 0 of 1 processes started.
ias-instance id=mid_instance
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
<rpserver_name>/ReportsServerComponent/<repserver_name>/
Error
--> Process (index=1,uid=<uid>,pid=<pid>)
failed to start a managed process after the maximum retry limit
Log: $INSTANCE_HOME/diagnostics/logs/ReportsServerComponent/<repservername>/console~<repservername>~1.log
Enabling Tracing for the failing Reports Server
The Reports Server seems to hang without further errors or symptoms
Changes
The below document was followed:
<Note:858200.1 >How to Setup jobStatusRepository Feature in Reports 11g
to configure jobStatusRepository & then 11.1.1.6.0 or 11.1.2.1.0 or 11.1.2.2.0 patch sets were applied
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 |