ILM_DT / ILM_ARCH_SW “not Nullable” In CI_TD_ENTRY.

(Doc ID 2158506.1)

Last updated on JULY 11, 2016

Applies to:

Oracle Utilities Customer Care and Billing - Version and later
Information in this document applies to any platform.


On : version,

ILM_DT / ILM_ARCH_SW “not nullable” in CI_TD_ENTRY.  

After the migration from 2.3.1 to one is not able anymore to update todo because of the ILM_DT / ILM_ARCH_SW wich is “not nullable” in CI_TD_ENTRY.
Is it normal to have a not nullable column for ci_td_entry. ILM_DT / ILM_ARCH_SW whereas all the other ILM_DT / ILM_ARCH_SW columns are nullable?

Moreover when you have a look to the meta data this comlum is supposed to be nullable (as you can see in the CI_MD_TBL_FLD_EXTRACT.
The workaround is to alter the CI_TD_ENTRY table to set those columns as nullable . Is it possible to confirm that this work around is correct ?

Expected behavior
One is able to update TODOs.

12:10:01,323 [CobolThread 4] ERROR (org.hibernate.engine.jdbc.spi.SqlExceptionHelper) ORA-01407: impossible de mettre à jour ("CISADM"."CI_TD_ENTRY"."ILM_DT") avec NULL
12:10:01,323 [CobolThread 4] ERROR ( Failed to flush session org.hibernate.QueryTimeoutException: ORA-01407: impossible de mettre à jour ("CISADM"."CI_TD_ENTRY"."ILM_DT") avec NULL

The issue can be reproduced at will with the following steps:
1. Migrate from 2.3.1 to
2. Try and update any todo
3. Expect the application to crash

The issue has the following business impact:
The system is crashing when he try to update a Todo.
A solution is needed today as the go live date is tomorrow, 2 July 2016.


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