Tableau Server 2022.3 Upgrade Failing with error "Internal error processing completeApplyMigrations"

Published: 08 Nov 2022
Last Modified Date: 21 Nov 2022


When upgrading Tableau Server to version 2022.3 the upgrade may fail running migrations and present the error:

Internal error processing completeApplyMigrations

Console Output Example:
41% - Running migrations failed.
50% - Disabling database services.
58% - Waiting for database services to disable.
66% - Upgrading database failed

This job failed due to unexpected error: 'TApplicationException'
org.apache.thrift.TApplicationException: Internal error processing completeApplyMigrations

Error message located in the databasemaintenance.log file:

2022-11-01 20:59:03.571 +0000 db-op-0 : ERROR com.tableausoftware.dbmigration.MigrationDriver - Migration Migration20220405030000MakeSiteIdOnBigTextsTableNotNull.sql (20220405030000) failed.
org.postgresql.util.PSQLException: ERROR: column "site_id" of relation "big_texts" contains null values



  • Tableau Server 2022.3 and newer


Typically once an upgrade process fails at this point, the server will be in an unrecoverable state and will require a rebuild. 

1. Make sure a recent backup (.tsbak) of Tableau Server is available in a location outside of the Tableau Server directories.
2. Obliterate the current Tableau Server installation.
3. Reinstall Tableau Server and restore the backup.
4. Contact Tableau Support for assistance in removing the big_texts table from your Tableau Postgres database.
5. After working with Tableau Technical Support, the upgrade can be completed.


The big_texts table in Postgres contains null values preventing the database migration during the upgrade process from completing.

Additional Information

The Postgres database can be queried for the big_texts table to verify that this entry contains rows with null values in the site_id column.

Access to the repository can be enabled through the steps indicated in the following Tableau Product Help guide, Collect Data with the Tableau Server Repository.
Did this article resolve the issue?