Oracle SNMP Support Reference Guide
The oraRepLink Table contains information for each database link used for replication at the current site. One instance of this table exists for each database link used for replication at the current site. These values are retrieved from both the replication catalog and the Deferred RPC tables.
All information is reported on a per-database link basis. For example, oraRepLinkError counts all errors from the database link oraRepLinkName within the instance of the oraRepLink Table that identifies that link. This is also true for oraRepLinkDeferredTransactions and oraRepLinkAdminRequests.
Administration requests are only made from the master definition sites to remote master sites. Snapshot sites neither send nor receive replication administration requests.
| Variable Name
| Object ID
|
| oraRepLinkIndex
| 1.3.6.1.4.1.111.4.3.5.1.1
|
| oraRepLinkName
| 1.3.6.1.4.1.111.4.3.5.1.2
|
| oraRepLinkDeferredTransactions
| 1.3.6.1.4.1.111.4.3.5.1.3
|
| oraRepLinkErrors
| 1.3.6.1.4.1.111.4.3.5.1.4
|
| oraRepLinkAdminRequests
| 1.3.6.1.4.1.111.4.3.5.1.5
|
Table A - 12. oraRepLink Table Variables and Corresponding Object ID's
| Syntax | INTEGER32 |
| Max-Access | read-only |
| Explanation | This is a numeric index whose value is unique among the replication links associated with a particular schema. |
| Typical Range | not applicable
|
| Significance | This provides a unique identifier for the link. |
| Related Variables | none
|
| Suggested Presentation | simple string
|
| Syntax | DisplayString |
| Max-Access | read-only |
| Explanation | This provides the name of the database link. |
| Typical Range | valid Oracle database link name
|
| Significance | This shows the destination to which transactions will be replicated. |
| Related Variables | none
|
| Suggested Presentation | simple string
|
| Syntax | Gauge32 |
| Max-Access | read-only |
| Explanation | This is the number of deferred transactions queued for propagation to the destination of the dblink. The transactions in the queue are stored, organized by destination, at the database originating the transaction. |
| Typical Range | configuration dependent
|
| Significance | As a general rule, there should not be a large backlog of queued transactions. A moderate queue size reduces poential problems with conflicts, integrity constraints, and cascading errors. This value is one measure of the cost of replication in terms of data traffic. |
| Related Variables | none
|
| Suggested Presentation | gauge or simple string
|
| Syntax | Gauge32 |
| Max-Access | read-only |
| Explanation | This is the number of errors at the local database that were caused by deferred transactions from the dblink in question. These errors are caused by incorrectly formed transactions or by conflicts. The errors in the queue are stored by source at the database at which the errors occurred. |
| Typical Range | 0
|
| Significance | Errors indicate unresolved conflicts or other problems with the replication environment (for example, replication users do not have the correct privileges or the database links were not created correctly). |
| Related Variables | none
|
| Suggested Presentation | gauge or warning indicator
|
| Syntax | Gauge32 |
| Max-Access | read-only |
| Explanation | This is the number of administration requests queued for the local database from the dblink in question. The items in the queue are stored by the source of the requests. |
| Typical Range | configuration dependent
|
| Significance | A large backlog of requests may indicate a problem in the background process which periodically pushes the queue. A gauge would be useful for displaying the percent completion of a single or of a set of adminstration requests (i.e., when the value reaches zero, all requests are complete) |
| Related Variables | none
|
| Suggested Presentation | gauge or simple string
|