Database Management

Divide existing DPA repositories

You can split the current DPA server into multiple servers.

First published date

10/31/2018 6:49 PM

Last published date

11/27/2023 9:46 PM

Overview

You can split the one DPA server into two servers by using the following steps. Reasons you might want to do this include:
  • The infrastructure resources supporting DPA (for example, storage availability, I/O throughput, RAM, and CPU) reach capacity as the volume of queries being analyzed increases.
  • Your monitored instances are distributed geographically, and the network lag time to distant instances is high. You can install separate DPA servers in each location.
  • You want to enable separate teams or business units to manage their subset of database instances.

The process involves backing up and restoring your current repository to a new one, and then removing half of the instances from each.

To view data from multiple DPA servers in a single interface, you can set up DPA Central. 

Product section

Database Performance Analyzer

Resolution

  1. Stop DPA monitors and shutdown DPA:
    1. Click Stop All Monitors on the DPA home page and verify all monitors stop.
    2. Shut down the Ignite PI Server Windows service to stop DPA.
  2. Make a backup of the current repository.
    • For a SQL Server repository, use the Backup/Restore tools.
    • For an Oracle repository, consider using export/import or data pump to make the backup.
  3. Restore the backup of the current repository.
    • For SQL Server, restore the backup to a new database in another instance.
    • For Oracle, create a new schema and restore export or data pump info into this new schema.
  4. Create a second DPA server.
    • For Windows you will need to install DPA onto a separate server.
    • For UNIX or Linux, you can use the same server, but create a second install directory. If you do this, you will need to configure that installation to use a different port.
  5. Create a DPA user for the restored database, or use an existing service account.
    • Make sure the new user is mapped to the DPA schema and has access to the new database.
    • Do not make it a SYSADMIN on SQL Server as that will not work properly.
  6. Copy and edit the repo.properties file from the current installation to the new one.
    • This file resides in installDir/iwc/tomcat/ignite_config/idc.
    • Adjust connection information as needed so it connects to the restored database.
  7. Determine which instances will be monitored in each DPA server, and remove the others.
    • To remove the instances, you can use Options > Unregister.
    • If you have many instances, contact Technical Support to get a script to help with this step.
  8. Start the original DPA server and start the monitors
    • Verify the correct instances are present in this installation.
  9. Start the new DPA server and start the monitors.
    • Verify the correct instances are present and the monitors are starting.