Performance warehouse migration troubleshooting

If the migration did not finish successfully or the connection status shows migration needed, see Performance warehouse administration for requirements and needed database permissions. There may be an error message in the client when you try to connect the Performance Warehouse (depending on your type of issue), which contains good hints for further analysis. Also, the repository log contains very helpful information. In the System Information dashlet, click Server > Support Information > Log Files to access the log.

The sections below show known PWH migration issues and the solutions. Check the error messages in the AppMon Client and in the repository log.

SEVERE [FlywayRepositorySchema] error

Error message

SEVERE [FlywayRepositorySchema] error during performance warehouse migration: com.dynatrace.diagnostics.repository.flyway.FlywayRepositorySchema a:314

org.flywaydb.core.api.FlywayException: Found non-empty schema "DT_APM" without metadata table. Use baseline() or set baselineOnMigrate to true to initialize the metadata table.

Affected database

DB2 only.

Affected AppMon version

6.3 and later.

Description

For DB2, the schema name must have eight characters. If the name is shorter (see the two blanks in the name "DT_APM" to fill up to 8 chars), the schema name cannot be requested correctly.

Solution

  1. Disconnect the Performance Warehouse in the client.
  2. Add a file named flyway.properties to the folder <DT_HOME>/server/conf/.
  3. Edit this file and add the line: flyway.schemas=<schema_name>. For example, flyway.schemas=DT_APM.
  4. Re-connect the PWH in the client.

SEVERE [AbstractRepositoryAccessor] [PWH SCHEMA UPDATE] error

Error message

SEVERE [AbstractRepositoryAccessor] [PWH SCHEMA UPDATE]
Migration V6.3.0.7__createIncidentProperties.ddl failed

Error Code : -613
Message : The primary key, unique key, or table partitioning key identified by "INCIDENTPROPERTIES_PKEY" is too long or has too many columns.. SQLCODE=-613, SQLSTATE=54008, DRIVER=4.14.122
Location : ddls/db2/update/6.3.x/V6.3.0.7__createIncidentProperties.ddl (/ddls/db2/update/6.3.x/V6.3.0.7__createIncidentProperties.ddl)
Line : 1
Statement : CREATE TABLE incidentproperties (
uuid_lsb BIGINT NOT NULL,
uuid_msb BIGINT NOT NULL,
propkey VARCHAR(100) NOT NULL,
value VARCHAR(1000) NOT NULL,


CONSTRAINT incidentproperties_pkey PRIMARY KEY (uuid_lsb, uuid_msb, propkey, value)
)

Affected database

DB2 only.

Affected AppMon versions

6.3 and later.

Description

The Performance Warehouse requires a page size of 16k. See Performance warehouse administration for details. The message The primary key, unique key, or table partitioning key identified by "INCIDENTPROPERTIES_PKEY" is too long or has too many columns indicates this issue.

Solution

Create the PWH in a 16k tablespace.

SEVERE [AbstractRepositoryAccessor] error

Error message

SEVERE [AbstractRepositoryAccessor] cannot create performance warehouse schema: com.dynatrace.diagnostics.sdk.logging.ThrottlingLogger a:150

org.flywaydb.core.api.FlywayException: Found non-empty schema [MS\dtuser] without metadata table. Use baseline() or set baselineOnMigrate to true to initialize the metadata table.

Affected database

SQL Server only.

Affected AppMon versions

6.3 and later.

Description

Some special configuration on the SQL server allows the usage of the domain name and the user name as schema name. The determiner between the two components is a backslash. This backslash causes problems with the used JDBC driver.

Solution

There is no solution, just a workaround. An additional schema for the PWH versioning table is needed:

  1. Disconnect the Performance Warehouse in the client.
  2. Add a file named flyway.properties to the folder <DT_HOME>/server/conf/.
  3. Edit this file and add the line: flyway.schemas=<schema_name>. For example, flyway.schemas=dtuser. Add the name of the new, additional schema here.
  4. Re-connect the PWH in the client.