Documentation forDatabase Performance Analyzer

Register a virtual machine and view performance data

When a database instance runs on a virtual machine, you can register the VM in addition to the database instance. When you register a VM, you can view performance metrics from the VM, the physical host, and the storage system. DPA displays metrics from all these layers of infrastructure on a single screen. You can use this data to correlate events in the underlying layers with performance issues in the database instance.

Monitoring a VM requires a VM license.

Register a VM

  1. Near the top left of the DPA homepage, click Register VMware for Monitoring.
  2. Enter the connection credentials for a VMware ESX/ESXi Host or a vCenter Server.
  3. Click Register.

    In most cases, DPA automatically detects the database instances running on the virtual machine. On the DPA homepage, the VM icon is displayed in the Type column.

Manually link a database instance to a VM

If DPA does not automatically associate a database instance with the VM that it runs on, you can manually link it.

  1. On the DPA homepage, click the Action menu to the right of the database instance name.
  2. Select Link to Virtual Machine.
  3. Select the virtual machine and click Link.
  4. Click Yes at the confirmation message, and then click OK.

    The database instance is listed under Running in a VM, and the VM icon is displayed in the Type column.

View VM performance data

After you register a VM, you can view recent performance data immediately. DPA must gather data for a few days before it shows performance trends and baselines.

If the trial period is over, you must allocate a VM license to the database instance before you can view VM performance data.

  1. At the top of the DPA homepage, click Virtualization.
  2. In the Database Instance list, click a database instance.

    DPA shows performance data from the database instance followed by metrics from the VM, the physical host, and the storage layer. Use these graphs to correlate waits in the database instance with events in the underlying layers.