Hi,
I've a perl DBI application that truncates an innodb table. We've run this code daily for a year or more under various mysql versions.
Execution of 'DELETE from mailinglog' throws the below output error message,
'18/06/12 12:28 @ [97489] @ 201806121227 @ Runner.pl main:: [# 210] @ DBD::mysql::st execute failed: Undo Log error: No more space left over in system tablespace for allocating UNDO log pages. Please add new data file to the tablespace or check if filesystem is full or enable auto-extension for the tablespace at pgm line 306.
This is 5.7.22 running on a virtualized gentoo linux boxen. There is a ton of free disk space. I am guessing the entire table is written to undo logs and we are running over some limit. Advice on a quick solution would be welcome.
I've a perl DBI application that truncates an innodb table. We've run this code daily for a year or more under various mysql versions.
Execution of 'DELETE from mailinglog' throws the below output error message,
'18/06/12 12:28 @ [97489] @ 201806121227 @ Runner.pl main:: [# 210] @ DBD::mysql::st execute failed: Undo Log error: No more space left over in system tablespace for allocating UNDO log pages. Please add new data file to the tablespace or check if filesystem is full or enable auto-extension for the tablespace at pgm line 306.
This is 5.7.22 running on a virtualized gentoo linux boxen. There is a ton of free disk space. I am guessing the entire table is written to undo logs and we are running over some limit. Advice on a quick solution would be welcome.