My Oracle Support Banner

'Unable to parse date' Error Passing Dates to UCM Metadata Fields When Archiving to UCM (Doc ID 1611632.1)

Last updated on JANUARY 24, 2018

Applies to:

Oracle Documaker - Version 12.1 and later
Information in this document applies to any platform.


An error occurs when using Dates in UCM Archive Metadata.

When configuring Document Factory to add custom fields to the metadata when Archiving to UCM the following exception is received in the Archiver when using a Date datatype to the metadata:

oracle.stellent.ridc.protocol.ServiceException: Content item 'XXX' was not successfully checked in. The field 'YYY' does not contain a valid date. Unable to parse date 'Tue Sep 24 01:00:00 BST 2013'.
at oracle.stellent.ridc.protocol.ServiceResponse.getResponseAsBinder(
at oracle.stellent.ridc.protocol.ServiceResponse.getResponseAsBinder(
at oracle.documaker.ezridc.ImportRequest.processResponse(
at oracle.documaker.ezridc.Request.executeRequest(
at oracle.documaker.ecmconnector.ucmdestination.UCMDestination.importDocument(
at oracle.documaker.ecmconnector.connectorapi.Destination.internalImportDocument(
at oracle.documaker.ecmconnector.connectorapi.Destination.importSingleDocument(
at oracle.documaker.ecmconnector.connectorapi.Source.importDocuments(
at oracle.documaker.archiver.Archiver.processTicket(

The above error was found in the archiver log (odee/documaker/docfactory/temp/archiver/logs/Archiver.log) not in the 'errs' table.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.