AAI not starting after upgrade from 5.8.6 to 6.0.2-1 - ORA-00942: table or view does not exist
search cancel

AAI not starting after upgrade from 5.8.6 to 6.0.2-1 - ORA-00942: table or view does not exist

book

Article ID: 203576

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

AAI not starting after upgrade from 5.8.6 to 6.0.2-1

 

ERROR [SystemCheckDataBuilder] could not get license information.: com.termalabs.common.datastore.DataAccessException: Error while executing query: "from UniversalJobProperties"
        at com.termalabs.common.connection.hibernate.RichQueryCommon.executeAndTime(RichQueryCommon.java:1047)
        at com.termalabs.common.connection.hibernate.RichQueryCommon.list(RichQueryCommon.java:969)
        at com.termalabs.server.hibernate.RichQuery$CollectionQuery.asSetUnfiltered(RichQuery.java:175)
        at com.termalabs.server.hibernate.RichQuery$CollectionQuery.asSet(RichQuery.java:155)
        at com.termalabs.server.hibernate.jaws.HibernateJawsJobData.initJobPropertiesInHibernateL1Cache(HibernateJawsJobData.java:320)
        at com.termalabs.server.hibernate.jaws.HibernateJawsJobData.primeJobsAndConditions(HibernateJawsJobData.java:272)
        at com.termalabs.server.cache.SchedulerDependentMapsCache.primeHibernateCache(SchedulerDependentMapsCache.java:269)
        at com.termalabs.server.cache.SchedulerDependentMapsCache.initializeSchedulerMapAndDependentMaps(SchedulerDependentMapsCache.java:153)
        at com.termalabs.server.cache.SchedulerDependentMapsCache.initializeSchedulerMapIfNecessary(SchedulerDependentMapsCache.java:135)
        at com.termalabs.server.cache.SchedulerDependentMapsCache.getSchedulers(SchedulerDependentMapsCache.java:128)
        at com.termalabs.server.cache.SchedulerVendorImpl.getSchedulers(SchedulerVendorImpl.java:342)
        at com.termalabs.server.cache.LicenseVendorImpl.getInstanceCounts(LicenseVendorImpl.java:313)
        at com.termalabs.server.cache.LicenseVendorImpl.getCurrentLicenseInfo(LicenseVendorImpl.java:282)
        at com.termalabs.server.cache.LicenseVendorImpl.getCurrentLicenseInfo(LicenseVendorImpl.java:266)
        at com.termalabs.server.scheduler.common.SystemCheckDataBuilder.build(SystemCheckDataBuilder.java:82)
        at com.termalabs.server.scheduler.common.SystemCheckDataBuilder.build(SystemCheckDataBuilder.java:69)
        at com.termalabs.server.system.ApplicationAlertCreator.loop(ApplicationAlertCreator.java:192)
        at com.termalabs.server.system.ApplicationAlertCreator$1.run(ApplicationAlertCreator.java:159)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)
Caused by: org.hibernate.exception.SQLGrammarException: could not execute query
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:90)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
        at org.hibernate.loader.Loader.doList(Loader.java:2235)
        at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2129)
        at org.hibernate.loader.Loader.list(Loader.java:2124)
        at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401)
        at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363)
        at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
        at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149)
        at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
        at com.termalabs.common.connection.hibernate.RichQueryCommon$1.execute(RichQueryCommon.java:972)
        at com.termalabs.common.connection.hibernate.RichQueryCommon$1.execute(RichQueryCommon.java:969)
        ... 19 in common
Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

 

 

Environment

Release : 6.0.2

Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE

Resolution

After the upgrade completes, there will be an upgradeJawsDbTo6.0.2-1.sql script in the /<install dir>/scripts folder.

These scripts should be run by the user that owns the AAI schema and the user that AAI is configured to connect to the database with.

If they are run by another user, you must grant permissions on any new tables that are added with each version.


Some of the new tables and columns can be found in the links below, depending on which version you are coming from there may be more tables, which you can check by reviewing the upgradeJawsDbTo6.0.2-1.sql for any new tables:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/automic-automation-intelligence/6-0-0/Minor_Release_Notes_1/release-notes-6_0_2/databaseschemaupgradesum6-0-2.html

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/automic-automation-intelligence/6-0-0/Minor_Release_Notes_1/release-notes-6_0_1/databaseschemaupgradesum.html


Once the permissions are granted to those tables, restart the AAI service and verify the log message above no longer appears.