Dates set to 2028 or beyond do not display properly within a SQLI Object when using Oracle
Article ID: 87144
Updated On:
Products
CA Automic Workload Automation - Automation Engine
AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction
Error Message :
N/A
The validity period for a SQLI variable that is set in or beyond 2028 is incorrectly displayed when the Preview button on the SQLI variable is selected.
For example, if the validity period is set for 1/1/2028 the year will resolve as 1/1/1772.
The problem only occurs when an Oracle database is used.
N/A
The validity period for a SQLI variable that is set in or beyond 2028 is incorrectly displayed when the Preview button on the SQLI variable is selected.
For example, if the validity period is set for 1/1/2028 the year will resolve as 1/1/1772.
The problem only occurs when an Oracle database is used.
Cause
Cause type:
Defect
Root Cause: Oracle date displayed incorrectly.
Defect
Root Cause: Oracle date displayed incorrectly.
Environment
Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:
Component:
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Fix Version(s):
Automation Engine 12.1.0 – Available
Automation Engine 12.0.1 – Available
Automation Engine 11.2.3 – Available
Automation Engine 11.1.5 – Available
Fix Status: Released
Fix Version(s):
Automation Engine 12.1.0 – Available
Automation Engine 12.0.1 – Available
Automation Engine 11.2.3 – Available
Automation Engine 11.1.5 – Available
Additional Information
Workaround :
Set validity periods to 2027 or earlier when using Oracle.
Set validity periods to 2027 or earlier when using Oracle.
Feedback
Powered by
