Number of Parses. Parsing is the work done by the
database to validate the SQL statement and generate the
query plan used for execution. When the parse count is
close to that of executions for a given statement, you may
be continually reparsing that statement. You can reduce
parsing by making sure that statements are reused as much
as possible in the shared pool. In general, a large number
of hard parses indicates that more memory is needed for
the shared pool.
Parsed from file oramod.my.txt
Company: None
Module: EMPIRE-ORAMOD
Number of Parses. Parsing is the work done by the
database to validate the SQL statement and generate the
query plan used for execution. When the parse count is
close to that of executions for a given statement, you may
be continually reparsing that statement. You can reduce
parsing by making sure that statements are reused as much
as possible in the shared pool. In general, a large number
of hard parses indicates that more memory is needed for
the shared pool.
Parsed from file EMPIRE-ORAMOD.mib
Module: EMPIRE-ORAMOD
Vendor: Concord Communications
Module: EMPIRE-ORAMOD (oramod.my)
Type: TABULAR
Access: read-only
Syntax: Gauge
Automatically extracted from www.mibdepot.com
oramodExpSqlPARSECNT OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "Number of Parses. Parsing is the work done by the database to validate the SQL statement and generate the query plan used for execution. When the parse count is close to that of executions for a given statement, you may be continually reparsing that statement. You can reduce parsing by making sure that statements are reused as much as possible in the shared pool. In general, a large number of hard parses indicates that more memory is needed for the shared pool." ::= { oramodExpSqlEntry 5 }
oramodExpSqlPARSECNT OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "Number of Parses. Parsing is the work done by the database to validate the SQL statement and generate the query plan used for execution. When the parse count is close to that of executions for a given statement, you may be continually reparsing that statement. You can reduce parsing by making sure that statements are reused as much as possible in the shared pool. In general, a large number of hard parses indicates that more memory is needed for the shared pool." ::= { oramodExpSqlEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.546.16.4.11.7.1.1.1 | oramodExpSqlSIDINDX | 0 | 0 | Sid Index Number. |
| 1.3.6.1.4.1.546.16.4.11.7.1.1.2 | oramodExpSqlSQLINDX | 0 | 0 | SQL Statement Index Number. |
| 1.3.6.1.4.1.546.16.4.11.7.1.1.3 | oramodExpSqlEXECUTION | 0 | 0 | Number of Executions. |
| 1.3.6.1.4.1.546.16.4.11.7.1.1.4 | oramodExpSqlDISKREAD | 0 | 0 | Number of Disk Reads. |
| 1.3.6.1.4.1.546.16.4.11.7.1.1.6 | oramodExpSqlBUFFGETS | 0 | 0 | Number of Buffer Gets. |
| 1.3.6.1.4.1.546.16.4.11.7.1.1.7 | oramodExpSqlSORTS | 0 | 0 | Number of Sorts. |
| 1.3.6.1.4.1.546.16.4.11.7.1.1.8 | oramodExpSqlSQL | 0 | 0 | Sql Statement truncated. |