Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > 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

Tags

Classifications

Public