Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

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

Move a DPA repository on Oracle

Table of contents
Created by Interspire Import, last modified by Melanie Boyd on Nov 09, 2017

Views: 1,311 Votes: 0 Revisions: 18


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

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


  • DPA, all versions


  1. Shut down the DPA Server.
    • Windows: Stop the Ignite PI Server service.
    • Linux: Run Ensure there are no crontab entries that will automatically restart DPA.
  2. Export the schema holding the DPA Repository. Enter the following command:
    exp DPA_username/DPA_user_password@repository_database file=ignite_repo.dmp owner=DPA_username grants=Y buffer=2000000
  3. Create a schema in the new repository database using any username/password you like.

    You may wish to create a DPA tablespace to hold the DPA data in the new Repository.

    SQL> create user DPA_username identified by DPA_user_password default tablespace DPA_tbsp;
    SQL> grant dba to DPA_username;
  4. Import the repository data from the previous step into the new database. Enter the following command:
    imp DPA_username/DPA_user_password@repository_database file=ignite_repo.dmp full=Y buffer=2000000
  5. Update the repository database information in the file on the DPA server to point to the new DPA repository.
    1. Open the file in a text editor.
      • Windows: DPA_install_dir\iwc\tomcat\ignite_config\idc
      • Linux: DPA_home/iwc/tomcat/ignite_config/idc
    2. Modify the following lines as needed:
  6. Start the DPA Server, and open the DPA interface.
    1. Ensure the server connects to the proper repository database.
    2. Review the status of monitors and start / stop accordingly.
    3. Review DPA log entries for obvious errors.
  7. Test to ensure the move is successful.
    1. Wait at least 10 minutes and drill into several databases.
    2. Does data for the last 10 minutes appear for all monitored databases?
  8. Connect to the old Repository Instance as a DBA user and remove the old repository:
    SQL> drop user DPA_username cascade
Last modified