Release Date of 1968 or Earlier Is Changed When Checking In Content Through IdcCommand (Doc ID 445961.1)

Last updated on JUNE 08, 2017

Applies to:

Release Date of 1968 or Earlier Is Changed When Checking In Content Through IdcCommand

Date:

January 11, 2007

Product and Version:

Content Server 7.5.1

Symptoms

If I check in a piece of content through the browser and set the Release Date to something like 1/5/1968, it gets checked in with the correct Release Date. However, if I do the same checkin through IdcCommand, the Release Date gets changed to 2068.

It looks like a Release Date of 1969 stays set to 1969, but 1968 and earlier gets changed to a 2000-year, like 2068.

I can see it might get changed if I just used the date 1/5/68, but I'm specifying the year with four-digits like 1/5/1968.

This is the command file I used. After running this and looking in the database, I see dInDate (which is the database field for Release Date) is changed to 2068:

@Properties LocalData  
IdcService=CHECKIN_UNIVERSAL  
dDocType=ADACCT  
dDocTitle=File testing date  
dDocAuthor=sysadmin  
dSecurityGroup=Public  
dInDate=1/5/1968  
primaryFile=D:/temp/Word Doc 1.doc  
@end  
<<EOD>>

How can I keep the Release Date set correctly when I check in an item through IdcCommand?

Cause

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