vSphere Replication creates temporary tables in the vSphere Replication database. If you use a DB2 database, the database might require additional configuration.

If the vSphere Replication user account that you use to log in to the vSphere Replication database cannot create temporary tables, configuration of vSphere Replication with an external DB2 database fails.

The virtual appliance management interface (VAMI) shows the error Error applying startup configuration: Please check the provided DB information.

The /opt/vmware/hms/logs/hms-configtool.log file in the vSphere Replication appliance contains the following error message:

ERROR com.vmware.hms.configtool.App [main] (..hms.configtool.App)  | 
Error while configuring HMS, exit code DATABASE_ERROR
com.vmware.hms.configtool.ConfigToolException: Database requires further configuration: 
Need user temporary tablespace.

This problem occurs only when you use a DB2 database.

The temporary tablespace was not configured for the user account that you use to connect to the vSphere Replication database.

1

Run an SQL script to verify that the vSphere Replication user account can create temporary tables in DB2 databases.

declare global temporary table testtable(foobar integer) on commit preserve rows not logged

If the script runs successfully, no further configuration is required. If it fails, you see a message like the following message:

A default table space could not be found with a page size of at least "4096" that 
authorization ID "VR_PROT" is authorized to use. SQLCODE=-286, SQLSTATE=42727, DRIVER=4.11.69
2

If the script fails, run an SQL script to configure the temporary tablespace.

CREATE USER TEMPORARY TABLESPACE tbsp_temp_vr_prot MANAGED BY AUTOMATIC STORAGE

GRANT USE OF TABLESPACE tbsp_temp_vr_prot TO USER VR_PROT