yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
88b6007443a8e430c32b5e29d5ecc604d46e9d27
doc-exports/docs/rds/umn/rds_08_0039.html
wangdengke2 88b6007443 rds_umn 
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2026-04-02 09:58:19 +00:00

3.7 KiB
Raw Blame History

Managing Historical Transactions

Introduction

This function is used to analyze and discover large transactions and the transactions that have been there for a long time without being committed in the database.

Data on historical transactions comes from the output of the SHOW ENGINE INNODB STATUS command. It shows the snapshot of historical transactions and is collected every 5 minutes.

Constraints

  • The snapshot of historical transactions only lists the transactions that are currently being executed. It does not include those that started and committed during a collection interval.
  • To collect historical transactions, enable Collect Slow Query Logs or Collect All SQL Statements first.
  • A maximum of 10,000 records generated in the past 7 days can be displayed.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target instance name.
  5. In the navigation pane, choose Locks & Transactions under DBA Assistant.
  6. Click the Historical Transactions tab.
  7. Enable Collect Historical Transactions and view historical transactions.
Parent topic: Problem Diagnosis