Nineteenth-century Dates Display as Twentieth-century Dates in Date-based Metadata Fields (Doc ID 1640081.1)

Last updated on APRIL 10, 2024

Applies to:

Symptoms

On : 11.1.1.8.0 version, Content Server

ACTUAL BEHAVIOR
---------------
On a new 11.1.1.8.0 Content Server, content was batchloaded in from an older content server that contained a custom metadata field called xmpubdate which was of type date. The content imported properly but when any meta data was changed the date in the custom metadata field was changed. ex. original date in xmpubdate was 01-01-1962. After metadata update the date became 01-01-2062. The date could be changed back manually and then it would stay.

EXPECTED BEHAVIOR
-----------------------
It is expected that the date would remain the same regardless of other metadata fields being updated.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Created testfield of type date
2. Updated database design, rebuilt search collection
3. Checked in test document with date of 01/01/1962
4. Updated a metadata field in the document
5. document's date is now 01/01/2062
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot find documents by publication date accurately

Cause

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