REP-52266 - Failed To Start 11g In-Process Report Server after Pointing Credential Key to Another Database for jobRepository
(Doc ID 1639869.1)
Last updated on MAY 15, 2023
Applies to:
Oracle Reports Developer - Version 11.1 to 11.1.2.2.0 [Release 11g]Information in this document applies to any platform.
Symptoms
Set up jobRepository as part of HA (High Availability) configuration per instructions in:
What are the Differences Between jobStatusRepository and jobRepository in 11g (Doc ID 1072504.1)
The in-process Reports Servers on both nodes were working fine.
After changing the rep_repository Credential Key to point from Test database to Prod database and bouncing the WLS_REPORTS and WLS_REPORTS1 managed servers, the in-process Reports Server now fails to start with error:
and the rwserver_diagnostic.log shows:
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
at oracle.reports.utility.Utility.newRWException(Utility.java:1053)
at oracle.reports.utility.DBConnection.handleSQLException(DBConnection.java:240)
at oracle.reports.server.BLOBHelper.readAll(BLOBHelper.java:451)
at oracle.reports.server.JobStoreDB.readPersistFile(JobStoreDB.java:317)
at oracle.reports.server.RWServer.startServer(RWServer.java:1231)
at oracle.reports.server.RWServer.run(RWServer.java:358)
at java.lang.Thread.run(Thread.java:736)
]]
Changes
For jobRepository, changed Credential Key to point to Prod database instead of Test database.
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 |