My Oracle Support Banner

OVM 3.4.6 DB Corruption repeatedly with corruption in the InnoDB tablespace (Doc ID 2686254.1)

Last updated on JULY 17, 2020

Applies to:

Oracle VM - Version 3.4.6 and later
Linux x86-64

Symptoms

 The OVM DB was been rebuilt (rather than restored) for 2 consecutive days and will still fail for a third time.  
Unable to login to the OVM Manager and the mysqld.err file has the last below update: - InnoDB: Failing assertion: bpage->buf_fix_count == 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.