Checking for Incompatibilities between Version 21.0.3 and 21.0.4

As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system.

The tables below list new features that might lead to compatibility issues or should be taken care of when upgrading; they do not list all new features of this AE version. New features are described in full in the Release Highlights and Release Notes.

More information:

To provide a better overview, the tables are categorized by the severity of the issue. There are three different categories:

Critical: Issues that must be addressed, otherwise the system will not work
Behavior change: Functionality changes in existing features that might have an impact on your system
Advisory: Different issues you should be aware of but might not have an impact on your system

The columns display the following information:

Topic: Name of the general topic or new feature
Changed behavior: What has been changed
Possible incompatibilities: Impact the change may have
Actions/Countermeasures: What can be done to identify and/or remove possible incompatibilities

This page includes the following:

Compatibility Issues

Automic Automation

Behavior Change

Topic	Changed Behavior	Possible Incompatibilities	Actions/Countermeasures
CREATE TRIGGER privilege Oracle DB	The CREATE TRIGGER privilege is now required when you install or upgrade an Oracle database	If you use an Oracle database that does not have this privilege and you upgrade your system, the system will not be able to access the database.	Make sure your Oracle DB has the CREATE TRIGGER privilege.

Advisory

Topic	Changed Behavior	Possible Incompatibilities	Actions/Countermeasures
General DB change Note: Information and the checking instructions apply to all versions, between your existing installation and the latest you want to upgrade to, respectively.	The DB scheme/structure has been changed.	Custom SQL queries on AE DB do not work anymore.	Check and adapt relevant SQL/SQLI/SQLJOBS objects accordingly Check and adapt relevant DB queries used in external tools/programs
JCP certificate renewal	The system checks the expiration date of JCP certificates every 24 hours (At midnight UTC) instead of every 30 days. The expiration date is also written into the JCP log every 24 hours (at midnight UTC)	No incompatibilities.	Objects that are executed on expiration check might be triggered more often since the system checks the expiration date every 24 hours.

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures

General DB change

Note: Information and the checking instructions apply to all versions, between your existing installation and the latest you want to upgrade to, respectively.

The DB scheme/structure has been changed.

Custom SQL queries on AE DB do not work anymore.

Check and adapt relevant SQL/SQLI/SQLJOBS objects accordingly
Check and adapt relevant DB queries used in external tools/programs

JCP certificate renewal

The system checks the expiration date of JCP certificates every 24 hours (At midnight UTC) instead of every 30 days.

The expiration date is also written into the JCP log every 24 hours (at midnight UTC)

No incompatibilities.

Objects that are executed on expiration check might be triggered more often since the system checks the expiration date every 24 hours.

Automic Automation Kubernetes Edition

Behavior Change

Topic	Changed Behavior	Possible Incompatibilities	Actions/Countermeasures
Enable TLS for AWI and JCP REST withing the cluster	TLS is always enabled for AWI and JCP REST for AAKE deployments.	Depending on the Controller being used, the ingress configuration might have to be adapted. The generated Ingresses for AWI and JCP-REST are changed automatically with the upgrade to AAKE 21.0.4.	Ingresses created manually might require changes to allow the usage of TLS within the cluster.