• Reference
  • Version · 6.0
  • Change Automation Reference

--db2z-tracking-tables-location-database

Last updated: August 12, 2026

--db2z-tracking-tables-location-database is a global parameter that specifies the database name for the Liquibase tracking tables on DB2 z/OS. There is no default value.

On DB2 z/OS, you may need to explicitly define the database where Liquibase places its tracking tables (DATABASECHANGELOG and DATABASECHANGELOGLOCK). Use this parameter to control which database receives the tracking tables, ensuring your deployment aligns with your organization's data architecture and storage policies.

When placing tracking tables in a pre-existing tablespace, Db2 does not automatically create the required indexes. Without them, the tracking tables are left in an unavailable state, preventing Liquibase from running. You must set --db2z-databasechangeloglock-index, --db2z-databasechangelog-index, --db2z-tracking-tables-location-tablespace, and (if applicable) --db2z-tracking-tables-location-database together. Omitting any of these parameters may leave the tracking tables unavailable or prevent Liquibase from running.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.db2z.trackingTables.location.database: <string>

Global flow file argument

globalArgs: { db2z-tracking-tables-location-database: "<string>" }

Global CLI parameter

liquibase --db2z-tracking-tables-location-database=<string>

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.db2z.trackingTables.location.database=<string>

Windows:

JAVA_OPTS=-D"liquibase.db2z.trackingTables.location.database"=<string>

Liquibase environment variable

LIQUIBASE_DB2Z_TRACKING_TABLES_LOCATION_DATABASE=<string>

PreviousLiquibase.bteq.maxerrorNextGlobal report parameters