smilint output for ./RDBMS-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 2 |
| error | 6 |
| minor error | 1 |
| change recommended | 7 |
| warning | 18 |
| Message Types |
|---|
| Type | Count |
|---|
| group-membership (change recommended) | 7 |
| import-failed (error) | 3 |
| import-unused (warning) | 1 |
| index-exceeds-too-large (warning) | 2 |
| integer-misuse (warning) | 11 |
| macro-not-imported (error) | 3 |
| notification-not-reversible (warning) | 2 |
| object-identifier-unknown (severe) | 2 |
| obsolete-import (warning) | 1 |
| revision-missing (minor error) | 1 |
| sequence-order (warning) | 1 |
Messages:
RDBMS-MIB
1: -- extracted from rfc1697.txt
2: -- at Mon Nov 15 17:11:51 1999
3:
4: RDBMS-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
8: Counter32, Gauge32, Integer32
8: warning -
warning: identifier `Integer32' imported from module `SNMPv2-SMI' is never used
9: FROM SNMPv2-SMI
10: DisplayString, DateAndTime, AutonomousType
11: FROM SNMPv2-TC
12: applIndex, applGroup
13: FROM APPLICATION-MIB
13: error -
identifier `applIndex' cannot be imported from module `APPLICATION-MIB'
13: error -
identifier `applGroup' cannot be imported from module `APPLICATION-MIB'
14: mib-2
14: warning -
warning: identifier `mib-2' should be imported from `SNMPv2-SMI' instead of `RFC1213-MIB'
15: FROM RFC1213-MIB;
16:
17: rdbmsMIB MODULE-IDENTITY
18: LAST-UPDATED "9406150655Z"
19: ORGANIZATION "IETF RDBMSMIB Working Group"
20: CONTACT-INFO
21: " David Brower
22:
23: Postal: The ASK Group, INGRES DBMS Development
24: 1080 Marina Village Parkway
25: Alameda, CA 94501
26: US
27:
28: Tel: +1 510 748 3418
29: Fax: +1 510 748 2770
30:
31: E-mail: daveb@ingres.com"
32: DESCRIPTION
33: "The MIB module to describe objects for generic relational
34: databases."
35:
36: ::= { mib-2 39 }
36: minor error -
revision for last update is missing
37:
38: rdbmsObjects OBJECT IDENTIFIER ::= { rdbmsMIB 1 }
39:
40: ----------------------------------------------------------------
41:
42: rdbmsDbTable OBJECT-TYPE
43: SYNTAX SEQUENCE OF RdbmsDbEntry
44: MAX-ACCESS not-accessible
45: STATUS current
46: DESCRIPTION
47: "The table of databases installed on a system."
48: ::= { rdbmsObjects 1 }
49:
50: rdbmsDbEntry OBJECT-TYPE
51: SYNTAX RdbmsDbEntry
52: MAX-ACCESS not-accessible
53: STATUS current
54: DESCRIPTION
55: "An entry for a single database on the host. Whether a
56: particular database is represented by a row in rdbmsDbTable
57: may be dependent on the activity level of that database,
58: according to the product's implementation. An instance of
59: rdbmsRelState having the value active, other, or restricted
60: implies that an entry, corresponding to that instance, will
61: be present."
62: INDEX { rdbmsDbIndex }
63: ::= { rdbmsDbTable 1 }
64:
65: RdbmsDbEntry ::=
66: SEQUENCE {
67: rdbmsDbIndex INTEGER,
68: rdbmsDbPrivateMibOID OBJECT IDENTIFIER,
69: rdbmsDbVendorName DisplayString,
70: rdbmsDbName DisplayString,
71: rdbmsDbContact DisplayString
72: }
73:
74: rdbmsDbIndex OBJECT-TYPE
75: SYNTAX INTEGER (1..2147483647)
75: warning -
warning: use Integer32 instead of INTEGER in SMIv2
76: MAX-ACCESS not-accessible
77: STATUS current
78: DESCRIPTION
79: "A numeric index, unique among all the databases from all
80: products on this host. This value is a surrogate for the
81: conceptually unique key, which is {PrivateMibOID,
82: databasename}"
83: ::= { rdbmsDbEntry 1 }
84:
85: rdbmsDbPrivateMibOID OBJECT-TYPE
86: SYNTAX OBJECT IDENTIFIER
87: MAX-ACCESS read-only
88: STATUS current
89: DESCRIPTION
90: "The authoritative identification for the private MIB for
91: this database, presumably based on the vendor, e.g., {
92: enterprises 111 <optional subidentifiers>} for Oracle
93: databases, {enterprises 757 <optional subidentifiers>} for
94: Ingres databases, { enterprises 897 <optional
95: subidentifiers>} for Sybase databases, etc.
96:
97: If no OBJECT IDENTIFIER exists for the private MIB, attempts
98: to access this object will return noSuchName (SNMPv1)
99: or noSuchInstance (SNMPv2)."
100: ::= { rdbmsDbEntry 2 }
101:
102: rdbmsDbVendorName OBJECT-TYPE
103: SYNTAX DisplayString
104: MAX-ACCESS read-only
105: STATUS current
106: DESCRIPTION
107: "The name of the vendor whose RDBMS manages this database,
108: for informational purposes."
109: ::= { rdbmsDbEntry 3 }
110:
111: rdbmsDbName OBJECT-TYPE
112: SYNTAX DisplayString
113: MAX-ACCESS read-only
114: STATUS current
115: DESCRIPTION
116: "The name of this database, in a product specific format. The
117: product may need to qualify the name in some way to resolve
118: conflicts if it is possible for a database name to be
119: duplicated on a host. It might be necessary to construct a
120: hierarchical name embedding the RDBMS instance/installation
121: on the host, and/or the owner of the database. For instance,
122: '/test-installation/database-owner/database-name'."
123: ::= { rdbmsDbEntry 4 }
124:
125: rdbmsDbContact OBJECT-TYPE
126: SYNTAX DisplayString
127: MAX-ACCESS read-write
128: STATUS current
129: DESCRIPTION
130: "The textual identification of the contact person for this
131: managed database, together with information on how to contact
132: this person.
133:
134: Note: if there is no server associated with this database, an
135: agent may need to keep this in other persistent storage,
136: e.g., a configuration file.
137:
138: Note that a compliant agent does not need to
139: allow write access to this object."
140:
141: ::= { rdbmsDbEntry 5 }
142:
143: ----------------------------------------------------------------
144:
145: rdbmsDbInfoTable OBJECT-TYPE
146: SYNTAX SEQUENCE OF RdbmsDbInfoEntry
147: MAX-ACCESS not-accessible
148: STATUS current
149: DESCRIPTION
150: "The table of additional information about databases present
151: on the host."
152: ::= { rdbmsObjects 2 }
153:
154: rdbmsDbInfoEntry OBJECT-TYPE
155: SYNTAX RdbmsDbInfoEntry
156: MAX-ACCESS not-accessible
157: STATUS current
158: DESCRIPTION
159: "Information that must be present if the database is actively
160: opened. If the database is not actively opened, then
161: attempts to access corresponding instances in this table may
162: result in either noSuchName (SNMPv1) or noSuchInstance
163: (SNMPv2). 'Actively opened' means at least one of the
164: rdbmsRelState entries for this database in the rdbmsRelTable
165: is active(2)."
166: INDEX { rdbmsDbIndex }
167: ::= { rdbmsDbInfoTable 1 }
168:
169: RdbmsDbInfoEntry ::=
170: SEQUENCE {
171: rdbmsDbInfoProductName DisplayString,
172: rdbmsDbInfoVersion DisplayString,
173: rdbmsDbInfoSizeUnits INTEGER,
174: rdbmsDbInfoSizeAllocated INTEGER,
175: rdbmsDbInfoSizeUsed INTEGER,
176: rdbmsDbInfoLastBackup DateAndTime
177: }
178:
179: rdbmsDbInfoProductName OBJECT-TYPE
180: SYNTAX DisplayString
181: MAX-ACCESS read-only
182: STATUS current
183: DESCRIPTION
184: "The textual product name of the server that created or last
185: restructured this database. The format is product specific."
186: ::= { rdbmsDbInfoEntry 1 }
187:
188: rdbmsDbInfoVersion OBJECT-TYPE
189: SYNTAX DisplayString
190: MAX-ACCESS read-only
191: STATUS current
192: DESCRIPTION
193: "The version number of the server that created or last
194: restructured this database. The format is product specific."
195: ::= { rdbmsDbInfoEntry 2 }
196:
197: rdbmsDbInfoSizeUnits OBJECT-TYPE
198: SYNTAX INTEGER {
199: bytes(1),
200: kbytes(2),
201: mbytes(3),
202: gbytes(4),
203: tbytes(5)
204: }
205: MAX-ACCESS read-only
206: STATUS current
207: DESCRIPTION
208: "Identification of the units used to measure the size of this
209: database in rdbmsDbInfoSizeAllocated and rdbmsDbInfoSizeUsed.
210: bytes(1) indicates individual bytes, kbytes(2) indicates
211: units of kilobytes, mbytes(3) indicates units of megabytes,
212: gbytes(4) indicates units of gigabytes, and tbytes(5)
213: indicates units of terabytes. All are binary multiples -- 1K
214: = 1024. If writable, changes here are reflected in the get
215: values of the associated objects."
216:
217: ::= { rdbmsDbInfoEntry 3 }
218:
219: rdbmsDbInfoSizeAllocated OBJECT-TYPE
220: SYNTAX INTEGER (1..2147483647)
220: warning -
warning: use Integer32 instead of INTEGER in SMIv2
221: MAX-ACCESS read-write
222: STATUS current
223: DESCRIPTION
224: "The estimated size of this database (in
225: rdbmsDbInfoSizeUnits), which is the disk space that has been
226: allocated to it and is no longer available to users on this
227: host. rdbmsDbInfoSize does not necessarily indicate the
228: amount of space actually in use for database data. Some
229: databases may support extending allocated size, and others
230: may not.
231:
232: Note that a compliant agent does not need to
233: allow write access to this object."
234:
235: -- Note: computing SizeAllocated may be expensive, and SNMP
236: -- agents might cache the value to increase performance.
237:
238: ::= { rdbmsDbInfoEntry 4 }
239:
240: rdbmsDbInfoSizeUsed OBJECT-TYPE
241: SYNTAX INTEGER (1..2147483647)
241: warning -
warning: use Integer32 instead of INTEGER in SMIv2
242: MAX-ACCESS read-only
243: STATUS current
244: DESCRIPTION
245: "The estimated size of this database, in rdbmsDbInfoSizeUnits,
246: which is actually in use for database data."
247:
248: -- Note: computing SizeUsed may be expensive, and SNMP
249: -- agents might cache the value to increase performance.
250: ::= { rdbmsDbInfoEntry 5 }
251:
252: rdbmsDbInfoLastBackup OBJECT-TYPE
253: SYNTAX DateAndTime
254: MAX-ACCESS read-only
255: STATUS current
256: DESCRIPTION
257: "The date and time that the latest complete or partial backup
258: of the database was taken. If a database has never been
259: backed up, then attempts to access this object will
260: result in either noSuchName (SNMPv1) or noSuchInstance
261: (SNMPv2)."
262: ::= { rdbmsDbInfoEntry 6 }
263:
264: ----------------------------------------------------------------
265:
266: rdbmsDbParamTable OBJECT-TYPE
267: SYNTAX SEQUENCE OF RdbmsDbParamEntry
268: MAX-ACCESS not-accessible
269: STATUS current
270: DESCRIPTION
271: "The table of configuration parameters for a database.
272: Entries should be populated according to the following
273: guidelines:
274: (1) The value should be specified through administrative
275: (human) intervention.
276: (2) It should be configured on a per-database basis.
277: (3) One of the following is true:
278: (a) The parameter has a non-numeric value;
279: (b) The current value is numeric, but it only changes due
280: to human intervention;
281: (c) The current value is numeric and dynamic, but the
282: RDBMS does not track access/allocation failures
283: related to the parameter;
284: (d) The current value is numeric and dynamic, the
285: RDBMS tracks changes in access/allocation failures
286: related to the parameter, but the failure has no
287: significant impact on RDBMS performance or
288: availability.
289: (e) The current value is numeric and dynamic, the
290: RDBMS tracks changes in access/allocation failures
291: related to the parameter, the failure has
292: significant impact on RDBMS performance or
293: availability, and is shown in the
294: rdbmsDbLimitedResource table."
295: ::= { rdbmsObjects 3 }
296:
297: rdbmsDbParamEntry OBJECT-TYPE
298: SYNTAX RdbmsDbParamEntry
299: MAX-ACCESS not-accessible
300: STATUS current
301: DESCRIPTION
302: "An entry for a single configuration parameter for a database.
303: Parameters with single values have a subindex value of one.
304: If the parameter is naturally considered to contain a
305: variable number of members of a class, e.g. members of the
306: DBA user group, or files which are part of the database, then
307: it must be presented as a set of rows. If, on the other
308: hand, the parameter represents a set of choices from a class,
309: e.g. the permissions on a file or the options chosen out of
310: the set of all options allowed, AND is guaranteed to always
311: fit in the 255 character length of a DisplayString, then it
312: may be presented as a comma separated list with a subindex
313: value of one. Zero may not be used as a subindex value.
314:
315: If the database is not actively opened, then attempts
316: to access corresponding instances in this table may result in
317: either noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
318: 'Actively opened' means at least one of the
319: rdbmsRelState entries for this database in the rdbmsRelTable
320: is active(2)."
321: INDEX { rdbmsDbIndex, rdbmsDbParamName, rdbmsDbParamSubIndex }
322: ::= { rdbmsDbParamTable 1 }
323:
324: RdbmsDbParamEntry ::=
325: SEQUENCE {
326: rdbmsDbParamName DisplayString,
327: rdbmsDbParamSubIndex INTEGER,
328: rdbmsDbParamID AutonomousType,
329: rdbmsDbParamCurrValue DisplayString,
330: rdbmsDbParamComment DisplayString
331: }
332:
333: rdbmsDbParamName OBJECT-TYPE
334: SYNTAX DisplayString (SIZE (1..64))
335: MAX-ACCESS not-accessible
336: STATUS current
337: DESCRIPTION
338: "The name of a configuration parameter for a database. This
339: name is product-specific. The length is limited to 64
340: characters to constrain the number of sub-identifiers needed
341: for instance identification (and to minimize network
342: traffic)."
343:
344: ::= { rdbmsDbParamEntry 1 }
345:
346: rdbmsDbParamSubIndex OBJECT-TYPE
347: SYNTAX INTEGER (1..2147483647)
347: warning -
warning: use Integer32 instead of INTEGER in SMIv2
348: MAX-ACCESS not-accessible
349: STATUS current
350: DESCRIPTION
351: "The subindex value for this parameter. If the parameter is
352: naturally considered to contain a variable number of members
353: of a class, e.g. members of the DBA user group, or files
354: which are part of the database, then it must be presented as
355: a set of rows. If, on the other hand, the parameter
356: represents a set of choices from a class, e.g. the
357: permissions on a file or the options chosen out of the set of
358: all options allowed, AND is guaranteed to always fit in the
359: 255 character length of a DisplayString, then it may be
360: presented as a comma separated list with a subindex value of
361: one. Zero may not be used as a value."
362: ::= { rdbmsDbParamEntry 2 }
363:
364: rdbmsDbParamID OBJECT-TYPE
364: change recommended -
warning: node `rdbmsDbParamID' must be contained in at least one conformance group
365: SYNTAX AutonomousType
366: MAX-ACCESS read-only
367: STATUS current
368: DESCRIPTION
369: "The ID of the parameter which may be described in some other
370: MIB (e.g., an enterprise-specific MIB module). If there is
371: no ID for this rdbmsDbParamName, attempts to access this
372: object will return noSuchName (SNMPv1) or noSuchInstance
373: (SNMPv2)."
374: ::= { rdbmsDbParamEntry 3 }
375:
376: rdbmsDbParamCurrValue OBJECT-TYPE
377: SYNTAX DisplayString
378: MAX-ACCESS read-write
379: STATUS current
380: DESCRIPTION
381: "The value for a configuration parameter now in effect, the
382: actual setting for the database. While there may multiple
383: values in the temporal domain of interest (for instance, the
384: value to take effect at the next restart), this is the
385: current setting.
386:
387: Note that a compliant agent does not need to
388: allow write access to this object."
389:
390: ::= { rdbmsDbParamEntry 4 }
391:
392: rdbmsDbParamComment OBJECT-TYPE
393: SYNTAX DisplayString
394: MAX-ACCESS read-write
395: STATUS current
396: DESCRIPTION
397: "Annotation which describes the purpose of a configuration
398: parameter or the reason for a particular parameter's
399: setting.
400:
401: Note that a compliant agent does not need to
402: allow write access to this object."
403:
404: ::= { rdbmsDbParamEntry 5 }
405:
406: ----------------------------------------------------------------
407:
408: rdbmsDbLimitedResourceTable OBJECT-TYPE
409: SYNTAX SEQUENCE OF RdbmsDbLimitedResourceEntry
410: MAX-ACCESS not-accessible
411: STATUS current
412: DESCRIPTION
413: "The table of limited resources that are kept per-database."
414: ::= { rdbmsObjects 4 }
415:
416: rdbmsDbLimitedResourceEntry OBJECT-TYPE
416: warning -
warning: index of row `rdbmsDbLimitedResourceEntry' can exceed OID size limit by 140 subidentifier(s)
417: SYNTAX RdbmsDbLimitedResourceEntry
418: MAX-ACCESS not-accessible
419: STATUS current
420: DESCRIPTION
421: "An entry for a single limited resource kept per-database.
422: A limited resource has maximum use determined by a parameter
423: that might or might not be changeable at run time, or visible
424: in the rdbmsDbParamTable. Examples would be the number of
425: available locks, or disk space on a partition. Arrays of
426: resources are supported through an integer sub index, which
427: should have the value of one for single-instance names.
428:
429: Limited resources that are shared across databases, are best
430: put in the rdbmsSvrLimitedResourceTable instead of this one.
431: If the database is not actively opened, then attempts to
432: access corresponding instances in this table may result in
433: either noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
434: 'Actively opened' means at least one of the rdbmsRelState
435: entries for this database in the rdbmsRelTable is active(2)."
436:
437: INDEX { rdbmsDbIndex, rdbmsDbLimitedResourceName }
438: ::= { rdbmsDbLimitedResourceTable 1 }
439:
440: RdbmsDbLimitedResourceEntry ::=
441: SEQUENCE {
442: rdbmsDbLimitedResourceName DisplayString,
443: rdbmsDbLimitedResourceID AutonomousType,
444: rdbmsDbLimitedResourceLimit INTEGER,
445: rdbmsDbLimitedResourceCurrent INTEGER,
446: rdbmsDbLimitedResourceHighwater INTEGER,
447: rdbmsDbLimitedResourceFailures Counter32,
448: rdbmsDbLimitedResourceDescription DisplayString
449: }
450:
451: rdbmsDbLimitedResourceName OBJECT-TYPE
452: SYNTAX DisplayString
453: MAX-ACCESS not-accessible
454: STATUS current
455: DESCRIPTION
456: "The name of the resource, for instance 'global locks' or
457: 'locks for the FOO database', or 'data space on /dev/rdsk/5s0
458: for FOO'. The length is limited to 64 characters to constrain
459: the number of sub-identifiers needed for instance
460: identification (and to minimize network traffic)."
461: ::= { rdbmsDbLimitedResourceEntry 1 }
462:
463: rdbmsDbLimitedResourceID OBJECT-TYPE
463: change recommended -
warning: node `rdbmsDbLimitedResourceID' must be contained in at least one conformance group
464: SYNTAX AutonomousType
465: MAX-ACCESS read-only
466: STATUS current
467: DESCRIPTION
468: "The ID of the resource which may be described in some other
469: MIB (e.g., an enterprise-specific MIB module). If there is
470: no ID for this rdbmsDbLimitedResourceName, attempts to access
471: this object will return noSuchName (SNMPv1) or noSuchInstance
472: (SNMPv2)."
473: ::= { rdbmsDbLimitedResourceEntry 2 }
474:
475: rdbmsDbLimitedResourceLimit OBJECT-TYPE
476: SYNTAX INTEGER (1..2147483647)
476: warning -
warning: use Integer32 instead of INTEGER in SMIv2
477: MAX-ACCESS read-write
478: STATUS current
479: DESCRIPTION
480: "The maximum value the resource use may attain.
481:
482: Note that a compliant agent does not need to
483: allow write access to this object."
484:
485: ::= { rdbmsDbLimitedResourceEntry 3 }
486:
487: rdbmsDbLimitedResourceCurrent OBJECT-TYPE
488: SYNTAX INTEGER (1..2147483647)
488: warning -
warning: use Integer32 instead of INTEGER in SMIv2
489: MAX-ACCESS read-only
490: STATUS current
491: DESCRIPTION
492: "The current value for the resource."
493: ::= { rdbmsDbLimitedResourceEntry 4 }
494:
495: rdbmsDbLimitedResourceHighwater OBJECT-TYPE
496: SYNTAX INTEGER (1..2147483647)
496: warning -
warning: use Integer32 instead of INTEGER in SMIv2
497: MAX-ACCESS read-only
498: STATUS current
499: DESCRIPTION
500: "The maximum value of the resource seen since applUpTime
501: was reset for the earliest server which has the database
502: actively opened.
503:
504: If there are two servers with the database open, and the
505: oldest one dies, the proper way to invalidate the value is by
506: resetting sysUpTime."
507: ::= { rdbmsDbLimitedResourceEntry 5 }
508:
509: rdbmsDbLimitedResourceFailures OBJECT-TYPE
510: SYNTAX Counter32
511: MAX-ACCESS read-only
512: STATUS current
513: DESCRIPTION
514: "The number of times the system wanted to exceed the limit of
515: the resource since applUpTime was reset for the earliest
516: server which has the database actively opened.
517:
518: If there are two servers with the DB open, and the
519: oldest one dies, the proper way to invalidate the value is by
520: resetting sysUpTime."
521: ::= { rdbmsDbLimitedResourceEntry 6 }
522:
523: rdbmsDbLimitedResourceDescription OBJECT-TYPE
524: SYNTAX DisplayString
525: MAX-ACCESS read-write
526: STATUS current
527: DESCRIPTION
528: "A description of the resource and the meaning of the integer
529: units used for Limit, Current, and Highwater.
530:
531: Note that a compliant agent does not need to
532: allow write access to this object."
533:
534: ::= { rdbmsDbLimitedResourceEntry 7 }
535:
536: ----------------------------------------------------------------
537:
538: rdbmsSrvTable OBJECT-TYPE
539: SYNTAX SEQUENCE OF RdbmsSrvEntry
540: MAX-ACCESS not-accessible
541: STATUS current
542: DESCRIPTION
543: "The table of database servers running or installed
544: on a system."
545: ::= { rdbmsObjects 5 }
546:
547: rdbmsSrvEntry OBJECT-TYPE
548: SYNTAX RdbmsSrvEntry
549: MAX-ACCESS not-accessible
550: STATUS current
551: DESCRIPTION
552: "An entry for a single database server. A server is an
553: independent entity that provides access to one or more
554: databases. Failure of one does not affect access to
555: databases through any other servers. There might be one or
556: more servers providing access to a database. A server may be
557: a 'process' or collection of 'processes', as interpreted by
558: the product."
559: INDEX { applIndex }
559: severe -
unknown object identifier label `applIndex'
560: ::= { rdbmsSrvTable 1 }
561:
562: RdbmsSrvEntry ::=
563: SEQUENCE {
564: rdbmsSrvPrivateMibOID OBJECT IDENTIFIER,
565: rdbmsSrvVendorName DisplayString,
566: rdbmsSrvProductName DisplayString,
567: rdbmsSrvContact DisplayString
568: }
569:
570: rdbmsSrvPrivateMibOID OBJECT-TYPE
571: SYNTAX OBJECT IDENTIFIER
572: MAX-ACCESS read-only
573: STATUS current
574: DESCRIPTION
575: "The authoritative identification for the private MIB for this
576: server, presumably based on the vendor, e.g., { enterprises
577: 111 <optional subidentifiers>} for Oracle servers, {
578: enterprises 757 <optional subidentifiers>} for Ingres
579: servers, { enterprises 897 <optional subidentifiers>} for
580: Sybase servers, etc.
581:
582: If no OBJECT IDENTIFIER exists for the private MIB, attempts
583: to access this object will return noSuchName (SNMPv1)
584: or noSuchInstance (SNMPv2)."
585: ::= { rdbmsSrvEntry 1 }
586:
587: rdbmsSrvVendorName OBJECT-TYPE
588: SYNTAX DisplayString
589: MAX-ACCESS read-only
590: STATUS current
591: DESCRIPTION
592: "The name of the vendor whose RDBMS manages this database,
593: for informational purposes."
594: ::= { rdbmsSrvEntry 2 }
595:
596: rdbmsSrvProductName OBJECT-TYPE
597: SYNTAX DisplayString
598: MAX-ACCESS read-only
599: STATUS current
600: DESCRIPTION
601: "The product name of this server. This is normally the
602: vendor's formal name for the product, in product specific
603: format."
604: ::= { rdbmsSrvEntry 3 }
605:
606: rdbmsSrvContact OBJECT-TYPE
607: SYNTAX DisplayString
608: MAX-ACCESS read-write
609: STATUS current
610: DESCRIPTION
611: "The textual identification of the contact person for this
612: managed server, together with information on how to contact
613: this person.
614:
615: Note: if there is no active server associated with this
616: object, an agent may need to keep this in other persistent
617: storage, e.g., a configuration file.
618:
619: Note that a compliant agent does not need to
620: allow write access to this object."
621:
622: ::= { rdbmsSrvEntry 4 }
623:
624: ----------------------------------------------------------------
625:
626: rdbmsSrvInfoTable OBJECT-TYPE
627: SYNTAX SEQUENCE OF RdbmsSrvInfoEntry
628: MAX-ACCESS not-accessible
629: STATUS current
630: DESCRIPTION
631: "The table of additional information about database servers.
632:
633: Entries in this table correspond to applications in the
634: APPLICATION-MIB applTable. Some objects in that table are
635: application-specific. When they are associated with an RDBMS
636: server in this table, the objects have the following
637: meanings.
638:
639: applName - The name of this server, i.e., the process or
640: group of processes providing access to this database. The
641: exact format will be product and host specific.
642:
643: applVersion - The version number of this server, in product
644: specific format.
645:
646: applOperStatus - up(1) means operational and available for
647: general use. down(2) means the server is not available for
648: use, but is known to the agent. The other states have broad
649: meaning, and may need to be supplemented by the vendor
650: private MIB. Halted(3) implies an administrative state of
651: unavailability. Congested(4) implies a resource or or
652: administrative limit is prohibiting new inbound associations.
653: The 'available soon' description of restarting(5) may include
654: an indeterminate amount of recovery.
655:
656: applLastChange is the time the agent noticed the most recent
657: change to applOperStatus.
658:
659: applInboundAssociation is the number of currently active
660: local and remote conversations (usually SQL connects).
661:
662: applOutboundAssociations is not provided by this MIB.
663:
664: applAccumulatedInboundAssociations is the total number of
665: local and remote conversations started since the server came
666: up.
667:
668: applAccumulatedOutbound associations is not provided by this
669: MIB.
670:
671: applLastInboundActivity is the time the most recent local or
672: remote conversation was attempted or disconnected.
673:
674: applLastOutboundActivity is not provided by this MIB.
675:
676: applRejectedInboundAssociations is the number of local or
677: remote conversations rejected by the server for
678: administrative reasons or because of resource limitations.
679:
680: applFailedOutboundAssociations is not provided by this MIB."
681:
682: ::= { rdbmsObjects 6 }
683:
684: rdbmsSrvInfoEntry OBJECT-TYPE
685: SYNTAX RdbmsSrvInfoEntry
686: MAX-ACCESS not-accessible
687: STATUS current
688: DESCRIPTION
689: "Information that must be present for a single 'up' database
690: server, with visibility determined by the value of the
691: corresponding applOperStatus object. If an instance of
692: applOperStatus is not up(1), then attempts to access
693: corresponding instances in this table may result in either
694: noSuchName (SNMPv1) or noSuchInstance (SNMPv2) being returned
695: by the agent."
696: INDEX { applIndex }
697: ::= { rdbmsSrvInfoTable 1 }
698:
699: RdbmsSrvInfoEntry ::=
699: warning -
warning: SEQUENCE element #4 `rdbmsSrvInfoDiskWrites' does not match order of columnar objects under `rdbmsSrvInfoEntry'
700: SEQUENCE {
701: rdbmsSrvInfoStartupTime DateAndTime,
702: rdbmsSrvInfoFinishedTransactions Gauge32,
703: rdbmsSrvInfoDiskReads Counter32,
704: rdbmsSrvInfoDiskWrites Counter32,
705: rdbmsSrvInfoLogicalReads Counter32,
706: rdbmsSrvInfoLogicalWrites Counter32,
707: rdbmsSrvInfoPageWrites Counter32,
708: rdbmsSrvInfoPageReads Counter32,
709: rdbmsSrvInfoDiskOutOfSpaces Counter32,
710: rdbmsSrvInfoHandledRequests Counter32,
711: rdbmsSrvInfoRequestRecvs Counter32,
712: rdbmsSrvInfoRequestSends Counter32,
713: rdbmsSrvInfoHighwaterInboundAssociations Gauge32,
714: rdbmsSrvInfoMaxInboundAssociations Gauge32
715: }
716:
717: rdbmsSrvInfoStartupTime OBJECT-TYPE
718: SYNTAX DateAndTime
719: MAX-ACCESS read-only
720: STATUS current
721: DESCRIPTION
722: "The date and time at which this server was last started."
723: ::= { rdbmsSrvInfoEntry 1 }
724:
725: rdbmsSrvInfoFinishedTransactions OBJECT-TYPE
726: SYNTAX Gauge32
727: MAX-ACCESS read-only
728: STATUS current
729: DESCRIPTION
730: "The number of transactions visible to this server that have
731: been completed by either commit or abort. Some database
732: operations, such as read-only queries, may not result in the
733: creation of a transaction."
734: ::= { rdbmsSrvInfoEntry 2 }
735:
736: rdbmsSrvInfoDiskReads OBJECT-TYPE
737: SYNTAX Counter32
738: MAX-ACCESS read-only
739: STATUS current
740: DESCRIPTION
741: "The total number of reads of database files issued to the
742: operating system by this server since startup. Numbers are
743: not comparable between products. What constitutes a
744: readand how it is accounted is product-specific."
745: ::= { rdbmsSrvInfoEntry 3 }
746:
747: rdbmsSrvInfoLogicalReads OBJECT-TYPE
748: SYNTAX Counter32
749: MAX-ACCESS read-only
750: STATUS current
751: DESCRIPTION
752: "The total number of logical reads of database files made
753: internally by this server since startup. The values of this
754: object and those of rdbmsSrvInfoDiskReads reveal the effect
755: of caching on read operation. Numbers are not comparable
756: between products, and may only be meaningful when aggregated
757: across all servers sharing a common cache."
758: ::= { rdbmsSrvInfoEntry 4 }
759:
760: rdbmsSrvInfoDiskWrites OBJECT-TYPE
761: SYNTAX Counter32
762: MAX-ACCESS read-only
763: STATUS current
764: DESCRIPTION
765: "The total number of writes to database files issued to the
766: operating system by this server since startup. Numbers are
767: not comparable between products."
768: ::= { rdbmsSrvInfoEntry 5 }
769:
770: rdbmsSrvInfoLogicalWrites OBJECT-TYPE
771: SYNTAX Counter32
772: MAX-ACCESS read-only
773: STATUS current
774: DESCRIPTION
775: "The total number of times parts of the database files have
776: been marked 'dirty' and in need of writing to the disk. This
777: value and rdbmsSrvInfoDiskWrites give some indication of the
778: effect of 'write-behind' strategies in reducing the number of
779: disk writes compared to database operations. Because the
780: writes may be done by servers other than those marking the
781: parts of the database files dirty, these values may only be
782: meaningful when aggregated across all servers sharing a
783: common cache. Numbers are not comparable between products."
784: ::= { rdbmsSrvInfoEntry 6 }
785:
786: rdbmsSrvInfoPageReads OBJECT-TYPE
787: SYNTAX Counter32
788: MAX-ACCESS read-only
789: STATUS current
790: DESCRIPTION
791: "The total number of pages in database files read by this
792: server since startup. 'Pages' are product specific units of
793: disk i/o operations. This value, along with
794: rdbmsSrvInfoDiskReads, reveals the effect of any grouping
795: read-ahead that may be used to enhance performance of some
796: queries, such as scans."
797: ::= { rdbmsSrvInfoEntry 7}
798:
799: rdbmsSrvInfoPageWrites OBJECT-TYPE
800: SYNTAX Counter32
801: MAX-ACCESS read-only
802: STATUS current
803: DESCRIPTION
804: "The total number of pages in database files written by this
805: server since startup. Pages are product-specific units of
806: disk I/O. This value, with rdbmsSrvInfoDiskWrites, shows the
807: effect of write strategies that collapse logical writes of
808: contiguous pages into single calls to the operating system."
809: ::= { rdbmsSrvInfoEntry 8 }
810:
811: rdbmsSrvInfoDiskOutOfSpaces OBJECT-TYPE
811: change recommended -
warning: node `rdbmsSrvInfoDiskOutOfSpaces' must be contained in at least one conformance group
812: SYNTAX Counter32
813: MAX-ACCESS read-only
814: STATUS current
815: DESCRIPTION
816: "The total number of times the server has been unable to
817: obtain disk space that it wanted, since server startup. This
818: would be inspected by an agent on receipt of an
819: rdbmsOutOfSpace trap."
820: ::= { rdbmsSrvInfoEntry 9 }
821:
822: rdbmsSrvInfoHandledRequests OBJECT-TYPE
823: SYNTAX Counter32
824: MAX-ACCESS read-only
825: STATUS current
826: DESCRIPTION
827: "The total number of requests made to the server on inbound
828: associations. The meaning of 'requests' is product specific,
829: and is not comparable between products.
830:
831: This is intended to encapsulate high level semantic
832: operations between clients and servers, or between peers.
833: For instance, one request might correspond to a 'select' or
834: an 'insert' statement. It is not intended to capture disk
835: i/o described in rdbmsSrvInfoDiskReads and
836: rdbmsSrvInfoDiskWrites."
837: ::= { rdbmsSrvInfoEntry 10 }
838:
839: rdbmsSrvInfoRequestRecvs OBJECT-TYPE
840: SYNTAX Counter32
841: MAX-ACCESS read-only
842: STATUS current
843: DESCRIPTION
844: "The number of receive operations made processing any requests
845: on inbound associations. The meaning of operations is product
846: specific, and is not comparable between products.
847:
848: This is intended to capture lower-level i/o operations than
849: shown by HandledRequests, between clients and servers, or
850: between peers. For instance, it might roughly correspond to
851: the amount of data given with an 'insert' statement. It is
852: not intended to capture disk i/o described in
853: rdbmsSrvInfoDiskReads and rdbmsSrvInfoDiskWrites."
854: ::= { rdbmsSrvInfoEntry 11 }
855:
856: rdbmsSrvInfoRequestSends OBJECT-TYPE
857: SYNTAX Counter32
858: MAX-ACCESS read-only
859: STATUS current
860: DESCRIPTION
861: "The number of send operations made processing requests
862: handled on inbound associations. The meaning of operations
863: is product specific, and is not comparable between products.
864: This is intended to capture lower-level i/o operations than
865: shown by HandledRequests, between between clients and
866: servers, or between peers. It might roughly correspond to
867: the number of rows returned by a 'select' statement. It is
868: not intended to capture disk i/o described in DiskReads."
869: ::= { rdbmsSrvInfoEntry 12 }
870:
871: rdbmsSrvInfoHighwaterInboundAssociations OBJECT-TYPE
872: SYNTAX Gauge32
873: MAX-ACCESS read-only
874: STATUS current
875: DESCRIPTION
876: "The greatest number of inbound associations that have been
877: simultaneously open to this server since startup."
878: ::= { rdbmsSrvInfoEntry 13 }
879:
880: rdbmsSrvInfoMaxInboundAssociations OBJECT-TYPE
881: SYNTAX Gauge32
882: MAX-ACCESS read-write
883: STATUS current
884: DESCRIPTION
885: "The greatest number of inbound associations that can be
886: simultaneously open with this server. If there is no limit,
887: then the value should be zero.
888:
889: Note that a compliant agent does not need to
890: allow write access to this object."
891:
892: ::= { rdbmsSrvInfoEntry 14 }
893:
894: ----------------------------------------------------------------
895:
896: rdbmsSrvParamTable OBJECT-TYPE
897: SYNTAX SEQUENCE OF RdbmsSrvParamEntry
898: MAX-ACCESS not-accessible
899: STATUS current
900: DESCRIPTION
901: "The table of configuration parameters for a server. Entries
902: should be populated according to the following guidelines:
903: (1) The value should be specified through administrative
904: (human) intervention.
905: (2) It should be configured on a per-server or a more global
906: basis, with duplicate entries for each server sharing
907: use of the parameter.
908: (3) One of the following is true:
909: (a) The parameter has a non-numeric value;
910: (b) The current value is numeric, but it only changes due
911: to human intervention;
912:
913: (c) The current value is numeric and dynamic, but the
914: RDBMS does not track access/allocation failures
915: related to the parameter;
916: (d) The current value is numeric and dynamic, the
917: RDBMS tracks changes in access/allocation failures
918: related to the parameter, but the failure has no
919: significant impact on RDBMS performance or
920: availability.
921: (e) The current value is numeric and dynamic, the
922: RDBMS tracks changes in access/allocation failures
923: related to the parameter, the failure has
924: significant impact on RDBMS performance or
925: availability, and is shown in the
926: rdbmsSrvLimitedResource table."
927: ::= { rdbmsObjects 7 }
928:
929: rdbmsSrvParamEntry OBJECT-TYPE
930: SYNTAX RdbmsSrvParamEntry
931: MAX-ACCESS not-accessible
932: STATUS current
933: DESCRIPTION
934: "An entry for a single configuration parameter for a server.
935: Parameters with single values have a subindex value of one.
936: If the parameter is naturally considered to contain a
937: variable number of members of a class, e.g. members of the
938: DBA user group, or tracepoints active in the server, then it
939: must be presented as a set of rows. If, on the other hand,
940: the parameter represents a set of choices from a class,
941: e.g. the permissions on a file or the options chosen out of
942: the set of all options allowed, AND is guaranteed to always
943: fit in the 255 character length of a DisplayString, then it
944: may be presented as a comma separated list with a subindex
945: value of one. Zero may not be used as a subindex value.
946:
947: Entries for a server must be present if the value of the
948: corresponding applOperStatus object is up(1). If an instance
949: of applOperStatus is not up(1), then attempts to access
950: corresponding instances in this table may result in either
951: noSuchName (SNMPv1) or noSuchInstance (SNMPv2) being returned
952: by the agent."
953: INDEX { applIndex, rdbmsSrvParamName, rdbmsSrvParamSubIndex }
954: ::= { rdbmsSrvParamTable 1 }
955:
956: RdbmsSrvParamEntry ::=
957: SEQUENCE {
958: rdbmsSrvParamName DisplayString,
959: rdbmsSrvParamSubIndex INTEGER,
960: rdbmsSrvParamID AutonomousType,
961: rdbmsSrvParamCurrValue DisplayString,
962: rdbmsSrvParamComment DisplayString
963: }
964:
965: rdbmsSrvParamName OBJECT-TYPE
966: SYNTAX DisplayString (SIZE (1..64))
967: MAX-ACCESS not-accessible
968: STATUS current
969: DESCRIPTION
970: "The name of a configuration parameter for a server. This
971: name is product-specific. The length is limited to 64
972: characters to constrain the number of sub-identifiers needed
973: for instance identification (and to minimize network
974: traffic)."
975: ::= { rdbmsSrvParamEntry 1 }
976:
977: rdbmsSrvParamSubIndex OBJECT-TYPE
978: SYNTAX INTEGER (1..2147483647)
978: warning -
warning: use Integer32 instead of INTEGER in SMIv2
979: MAX-ACCESS not-accessible
980: STATUS current
981: DESCRIPTION
982: "The subindex value for this parameter. If the parameter is
983: naturally considered to contain a variable number of members
984: of a class, e.g. members of the DBA user group, or files
985: which are part of the database, then it must be presented as
986: a set of rows. If, on the other hand, the parameter
987: represents a set of choices from a class, e.g. the
988: permissions on a file or the options chosen out of the set of
989: all options allowed, AND is guaranteed to always fit in the
990: 255 character length of a DisplayString, then it may be
991: presented as a comma separated list with a subindex value of
992: one. Zero may not be used as a value."
993: ::= { rdbmsSrvParamEntry 2 }
994:
995: rdbmsSrvParamID OBJECT-TYPE
995: change recommended -
warning: node `rdbmsSrvParamID' must be contained in at least one conformance group
996: SYNTAX AutonomousType
997: MAX-ACCESS read-only
998: STATUS current
999: DESCRIPTION
1000: "The ID of the parameter which may be described in some
1001: other MIB. If there is no ID for this rdbmsSrvParamName,
1002: attempts to access this object will return noSuchName
1003: (SNMPv1) or noSuchInstance (SNMPv2)."
1004: ::= { rdbmsSrvParamEntry 3 }
1005:
1006: rdbmsSrvParamCurrValue OBJECT-TYPE
1007: SYNTAX DisplayString
1008: MAX-ACCESS read-write
1009: STATUS current
1010: DESCRIPTION
1011: "The value for a configuration parameter now in effect, the
1012: actual setting for the server. While there may multiple
1013: values in the temporal domain of interest (for instance, the
1014: value to take effect at the next restart), this is the
1015: current setting.
1016:
1017: Note that a compliant agent does not need to
1018: allow write access to this object."
1019:
1020: ::= { rdbmsSrvParamEntry 4 }
1021:
1022: rdbmsSrvParamComment OBJECT-TYPE
1023: SYNTAX DisplayString
1024: MAX-ACCESS read-write
1025: STATUS current
1026: DESCRIPTION
1027: "Annotation which describes the purpose of a configuration
1028: parameter or the reason for a particular parameter's
1029: setting.
1030:
1031: Note that a compliant agent does not need to
1032: allow write access to this object."
1033:
1034: ::= { rdbmsSrvParamEntry 5 }
1035:
1036: ----------------------------------------------------------------
1037:
1038: rdbmsSrvLimitedResourceTable OBJECT-TYPE
1039: SYNTAX SEQUENCE OF RdbmsSrvLimitedResourceEntry
1040: MAX-ACCESS not-accessible
1041: STATUS current
1042: DESCRIPTION
1043: "The table of limited resources relevant to a server."
1044: ::= { rdbmsObjects 8 }
1045:
1046: rdbmsSrvLimitedResourceEntry OBJECT-TYPE
1046: warning -
warning: index of row `rdbmsSrvLimitedResourceEntry' can exceed OID size limit by 139 subidentifier(s)
1047: SYNTAX RdbmsSrvLimitedResourceEntry
1048: MAX-ACCESS not-accessible
1049: STATUS current
1050: DESCRIPTION
1051: "An entry for a single limited resource kept by the server.
1052: A limited resource has maximum use determined by a parameter
1053: that might or might not changeable at run time, or visible in
1054: the rbmsSrvParamTable. Examples would be the number of
1055: available locks, or number of concurrent executions allowed
1056: in a server. Arrays of resources are supported through an
1057: integer subindex, which should have the value of one for
1058: single-instance names.
1059:
1060: Limited resources that are shared across servers or databases
1061: are best duplicated in this table across
1062: all servers accessing the resource."
1063: INDEX { applIndex, rdbmsSrvLimitedResourceName }
1064: ::= { rdbmsSrvLimitedResourceTable 1 }
1065:
1066: RdbmsSrvLimitedResourceEntry ::=
1067: SEQUENCE {
1068: rdbmsSrvLimitedResourceName DisplayString,
1069: rdbmsSrvLimitedResourceID AutonomousType,
1070: rdbmsSrvLimitedResourceLimit INTEGER,
1071: rdbmsSrvLimitedResourceCurrent INTEGER,
1072: rdbmsSrvLimitedResourceHighwater INTEGER,
1073: rdbmsSrvLimitedResourceFailures Counter32,
1074: rdbmsSrvLimitedResourceDescription DisplayString
1075: }
1076:
1077: rdbmsSrvLimitedResourceName OBJECT-TYPE
1078: SYNTAX DisplayString
1079: MAX-ACCESS not-accessible
1080: STATUS current
1081: DESCRIPTION
1082: "The name of the resource, for instance 'threads' or
1083: 'semaphores', or 'buffer pages'"
1084: ::= { rdbmsSrvLimitedResourceEntry 1 }
1085:
1086: rdbmsSrvLimitedResourceID OBJECT-TYPE
1086: change recommended -
warning: node `rdbmsSrvLimitedResourceID' must be contained in at least one conformance group
1087: SYNTAX AutonomousType
1088: MAX-ACCESS read-only
1089: STATUS current
1090: DESCRIPTION
1091: "The ID of the resource which may be described in some other
1092: MIB. If there is no ID for this rdbmsSrvLimitedResourceName,
1093: attempts to access this object will return noSuchName
1094: (SNMPv1) or noSuchInstance (SNMPv2)."
1095: ::= { rdbmsSrvLimitedResourceEntry 2 }
1096:
1097: rdbmsSrvLimitedResourceLimit OBJECT-TYPE
1098: SYNTAX INTEGER (1..2147483647)
1098: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1099: MAX-ACCESS read-write
1100: STATUS current
1101: DESCRIPTION
1102: "The maximum value the resource use may attain.
1103:
1104: Note that a compliant agent does not need to
1105: allow write access to this object."
1106:
1107: ::= { rdbmsSrvLimitedResourceEntry 3 }
1108:
1109: rdbmsSrvLimitedResourceCurrent OBJECT-TYPE
1110: SYNTAX INTEGER (1..2147483647)
1110: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1111: MAX-ACCESS read-only
1112: STATUS current
1113: DESCRIPTION
1114: "The current value for the resource."
1115: ::= { rdbmsSrvLimitedResourceEntry 4 }
1116:
1117: rdbmsSrvLimitedResourceHighwater OBJECT-TYPE
1118: SYNTAX INTEGER (1..2147483647)
1118: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1119: MAX-ACCESS read-only
1120: STATUS current
1121: DESCRIPTION
1122: "The maximum value of the resource seen since applUpTime
1123: was reset."
1124: ::= { rdbmsSrvLimitedResourceEntry 5 }
1125:
1126: rdbmsSrvLimitedResourceFailures OBJECT-TYPE
1127: SYNTAX Counter32
1128: MAX-ACCESS read-only
1129: STATUS current
1130: DESCRIPTION
1131: "The number of times the system wanted to exceed the limit of
1132: the resource since applUpTime was reset."
1133: ::= { rdbmsSrvLimitedResourceEntry 6 }
1134:
1135: rdbmsSrvLimitedResourceDescription OBJECT-TYPE
1136: SYNTAX DisplayString
1137: MAX-ACCESS read-write
1138: STATUS current
1139: DESCRIPTION
1140: "A description of the resource and the meaning of the integer
1141: units used for Limit, Current, and Highwater.
1142:
1143: Note that a compliant agent does not need to
1144: allow write access to this object."
1145:
1146: ::= { rdbmsSrvLimitedResourceEntry 7 }
1147:
1148: ----------------------------------------------------------------
1149:
1150: rdbmsRelTable OBJECT-TYPE
1151: SYNTAX SEQUENCE OF RdbmsRelEntry
1152: MAX-ACCESS not-accessible
1153: STATUS current
1154: DESCRIPTION
1155: "A table relating databases and servers present on a host."
1156: ::= { rdbmsObjects 9 }
1157:
1158: rdbmsRelEntry OBJECT-TYPE
1159: SYNTAX RdbmsRelEntry
1160: MAX-ACCESS not-accessible
1161: STATUS current
1162: DESCRIPTION
1163: "An entry relating a single database server to a single
1164: database to which it may provide access. The table is
1165: indexed first by the index of rdbmsDbTable, and then
1166: rdbmsSrvTable, so that all servers capable of providing
1167: access to a given database may be found by SNMP traversal
1168: operations (get-next and get-bulk). The makeup of this table
1169: depends on the product's architecture, e.g. if it is one
1170: server - many databases, then each server will appear n
1171: times, where n is the number of databases it may access, and
1172: each database will appear once. If the architecture is one
1173: database - many servers, then each server will appear once
1174: and each database will appear n times, where n is the number
1175: of servers that may be accessing it."
1176: INDEX { rdbmsDbIndex, applIndex }
1177: ::= { rdbmsRelTable 1 }
1178:
1179: RdbmsRelEntry ::=
1180: SEQUENCE {
1181: rdbmsRelState INTEGER,
1182: rdbmsRelActiveTime DateAndTime
1183: }
1184:
1185: rdbmsRelState OBJECT-TYPE
1186: SYNTAX INTEGER{
1187: other(1),
1188: active(2),
1189: available(3),
1190: restricted(4),
1191: unavailable(5)
1192: }
1193: MAX-ACCESS read-only
1194: STATUS current
1195: DESCRIPTION
1196: "The state of this server's access to this database.
1197: Active(2) means the server is actively using the database.
1198: Available(3) means the server could use the database if
1199: necessary. Restricted(4) means the database is in some
1200: administratively determined state of less-than-complete
1201: availability. Unavailable(5) means the database is not
1202: available through this server. Other(1) means the
1203: database/server is in some other condition, possibly
1204: described in the vendor private MIB."
1205:
1206: ::= { rdbmsRelEntry 1 }
1207:
1208: rdbmsRelActiveTime OBJECT-TYPE
1209: SYNTAX DateAndTime
1210: MAX-ACCESS read-only
1211: STATUS current
1212: DESCRIPTION
1213: "The time the database was made active by the server. If an
1214: instance of rdbmsRelState is not active(1), then attempts to
1215: access the corresponding instance of this object may result
1216: in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2)
1217: being returned by the agent."
1218: ::= { rdbmsRelEntry 2 }
1219:
1220: ----------------------------------------------------------------
1221:
1222: -- Well known resources for which limits, high water marks,
1223: -- access or allocation failures, and current levels of use
1224: -- are possibly available in either the rdbmsDbLimitedResources
1225: -- or the rdbmsSrvLimitedResources tables.
1226:
1227: rdbmsWellKnownLimitedResources OBJECT IDENTIFIER
1228: ::= { rdbmsObjects 10 }
1229:
1230: rdbmsLogSpace OBJECT-IDENTITY
1230: error -
macro `OBJECT-IDENTITY' has not been imported from module `SNMPv2-SMI'
1231: STATUS current
1232: DESCRIPTION
1233: "Storage allocated for redo and undo logs."
1234: ::= { rdbmsWellKnownLimitedResources 1}
1235:
1236: ----------------------------------------------------------------
1237:
1238: rdbmsTraps OBJECT IDENTIFIER ::= { rdbmsMIB 2 }
1239:
1240: rdbmsStateChange NOTIFICATION-TYPE
1240: warning -
warning: notification `rdbmsStateChange' is not reverse mappable
1240: change recommended -
warning: notification `rdbmsStateChange' must be contained in at least one conformance group
1241: OBJECTS { rdbmsRelState }
1242: STATUS current
1243: DESCRIPTION
1244: "An rdbmsStateChange trap signifies that one of the database
1245: server/databases managed by this agent has changed its
1246: rdbmsRelState in a way that makes it less accessible for use.
1247: For these purposes, both active(2) and available(3) are
1248: considered fully accessible. The state sent with the trap is
1249: the new, less accessible state."
1250: ::= { rdbmsTraps 1 }
1251:
1252: rdbmsOutOfSpace NOTIFICATION-TYPE
1252: warning -
warning: notification `rdbmsOutOfSpace' is not reverse mappable
1252: change recommended -
warning: notification `rdbmsOutOfSpace' must be contained in at least one conformance group
1253: OBJECTS { rdbmsSrvInfoDiskOutOfSpaces }
1254: STATUS current
1255: DESCRIPTION
1256: "An rdbmsOutOfSpace trap signifies that one of the database
1257: servers managed by this agent has been unable to allocate
1258: space for one of the databases managed by this agent. Care
1259: should be taken to avoid flooding the network with these
1260: traps."
1261: ::= { rdbmsTraps 2 }
1262:
1263: ----------------------------------------------------------------
1264:
1265: -- compliance information
1266:
1267: rdbmsConformance OBJECT IDENTIFIER ::= { rdbmsMIB 3 }
1268: rdbmsCompliances OBJECT IDENTIFIER ::= { rdbmsConformance 1 }
1269: rdbmsGroups OBJECT IDENTIFIER ::= { rdbmsConformance 2 }
1270:
1271: -- compliance statements
1272:
1273: rdbmsCompliance MODULE-COMPLIANCE
1273: error -
macro `MODULE-COMPLIANCE' has not been imported from module `SNMPv2-CONF'
1274: STATUS current
1275: DESCRIPTION
1276: "The compliance statement for SNMP entities which
1277: implement the RDBMS MIB"
1278: MODULE HOST-RESOURCES-MIB
1279: MANDATORY-GROUPS { hrSystem }
1280: MODULE APPLICATION-MIB
1281: MANDATORY-GROUPS { applGroup }
1281: error -
identifier `applGroup' cannot be imported from module `APPLICATION-MIB'
1281: severe -
unknown object identifier label `applGroup'
1282: MODULE RDBMS-MIB
1283: MANDATORY-GROUPS { rdbmsGroup }
1284:
1285: GROUP rdbmsGroup
1286: DESCRIPTION
1287: "The rdbmsGroup is mandatory, but no write access
1288: to objects is required for compliance."
1289: OBJECT rdbmsDbContact
1290: MIN-ACCESS read-only
1291: DESCRIPTION
1292: "A compliant system need not allow write-access to this
1293: object."
1294: OBJECT rdbmsDbParamCurrValue
1295: MIN-ACCESS read-only
1296: DESCRIPTION
1297: "A compliant system need not allow write-access to this
1298: object."
1299: OBJECT rdbmsDbParamComment
1300: MIN-ACCESS read-only
1301: DESCRIPTION
1302: "A compliant system need not allow write-access to this
1303: object."
1304: OBJECT rdbmsDbLimitedResourceLimit
1305: MIN-ACCESS read-only
1306: DESCRIPTION
1307: "A compliant system need not allow write-access to this
1308: object."
1309: OBJECT rdbmsDbLimitedResourceDescription
1310: MIN-ACCESS read-only
1311: DESCRIPTION
1312: "A compliant system need not allow write-access to this
1313: object."
1314: OBJECT rdbmsSrvContact
1315: MIN-ACCESS read-only
1316: DESCRIPTION
1317: "A compliant system need not allow write-access to this
1318: object."
1319: OBJECT rdbmsSrvInfoMaxInboundAssociations
1320: MIN-ACCESS read-only
1321: DESCRIPTION
1322: "A compliant system need not allow write-access to this
1323: object."
1324: OBJECT rdbmsSrvParamCurrValue
1325: MIN-ACCESS read-only
1326: DESCRIPTION
1327: "A compliant system need not allow write-access to this
1328: object."
1329: OBJECT rdbmsSrvParamComment
1330: MIN-ACCESS read-only
1331: DESCRIPTION
1332: "A compliant system need not allow write-access to this
1333: object."
1334: OBJECT rdbmsSrvLimitedResourceLimit
1335: MIN-ACCESS read-only
1336: DESCRIPTION
1337: "A compliant system need not allow write-access to this
1338: object."
1339: OBJECT rdbmsSrvLimitedResourceDescription
1340: MIN-ACCESS read-only
1341: DESCRIPTION
1342: "A compliant system need not allow write-access to this
1343: object."
1344:
1345: ::= { rdbmsCompliances 1 }
1346:
1347: -- units of conformance
1348:
1349: -- rdbmsStateChange and rdbmsOutOfSpace traps are omitted
1350: -- intentionally. They are not required or part of any
1351: -- conformance group.
1352:
1353: rdbmsGroup OBJECT-GROUP
1353: error -
macro `OBJECT-GROUP' has not been imported from module `SNMPv2-CONF'
1354: OBJECTS {
1355: rdbmsDbPrivateMibOID, rdbmsDbVendorName,
1356: rdbmsDbName, rdbmsDbContact,
1357:
1358: rdbmsDbInfoProductName, rdbmsDbInfoVersion,
1359: rdbmsDbInfoSizeUnits, rdbmsDbInfoSizeAllocated,
1360: rdbmsDbInfoSizeUsed, rdbmsDbInfoLastBackup,
1361:
1362: rdbmsDbParamCurrValue, rdbmsDbParamComment,
1363:
1364: rdbmsDbLimitedResourceLimit,
1365: rdbmsDbLimitedResourceCurrent,
1366: rdbmsDbLimitedResourceHighwater,
1367: rdbmsDbLimitedResourceFailures,
1368: rdbmsDbLimitedResourceDescription,
1369:
1370: rdbmsSrvPrivateMibOID, rdbmsSrvVendorName,
1371: rdbmsSrvProductName, rdbmsSrvContact,
1372:
1373: rdbmsSrvInfoStartupTime,
1374: rdbmsSrvInfoFinishedTransactions,
1375: rdbmsSrvInfoDiskReads, rdbmsSrvInfoDiskWrites,
1376: rdbmsSrvInfoLogicalReads, rdbmsSrvInfoLogicalWrites,
1377: rdbmsSrvInfoPageReads, rdbmsSrvInfoPageWrites,
1378: rdbmsSrvInfoHandledRequests,
1379: rdbmsSrvInfoRequestRecvs, rdbmsSrvInfoRequestSends,
1380: rdbmsSrvInfoHighwaterInboundAssociations,
1381: rdbmsSrvInfoMaxInboundAssociations,
1382:
1383: rdbmsSrvParamCurrValue, rdbmsSrvParamComment,
1384:
1385: rdbmsSrvLimitedResourceLimit,
1386: rdbmsSrvLimitedResourceCurrent,
1387: rdbmsSrvLimitedResourceHighwater,
1388: rdbmsSrvLimitedResourceFailures,
1389: rdbmsSrvLimitedResourceDescription,
1390:
1391: rdbmsRelState, rdbmsRelActiveTime }
1392: STATUS current
1393: DESCRIPTION
1394: "A collection of objects providing basic instrumentation of an
1395: RDBMS entity."
1396: ::= { rdbmsGroups 1 }
1397:
1398: ----------------------------------------------------------------
1399:
1400: END