Historian Simple Retention Throws Unexpected Exception
(Doc ID 2870313.1)
Last updated on MAY 20, 2022
Applies to:
Oracle Documaker - Version 12.6.4 and laterInformation in this document applies to any platform.
Symptoms
On : 12.6.4 version, Enterprise Edition
When using Simple Retention (RETENTION-Configuration-Historian-Retention Type = Simple), the Historian fails to process any records with the following error:
2022-04-26 13:10:00.231 UTC-DEBUG-[HistorianQuartzScheduler_Worker-1]-[HistorianTask.java:2168]-oracle.documaker.historian.HistorianTask.setRetentionWithProperties: UPDATE BCHS_RCPS SET BCHRCPHISTORICAL = 1 , BCHS_RCPS.BCHRCPRETENTION = BCHRCPRETENTION=Thu May 26 13:10:00 UTC 2022WHERE JOB_ID IN(-1)
2022-04-26 13:10:00.236 UTC-ERROR-[HistorianQuartzScheduler_Worker-1]-[HistorianTask.java:2376]-oracle.documaker.historian.HistorianTask.setRetentionWithProperties: Unexpected exception in with error at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1821)
The debug statement above the stack trace shows the exact problem -- the SQL statement is malformed. The date value is not delimited, and the column assignment value is incorrectly written as the column name is repeated twice, and the statement will not have a WHERE clause since the date is not delimited.
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 |
| References |