Rep-56055 When the Same Reports Server Name is Used as In-Process and Standalone
(Doc ID 733990.1)
Last updated on OCTOBER 03, 2023
Applies to:
Oracle Reports Developer - Version 10.1.2.0.2 to 10.1.2.3 [Release Oracle10g to 10gr2]Information in this document applies to any platform.
Symptoms
The following error occurs when attempting to use a report server that was working fine before:
All the reports generate the same REP-56055 error message. The maxConnect value has been increased dramatically in $OH/reports/conf/rep_name.conf file (ie, maxConnect=200 instead of 20), but the issue continues reproducing once a week.
The issue can be reproduced at will with the following steps:
1. Run your Reports as normal for some days
2. If not reboot of the Reports Server is done at least weekly, the REP-56055 appears.
3. Sometimes Multiple re-bouncing of the Middle Tier are needed to bring up the report server.
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 |
Cause |
Solution |
References |