My Oracle Support Banner

An Error Occurs When Using Dates In UCM Archive Metadata (Doc ID 2443452.1)

Last updated on FEBRUARY 26, 2019

Applies to:

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

Symptoms

On : 12.5 version, Enterprise Edition

ISSUE:
---------------------------------

- An error occurs when using Dates in UCM Archive Metadata even after implementing the solution in Oracle Support Knowledge Base Doc ID 1611632.1


ERROR
-----------------------
- ARC0400400036
- 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: 2017-08-24 05:28:33.875 UTC-ERROR-[Thread-10]-[ImportRequest.java:235]-oracle.documaker.ezridc.ImportRequest.processResponse: Error importing document
oracle.stellent.ridc.protocol.ServiceException: Content item 'DEV037891' was not successfully checked in. The field 'DocDate' does not contain a valid date. Unable to parse date 'Tue Aug 15 01:58:05 UTC 2017'.
  at oracle.stellent.ridc.protocol.ServiceResponse.getResponseAsBinder(ServiceResponse.java:142)
  at oracle.stellent.ridc.protocol.ServiceResponse.getResponseAsBinder(ServiceResponse.java:108)
  at oracle.documaker.ezridc.ImportRequest.processResponse(ImportRequest.java:202)
  at oracle.documaker.ezridc.Request.executeRequest(Request.java:68)
  at oracle.documaker.ecmconnector.ucmdestination.UCMDestination.importDocument(UCMDestination.java:158)
  at oracle.documaker.ecmconnector.connectorapi.Destination.internalImportDocument(Destination.java:174)
  at oracle.documaker.ecmconnector.connectorapi.Destination.importSingleDocument(Destination.java:143)
  at oracle.documaker.ecmconnector.connectorapi.Source.importDocuments(Source.java:209)
  at oracle.documaker.archiver.BatchProcessor.run(BatchProcessor.java:326)
  at oracle.documaker.archiver.Archiver.processTicket(Archiver.java:358)
  at oracle.documaker.archiver.Archiver.run(Archiver.java:307)




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
- The data field from XML input is mapped with the {TRNS.TRNCUSDATE001} field. The data is filled correctly in {TRNS.TRNCUSDATE001} column.
- The {TRNS.TRNCUSDATE001} is TIMESTAMP(6) format.
- The solution (Doc ID 1611632.1) was based by a TRNS.TRNCUSSTRnnn (STRING) field, so that is not aplicable in this scenario.
- There is no available TRNCUSSTRnnn (STRING) field, therefore need to use this TRNCUSDATE001 timestamp field.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use data fields in mapping.

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


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