Error Scanning or Importing Batch with Site Minder SSO "oracle.oddc.client.batchbuilder.BatchBuilderException: Error creating batch"
(Doc ID 2275293.1)
Last updated on NOVEMBER 28, 2023
Applies to:
Oracle WebCenter Enterprise Capture - Version 11.1.1.8.0 to 11.1.1.9.0 [Release 11g]Information in this document applies to any platform.
Symptoms
Using Enterprise Capture 11.1.1.9.0 with Cumulative Patch 1 <Patch 20865786>, an error occurs when attempting to scan or import a batch using any client profile to create a batch when using SSO url / users. The stack trace in the dc-client page is:
Message:
oracle.oddc.client.batchbuilder.BatchBuilderException: Error creating batch
Level:
WARNING
Stack Trace:
Error creating batch
oracle.oddc.client.batchbuilder.AbstractBatchBuilder.createCaptureBatchObject(AbstractBatchBuilder.java:168)
oracle.oddc.client.batchbuilder.AbstractBatchBuilder.createBatch(AbstractBatchBuilder.java:149)
oracle.oddc.client.BatchEditForm$48.run(BatchEditForm.java:4019)
Error 403--Forbidden
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
xx.x.x 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
oracle.oddc.client.batchbuilder.BatchBuilderException: Error creating batch
Level:
WARNING
Stack Trace:
Error creating batch
oracle.oddc.client.batchbuilder.AbstractBatchBuilder.createCaptureBatchObject(AbstractBatchBuilder.java:168)
oracle.oddc.client.batchbuilder.AbstractBatchBuilder.createBatch(AbstractBatchBuilder.java:149)
oracle.oddc.client.BatchEditForm$48.run(BatchEditForm.java:4019)
Error 403--Forbidden
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
xx.x.x 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
The access.log file in the Capture managed server \Logs directory the logging showed a message "403 Forbidden" returned when accessing:
PUT http://:16400/dc-client/jersey/oddcclient/persistBatch?.....
Changes
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 |