Forecast job fails with "Invalid year value" error when using the ojdbc14 driver in v8


Article ID: 84532


Updated On:


CA Automic Applications Manager (AM)


Error Message :
ErrorMsg: AwE-9999 Internal error (8/6/15 11:59 PM)
Details: Invalid year value

This issue is specific to Applications Manager (AM) version 8.0x using Oracle 11g with a RA Banner Agent using 12c installed on the same machine as the Master.  

When the AM database (DB) is Oracle 11g and the Banner DB is Oracle 12c and is located on the Master's server, you are required to replace the ojdbc14 driver for ojdbc6 to allow this configuration to work. One of the side affects of doing this is that the FORECAST job will appear to run successfully but will actually fail with an 'Invalid year value" error similar to this in the Master log:
ErrorMsg: AwE-9999 Internal error (8/6/15 11:59 PM)
Details: Invalid year value
0 start_date: IN:TIMESTAMP:java.sql.Timestamp:12-31-1969 18:00:00 CST
1 end_date: IN:TIMESTAMP:java.sql.Timestamp:08-17-292278994 01:12:55 CST
2 levels: IN:NUMERIC:java.lang.Integer:33
3 granularity: IN:VARCHAR2:java.lang.String:1

ErrorMsg: AwE-9999 Internal error (8/6/15 11:59 PM)
Details: java.lang.IllegalArgumentException: Invalid year value
forecast cache thread

This invalid year value error may also be seen when executing any job that uses our standard SQLP script while the ojdbc14 driver is in place and you are using AM v8.0x against Oracle 11g.


Cause type:
Root Cause: The root cause appears to be using the ojdbc6 against an 11g DB. While this allows you to run 12c for Banner it does cause some issues with our standard SQLP Jobs.


Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent


We recommend one of these two options.:
  1. Upgrade AM to V9.x
  1. Install a second remote Agent on the Master server. If the Master's local Agent is using a host name you would use the IP address in the second remote Agent and then use the IP address on the Banner Agent or vise versa so you have a unique server name. You could then replace the odjbc file on the second Agent rather than the Master's local Agent. Please be aware this might require a licensing change if you are only licensed for one agent in this environment.

Fix Status: No Fix