Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Database Performance Analyzer (DPA) > Move a DPA repository on MySQL

Move a DPA repository on MySQL

Table of contents
Created by Anthony.Rinaldi, last modified by Chris.Moyer on Sep 23, 2016

Views: 6 Votes: 0 Revisions: 6

Updated July 5, 2016

Overview

This article explains how to move a DPA repository from one MySQL database to another.

If you need to move a SQL Server or Oracle repository, see the following:

Environment

  • DPA 10.2 and later

Steps

  1. In DPA, click Stop All Monitors in the upper right.
  2. Shut down DPA.
    • Windows: Stop the IgnitePI service.
    • Linux: Run shutdown.sh in the DPA installation directory. Ensure there are no crontab entries that will restart DPA.
  3. Create a new empty database on the destination MySQL instance:
    mysqladmin -u username --password="password" -h destination_hostname 
    create databasename_name
  4. Copy the database to the destination server:
    mysqldump -u username --password="password" current_db_name | mysql 
    -u destination_username --password="destination_password" -h hostname 
    databasename_name

    For more information, see the MySQL documentation.

  5. On the DPA server, open the repo.properties file in a text editor.
    • Windows: This file is located at DPA_install_dir\iwc\tomcat\ignite_config\idc
    • Linux: This file is located at DPA_home/iwc/tomcat/ignite_config/idc
  6. Edit the values for the following lines to point to the new repository:
    repo.user=
    repo.databaseName=
    repo.host=
    repo.password=
    repo.name=
    
  7. Start DPA.
    • Windows: Start the IgnitePI service.
    • Linux: Run startup.sh in the DPA installation directory.
  8. In DPA, make sure the server connects to the new MySQL repository database.
  9. Review the status of the database monitors, and start or stop them accordingly.
  10. Review the DPA log for errors.
  11. Wait for 10 minutes, and drill down into each monitored database instance.
  12. Make sure that you see data from the last 10 minutes for the database instances.

 

 

 

Last modified
14:46, 23 Sep 2016

Tags

Classifications

Public