DBAT Connector- Unparseable Date Error during Provisioning of user.

(Doc ID 1622715.1)

Last updated on AUGUST 01, 2017

Applies to:

Identity Manager Connector - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

 In a OIM11.1.1.5.x with DBAT 9.1.0x.x Connector setup with SQL DB: Create a user in a SQL Database using Oracle Identity Manager's DBAT Connector. It is complaining about a parsing error for the date.

[oim_server1] [ERROR] [] [OIMCP.DATC] [tid: [ACTIVE].ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: dd36a2c4d082488d:32e945ca:141e86fd259:-8000-0000000000004bb2,0] [APP: oim#11.1.1.3.0] Class/Method: DBFacade/getSQLObject encounter some problems: Unparseable date: "2013-10-25 00:00:00.0"[[
java.text.ParseException: Unparseable date: "2013-10-25 00:00:00.0"
at java.text.DateFormat.parse(DateFormat.java:337)
at com.thortech.xl.gc.impl.common.DBFacade.getSQLObject(Unknown Source)
at com.thortech.xl.gc.impl.common.DBFacade.getStmt(Unknown Source)
at com.thortech.xl.gc.impl.common.DBFacade.createParentRecord(Unknown Source)
at com.thortech.xl.gc.impl.prov.DBProvisioningTransportProvider.sendData(Unknown Source)
at com.thortech.xl.gc.runtime.GCAdapterLibrary.executeFunctionality(GCAdapterLibrary.java:574)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 

Connector (Target) Database
-------------------------
SQL Server
Column is set to "datetime"
Date values in the table dbo.SYS_USER look like "2013-04-26 08:50:45.700"


OIM (Source) Database
------------------------
OIM  - Oracle DB
Column is set to "date"
Date in the UD_SQL_USR table looks like 28-OCT-13

XL.DefaultDateFormat is set to yyyy/MM/dd HH:mm:ss z

 

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