beautypg.com

1 introduction, Repository features and interfaces, Chapter 1: introduction – HP Neoview Release 2.4 Software User Manual

Page 15

background image

1 Introduction

Repository Features and Interfaces

The Neoview Manageability Repository is a Neoview SQL database and set of programs that
automatically collect and store statistics and other information about the following entities on a
Neoview platform:

Queries initiated through ODBC and JDBC, including queries managed by Workload
Management Services (WMS). All query data is written to a single location and accessible
through two views, one of which holds the full SQL text. Certain data about queries is
available from the time the query starts; other data becomes available only after the query
is complete.

Processing nodes (CPUs). Information about processing nodes is collected from the Neoview
platform every five minutes.

Table statistics. Deprecated. This feature is off by default and no data is returned. Use the
Neoview Command Interface (NCI) automated Update Statistics feature to update histogram
statistics for tables.

Disks. Information about disk availability and performance is collected from the Neoview
platform and sent to the Repository every 5 minutes, by default.

Error and other events that are tracked in the Neoview event logs. A Repository view provides
access to the event data and you can use SQL queries to obtain information about a variety
of events occurring on the Neoview platform.

Space management. Repository views provide access to inventory data about table partitions
and aging historical data about table partitions.

Optional processes involved in query execution. Process statistics gathering is disabled by
default
, but if you enable this feature, the information is collected from the Neoview platform
processes started by a specific query (NDCS connectivity server process). Different views
provide access to information about individual processes and sets of processes of the same
type, for example all query execution processes started by a specific query (NDCS connectivity
server process). The Repository data collector process is also monitored. Aggregates for sets
of related processes are computed every five minutes with a 15-minute delay; thus, aggregate
data becomes available from the Repository 15 minutes after the end of the sampling interval.

Process collectors should not be turned on and left on for a long time because they place a
load on the platform. They should be turned off after the measurement period has completed.

NOTE:

As part of the retirement of the process statistics collectors, the collectors are not

installed nor configured on systems configured with Unicode characters sets.

The Repository is used to store historical information that the DBA can access to see patterns of
queries which were run on the Neoview platform. Some examples of the resource information
that can be obtained from the Repository includes:

Platform CPU (Node) usage by time (hourly, daily, and distribution by segment)

Platform disk space usage

Information on queries run by specific users, applications, client PCs, type of queries run at
which time, the number of queries run

More information and sample queries are available from within the Neoview Reports product.

Any database administrator (ROLE.DBA) can issue queries against the Repository, using Neoview
Command Interface or another standard SQL interface, and can grant other users access to the
Repository. Prepackaged queries are also available for display in the Neoview Reports tool,
described in the Neoview Reports Online Help.

Repository Features and Interfaces

15