Update Alation to 2026.4.0.0

Customer Managed Applies to customer-managed instances of Alation

2026.4.0.0 Update Version Dependencies

Alation supports a direct update to version 2026.4.0.0 from the following previous versions:

  • 2026.1.0.0

  • 2025.3.4.1

The information about new features and bug fixes in 2026.4.0.0 is available in 2026 Release Notes for Customer-Managed Alation Releases.

Update from Version 2025.1.x or Older

Direct update to version 2026.4.0.0 is not supported from 2025.1.x or older versions. First, update Alation to a version that supports the update to 2026.4.0.0, and then perform a second update.

Update Known Issues

Reset Postgres Password

If you have a password set on the internal PostgreSQL database (Rosemeta), the update will result in an error similar to the following:

WARN: unable to check pg-1: [DbConnectError] unable to connect to 'dbname='postgres' port=5432':
FATAL: password authentication failed for user "postgres"
password retrieved from file "/home/postgres/.pgpass"
ERROR: [056]: unable to find primary cluster - cannot proceed

The update process requires that the password on the internal PostgreSQL database should be cleared for the time of the update. The password can be set again after the update is completed. On how to set the Postgres password, see Set Password for Internal PostgreSQL Instances.

Release-Specific Information

PostgreSQL Version Update to 16.13

In release 2026.4.0.0, the internal PostgreSQL database and Alation Analytics PostgreSQL database were upgraded to version 16.13. The PostgreSQL upgrade is performed automatically as part of the standard Alation and Alation Analytics update process.

Elasticsearch Update to 8.19.12

In version 2026.4.0.0, the Elasticsearch component of Alation was updated to version 8.19.12, which resolves security concerns.

Update Steps

Step 1: Scan Postgres

We recommend using the scan_postgres action to validate that the internal Postgres database is in a healthy state before the update. For steps, see How to Scan Postgres for Corrupted Indexes.

Note

If in your instance the Postgres scan runs on a schedule, you can check the scan-postgres.log file in /opt/alation/site/logs inside the Alation shell to check the Postgres state.

Step 2: Verify Backup Availability

Ensure you have a valid, up-to-date Alation backup. We recommend taking the most recent backup possible to closely match your current data.

Step 3: Update the Alation Application

Step 4: Update Alation Connector Manager

This step applies if you are using Open Connector Framework (OCF) and OCF connectors.

Update Alation Connector Manager using the steps in Update Alation Connector Manager.

Step 5: Update Alation Analytics

This step applies if you are using the Alation Analytics application.

Use the steps in Update Alation Analytics V2 to update the Alation Analytics application.