# Ignition Alarm Journal component going into error

**URL:** <https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [May 3, 2023, 2:15pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205 "2023-05-03T14:15:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rkumar](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@rkumar](https://forum.inductiveautomation.com/u/rkumar)\
**Post date:** [May 3, 2023, 2:15pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205/1 "2023-05-03T14:15:12Z")

</div>

Hello,  
We are trying to use Ignition Alarm Journal component but it is going into error. We are using Oracle database for storing the journal data.

Initially we thought that it is date parameter issue which is being passed in the component but even if we call the script to get the journal data, without date parameters, it is failing with the same error message as below

**java.util.concurrent.ExecutionException: com.inductiveautomation.ignition.client.gateway\_interface.GatewayException: java.lang.ClassCastException: Cannot coerce value '2023-05-02 10:08:36.081' into type: class java.util.Date**

Ignition version: 8.0.7 (b2019122014)  
Oracle Version: 19c  
JDBC: ojdbc8.jar

Any pointers to resolve this issue will be helpful.

thanks,  
rajiv kumar,  
[rkumar@optebiz.com](mailto:rkumar@optebiz.com)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 3, 2023, 2:30pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205/2 "2023-05-03T14:30:42Z")

</div>

Somewhere before the timestamp gets to Oracle, something in Ignition is converting it to a string, which Oracle then chokes on. If you have customized any of this, make sure you aren't using curly braces in your SQL--use a named query or a "Prep" update with question-mark substitution parameters.

If you haven't customized this, then it is likely an Ignition bug, and you might be [expletive]. Ignition v8.0 is long past end of life (it was not a long-term-support version) and hasn't been getting any bugfixes for more than a couple years. Upgrade to the last v8.0 at least, but preferably to v8.1.

---

<div class="post-metadata">

**Author:** ![rkumar](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@rkumar](https://forum.inductiveautomation.com/u/rkumar)\
**Post date:** [May 3, 2023, 2:55pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205/3 "2023-05-03T14:55:30Z")

</div>

thanks Phil,  
We have not customized anything at oracle level. The Alarm status component is showing the data correctly from the same tables, I suppose, but Alarm Journal is not. We will upgrade Ignition version also to 8.1 as suggested by you.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 3, 2023, 2:57pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205/4 "2023-05-03T14:57:32Z")

</div>

Note that upgrades from v8.0 to v8.1 are not free unless your support contract is current.

---

<div class="post-metadata">

**Author:** ![rkumar](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@rkumar](https://forum.inductiveautomation.com/u/rkumar)\
**Post date:** [May 17, 2023, 7:53am UTC](https://forum.inductiveautomation.com/t/ignition-alarm-journal-component-going-into-error/73205/5 "2023-05-17T07:53:08Z")

</div>

I upgraded Ignition and it did resolve the issue. I went to latest but versions above 8.0.11 should not have this problem.
