Database migration fails with no distinguishable error
Article ID: 100046333
Updated On:
Description
Error Message
From migrate log:
[java] 2019-09-22 09:22:09,722 INFO [STDOUT] (main:) 2019-09-22 09:22:09.706 - Dropping DB schema 'esadb_wdccwcmw01_lds_evidence_repo_amjckxnsau'... done. (16 msec)
[java] 2019-09-22 09:22:09,722 INFO [STDOUT] (main:) 2019-09-22 09:22:09.722 - done. (20535 msec)
[java] 2019-09-22 09:22:09,722 WARN [STDERR] (main:) com.teneo.esa.cluster.MigrateDbNamespace$FailedMigrationException: Migrating appliance DB and namespace failed.
[java] 2019-09-22 09:22:09,722 WARN [STDERR] (main:) at com.teneo.esa.cluster.MigrateDbNamespace.migrate(MigrateDbNamespace.java:348)
[java] 2019-09-22 09:22:09,722 WARN [STDERR] (main:) at com.teneo.esa.cluster.MigrateDbNamespace.main(MigrateDbNamespace.java:1023)
2019-09-22 09:22:09,722 WARN [STDERR] (main:) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
From ant_output.log:
09-22-19:08:55 WARN tools.ant.taskdefs.Echo - Starting service = MySQL
09-22-19:08:55 ERROR tools.ant.taskdefs.ExecTask - Result: 2
09-22-19:09:22 ERROR apache.tools.ant.UnknownElement - Task "java" finished with error.
D:\CW\V82\build\build-schema.xml:1437: Java returned: -1
NOTE: If there is an error it may point to the "xxxxx_lds_collection_reslt_xxxxxxx" database.
Cause
This is caused by collection data existing in the cluster master server database.
Resolution
To resolve this issue a property needs to be added to the cluster master.
1. Log into the eDP user interface as an administrator.
2. System > Support Features > Property Browser
3. Ensure the following is set:
Appliance = cluster master
Select the case (or system) = system
Name of property to change = esa.common.dbms.fastRestore
New value (leave blank to remove) = false
Confirm change. Are you sure? = Checked
4. Click Submit.
5. Stop services and try the migration again.
Issue/Introduction
Additional Information
