Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.0 Administrator Guide > DPA licensing > Troubleshoot over-allocated licenses

Troubleshoot over-allocated licenses

Table of contents
No headers
Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Sep 15, 2016

Views: 29 Votes: 0 Revisions: 5

A red banner displays on the home page if SolarWinds DPA is monitoring more registered database instances than you have licenses to monitor. This can happen in two situations:

  • A license expires when you have unexpired licenses of the same type on the server.
  • You deactivate a license and have other licenses of the same type on the server.

If SolarWinds DPA licenses are over-allocated, you cannot view or analyze your database instances until you deallocate the extra licenses. SolarWinds DPA continues monitoring the databases, so you will not lose data while you bring the allocated licenses to an allowable level.

To correct an issue of over-allocated licenses, deallocate database instances until you reach the proper number of licenses. If Category 2 licenses are over-allocated, assign available Category 1 licenses to cover the shortage. If Azure SQL Database licenses are over-allocated, assign Category 1 or 2 licenses to cover the shortage.

  1. On the DPA home page, click License Management.
  2. Locate the over-allocated license type on the allocations chart. Over-allocated license types are shown in red.
  3. Clear Cat 1, Cat 2, Azure, or VM check boxes until the chart is no longer red.
  4. Click Save.

    You should now see your database instances in your views.

Last modified
13:50, 15 Sep 2016

Tags

Classifications

Public