Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2
RFC 1697
Network Working Group D. Brower, Editor
Request for Comments: 1697 The ASK Group, INGRES DBMS Development
Category: Standards Track B. Purvy, RDBMSMIB Working Group Chair
Oracle Corporation
A. Daniel
Informix Software, Inc.
M. Sinykin
J. Smith
Oracle Corporation
August 1994
Relational Database Management System (RDBMS)
Management Information Base (MIB) using SMIv2
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Table of Contents
1. Introduction .............................................. 1
2. The SNMPv2 Network Management Framework ................... 2
2.1 Object Definitions ....................................... 2
3. Overview .................................................. 2
3.1 Terminology .............................................. 3
3.2 Structure and Features ................................... 4
3.2.1 Tables ................................................. 4
3.2.2 Writable objects ....................................... 5
3.2.3 Traps .................................................. 5
4. Definitions ............................................... 6
5. Acknowledgements .......................................... 35
6. References ................................................ 36
7. Security Considerations ................................... 37
8. Authors' Addresses ........................................ 37
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing
relational database (RDBMS) implementations.
Brower, Purvy, Daniel, Sinykin & Smith [Page 1]
RFC 1697 RDBMS-MIB August 1994
2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
o RFC 1442 [1] which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
objects for the Internet suite of protocols.
o RFC 1445 [3] which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 [4] which defines the protocol used for network
access to managed objects.
o RFC 1443 [5] which describes textual conventions for the
framework.
The framework permits new objects to be defined for the purpose of
experimentation and evaluation. In particular, the RDBMS-MIB can be
seen as an extension of
o RFC 1565 [6] which defines the MIB for monitoring network
service applications.
2.1. Object Definitions
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to refer to the
object type.
3. Overview
The RDBMS-MIB contains objects that may be used to manage relational
database implementations. Specifically, it contains information on
installed databases, servers, and on the relation of databases and
servers. The terms used in this database are described below.
Brower, Purvy, Daniel, Sinykin & Smith [Page 2]
RFC 1697 RDBMS-MIB August 1994
3.1. Terminology
Vendors and Products
are providers of database systems on a host. These vendors
may have more than one database product that is manageable
through this MIB. On a host, there may be systems from
multiple vendors, multiple systems from a single vendor, or
any other combination. There may be a private MIB for each
Show full document text