Error: "An unexpected database error has occurred" when attempting to create Cold Migration Templates
search cancel

Error: "An unexpected database error has occurred" when attempting to create Cold Migration Templates

book

Article ID: 430747

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

  • When attempting to load the Cold Migration Templates UI it fails with the following error in the UI:  'An unexpected database error has occurred' 
  • The Cloud Director Availability Replicator(s) were recently upgraded to 4.7.4.
  • In the /opt/vmware/h4/cloud/log/cloud.log file on the source Cloud Director Replication Management Appliance, you see entries similar to:

    2026-02-19 09:21:14.701 ERROR - [######-####-####-####-############] [cold-migration-scheduler-1] c.v.h.c.r.ColdMigrationDiscoveryService  : Failed to refresh cold migrations from H4DM

    com.vmware.h4dm.client.fault.DatabaseFault: An unexpected database error has occurred.
            at jdk.internal.reflect.GeneratedConstructorAccessor284.newInstance(Unknown Source)
            at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
            at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
            at com.fasterxml.jackson.databind.introspect.AnnotatedConstructor.call(AnnotatedConstructor.java:128)
            at com.fasterxml.jackson.databind.deser.std.StdValueInstantiator.createFromObjectWith(StdValueInstantiator.java:291)
            at com.fasterxml.jackson.databind.deser.ValueInstantiator.createFromObjectWith(ValueInstantiator.java:288)
            at com.fasterxml.jackson.databind.deser.impl.PropertyBasedCreator.build(PropertyBasedCreator.java:202)
            at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:444)
            at com.fasterxml.jackson.databind.deser.std.ThrowableDeserializer.deserializeFromObject(ThrowableDeserializer.java:65)
            at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeOther(BeanDeserializer.java:220)
                      :
                      :
    Caused by: com.vmware.rest.client.exception.UnexpectedTextResponseStatusError: Unexpected response status: 500 Internal Server Error
            at com.vmware.rest.client.converters.DefaultConverter.deserializeTextError(DefaultConverter.java:112)
            at com.vmware.h4dm.faults.H4dmClientFaultDeserializer.deserialize(H4dmClientFaultDeserializer.java:31)
            ... 12 common frames omitted

  • In the /opt/vmware/h4/h4dm/log/h4dm.log on the source replicator(s) you will see entries similar to:

    2026-02-08T13:35:04.459908Z DEBUG http_req{opId=########-####-####-####-############_##}:cold_mig_list: epic: code: DatabaseFault, args: [], msg: An unexpected database error has occurred., orig_msg: Query Error: error returned from database: column cold_migrations.root_disk_lvm_id does not exist
       0: convert_seaorm_error
                 at /__w/h4dm/h4dm/crates/epic/src/database_errors.rs:20:5
       1: from
                 at /__w/h4dm/h4dm/crates/epic/src/lib.rs:210:9
       2: call_once<fn(sea_orm::error::DbErr) -> epic::Fault, (sea_orm::error::DbErr)>
                 at /rustc/########################################/library/core/src/ops/function.rs:253:5
       3: map_err<alloc::vec::Vec<(database::entities::cold_migrations::Model, alloc::vec::Vec<database::entities::cold_migration_disks::Model, alloc::alloc::Global>), alloc::alloc::Global>, sea_orm::error::DbErr, epic::Fault, fn(sea_orm::error::DbErr) -> epic::Fault>
                 at /rustc/########################################/library/core/src/result.rs:914:27
       4: {async_fn#0}
                 at /__w/h4dm/h4dm/crates/database/src/cold_migrations.rs:186:10
       5: {async_block#0}
                 at /__w/h4dm/h4dm/h4dm/src/rest/handlers/os_based.rs:175:73
       6: poll<h4dm::rest::handlers::os_based::cold_mig_list::{async_fn#0}::{async_block_env#0}>
                 at /home/andrew/.cargo/registry/src/packages.vcfd.broadcom.net-################/tracing-0.1.41/src/instrument.rs:321:15
       7: {async_fn#0}
                 at /__w/h4dm/h4dm/h4dm/src/rest/handlers/os_based.rs:168:1
       8: {async_fn#0}
                 at /__w/h4dm/h4dm/h4dm/src/warpgen/os-based.rs:302:119

 

Environment

VMware Cloud Director Availability 4.7.4

Cause

This issue is occurs due to missing columns in the h4dm database. This issue only affects replicators that were upgraded to Cloud Director Availability 4.7.4. Newly deployed replicators are not affected.

Resolution

Broadcom Engineering is aware of this issue and it will be resolved in a future release.

To work around this issue, contact VMware Cloud Director Support and note this Article ID 430747 in the problem description. For more information, see Creating and managing Broadcom support cases.

Powered by Wolken Software