Batch Loader Does Not Store Seconds Of Date/Time Value
(Doc ID 952902.1)
Last updated on MAY 09, 2023
Applies to:
Oracle WebCenter Content - Version 10.0 and laterInformation in this document applies to any platform.
This problem can occur on any platform.
Symptoms
Documents checked-in via Batchloader missing timestamp information (seconds) for Release date. However documents checked-in via Content Server UI have their timestamp information correctly captured for Release Date.
Steps to reproduce the issue:
------------------------------
1. Set the Content Server locale to any required value (Eg: English-UK) and enable the locale via System Properties.
2. Next use a batchloader file where you specifiy the ReleaseDate like this:
dInDate=30/09/2009 0:28:14
3. When looking in the revisions table you can see the dInDate (ReleaseDate) for the document containing only date and time in hours and minutes without seconds.
4. If you check-in the document by entering the date string with seconds from the Content Server check-in page, then the time is correctly stored in the database.
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 |
| Cause |
| Solution |