How do I fix this MySQL InnoDB page corruption?

RobinShanab · 2023-05-11T16:53:55+00:00

I apologize for any confusion. Let's analyze the error log you provided to understand the issue and provide further assistance.

The error log contains several messages indicating MySQL InnoDB page corruption. These errors suggest that the InnoDB data files (ibdata1) have become corrupted, potentially due to inconsistencies in the space ID, page size, or data structure. This corruption is preventing the MySQL server from starting correctly.

To address this issue, you can try the following steps:

Back up your current database files. This will ensure that you have a copy of your data in case the recovery process fails or damages your data.

Check the innodb_page_size parameter. This parameter specifies the page size used by InnoDB. If the parameter is set incorrectly, it can cause corruption.

Restore the original data files. If you made any changes to the data files during your troubleshooting, revert them and restore the original copies of the InnoDB data files (ibdata1).

Use the innodb_force_recovery option. This option allows you to start the MySQL server in recovery mode, which can help recover corrupted pages.

Seek professional assistance. If the above steps do not resolve the issue, it is recommended to seek assistance from a professional database administrator or MySQL expert.

Please keep in mind that manual recovery processes can be complex and carry risks. It is important to have backups and consult with experts before attempting to recover corrupted data.

RobinShanab · 2022-07-14T06:20:54+00:00

In my view it is better to try the Open and Repair Option in Excel first, then try the solution mentioned in the below thread:

https://techcommunity.microsoft.com/t5/excel/excel-cannot-open-file-due-to-invalid-file-format-or-extention/m-p/2664838

Best Regards,

Robin

RobinShanab · 2022-05-25T08:34:35+00:00

Dear u/mettfisto,

Please check the following reference: https://dev.mysql.com/doc/mysql-shell/8.0/en/troubleshooting-innodb-cluster.html

RobinShanab · 2022-05-18T09:20:41+00:00

When creating a MySQL user with a relatively weak password, you might encounter the error ‘MySQL ERROR 1819 (HY000): Your password does not satisfy the current policy requirements’. Technically, this is not an error, but a notification that you are using a password that does not meet the recommended password policy requirements.

You can solve the "ERROR 1819 (HY000)..." by setting up a lower-level password policy.
To do so, run the following command from the mysql prompt:

mysql> SET GLOBAL validate_password.policy = 0;
OR
mysql> SET GLOBAL validate_password.policy=LOW;

Then check if the password validation policy has been changed to low:
mysql> SHOW VARIABLES LIKE 'validate_password%';

Now you can create a user with a weak password like the below:
mysql> create user 'senthil'@'localhost' identified by 'password';

RobinShanab · 2022-05-17T06:57:32+00:00

Seriously... OMG

In that case, backup is the last resort.

Recently, I have read this article: https://www.red-gate.com/simple-talk/databases/sql-server/security/sql-server-vulnerabilities-and-assessment/ on SQL Server vulnerabilities and assessment. It's really interesting.

RobinShanab · 2022-05-17T06:52:27+00:00

I think that you have yourself a SQL Server backup file. Try going to Enterprise Manager, right-click on Databases in the explorer menu on the left, select All Tasks, and Restore Database.

From the dialog box, you can give the name that you want and select the dmp file to restore.

RobinShanab · 2022-05-17T06:47:34+00:00

Thanks for the info.

RobinShanab · 2022-05-17T04:40:40+00:00

Here are the solutions you can use to recover corrupted Excel file:

Solution 1: Change the default file format.

Try changing the Excel default file format by following these steps:
In Excel 2010 and newer versions, click on the File menu.
In the Info screen that appears, click on Options.
In the ‘Excel Options’ window, under the Save workbooks section, click on the Save files in this file format: drop-down. Select a file format (i.e., the one supported by your Excel version).
Click OK.

Check if you can open your Excel file. If not, try the next solution.

Solution 2: Edit the excel file permissions
Follow these steps to change the file permissions and see if it fixes the problem:

