Release 8.0.5
A64404-01
Library |
Product |
Contents |
Index |
| Oracle
SNMP Support Reference Guide
Release 8.0.5 A64404-01 |
|
This appendix provides information to help you interpret
individual variables in the Oracle implementation of the public RDBMS MIB.
Note that this appendix emphasizes Oracle's implementation. For information
concerning other implementation alternatives for these variables, refer
to MIB itself.
This appendix includes sections covering public RDBMS MIB variables that Oracle implements in the following tables
Note that Oracle does not implement the following tables of the public RDBMS MIB:
Attempts to access any of the variables that Oracle is not
implementing results in noSuchName (SNMPv1) or noSuchInstance (SNMPv2)
being returned.
The rdbmsDbTable contains general information on each database
installed on the managed node. Any installed database that has been configured
for SNMP support, whether or not it is actively opened, is represented
by a row in the rdbmsDbTable.
Each entry in the rdbmsDbTable represents a given database
installed on the node. Each entry is indexed by rdbmsDbIndex. The current
values of the rdbmsDbTable variables are retrieved from a variety of sources
on the managed node.
Oracle implements all rdbmsDbTable variables; Table D-1 lists each of them, together with its corresponding object ID.
INTEGER (1 - 2147483647)
not-accessible
A numeric index, unique among all of the vendors' databases installed on this managed node. This value is a surrogate for the conceptually unique key, which is {vendorOID, databasename }. In the Oracle implementation, the value of this variable when not running the Oracle Parallel Server is the value of rdbmsSrvIndex for this installed database server.
1 - 10
very important
rdbmsSrvIndex
OBJECT IDENTIFIER
read-only
Displays the authoritative identification for the private MIB of this installed database. In the Oracle implementation, the value of rdbmsDbVendorOID is hardcoded as the root of Oracle's OID subtree (1.3.6.1.4.1.111).
1.3.6.1.4.1.111 (only)
very important
rdbmsSrvVendorOID
DisplayString
read-only
Displays the name of the vendor whose RDBMS manages this installed database, for informational purposes. In the Oracle implementation, the value of this variable is hardcoded in the subagent as "Oracle."
6 characters (only)
important
rdbmsSrvVendorName
DisplayString
read-only
Displays the name of this installed database, in product-specific format. In the Oracle implementation, the value of rdbmsDbName is retrieved from the DB__NAME variable in SNMP.ORA. This name is globally unique and includes domain information.
5 - 25 characters
important
rdbmsSrvName
DisplayString
read-write
Displays the name of the contact person for this installed database, together with information indicating how to contact this person. In the Oracle implementation, the value of this variable is retrieved from the SNMP.ORA configuration file.
2 - 255 characters
important
rdbmsSrvContact
The rdbmsDbInfoTable contains additional general information
about actively opened database instances on the managed node. If an installed
database has been configured for SNMP support but is not actively opened,
then attempts to access corresponding instances in this table may result
in either noSuchName (SNMPv1), or noSuchInstance (SNMPv2). "Actively opened"
is determined by the values of all the rdbmsRelState entries for this database
in the rdbmsRelTable.
Each entry in the rdbmsDbInfoTable represents a particular
actively opened database instance on the node. Each entry is indexed by
rdbmsDbIndex. However, because rdbmsDbTable contains an entry for each
database installed on that node, whether or not it is actively open, there
may or may not be a one-to-one correspondence between entries in the two
tables at any point in time. The current value of the rdbmsDbInfoTable
variable are retrieved from a variety of sources on the managed node.
Table D-2 lists each rdbmsDbInfoTable variable that Oracle is implementing, together with its corresponding object ID.
* Variables marked with an asterisk
are not supported.
Attempts to access these variables
may result in errors.
Note that Oracle is not implementing rdbmsDbInfoLastBackup
because Oracle allows individual tablespaces to be backed up; thus, the
time of the last full database backup is not meaningful.
DisplayString
read-only
Displays the textual product name of the server that created or last restructured this database instance. In the Oracle implementation, the value of this variable is retrieved from the BANNER field in V$VERSION.
253 characters
important
rdbmsSrvProductName
DisplayString
read-only
Displays the version number of the server that created or last restructured this database instance. The format is specific to the product. In the Oracle implementation, the value of this variable is derived internally.
not applicable
important (depending on the application)
applVersion
INTEGER (1) bytes, (2) kbytes, (3) mbytes, (4) gbytes, or (5) tbytes.
read-write
Displays the units used to measure the size of this database
instance, as indicated by the values for rdbmsDbInfoSizeAllocated and rdbmsDbInfoSizeUsed.
In the Oracle implementation, the value of rdbmsDbInfoSizeUnits is the
least that allows rdbmsDbInfoSizeAllocated to be expressed as a 32-bit
integer.
(1) bytes, indicates size measured in bytes; (2) kbytes, indicates units of kilobytes; (3) mbytes, indicates units of megabytes; (4) gbytes, indicates units of gigabytes; or (5) tbytes, indicates units of terabytes. Each of these unit measurements are binary multiples (1K = 1024).
enumerated 1 - 5
very important
rdbmsDbInfoSizeAllocated, rdbmsDbInfoSizeUsed
INTEGER (1 - 2147483647)
read-write
Displays the estimated size of this database instance (in rdbmsDbInfoSizeUnits), which is the disk space that has been allocated to it and is no longer available to users on this host. The rdbmsDbInfoSizeAllocated variable does not necessarily indicate the amount of space actually in use for database data; rdbmsDbInfoSizeUsed retrieves this value instead. In the Oracle implementation, the value of this variable is the sum of the BYTES field for the rows of the DBA_DATA_FILES tables.
1 - 2147483647
very important
rdbmsDbInfoSizeUnits, rdbmsDbInfoSizeUsed
INTEGER (1 - 2147483647)
read-only
Displays the estimated size of this database instance (in rdbmsDbInfoSizeUnits), actually in use for database data. In the Oracle implementation, the value of rdbmsDbInfoSizeUsed is the sum of values in the BYTES field of DBA_DATA_FILES minus the sum of values in the BYTES field of DBA_FREE_SPACE. rdbmsDbInfoSizeUsed should always be less than or equal to rdbmsDbInfoSizeAllocated.
1 - 2147483647
very important
rdbmsDbInfoSizeAllocated, rdbmsDbInfoSizeUnits
The rdbmsSrvTable contains generic information on each database
server installed on the managed node. In the standard Oracle configuration,
one server supports one database. Thus, while the content of rdbmsSrvTable
essentially mirrors the content of rdbmsDbTable, Oracle has chosen to implement
both tables in order to fully adhere to one of the central precepts of
the public RDBMS MIB standard. This precept is that a distinction between
the database and its server must be made, in order to account for other
vendors' architectures.
Any installed database that has been configured for SNMP
support, whether or not it is actively opened, is represented by a row
in the rdbmsDbTable. Each entry in the rdbmsSrvTable represents a given
database server on the node. Each entry is indexed by applIndex. The current
value of each rdbmsSrvTable variable is retrieved directly from a variety
of sources on the managed node.
Oracle implements all rdbmsSrvTable variables. Table D-3 lists each of them, together with its corresponding object ID.
| Variable Name | Object ID |
|---|---|
|
rdbmsSrvPrivateMIBOID |
1.3.6.1.2.1.39.1.5.1.1 |
|
rdbmsSrvVendorName |
1.3.6.1.2.1.39.1.5.1.2 |
|
rdbmsSrvProductName |
1.3.6.1.2.1.39.1.5.1.3 |
|
rdbmsSrvContact |
1.3.6.1.2.1.39.1.5.1.4 |
OBJECT IDENTIFIER
read-only
Displays the authoritative identification for the private MIB for this server. In the Oracle implementation, the value of this variable is hardcoded as the root of Oracle's OID subtree (1.3.6.1.4.1.111). If no OBJECT IDENTIFIER exists for the private MIB, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
1.3.6.1.4.1.111 (only)
very important
rdbmsDbVendorOID
DisplayString
read-only
Displays the name of the vendor of this installed database server. In the Oracle implementation, the value of this variable is hardcoded in the subagent as "Oracle."
6 characters (only)
important
rdbmsDbVendorName
DisplayString
read-only
Displays the product name of this server. In the Oracle implementation, the value of this variable is hardcoded as "Oracle7 server."
14 characters (only)
important
rdbmsDbInfoProductName
DisplayString
read-write
Displays the textual identification of the contact person for this managed server, together with information indicating how to contact this person. In the Oracle implementation, the value of this variable is retrieved from the SNMP.ORA configuration file.
0 - 255 characters
important
rdbmsDbContact
The rdbmsSrvInfoTable contains additional information about
each database server instance actively running on the managed node. The
visibility of a database server instance in rdbmsSrvInfoTable is determined
by the value of the corresponding applOperStatus object for that database
server. (For details about applOperStatus, see Appendix E, "Interpreting
Implemented Variables of the Network Services MIB.") Monitoring these variables
is important for tuning server functions such as I/O, access and activity.
Each entry in the rdbmsDbSrvInfoTable represents a given
actively opened database server instance on the node. Each entry is indexed
by applIndex. The current value of each rdbmsSrvInfoTable variable is retrieved
directly from various V$ dynamic performance tables of this database server
instance.
Table D-4 lists each of the rdbmsDbInfoTable variables that Oracle is implementing, together with its corresponding object ID.
Oracle is not implementing the following rdbmsDbInfoTable variables:
DateAndTime
read-only
Displays the date and time at which this server was last started. In the Oracle implementation, the value of this variable is computed from the STARTUP TIME-JULIAN and STARTUP TIME-SECONDS fields in V$INSTANCE.
not applicable
important
applUpTime
Gauge32
read-only
Displays the number of transactions (visible to this server) upon which either COMMIT or ABORT operations have been completed since startup of this database server instance. Some database operations, such as read-only queries, may not result in the creation of a transaction. In the Oracle implementation, the value of this variable is the sum of USER ROLLBACKS and USER COMMITS from V$SYSSTAT.
0 - 4294967295
very important
none
Counter32
read-only
Displays the total number of reads of database files this server has issued to the operating system since startup of this database server instance. In the Oracle implementation, the value of this variable is retrieved from PHYSICAL READS in V$SYSSTAT.
0 - 4294967295
very important
rdbmsSrvInfoLogicalReads, rdbmsSrvInfoPageReads
Counter32
read-only
Displays the total number of logical reads of database files that this server has made internally since startup. This value and the value of rdbmsSrvInfoDiskReads reveal the effect of caching on read operations. In the Oracle implementation, the value of this variable is the sum of CONSISTENT GETS and DB BLOCK GETS in V$SYSSTAT.
0 - 4294967295
very important
rdbmsSrvInfoDiskReads
Counter32
read-only
Displays the total number of writes to database files this server has issued to the operating system since startup. In the Oracle implementation, the value of this variable is retrieved from PHYSICAL WRITES in V$SYSSTAT.
0 - 4294967295
very important
rdbmsSrvInfoPageWrites, rdbmsSrvInfoLogicalWrites
Counter32
read-only
The total number of times parts of the database files have been marked "dirty" and in need of writing to the disk. This value and rdbmsSrvInfoDiskWrites give some indication of the effect of "write-behind" strategies in reducing the number of disk writes compared to database operations. Because the writes may be done by servers other than those marking the parts of the database files dirty, these values may only be meaningful when aggregated across all servers sharing a common cache. Numbers are not comparable between products. In the Oracle implementation, the value of this variable is retrieved from DB BLOCK CHANGES in V$SYSSTAT.
0..4294967295
very important
rdbmsSrvInfoDiskWrites
Counter32
read-only
Displays the total number of pages in database files this server has read since startup of this database server instance. "Pages" are product-specific units of disk I/O operations. This value, together with the value of rdbmsSrvInfoDisksReads, reveals the effect of any grouping read-ahead that may be used to enhance performance of some queries, such as scans. In the Oracle implementation, the value of this variable is the sum of all PHYBLKRD entries in V$FILESTAT.
0 - 4294967295
very important
rdbmsSrvInfoDiskReads
Counter32
read-only
Displays the total number of pages in database files this server has written since this startup of this database server instance. Pages are product-specific units of disk I/O. This value, together with the value of rdbmsSrvInfoDiskWrites, shows the effect of write strategies that collapse logical writes of continuous pages into single calls to the operating system. In the Oracle implementation, the value of this variable is the sum of all PHYBLKWRT entries in V$FILESTAT.
0 - 4294967295
very important
rdbmsSrvInfoDiskWrites
Counter32
read-only
Displays the total number of requests made to the server
on inbound associations since this startup of this database server instance.
rdbmsSrvInfoRequestsHandled is intended to encapsulate high
level semantic operations between clients and servers, or between peers.
For example, one request might correspond to a SELECT or an INSERT statement.
In contrast to rdbmsSrvInfoDiskReads or rdbmsSrvInfoDiskWrites, this variable
is not intended to capture disk I/O operations.
In the Oracle implementation, the value of this variable is retrieved from "user calls" in V$SYSSTAT.
0 - 4294967295
very important
rdbmsSrvInfoRequestRecvs, rdbmsSrvInfoRequestSends
Gauge32
read-only
Displays the greatest number of inbound associations that have been simultaneously open to this server since this startup of this database server instance. In the Oracle implementation, the value of this variable is retrieved from SESSION_HIGHWATER in V$LICENSE.
0 - value of rdbmsSrvInfoMaxInboundAssociations
important
rdbmsSrvInfoMaxInboundAssociations
INTEGER (1..2147483647)
read-write
Displays the greatest number of inbound associations that can be simultaneously open with this server. If there is no limit, then the value should be zero. In the Oracle implementation, the value of this variable is retrieved from SESSIONS_MAX in V$LICENSE.
1 - 2147483647
important
applInboundAssociations, rdbmsSrvInfoHighwaterInboundAssociations
The rdbmsSrvParamTable contains configuration parameters
for a database server installed on this managed node. This table roughly
corresponds to the oraDbConfigTable of the private Oracle Database MIB,
covered in Appendix A. If you are developing an Oracle-specific application,
you not need to concern yourself with this table; instead, you should focus
your attention on oraDbConfigTable, which has been designed for more convenient
use.
Each entry in the rdbmsSrvParamTable represents a particular
configuration parameter for a database server on the node. Each entry is
indexed first by applIndex, then by rdbmsSrvParamName, and finally by rdbmsSrvParamSubIndex;
thus, there normally is a one-to-many relationship between a database server
and its configuration parameters, and a one-to-many relationship between
a configuration parameter and its multiple values. (For details about applIndex,
see Appendix E, "Interpreting Implemented Variables of the Network Services
MIB.") However, in the Oracle implementation, multiple values for a configuration
parameter are concatenated into a single entry for that parameter. The
current value of each rdbmsSrvInfoTable variable is retrieved directly
from a corresponding variable in the INIT.ORA configuration file for this
database server.
Entries for a server must be present if the value of the
corresponding applOperStatus object is up (1). (See Appendix E for more
information on the applOperStatus object.) If an instance of applOperStatus
is not up (not 1), then attempts to access corresponding instances in this
table may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2)
being returned by the agent.
Table D-5 lists each rdbmsSrvParamTable variable that Oracle is implementing, together with its corresponding object ID.
* Variables marked with an asterisk
are not supported.
Attempts to access these variables may result in errors.
Oracle is not implementing the following rdbmsSrvParamTable variables:
DisplayString (1..64)
not-accessible
Displays the name of a configuration parameter for a server. This name is product- specific. The length is limited to 64 characters to minimize traffic of keys and to fit on one line. In the Oracle implementation, the value of this variable is the name of a parameter in the INIT.ORA file.
1 - 45 characters
less important
each oraDbConfigTable variable
INTEGER (1 - 2147483647)
not-accessible
The subindex value for this parameter. In this Oracle implementation, the value of this variable is always 1.
1 (only)
less important
none
DisplayString
read-write
Displays the current value for this configuration parameter, as retrieved from the INIT.ORA file in the Oracle implementation.
0 - 255 characters
less important
oraDbConfigTable variables
The rdbmsRelTable indicates how databases and servers on
this managed node are related. In the standard Oracle implementation, one
server supports one database; nevertheless, this table has been implemented
in order to fully adhere to the public RDBMS MIB standard.
Each entry in the rdbmsDbRelTable represents a mapping between
a database server and a database on the node. Each entry is indexed first
by rdbmsDbIndex, and then by applIndex; thus, for the standard Oracle configuration
of one server per database, these two indices are the same. (For details
on applIndex, see Appendix E, "Interpreting Implemented Variables of the
Network Services MIB.)
Table D-6 lists the rdbmsRelTable variable that Oracle is implementing, together with its corresponding object ID.
| Variable Name | Object ID |
|---|---|
|
rdbmsRelState |
1.3.6.1.2.1.39.1.9.1.1 |
|
rdbmsRelActiveTime |
1.3.6.1.2.1.39.1.9.1.2 |
INTEGER (2) active or (5) unavailable.
read-write
Displays the state of this server's access to this database. Oracle implements (2) active and unavailable (5) only. Active (2) means the server is actively using the database. Unavailable (5) means the database is not available through this server.
2 or 5
very important
appleOperStatus, rdbmsStateChange
Unlike other SNMP variables, a trap variable is not an agent's
response to a management station's request for information. Rather, it
is a message that an agent can send unsolicited to a management station
when that agent notices that some condition has occured (a threshold has
been reached, for example).
Table D-7 lists each rdbmsTraps variable and its corresponding object ID.
| Variable Name | Object ID |
|---|---|
|
rdbmsStateChange |
1.3.6.1.2.39.2.1.1.1 |
{rdbmsRelState }
An rdbmsStateChange trap signifies that one of the database servers this on this node has changed its rdbmsRelState in a way that makes it less accessible for use. In the Oracle implementation, active (2) is considered fully accessible. The state sent with the trap is the new, less accessible state ((5) unavailable).
5 (only)
very important
rdbmsRelState
alarm
