Why is the Job Redirected When "Error - The job has been transferred to {0}, the new job ID is {1}"?
(Doc ID 1395597.1)
Last updated on NOVEMBER 14, 2023
Applies to:
Oracle Reports Developer - Version 11.1.1.4.0 and laterOracle Forms for OCI - Version 12.2.1.4.0 and later
Information in this document applies to any platform.
Goal
You have configured your Reports Servers for High Availability. You have 2 Reports Servers sharing the same job repository. Running your jobs, you sometimes get an error in the web browser:
The job has been transferred to {0}, the new job ID is {1}.
Here {0} is the *other* Reports Server, and {1} is the job id of the report job running there.
Strange is that the *original* Reports Server, where you started the report job, has enough free engines to run the job.
Details:
In the browser, you get the REP-50133 'error':
Cause: The job has been transferred to another server.
Action: No action required.
Level: 1
Type: ERROR
Impact: Other
In the trace files (rwserver_diagnostic-xx.log), you can see a REP-56091 'error':
Cause: This a notification message that the specified job has been transferred to another server's engine.
Action: This is for information only, no action is needed.
Level: 1
Type: ERROR
Impact: Other
Solution
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
Goal |
Solution |