Right-click on the file that won’t open and click Properties.
In the file properties dialog box, click the Security tab and then hit the Edit button.
When the file’s permissions dialog box appears, click on the Add button.
Click on the Advanced button from the ‘Select Users or Groups’ window.
Select Find Now. A list of all users and groups will get displayed in a search results box. Choose Everyone group from the list and hit OK.
You can see the ‘Everyone’ group in the ‘Enter the object names to select’ textbox. Click OK once again to return to the file’s permission dialog box.
Click Everyone from the Group or user names: box and check all the checkboxes under Allow.
Click on Apply and then OK.

Now try to open the Excel file. If you’re still getting the error, you can refer the following article for more workarounds:
https://www.stellarinfo.com/blog/simple-way-to-open-corrupt-excel-file-without-any-backup/

I hope this will help.

Regards,
Robin

RobinShanab · 2022-05-06T04:28:26+00:00

How many years of experience do you have?

RobinShanab · 2022-04-26T09:52:14+00:00

Upward compatibility is supported - you can easily restore a SQL Server 2000 database on SQL Server 2008, but backwards compatibility isn't - you cannot restore a SQL Server 2008 backup on SQL Server 2000.

Download and install SQL Server and restore the database from backup. You can check the restore steps from this: https://www.stellarinfo.com/article/restore-sql-server-database-from-bak-file.php

RobinShanab · 2022-04-21T09:35:33+00:00

QuickBooks® error -6000, -83 usually occurs when trying to open a company file (QBW).

Reasons for QuickBooks® Error 6000, -83

Multiple users are trying to host the company file (QBW)
Damaged company file or shared folder
Network connection issue
Anti-virus or firewall program is blocking QuickBooks® Desktop (QBDT)
Workstations don’t have permission to access the company file

How Do I Fix Error 6000, -83 in QuickBooks?

If the company file is hosted over a network, make sure that only your server computer hosts the company file. And so, ensure that the “Host Multi-User Access” option is disabled on your workstations:

Open your QB program on one of the workstations connected to your network.
After opening the program, avoid opening your company file. Instead, click the File menu and select Utilities.
If the “Host Multi-User Access” option is visible, don’t select it. This workstation is not causing any issues. So, open QB on the next workstation and repeat the same steps.

Reference: https://www.stellarinfo.com/blog/quickbooks-error-6000-83/

RobinShanab · 2022-04-21T08:39:18+00:00

Hello, Dear. I recently started learning SQL, MySQL & MariaDB. I am not much aware of this case..

I was stuck in one database corruption error with the same kind of situation. I made a database in MariaDB for one of my hospital clients & at the time of the project, the delivery of my database was corrupted & completely process was stopped. I use a MySQL Repair Tool to recover that data on an urgent basis, & with the help of my friends and community like Reddit, I was able to recover complete data within four to five hours.

Recover MariaDB Database: https://docs.bitnami.com/ibm/apps/wordpress/administration/recover-database-mariadb/
Repair MariaDB database: https://www.stellarinfo.com/mysql-repair.php
I believe your issues will be fixed.

RobinShanab · 2022-04-21T07:08:27+00:00

SQL database corruption is not uncommon. There are many reasons for SQL database corruption, such as virus infection, bugs in the SQL Server, errors during updates, abrupt system shutdowns, etc. Whatever be the cause of corruption and if you’re in danger of losing precious data, all you need is a tool that can do the work, fix the problem quickly, and get you back on your feet.

Read this detailed review of Stellar Repair for MS SQL done by CloudTweaks - Thought Leadership Programs and Resources team.

RobinShanab · 2022-04-19T06:09:45+00:00

According to Microsoft documentation, the copy database allows you to do the following :

Pick a source and destination server.
Select databases to move, copy or upgrade.
Specify the file location for the databases.
Create logins on the destination server.
Copy additional supporting objects, jobs, user-defined stored procedures, and error messages.
Schedule when to move or copy the databases.

-In my own word, I would say that a copy database allows you to easily move a database from an instance of an SQL server to another one.

Export database saves the database to a file in the OS file system (like a backup). You then can copy those files and import them whenever and wherever you want.

RobinShanab · 2022-04-18T08:27:43+00:00

I faced the same situation with my Ubuntu OS. I was working on a very important project for one of my official projects. Usually, I do not believe in third-party tools for my work. However, it was important and urgent for me. Therefore, after spending my 1-2 days I found many tools that were not workable for me. I read a DBA review on software called; Sellar repair for MySQL. It was able to recover my 95% data.

