Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > Database activation and deactivation in DB2

Database activation and deactivation in DB2

Table of contents

Overview

This article provides information on database activation and deactivation in DB2.

Environment

  • All versions of DPA

Detail

DPA uses DB Snapshot Monitor to retrieve information about the database. The Snapshot Monitor contains data obtained from the system monitor. According to the DB2 documentation:

The system monitor accumulates information for a database only while it is active. If all applications disconnect from a database and the database deactivates, then the system monitor data for that database is no longer available. You can keep the database active until your final snapshot has been taken, either by starting the database with the ACTIVATE DATABASE command, or by maintaining a permanent connection to the database.

 

If a database deactivates and the system monitor is no longer available, DPA is unable to accurately determine statistics for that DB2 database. The following error appears when DPA has detected one or more databases deactivated: 

 

These statistics may be inaccurate as this DB2 instance has databases that have been deactivated.

 

If you would like to reset the list of deactivated databases that Ignite has detected, you can run the following delete command:

 

delete from CON_MSSQL_DB
where COND_ID = (select ID
                 from COND 
                 where NAME = 'name'
                 and DB_TYPE = 'DB2')

Last modified
19:08, 22 Jun 2016

Tags

Classifications

Public