Incorrect Date Format Displayed In Searches And The Year 2037 Limitation

(Doc ID 2317476.1)

Last updated on OCTOBER 13, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.9.0 and later
Information in this document applies to any platform.

Goal

Search results of the user metadata dates are displayed as 2 digit years. After adding SystemDateFormat=M/d{/yyyy} {h:mm[:ss] {aa} [zzz]}!mAM,PM to the config.cfg file located in [WCC_Domain]/ucm/cs/config directory followed by managed server(s) restart, the search results show 4 digit years, but incorrectly such as "86" for "1986" displays as "1686"

According to the Configuration Reference for WebCenter Content at - https://docs.oracle.com/middleware/11119/wcc/config-reference/configvariables.htm#CACIAFEI SystemDateFormat sets the date/time format for the Content Server instance in two types of date formats: one that stores seconds and another that truncates seconds and stores the date up to the minute. If seconds are used, dates can only be stored up to the year 2037. Why is this a limitation, and why should the seconds modifier be used?

Also, the system locale was specified and so was date format in the SystemProperties utility but that didn't seem to help. Only after changing the SystemDateFormat in the config.cfg file followed by server restart, correct dates are displayed. What is the point of using the SystemProperties utility if it doesn't do what it intuitively seems it should?

Solution

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 hundreds of Community platforms