Allocate or deallocate DPA licenses
If your DPA server uses individual licenses, a license must be allocated to each registered database instance that you want to monitor. DPA starts monitoring new instances immediately after licenses are allocated.
If your DPA server is deployed in the Amazon Web Services (AWS) Marketplace, DPA uses the AWS Marketplace Metering Service to calculate charges. You do not need to purchase, activate, or allocate individual licenses.
Category 1, Category 2, and Azure SQL Database licenses collect the data shown in the Performance view. VM licenses collect the data shown in the Virtualization view.
Automatic license allocation
When you register a database instance or activate a license, DPA determines if it can automatically allocate a license to each database instance. DPA automatically allocates licenses if there are enough activated licenses to cover all of the database instances in that license category. DPA automatically allocates VM licenses if there are enough VM licenses to cover all database instances that:
- Are linked to a VM
- Have been allocated a Category 1 or 2 license
If you have not activated enough licenses to cover all instances that require that license type, DPA does not allocate any of the licenses. You must manually allocate licenses to the database instances you want to monitor.
Example 1:
- You register 10 Oracle Enterprise Edition database instances, which require Category 1 licenses.
-
You activate 15 Category 1 licenses.
Result: DPA automatically allocates 10 of the licenses to the Oracle Enterprise Edition database instances.
-
You register 5 additional Oracle Enterprise Edition database instances.
Result: DPA automatically allocates the remaining 5 Category 1 licenses.
Example 2:
- You register 15 MySQL database instances, which require Category 2 (or greater) licenses.
-
You activate 10 Category 2 licenses. No Category 1 licenses are available.
Result: DPA does not allocate any of the licenses. You can either activate at least 5 additional licenses, or manually allocate licenses to the instances you want to monitor.
Instances without a license allocated to them remain registered with DPA, and you can view performance data that was collected in the past. You can deallocate a license from one registered instance and allocate it to another if necessary.
Manually allocate licenses to database instances
Use License Allocation to configure how your licenses are allocated to database instances.
View current license allocation
- On the DPA home page, click License Management.
- See the current license allocations in the summary boxes near the top of the License Allocation page.
Allocate licenses to database instances
- On the License Allocation page, find the database instance you want in the list of registered database instances.
- Select the Cat 1, Cat 2, or Azure checkbox next to the instance.
-
Click Save.
The license count is updated after you allocate a license.
Allocate VM licenses to VM database instances
If a database instance runs on a virtual machine (VM), you can allocate a VM license to it in addition to a Category 1 or 2 license. When you allocate a VM license, DPA collects performance metrics from the VMware system (vCenter Server or ESX/ESXi Host) on which the database instance runs.
- On the License Allocation page, locate a VM-hosted database instance that has a Category 1 or 2 license allocated to it.
- Select the VM checkbox next to the instance.
- Click Save.
If you are monitoring a database instance that runs in a virtual machine (VM) cluster, a user with at least read-only permissions is required on the hosts and VMs that will be monitored.
Deallocate licenses
You can deallocate the license from one database instance to make it available to another database instance.
- On the DPA home page, click License Management.
-
Clear the Cat 1, Cat 2, or Azure checkbox to deallocate licenses.
If you clear a Category 1 or 2 license from an instance that also has a VM license, DPA automatically clears the VM license as well.
Learn more
For more information about licensing, see the following topics: