EnterpriseDB: Add/Remove Cluster
Oracle Tips by
really rather that the people at EnterpriseDB had called this
"registering a cluster" rather than add and remove a cluster (Figure
6.3). This menu option does not actually add or remove a cluster
from your environment. It adds a cluster to this instance of the
DBA Management Server. When you add a cluster, the management
server will add a new tab to the home page and start tracking
available statistics for the cluster.
6.3: Add/Modify Cluster
want to start tracking statistics in a database in the existing
cluster, click the check box next to the database. If you do not
want to track statistics in a database, uncheck the box.
To add a
cluster to this instance of the DBA Management Server, choose
Configure New Cluster. Remember that you are not really adding
or changing a cluster anywhere. You are just telling the
management server to start tracking that cluster’s statistics.
Configure New Cluster dialog (Figure 6.4) will allow you to enter the
server name, port and database to track.
6.4: Configure Cluster
enter either text server name or an ip address. All fields are
required. Once you have entered the information, choose
Configure and you are taken back to the Add/Remove Cluster page.
verify that you have added the cluster and made your changes by
returning to the Home Page (under the Home menu option). You
should see a tab for each cluster that you've added and you should see
additional databases if you have added those (Figure 6.5).
6.5: Verify Cluster Changes
menu option is the Monitoring option. This is where you can get
a view of who is doing what in your database instance.
Activity page (Figure 6.6) will show you who is logged in and what
they are currently running. If you have turned on the
stats_command_string option (see below in Monitoring Configuration),
you will be able to see that actual command string. You can
configure some databases to log the command and others not to.
You may want to turn off command logging on heavy transaction
databases such as the MGMTSVR database.
6.6: Monitor User Activity
choose the database to monitor from the Database dropdown. You
can also turn off auto-refresh if you would like to refresh manually.
Status page (Figure 6.7) shows current database locks. Locks are
normally transient in EnterpriseDB (and PostgreSQL) due to the
superior locking mechanism in the database. It is not unusual
for this page to be empty.
6.7: Monitor Locks
Ironically, this report temporarily locks a critical system table.
You should only run this report when needed and you should probably
turn off Auto Refresh to prevent performance issues in the database.
Buffer Cache page (Figure 6.8) shows active hits on the memory area of
EnterpriseDB. You can get an idea about how your processes are
using data from this screen.
query behind this page also locks a critical system table so you
should only run it when needed.
6.8: Monitor Objects in Buffer Cache
about this page in detail in Chapter 2. See figure 2.5 and the
text around that figure.
re-iterate, these configuration options determine how much data the
management server gathers and saves for monitoring purposes.
Like all monitoring, there is always a downside. The more you
gather, the heavier the load on the system.
system (Figure 6.9), I have all of the monitoring options turned on.
This is not a production instance though. How you set your
instance is partially determined by how you will use it and what kind
of available resources you have.
6.9: Monitor Statistics Collection Configuration
is an excerpt from the book "EnterpriseDB:
The Definitive Reference" by Rampant TechPress.