My Oracle Support Banner

DeathClaimSettlement Activity System Error Occurs When BackDating EffectiveDate (Doc ID 2865760.1)

Last updated on APRIL 29, 2022

Applies to:

Oracle Insurance Policy Administration J2EE - Version 11.3.1.6 and later
Information in this document applies to any platform.

Symptoms

On : 11.3.1.6 version, General

Following an upgrade from V10.2.0.39 to V11.3.1.6, when changing the EffectiveDate on a DeathClaimSettlement Activity,
the following error occurs:


ERROR
-----------------------
java.lang.RuntimeException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.8.WAS-v20210604-ce829afecd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.ibm.db2.jcc.am.SqlException: [jcc][1093][10427][4.24.92] Invalid data conversion: Parameter instance 1/11/2022 is invalid for the requested conversion to java.sql.Timestamp. ERRORCODE=-4220, SQLSTATE=null
Error Code: -4220



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Navigate to the specific Policy.

2. Add a DeathClaimSettlement Activity:
- The EffectiveDate will initialize with the current system date (1/12/2022).
- Change the EffectiveDate to be 1/11/2022 and tab off the field.

3. A System Error occurs:
- The System Error occurs when regions are in Production Mode.
- The System Error does not occur when regions are in Development Mode.


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.