Problem Note 63564: A scenario firing event on an entity with an ID that is longer than 36 characters can cause errors in SAS® Visual Investigator
 |  |  |  |  |
A scenario firing event fails for an entity that has an ID that is longer than 36 characters. When this issue occurs, you can experience errors in the alerting event save job that look similar to the following:
2018-10-10 16:16:54.643 WARN 13 — o.h.engine.jdbc.spi.SqlExceptionHelper : sas.svi-alert@@acme [2ca22a473fac22e9] SQL Error: 0, SQLState: 22001
2018-10-10 16:16:54.643 ERROR 13 — o.h.engine.jdbc.spi.SqlExceptionHelper : sas.svi-alert@@acme [2ca22a473fac22e9] ERROR: value too long for type character varying(36)
2018-10-10 16:16:54.643 ERROR 13 — o.h.engine.jdbc.spi.SqlExceptionHelper : sas.svi-alert@@acme [2ca22a473fac22e9] ERROR: value too long for type character varying(36)
A corresponding error in the job service information for that task also appears:
could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.DataException: could not execute statement
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Investigator | Linux for x64 | 10.4 | 10.4 | Viya | Viya |
An update for this issue is available for SAS Visual Investigator 10.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdates
The alerting event save job fails when a scenario fires on an entity that has an ID value that is greater than 36 characters.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-02-04 09:49:41 |
| Date Created: | 2019-01-28 17:03:01 |