Checking the execution results of the dbmigration tool

If needed, you can change the log4j configuration information in the file <$INSTALLDIR>/tools/dbmigration/log4j.properties. For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.

log4j.rootCategory=INFO,CONSOLE,FILE

log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%p [%c] - %m%n

log4j.appender.FILE=org.apache.log4j.RollingFileAppender
log4j.appender.FILE.File=dbmigration.log
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.ConversionPattern=%d %p [%c] - %m%n

By default, the log information is stored in the file <$INSTALLDIR>/tools/dbmigration/dbmigration.log.

When you migrate MDM instances using the dbmigration tool, you can check the log information in the file dbmigration.log to troubleshoot migration issues.

2015-12-16 18:25:36,486 ERROR [org.talend.mdm.db.migration.rest.RESTXmlServer] - Unable to commit on 'Product' (total 2 records, some of them rollbacked)

Additionally, you can check the file <$INSTALLDIR>/logs/mdm.log on the source MDM server and target MDM server respectively to learn more information about the execution results of the dbmigration tool.