Database Tuning (MOSC)

MOSC Banner

Undo log file is growing as high as 400 GB but innodb_max_undo_log_size is 1 GB

edited Jun 20, 2024 8:31AM in Database Tuning (MOSC) 1 commentAnswered

Out of the 2 undo log files ,the size of one of the file is growing as high as 400 GB. The parameters for undo log truncation as already set as below.

mysql> show variables like '%undo%';
+--------------------------+------------+
| Variable_name | Value |
+--------------------------+------------+
| innodb_max_undo_log_size | 1073741824 |
| innodb_undo_directory | ./ |
| innodb_undo_log_encrypt | OFF |
| innodb_undo_log_truncate | ON |
| innodb_undo_tablespaces | 2 |
+--------------------------+------------+

Mysql version : 8.0.17

Why is this happening.?
How can we purge out the size taken file ?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center