Troubleshooting

Icons next to the product server names indicate if database connections are valid. If connection errors occur, click View Log on the Import Schedule page to view the server application log and diagnose connection problems. See Viewing the log.

When using ALM Data Warehouse 2014.1 and earlier, the Helix ALM License Server version must match the data warehouse version.

If the data warehouse version is newer than the license server version, the following error is returned: ALM DW is not compatible with Helix ALM License Server database version (#). To fix this issue, run the Helix ALM or Surround SCM installer to upgrade the license server to the same version as ALM Data Warehouse.

If the license server version is newer than the data warehouse version, the following error is returned: The Helix ALM License Server database version (#) is newer than versions compatible with ALM DW. To fix this issue, upgrade the data warehouse to the same version as the license server.

If the data warehouse detects duplicate universally unique identifiers (UUIDs) in Helix ALM or Surround SCM databases, the following error is displayed: More than one Helix ALM project or Surround SCM mainline has the same UUID. Imports may not work correctly until the conflict is resolved.

The duplicate UUIDs must be fixed to correctly import data. To fix the issue in Helix ALM, see Surround SCM or ALM Data Warehouse Cannot Retrieve Helix ALM Data or Display Incorrect Helix ALM Data. To fix the issue in Surround SCM, contact Perforce Support.

A Could not get JDBC Connection error is returned when importing from product servers and databases hosted in PostgreSQL because remote connections are not enabled for the PostgreSQL server. See Enabling Remote Connections on PostgreSQL Servers for information.

The data warehouse and the SQLite Importer use a Java Virtual Machine (JVM). By default, 64-bit data warehouse is configured to allow the JVM to use a minimum memory heap of 1024 MB and a maximum of 2048 MB. The OutOfMemory error indicates that the data warehouse requires more heap memory to perform some operations, such as large data imports. To resolve this, adjust the heap settings.

1. Using regedit, browse to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\ALMDW\Parameters\Java.

2. To change the minimum Java heap size, edit the JvmMs entry. To change the maximum size, edit the JvmMx entry.

3. Save the file and restart the ALM Data Warehouse Server and SQLite Importer. See Starting the ALM Data Warehouse Server and Starting the Helix ALM SQLite Importer.