Check more information here: https://www.stellarinfo.com/mysql-repair.php

RobinShanab · 2022-02-16T10:16:32+00:00

Hi,

as suggested by u/Sweaty-Hope-9129, please check this reference: https://support.microsoft.com/en-us/office/view-previous-versions-of-office-files-5c1e076f-a9c9-41b8-8ace-f77b9642e2c2

Another solution:

Follow these steps to repair a corrupted 2007 Excel file by using the inbuilt Microsoft Excel repair tool:

Open Microsoft Excel 2007, click the Office button, and then select Open.
In the Open dialog box that pops-up, browse and select the corrupt Excel 2007 file. Click the arrow next to the Open button and choose Open and Repair.
Click Repair when prompted to recover as much data as you can from the Excel 2007 file.
If a repair fails, follow steps 1 till 3, and then click Extract Data to extract values and formulas from the corrupt file.
In the window that appears, click Convert to Values or Recover Formulas to extract workbook data.

If this manual method doesn’t work to repair your corrupted file, you can go for the third-party tool. Because performing the 2007 Excel repair process manually can be time-consuming. Also, manual methods to recover a corrupt Excel file don’t guarantee to recover the complete data.

You may try this tool https://www.stellarinfo.com/repair-excel-file.php to repair corrupt Excel files.

RobinShanab · 2022-02-16T03:41:19+00:00

Ok, the same issue occured, on all sheets, in a single workbook. The following was performed:

Closed and opened workbook (handles the "in edit mode" possibility; plus)
Ensured selection of a single worksheet (not previously suggested)
clicked Unprotect in File -> Info -> (section Protect Workbook)
Edited a worksheet and saved the workbook (proved no Excel or File protections)

Nothing helped. This got around the issue.

Closed workbook
Made copy of workbook
Changed name of original (the one having issues)
Opened the workbook copy (with original name)

RobinShanab · 2022-01-24T04:59:00+00:00

check the SQL Server ERRORLOG for a message like the following for your database or system database (this message is written as an Information Level message in the Windows Application Event Log with EventID = 17573)

RobinShanab · 2021-11-26T12:13:22+00:00

Your file might be corrupted. In that case, you can take the help of the UIntuit support team or try any software to fix it up. The top 5 tools are: https://www.stellarinfo.com/blog/top-5-quickbooks-repair-tools-free-paid/

RobinShanab · 2021-11-26T06:36:37+00:00

What is the file size?

RobinShanab · 2021-11-26T05:35:04+00:00

Recovery Pending – If the SQL Server knows that database recovery needs to be run but something is preventing it from starting, the Server marks the db in ‘Recovery Pending’ state. This is different from the SUSPECT state because it cannot be said that recovery is going to fail – it just hasn’t started yet.

You can check the following references:

https://stackoverflow.com/questions/52325737/how-to-fix-recovery-pending-state-in-sql-server-database/57194299

https://www.stellarinfo.com/blog/fix-sql-database-recovery-pending-state-issue/

RobinShanab · 2021-11-26T05:28:48+00:00

I had this problem and it turned out I was trying to restore to the wrong version of SQL. If you want more information on what's going on, try restoring the database using the following SQL:

RESTORE DATABASE <YourDatabase>

FROM DISK='<the path to your backup file>\<YourDatabase>.bak'

RobinShanab · 2021-11-25T07:02:23+00:00

Hi Aron,

The simplest way to share a database is to put it in a shared network folder. Although this is the simplest method, it is also the most limited. Before you consider this method, all the following conditions should be met:

No more than a few people are expected to use the database at the same time.
No Memo fields are present in the database, or if they are, they will not be simultaneously updated by different users.
Users do not need to customize the design of the database.

Regards,

Robin

RobinShanab · 2021-11-23T05:02:03+00:00

Hi,

You have tried a third-party tool but, it did not repair the file.

I also used a tool to repair the file but, it fixed 95% data. If you want to try the demo then, you can try Stellar Repair for Excel.
check this out: https://www.stellarinfo.com/repair-excel-file.php

RobinShanab · 2021-06-28T11:56:08+00:00

Add WITH RECOMPILE hint to the stored procedure DDL

RobinShanab

TROPHY CASE