My Oracle Support Banner

MySQL Enterprise Backup (MEB) Fails With : "mysqlbackup: ERROR: Page at offset XXXX in /path/to/ibdata1 seems corrupt!" (Doc ID 1644743.1)

Last updated on SEPTEMBER 09, 2018

Applies to:

MySQL Enterprise Backup - Version 3.8 to 3.8 [Release 3.8]
Information in this document applies to any platform.

Symptoms

MySQL Enterprise Backup (MEB) fails with below error :

mysqlbackup: Progress in MB: 200 400 600 800 1000 1200 1400 1600 1800 2000 2200 2400 2600 2800 3000 3200 3400 3600 3800 4000 4200 4400 4600 4800 5000 

mysqlbackup: INFO: Re-reading page at offset 5237194752 in /path/to/ibdata1
mysqlbackup: INFO: Re-reading page at offset 5237194752 in /path/to/ibdata1
...
...
131203  9:27:00  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 10341b8c0004e0a5.......
.....
InnoDB: End of page dump
131203  9:27:00  InnoDB: Page checksum 3123995015, prior-to-4.0.14-form checksum 1239382402
InnoDB: stored checksum 271850380, prior-to-4.0.14-form stored checksum 2787163084
InnoDB: Page lsn 8109 752137403, low 4 bytes of lsn at page end 2033121304
InnoDB: Page number (if stored to page already) 319653,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 18446744069414584320
mysqlbackup: ERROR: Page at offset 5237194752 in /path/to/ibdata1 seems corrupt!

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
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.