Wireless AP information not removed by Database Maintenance in NPM

5/13/2019 5:35 PM

10/31/2025 9:51 PM

This article describes an issue with Database maintenance unable to remove stale Wireless AP data causing database suspended processes and extended running SQL maintenance.

It's also important to understand that there are various reason why stale WAP information and accumulate in the database. Typically this is because of a change in how the WAP is being identified to the WC and how the WC stores and keeps track of the WAPs. When that information changes, changes in how the WAPs are indexed can be updated in the adatabase, creating new entries of WAP data, but not clearing out the old WAP data. Here are some reasons that might occur: 
 

1. Controller Reboot or Firmware Update: Sometimes, after a system reboot or firmware update, the order in which WAPs register with the controller can change, potentially leading to a change in their identifiers, especially if the identifiers are dynamically assigned.

2. WAP Replacement: If a WAP is replaced, the new WAP will have a different MAC address and, consequently, a different identifier in the system.

3. Network Topology Changes: Changes in the network topology, such as adding a new subnet or VLAN, might cause WAPs to re-register with the controller, potentially affecting their identifiers.

4. Controller Configuration Reset: If the controller's configuration is reset to default settings, WAP identifiers might be reinitialized.

5. Manual Reconfiguration: Administrators can sometimes manually change the identifier or name assigned to a WAP within the controller's interface.

6. Adding New WAPs: When new WAPs are added to the network, depending on how identifiers are assigned, this might cause a reordering or re-indexing of existing WAPs.

7. Dynamic Assignment: If the controller assigns identifiers dynamically based on the order WAPs connect, then any event causing WAPs to reconnect (e.g., power outages, network disruptions) might change the order and thus their identifiers.

Network Performance Monitor

These Issues seem to be caused by low performance on SQL server and numerous Wireless entities.

Open SSMS

1. Open or download SQL Management Studio: SQL Management Studio Direct Download Link
2. Login to SQL Management Studio with an 'sa' type.
3. If the Database Maintenance is currently running, find the 'dbmaintenance.exe' procedure 'spid' 
   • Kill the process

Option 1

1. Navigate to Stored Procedures under [DatabaseName] --> Programmability --> Stored Procedures
2. right-click the [dbo].[Wireless_DeleteStale] and select 'Modify'
3. Find '@chunksize = 10000' Change to '@chunksize = 5000'
4. Click 'Execute query' button in top row menu bar only not in File menu bar
5. Run database maintenance utility manually or wait till normal maintenance runs as scheduled

Option 2

1. Or you can change/execute the following query on the procedure by right-clicking the procedure and selecting 'new query' then executing:

   -- Scripts are not supported under any SolarWinds support program or service.
   -- Scripts are provided AS IS without warranty of any kind. SolarWinds further
   -- disclaims all warranties including, without limitation, any implied warranties
   -- of merchantability or of fitness for a particular purpose. The risk arising
   -- out of the use or performance of the scripts and documentation stays with you.
   -- In no event shall SolarWinds or anyone else involved in the creation,
   -- production, or delivery of the scripts be liable for any damages whatsoever
   -- (including, without limitation, damages for loss of business profits, business
   -- interruption, loss of business information, or other pecuniary loss) arising
   -- out of the use of or inability to use the scripts or documentation.
   
   DECLARE @ChunkSize as Int 
    Set @ChunkSize = 5000

2. Run database maintenance utility manually or wait till normal maintenance runs as scheduled

** Maintenance may run longer than normal the first time but should be back to normal after that