Support Center > Search Results > SecureKnowledge Details
Secondary MDS or MLM import fails due to sync error Technical Level
Symptoms
  • MLM Import fails with the following generic messages in the migrate-X.log:

    [DATE TIME] [DbUpgrader::RunCustomCpdbCommand] Going to run custom cpdb upgrade command/opt/CPmds-R80.20/bin/upgrade_standby_server -migrate -primaryip 10.1.1.1 -mdsdb
    [DATE TIME] ...--> DbUpgrader::ExecuteCpdb
    [DATE TIME] [DbUpgrader::ExecuteCpdb] Executing cpdb using the following arguments: /opt/CPmds-R80.20/bin/upgrade_standby_server -migrate -primaryip 10.1.1.1 -mdsdb
    [DATE TIME] [runShellCommand] Executing command: '/opt/CPmds-R80.20/bin/upgrade_standby_server -migrate -primaryip 10.1.1.1 -mdsdb'
    [DATE TIME] [runShellCommand] Execution result: 1, exit code: 5
    [DATE TIME] [DbUpgrader::ExecuteCpdb] ERR: cpdb completed with error code '5'
    [DATE TIME] ...<-- DbUpgrader::ExecuteCpdb
    [DATE TIME] ..<-- DbUpgrader::RunCustomCpdbCommand
    [DATE TIME] [DbUpgrader::exec] ERR: Failed to execute custom upgrade command
    [DATE TIME] .<-- DbUpgrader::exec

  • Cpm_for_cpd log during the import indicates that full sync has failed:

    DATE TIME,PID ERROR utils.runtime.CpAssert$DefaultAssertionErrorHandler [qtp-758318607-168]: AssertionError has been caught: failed loading data of full sync!
    failed loading data of full sync!
Cause

Full sync between the secondary MDS or MLM fails with the primary MDS during the import process.


Solution
 Note: To view this solution you need to Sign In .