Automic Community

Expand all | Collapse all

Does Applications Manager 8.0 support Oracle 12c?

  • 1.  Does Applications Manager 8.0 support Oracle 12c?

    Posted 11-09-2017 10:21 AM
    Does Applications Manager 8.0 support Oracle 12c as the database or will an application upgrade be required? We require Ellucian Banner integration.


  • 2.  Does Applications Manager 8.0 support Oracle 12c?

    Posted 11-09-2017 10:25 AM

    We require that Applications Manager be on version 9.x to utilize 12c as our Oracle DB for the Application.

    Under specific circumstances it is possible to use 12c for JUST the Banner DB on version 8 but this will affect some of our system jobs.



  • 3.  Does Applications Manager 8.0 support Oracle 12c?

    Posted 11-09-2017 10:32 AM
    To add to Doug's comment the following issue is seen when running a 12c banner database with Applications Manager 8.

    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
    aw_web_api.aw_prod_sched
    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

    jdbc:oracle:thin:@appworx.home.edu:1521:AMPRD:APPWORX

    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.

    Work Around....

    We recommend one of these two options. 1) Upgrade AM to V9.x 2) 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.