Support Center > Search Results > SecureKnowledge Details
The cma_migrate operation ends with errors
Symptoms
  • The cma_migrate operation ends unsuccessfully with “Renamed Global Objects Detector completed with errors” message.

  • The warnings are:
    ...
    ^^^ Executing Global Policy on Source Database Detector
    
    Warning: Global policy was detected on the source database:
             /opt/CPmds-R77/customers/CMA name/CPsuite-R77/fw1/tmp//export_db/fwdir
             The Domain Management Server after migration will have global rules and/or objects,
             but there will be no indication that a global policy is assigned on it.
             After migration, in order to have a global policy assigned on this
             Domain, use ^Assign Global Policy^.
    
    Todo:    Stop the migration process and remove the global policy from the
             source database, or continue with the migration process.
    ----------------------------------------------------------------------
    Global Policy on Source Database Detector completed with warnings
    
    ======================================================================
    ^^^ Executing Renamed Global Objects Detector
    
    Warning: Renamed global objects were found on the source database:
             /opt/CPmds-R77/customers/CMA name/CPsuite-R77/fw1/tmp//export_db/fwdir
             The Domain Management Server after migration will have not updated global objects,
             but there will be no indication about that.
    
Cause

The cma_migrate script runs pre_upgrade validations, including validations for renamed objects. It fails if there is any content in gdb_rename table, no matter what is the domain.


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