Tuxedo
0
e-docs > Tuxedo > SNMP Agent MIB Reference > Core MIB

SNMP Agent MIB Reference

 Previous Next Contents Index View as PDF  

tuxTranGstate

Syntax

INTEGER { active(1) | aborted(2) | rd-only(3) | ready(4) | hcommit(5) | habort(6) | done(7) | pre-prepare(8) | post-abort(9) | post-commit(10) | unknown(11) )

Access

read-write

Description

The values for GET and SET operations are as follows:

GET: active(1)|aborted(2)|rd-only(3)|ready(4)|hcommit(5)|habort(6)
|done(7)

A GET operation retrieves run-time information for the selected tuxTranTbl instance(s) pertaining to the indicated group. The following states indicate the meaning of a tuxTranGstate returned in response to a GET request. States not listed are not returned. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) can indicate differing states for individual groups. In general, the state indicated on the group's site indicates the true state of the group's participation in the transaction. The exception is when the coordinator site determines that the transaction should abort and sets each participant group state to aborted(2). This transition is propagated to the group's site and results in the rollback of the group's work in the transaction, but cannot be reflected immediately

active(1)

The transaction is active in the indicated group.

aborted(2)

The transaction has been identified for rollback and rollback has been initiated for the indicated group.

rd-only(3)

The group has successfully completed the first phase of two-phase commit and has performed only read operations on the resource manager, thus making it unnecessary to perform the second phase of commit for this group.

ready(4)

The group has successfully completed the first phase of two-phase commit and is ready to be committed.

hcommit(5)

The group has been heuristically committed. This state might or might not agree with the final resolution of the transaction.

habort(6)

The group has been heuristically rolled back. This state might or might not agree with the final resolution of the transaction.

done(7)

This group has completed the second phase of the two-phase commit.

pre-prepare(8)

Indicates that the transaction group contains Tuxedo servers that have called xa_end (TMSUSPEND) during the course of transactional work and that commit processing is beginning. This state exists until either (1) all servers that called xa_end (TMSUSPEND) have caused a call to xa_end (TMSUCCESS), at which point the group state becomes ready, or (2) one of the target servers does a rollback of the transaction, at which point the group state becomes either post-abort(9) or aborted(2).

Note: This state is supported only for Tuxedo 8.0 or later applications.

post-abort(9)

Indicates that a Tuxedo server called xa_end (TPFAIL) and that the TMS has not yet called xa_rollback(). In this case, other Tuxedo servers that called xa_end (TMSUSPEND) are being notified by the TMS in order to clean up their associated CORBA objects.

Note: This state is supported only for Tuxedo 8.0 or later applications.

post-commit(10)

This state is not implemented yet.

Note: This state is supported only for Tuxedo 8.0 or later applications.

SET: hcommit(5)| habort(6)

A SET operation updates run-time information for the first group in the originating request within the selected tuxTranTbl instance. The following states indicate the meaning of a tuxTranGstate set in a SET request. States not listed cannot be set. State transitions are allowed only when performed within the object representing the group's site.

hcommit(5)

Heuristically commit the group's work as part of the indicated transaction. State change is allowed only when tuxTranGstate is ready, tuxTranState is ready, and the indicated group is not on the coordinator's site. Successful return leaves the object in the hcommit(5) state.

habort(6)

Heuristically rollback the group's work as part of the indicated transaction. State change is allowed only when tuxTranGstate is active(1) or ready(4), tuxTranState is ready(4), and the indicated group is not on the coordinator's site. Successful return leaves the object in the habort(6) state.

 

tuxTulogTable

The tuxTulogTable group contains objects that represent run-time characteristics of userlog (ULOG) files within an application. The index into this table is tuxTulogSerNo. The values returned for objects in this table are controlled by the MIB control group tuxTulogCtrl.

Object Name

Object ID

tuxTulogSerNo

.1.3.6.1.4.1.140.300.9.1.1.1

tuxTulogLmid

.1.3.6.1.4.1.140.300.9.1.1.2

tuxTulogPmid

.1.3.6.1.4.1.140.300.9.1.1.3

tuxTulogMmDdYy

.1.3.6.1.4.1.140.300.9.1.1.4

tuxTulogTime

.1.3.6.1.4.1.140.300.9.1.1.5

tuxTulogLine

.1.3.6.1.4.1.140.300.9.1.1.6

tuxTulogMsg

.1.3.6.1.4.1.140.300.9.1.1.7

tuxTulogTpTranId

.1.3.6.1.4.1.140.300.9.1.1.8

tuxTulogXid

.1.3.6.1.4.1.140.300.9.1.1.9

tuxTulogPid

.1.3.6.1.4.1.140.300.9.1.1.10

tuxTulogSeverity

.1.3.6.1.4.1.140.300.9.1.1.11

tuxTulogCat

.1.3.6.1.4.1.140.300.9.1.1.12

tuxTulogMsgNum

.1.3.6.1.4.1.140.300.9.1.1.13

tuxTulogProcName

.1.3.6.1.4.1.140.300.9.1.1.14

tuxTulogThreadID

.1.3.6.1.4.1.140.300.9.1.1.20

tuxTulogContextID

.1.3.6.1.4.1.140.300.9.1.1.30

 

 

Back to Top Previous Next
dev2devesupporthttp://www.oracle.com/technology/documentation/index.htmlpartner net
Contact e-docsContact BEAwebmasterprivacy