Rep-51002 Unable to Bind Report Server.Report Server is up and Running.
(Doc ID 418718.1)
Last updated on JULY 20, 2021
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.
Not able to execute show jobs and any other URL accessing report server of Mid2 over HTTP of Mid1.
That is report server's are not accessible across mid-tiers.
There are two mid tier installation on the same server, let's call them Mid1 and Mid2 respectively. Each of these middle tiers have its own reports server, let's call Rep1 and Rep2 respectively. Access from HTTP server of Mid1 to Reports Server of Mid2 (ie Rep2) fails with :
Rep-51002 Unable to bind to report Server.
And also vice versa, connecting from HTTP Server of Mid2 to Reports Server of Mid1 (ie Rep1)
There is also a hardware load balancer to distribute the load to either HTTP Server of Mid1 or Mid2. So some requests reaching to one Mid tier with a request to other's Reports Server fails with REP-51002 error.
It is requested that, irrespective of whichever HTTP server is chosen by loadbalancer to execute report request, each Reports Server should be accessible.
Also "rwdiag.sh -findall" only shows the report server started from the same mid tier installation.
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