[AWA] Rebind Errors when upgrading the UC4 DB2 database from DB2 V10.1 to DB2 11.1

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

After UC4 Dev db UC4DB has been successfully upgraded from UC4 V10 to UC4 V12, and a db backup has been taken.
We are now attempting to upgrade the back end DB2 database. While upgrading db2 (from db2 v10.1 to db2v 11.1) we encountered the following rebind failures when attempting to upgrade the UC4 Dev database UC4DB (which was generated from a copy of our UC4 Prod db). Note, the 'Upgrade Database' command included the REBINDALL utility which rebinds 'all' packages found in the database.
 

Package 'UC4PROD.P1097122080' of database 'UC4DB' did not succeed to rebind. UniqueID = 69424B7157614764 
sqlcode = -440; sqlerrmc = APPLICAT; sqlrrp = SQLNQ259APPLICAT 
SQL0440N No authorized routine named "APPLICATION_ID" of type "FUNCTION" having compatible argum 

Package 'UC4PROD.P1255587147' of database 'UC4DB' succeeded to rebind. UniqueID = 41414C7157614764 
Package 'UC4PROD.P878039475' of database 'UC4DB' did not succeed to rebind. UniqueID = 4B414C7157614764 
sqlcode = -440; sqlerrmc = APPLICAT; sqlrrp = SQLNQ259APPLICAT 
SQL0440N No authorized routine named "APPLICATION_ID" of type "FUNCTION" having compatible argum

These 2 packages align with the following UC4PROD routine Packages

UC_GET_LAST_AGENT_LOG P1097122080 
UC_GET_OLD_REP P878039475

Before we proceed any further with the db2 upgrade could you let us know if there are any issues with these rebind failures?
 

Environment

Release:
Component: AAUTEN

Resolution

The two Routine packages:

- UC_GET_LAST_AGENT_LOG P1097122080 
- UC_GET_OLD_REP P878039475

are not used anymore. These procedures were used during the upgrade from v6 to v8 (changed all history tables to support ILM). So you can drop them to avoid future issues during a DB upgrade.