Type: Bug Fix
Affects Version/s: 2.0
Security Level: Public (Public: Anyone can view)
KULRICE-7018 Apply sql to master db for KULRICE-6916: KRIM_ENTITY_CACHE_T.PRSN_NM is too small KULRICE-7997 Quickfinder lightbox too small KULRICE-7860 KRAD Lookup window - too small to be useful. KULRICE-11580 Small button size is too big KULRICE-7558 Default sizes for Rice caches are too small and timeToLiveSeconds is not configured properly KULRICE-2305 seq_rule_expr sequence missing from mysql.ddl, rule_expr size too small KULRICE-8999 Windows 2008 IE Resize issue PeopleFlow small size KULRICE-7586 ConversionNotSupportedException error when working with Uif-SecondaryActionButton-Small KULRICE-5338 Data table does not resize correctly when page is initially small KULRICE-1172 KIM name sequence too long
KAI Review Status:Not Required
KTI Review Status:Not Required
This came in off the collab list, pasting the message from Jannie Louwrens:
I noticed a lot of the following error message is logged in the server log:
Exception in thread "PMS/KSB-pool-1-thread-18" java.lang.RuntimeException: org.springframework.dao.DataIntegrityViolationException: OJB operation; SQL ; Data truncation: Data too long for column 'PRSN_NM' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'PRSN_NM' at row 1
Caused by: org.springframework.dao.DataIntegrityViolationException: OJB operation; SQL ; Data truncation: Data too long for column 'PRSN_NM' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'PRSN_NM' at row 1
I have traced it to IdentityArchiveServiceImpl.EntityArchiveWriter.call() method at statement entityCache.add(new EntityDefaultInfoCacheBo( entityToInsert ));
Looks like the EnitytDefault.EntityName.compositeNameUnmasked is set as a composition of lastname, firstname and middlename of an Entity, which is way too big for the Krim_Entity_Cache_T table's prsn_nm:varchar(40)
Is this a known bug in the impex table schema create sql?
Seems the fix would be to make KRIM_ENTITY_CACHE_T.PRSN_NM at least long enough to hold the first, middle and last plus extra formatting characters. Looking at KRIM_ENTITY_NM_T as well as the implementation of EntityName.Builder.getCompositeNameUnmasked() it looks like that would require at least 163 characters (40 + 40 + 80 for column sizes, and then 2 + 1 for extra characters).