Home
AdministeringIn addition to administering the database server, you can tune performance, replicate data, and archive data.
System administrationThese topics contain concepts, procedures, and reference information for database and database server administrators to use for managing and tuning HCL OneDB™ database servers.
Administrator's ReferenceThe HCL OneDB™ Administrator's Reference includes comprehensive descriptions of HCL OneDB™ configuration parameters, the system-monitoring interface (SMI) tables in the sysmaster database, the syntax of database server utilities such as onmode and onstat, logical-log records, disk structures, event alarms, and unnumbered error messages.
Administrative Utilities
The onstat utilityThe onstat utility reads shared-memory structures and provides statistics about the database server at the time that the command runs.
onstat -x command: Print database server transaction informationUse the onstat -x command to display transaction information on the database server.
Determine the mode of a global transactionThe onstat -x command is useful for determining whether a global transaction is executing in loosely-coupled or tightly-coupled mode.

Determine the mode of a global transaction

The onstat -x command is useful for determining whether a global transaction is executing in loosely-coupled or tightly-coupled mode.

The second position of the flags column in the output from the onstat -x command displays the flags for global transactions. The T flag indicates tightly-coupled mode and the L flag indicates loosely-coupled mode.

Loosely-coupled mode means that the different database servers coordinate transactions but do not share locks. Each branch in a global transaction has a separate transaction XID. The records from all branches display as separate transactions in the logical log.
Tightly-coupled mode means that the different database servers coordinate transactions and share resources such as locking and logging. In a global transaction, all branches that access the same database share the same transaction XID. Log records for branches with the same XID appear under the same session ID. MTS uses tightly-coupled mode.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.