Method for diagnosing large transactions and hotspot transactions of Oracle database

Abstract

The invention discloses a method for diagnosing large transactions and hotspot transactions of an Oracle database. In the operation process of an Oracle database application system, by relating the applications of the system with the database transactions, correlating an application layer with a database layer and monitoring the operation time and operation frequency of the transactions through an automatic monitoring way, the applications of large transactions and hotspot transactions are accurately positioned and started for the transactions reaching the threshold standard based on the established relation between the transactions and the application module; and the diagnosis of large transactions and hotspot transactions in an operation process of the Oracle database application system comprises the following specific steps: 1) configuring an application module identifier and an Oracle database transaction identifier, and setting a transaction threshold; 2) starting the work threads or processes of the database application system background, wherein the work threads or processes include a sampling thread or process, a screening thread or process and an alarm thread or process; 3) initializing a special database connection pool module, and establishing relation between the application layer and the database layer; and 4) performing transaction sampling, wherein a sampling thread periodically obtains the transaction time consumption information of the transaction identifier from the view of the Oracle database application system.

Description

technical field [0001] The invention belongs to the technical field of databases, in particular to database system monitoring technology, in particular to a method for diagnosing large and hot issues of an Oracle database Background technique [0002] Database Transaction (Database Transaction) refers to a series of operations performed as a single logical unit of work, either completely executed or not executed at all. Transactions ensure that data-oriented resources are not permanently updated unless all operations within the transactional unit complete successfully. A transaction is a logical unit of work in database operation, and the transaction management subsystem in the DBMS is responsible for transaction processing. [0003] Transactions that take too long to run in the database are collectively referred to as large transactions, and transactions that run frequently in the database are collectively referred to as hot transactions. Whether they are large transaction...

AI Technical Summary

Problems solved by technology

[0004] Furthermore, when using traditional monitoring methods to monitor transactions, it is generally only possible to obtain SQL from the monitoring of the database level when identifying large or hot transactions, but cannot accurately obtain the source of the application module that started the transaction, which increases the need for accurate diagnosis of transaction problems difficulty

Images