000028129 - KB-1390 - What date formats are accepted in the collectors

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028129
Applies ToAffected Versions: All Versions
ResolutionDifferent data sources use different date strings and not all are compatible with the Aveksa JDBC drivers, invalid date formats may result in admin errors like this:
 
Data Format Error in Account Record. Record ID=bob, Attribute=LAST_LOGIN_DATE, Value="May 27 2010 11:04AM", Expected Data Type=DATE

or the collector crashing with a stack trace and this error:
 
Caused by: java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character to number conversion error

The best solution is to modify your collector SQL to convert the source input date string into one of the supported date formats listed below:
 
Friday, August 4, 2006 11:38:39 AM EST
Friday, August 4, 2006 11:38:39 AM
Friday, August 4, 2006 11:38 AM
August 4, 2006 11:38:39 AM EST
August 4, 2006 11:38:39 AM
August 4, 2006 11:38 AM
Aug 4, 2006 11:38:39 AM EST
Aug 4, 2006 11:38:39 AM
Aug 4, 2006 11:38 AM
8/4/06 11:38:39 AM EST
8/4/06 11:38:39 AM
8/4/06 11:38 AM EST
Friday, August 4, 2006
August 4, 2006
Aug 4, 2006
8/4/06

The output string format is governed through a system setting value in T_SYSTEM_SETTINGS table. The ‘OutputDateFormat” parameter contains the format in which the date fields have to printed. The default pattern for the format is ‘dd-MMM-yy’, this is used if none is specified in the system settings. This will generate an out put like ’04-Aug-06’ for all the above input formats.

Attachments

    Outcomes