DEV Community: Arun Kumar

Step-by-Step Guide to Resolve Access Database Loading DLL Error

Arun Kumar — Wed, 25 Feb 2026 12:01:09 +0000

While accessing ActiveX Data Objects to import an Access database from one application into another—using the query wizard, report wizard, and control wizard—you may encounter the run-time error 48: "Error in loading DLL." This error may also appear as "Object library not registered." It often occurs when the application fails to load the DLL file - a component of Windows operating system, which is required to run the applications smoothly. The reasons why DLL fails, are many. In this article, we will discuss the common causes that might be responsible for this error. We will also provide solutions to resolve this Access database loading error. In case your Access database is corrupted, it is suggested to use a powerful Access recovery software that can help resolve the issue within minimum time.

Causes for Access Database Loading DLL Error
This error 48 is directly related to DLL files. It can occur due to one or more of the following reasons:

The DLL used by Access application fails to export its function properly. It usually occurs when Access fails to find the required entries of the function.
The Access application you’re running is 64-bit, and you’re using the DLL file with 32-bit.
You're using VBA code to link/import a library that contains the incorrect references.
DLL file is corrupted or outdated.
DLL file is not compiled or registered correctly.
DLL file is not present at the path specified in the directory.
Windows registry issues caused damage to the DLL file.
Damaged Access installation.
Registry keys may not exist. Methods to Resolve Access Database Loading DLL Error

Basis troubleshooting steps:

Make sure the DLL file is present and registered.
Check the compatibility of the DLL file. If you're using 64-bit Access, make sure the DLL file is also 64-bit.

Here are the advanced methods you can follow to resolve the Access database loading DLL error.

Method 1 - Register Dao360 and Msado15 DLL Files

As we all know, the Access application allows you to connect to other database files like MDF, using linked tables or external data sources. Such a database connection requires DAO/ADO libraries, which work with Dao360.dll and Msado15.dll. If, for any reason, these DLLs fail to load, it leads to the Error 48: error in loading DLL. To resolve this, you can re-register these DLL files by following these steps:

Open the Run window and type the below command:

Regsvr32.exe "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll

Next, type the following command:

Regsvr32.exe "C:\Program Files\Common Files\system\ado\Msado15.dll"

Click OK. These commands will re-register these Access-based DLL files

Method 2 - Repair and Clear the Registry

The Windows Registry logs every action that takes place in the system. When the DLL error 48 occurs, the Windows Registry gets updated simultaneously. Checking the Windows Registry can help you fix and clear the error. You can use the Windows Registry checker tool to scan the system registry for invalid entries.

Method 3 - Reinstall the Access Application

You can try reinstalling your Access application. This helps in replacing the corrupted or damaged program files, restoring missing or unregistered DLLs, and broken registry entries. But as you already know that DLLs are shared across multiple applications, it is recommended to first check Access' DLL before uninstalling. If you uninstall or install the Access application, which already shares its DLL, it can cause errors in associated applications.

What If the Access Database gets Corrupted due to DLL Issues?

The DLL error can crash your Access application and lead to database corruption. If the Access database is corrupted, damaged, or in an inconsistent state, then you can try importing the data from the affected database into a new database. The steps are as follows:

In MS Access application, click the External Data option.
Then, select the Import Access Database option.
In the Get External Data - Access Database window, select the “Import tables, forms, reports, macros, and modules into the current database” option.

Select the objects and VBA module from the database that you want to import into the new database, and then click OK.

This method will help you import all the selected objects from the affected database to a new database file. If it fails, then you can Compact and Repair the Access database. This removes the unutilized space and compacts the database, and then tries to repair it. Before using the Compact and Repair tool, make sure no other user is actively using the database file. This tool may not repair severely corrupted VBA modules and may fail to resolve complex corruption-based errors.

An Alternative Solution to Quickly Repair the Access Database

Alternatively, you can use Stellar Repair for Access - a professional database repair tool. It can help in resolving all types of complex corruption-based issues in Access database. It quickly repairs critically corrupted ACCDB files, MDF files, and split databases. Additionally, it performs recovery of corrupt VBA modules, like macros, indexes, queries, etc. The product is considered to be a life-saving utility for database administrators who couldn’t afford to lose their records by means of any corruption or database errors.

Conclusion

When the DLL fails to load with the error 48, it may crash your Access application's active window or you may experience repeated system crashes as the DLLs are shared libraries used to run multiple applications. If the sudden system crashes have corrupted the Access database files, then you can take the help of a professional Access repair tool, such as Stellar Repair for Access to repair them in a few minutes.

How to Perform Point-in-Time Recovery in MySQL - A Step-by-Step Guide

Arun Kumar — Tue, 09 Dec 2025 09:55:38 +0000

Point-in-time recovery (PITR) is one of the data recovery methods in MySQL Server that helps you restore data to a specific moment in the past, rather than the complete backup. This you can use when you just need to undo/rollback unwanted changes made to the database since the last backup. In other words, it allows you to return the database to the state before something went wrong.

Here are some situations where Point-in-Time Recovery comes into the picture:

• If you have mistakenly used the DROP or DELETE command and removed an important table from the MySQL database.
• If you forgot to include the WHERE clause and deleted all rows from a table.
• If hard-disk issues or system crash leave your MySQL data in an inconsistent state.

In this post, we will mention the process to perform point-in-time recovery in MySQL. If PITR fails or you fail to open the MySQL tables after restoring, then you can use a professional MySQL recovery tool mentioned in this post.

Key Things to Consider for Point-in-Time Recovery in MySQL

Here are some things to consider to perform point-in-time recovery in MySQL Server.

Full Backup:

A full backup contains the complete database at a specific time. It serves as the initial point for PITR and enables incremental changes

Binary Logs:

The binary log files record all changes made to the database and allow you to replay those changes to a required specific point. These are version-specific, so make sure the version of the MySQL Server you're using to restore the backup is compatible with the version that created the binary logs.

Storage Engine Compatibility:

As MyISAM is non-transactional and lacks advanced features, like crash recovery and transactions, it does not provide consistent recovery using point-in-time. The PITR process relies entirely on binary logs, which record changes to the database as transactions occur. So, make sure you’re using the PITR method to recover InnoDB tables in MySQL.

Check and Find Target Recovery Point:
You should know the exact time when the corruption or accidental deletion occurred to perform point-in-time recovery.

Check Permissions:

Make sure you've the desired permissions, like SUPER, DROP, SELECT, CREATE, etc., to restore the MySQL database.

Procedure to Perform Point-in-Time Recovery in MySQL Server/Workbench

You can perform point-in-time recovery using Binary Log file. Here are the detailed steps:

Step 1 - Check the Error Logs
This helps in finding the exact time or event when corruption/issue occurs. You can find the error log in configuration file, which is located in your MySQL installation directory. Next, check for entries with InnoDB-related errors and warnings, and note the timestamp when corruption/issue was reported.

Step 2 - Restore the Full Backup

Now restore the full back up. You can use the command-line utility - Mysqldump to restore the backup file in MySQL.

Step 3 - Locate Binary Logs
First, make sure the binary logging is enabled on your MySQL Server to perform the point-in-time recovery. To verify this, run the following command:

mysql> SHOW VARIABLES LIKE 'log_bin';

Next, run mysqlbinlog utility to find and process binary logs.

Step 4 - Filter Logs to Recovery Point

The binary logs record events related to modifications to the contents of your database. The binary logs record info according to the time or position of events. This content is in binary format. You can use mysqlbinlog file to open and view the file in a text editor. Next, use the time-stamp or log position to extract transaction specific to the moment before corruption/issue. Here are the commands:

mysqlbinlog --stop-datetime="2025-11-25 10:00:00" mysql-bin.000001 > recovery.sql mysqlbinlog --stop-position=12345 mysql-bin.000001 > recovery.sql

Step 5 - Replay the Logs

Once you have filtered the logs, then apply the filtered logs and restore database using the below command:

mysql -u root -p < recovery.sql

Limitations of Point-in-Time Recovery

The point-in-recovery method can help you recover the data to a specific moment, but it has some limitations, such as:

• Not suitable to recover severely corrupted MySQL tables
• Does not work if backup file is not readable
• Required readable Binary Log file
• Binary logging should be enabled

Alternative Tool to Restore MySQL Database

In point-in-time recovery, you require full backup and binary logs. If binary log file or backup (dump) file is corrupted or unavailable, then PITR is not possible. Also, this method may not work if the MySQL database file is severely corrupted or if the database you’re trying to recover is created with MyISAM engine. To repair the InnoDB and MyISAM tables quickly without backup or binary log file, you can use a professional MySQL repair tool, such as Stellar Repair for MySQL. It helps in specific object recovery with no data loss. Also, it helps in resolving complex corruption errors in both transactional and non-transactional tables in MySQL.

To Conclude

You can use point-in-time recovery feature in MySQL Server to recover data. It allows you to easily restore the data to a precise moment, which helps in minimizing workflow disruption. Follow this post to perform point-in-time recovery in a smooth way. If disabled binary logging or incomplete backup has prevented you from performing PITR, then you can rely on a professional MySQL repair tool – Stellar Repair for MySQL. It can help you recover InnoDB and MyISAM tables with complete integrity.

mysqld Crashes with Signal 11 and Page Corrupt Error

Arun Kumar — Mon, 29 Sep 2025 07:26:59 +0000

Many MySQL users have reported encountering an issue where their MySQL Server crashes with the “mysqld got signal 11” error, along with some hexadecimal code. This is a run-time error that the operating system throws when there is a segmentation fault. You can see this error while using MySQL in Linux/Unix-based environments, like Ubuntu, CentOS, etc. It indicates that the mysqld service or MySQL Workbench failed when it tried to access an invalid memory segment. It can happen due to various reasons, such as:

• Bugs in the MySQL binary or linked libraries
• Misconfigured MySQL configuration file
• Corruption in system memory
• Hardware issues
• Corruption in InnoDB tables
• Corrupt index records or pages in the MySQL database
• Bugs in MySQL server plugins

In this article, we will discuss the troubleshooting methods to resolve the mysqld got signal 11 error in MySQL Server.

Methods to Resolve MySQL Server crashes with mysqld got Signal 11 Error

The mysqld got signal 11 error usually occurs due to bugs in the MySQL Server or its plugins, misconfigured configuration files, or corruption in data or indexes. You can follow the methods mentioned below to identify the root cause of the error and troubleshoot it effectively.

Method 1 – Use Stack Trace in the Error Log
The MySQL error log contains a stack trace that records complete details related to the mysqld crash. This trace helps identify the function calls that lead to the crash, detect failed operations, faulty MySQL plugins, bugs in code, and memory address issues in the binaries.
You can use the stack trace in the error log to find out the cause behind the mysqld crashes with signal 11. Here’s how to find the stack trace:

Note: Stack trace works only if you have not used the -fomit-frame-pointer option with GCC while compiling mysqld. To read the stack trace accurately, ensure MySQL is not compiled with this option.

• Locate the MySQL error log by following the below path:
/var/log/mysql/error.log
• In the error log, search for “Stack Trace”. It looks like:

mysqld got signal 11;
Attempting backtrace. You can use the following information
to find out where mysqld died. If you see no messages after
this, something went terribly wrong...

stack_bottom = 0x41fd0110 thread_stack = 0x40000
mysqld(my_print_stacktrace+0x32)[0x9da402]
mysqld(handle_segfault+0x28a)[0x6648e9]
/lib/libpthread.so.0[0x7f1a5af000f0]
/lib/libc.so.6(strcmp+0x2)[0x7f1a5a10f0f2]
mysqld(_Z21check_change_passwordP3THDPKcS2_Pcj+0x7c)[0x7412cb]
mysqld(_ZN16set_var_password5checkEP3THD+0xd0)[0x688354]

• Read and understand the information in the stack trace carefully. Next, use the addr2line utility to decode addresses from the stack trace into human-readable language. This utility is available in the binutils package on Linux. For example, to decode mysqld(_Z21check_change_passwordP3THDPKcS2_Pcj+0x7c)[0x7412cb] using this utility, run the following command:

$> addr2line -fie /usr/sbin/mysqld 0x7412cb
check_change_password
mysql-server/sql/sql_acl.cc:1234

It will display the check_change_password function behind the mysqld crash, along with the exact line number in the code. Once you have found the exact function name, then try to fix the issue. For example, as displayed above, there is an issue in the check_change_password function. So, locate the MySQL source code in the MySQL data directory to fix it.

Method 2 - Enable InnoDB Recovery Mode and Use the Drop and Reload Method

The MySQL "got signal 11" error can also occur if corruption is present in pages, indexes, or InnoDB tables (.ibd or ibdata1) files. In such a case, you can use innodb_force_recovery to enable the recovery mode. Enabling this option skips the crash recovery and allows MySQL to start. Next, repair the InnoDB tables using the Drop and Reload method. Here’s how to do so:

_Note: Before proceeding, create a backup of the database_

• Enable InnoDB Recovery Mode to access inaccessible MySQL tables. For this, change the my.cnf configuration file. The configuration file is located at /var/log/mysql/error.log.
Alternatively, you can run the below command to go to the configuration file:
sudo nano /etc/mysql/my.cnf
• Add the below line under the [mysqld] section:
innodb_force_recovery=1
• You can increase the recovery level from 1-6. However, setting the value to 4 or above can cause data loss.
• After changes, save the file and restart MySQL.

Now, dump and reload the tables using the below steps:

• First, dump all the tables in the MySQL database.
mysqldump -u [username] -p [database_name] [table_name] > dump.sql mysql -u [username] -p [database_name] < dump.sql
• Next, drop and recreate the table.
DROP TABLE [table_name]; CREATE TABLE [table_name] (...);
• Then, rebuild the table using the ALTER statement.
sql ALTER TABLE [table_name] ENGINE=InnoDB;
• Next, disable the InnoDB recovery mode by using this line of code:
#innodb_force_recovery=…
• Save the changes made to the configuration file and then start the MySQL Server.

Repair MySQL Database using a Professional MySQL Repair Tool

If corruption in the database is too high, you can use a professional MySQL repair tool, like Stellar Repair for MySQL. It can repair corrupted tables created in InnoDB and MyISAM storage engines, with complete integrity. It can restore all the data from .ibd and .ibdata1 files, including indexes, tablespaces, and keys, without any modifications. The tool is compatible with Linux and Windows operating systems. It helps you resolve all the corruption-related errors, including fatal errors that occur due to database corruption. It can repair databases created in MySQL 8.0.36 and earlier versions.

Conclusion

You may face a situation where the MySQL Server crashes with the “mysqld got signal 11” error. It can occur due to various reasons. If the error has occurred due to corruption in InnoDB tablespace or data files, you can try starting MySQL in recovery mode using the innodb_force_recovery option. If the corruption is severe, you can use an advanced MySQL repair tool, like Stellar Repair for MySQL. It can repair corrupt MySQL database files with ease. It can recover all the data from damaged or corrupted MySQL database files.

Incorrect PFS Free Space Information Error in SQL Server: A DBA’s Guide

Arun Kumar — Thu, 31 Jul 2025 09:08:26 +0000

“Incorrect PFS free space information for page (1:103151) in object ID 1993058136, index ID 1, partition ID 72057594434682880, alloc unit ID 71906736119218176 (type LOB data).”

This error typically indicates a mismatch between the actual page allocation and what’s recorded in the Page Free Space (PFS) pages. It can affect database consistency checks and indicates underlying corruption in the database file. In this article, we will see how to fix the “incorrect PFS free space information for page” error in SQL Server.

Causes for Incorrect PFS Free Space Information Error in SQL Server

This error occurs when there is some issue with page free space (PFS) pages. The PFS pages can become inconsistent or corrupted due to one of the following reasons:

• Corruption in SQL Server database.
• Bugs in MS SQL Server.
• Bad sectors on the disk storing the database.
• System where the database is located is virus-infected.
• Sudden system shutdown.

Methods to Resolve Incorrect PFS Free Space Information Error in SQL Server

The error message usually displays the information related to the problematic pages. You can try the below troubleshooting methods to resolve the error.

Method 1: Move Data to New Pages

If the error message contains the name of table in which corrupt PFS pages are stored, you can try moving the data from that table to a new table. To copy the table data, run the SELECT command as shown below:

`SELECT * INTO newtablename FROM damagedtable`

Next, delete the original table to clear the problematic PFS entries. Then, rename the new table with the name of original table. To rename the table, use the ALTER TABLE command:

ALTER TABLE damagedtable
RENAME TO newtablename;

Method 2: Restore Database from Backup

If you have an updated database backup file, you can restore the backup file. It helps you replace corrupt pages metadata with the clean data. To restore the backup file, run the following query:

RESTORE DATABASE databasetest17 
FROM DISK = 'Z:\SQLServerBackups\databasetest13.bak' ;

It restores the entire database from backup, rather than specific pages.

Method 3: Perform Page-Level Restore

If the error message displays information related to a problem with pages, then you can perform Page-level Restore. This will help you to restore only the corrupt pages. However, it does not restore the Transaction logs, Allocation pages, Page 0 of all data files (the file boot page), Page 1:9 (the database boot page), and Full-text catalog.

You can use the SQL Server Management Studio (SSMS) to restore the pages or use the following T-SQL command:

Note: You must know the File ID where the page is located and the Page ID of corrupted page.

RESTORE DATABASE <database_name> 
 PAGE = '<file: page> [ ,... n ] ' [ ,... n ]
 FROM <backup_device> [ ,... n ]
 WITH NORECOVERY

Method 4: Use DBCC CHECKDB Command

You can also use the DBCC CHECKDB command to repair the corrupt SQL database. Here’s how to use the command with REPAIR_ALLOW_DATA_LOSS option:
• First, set the database in single-user mode by running the below command:

ALTER DATABASE databasetest17   SET SINGLE_USER

• Then, run the below command to repair the database:

DBCC CHECKDB (N ’ databasetest17  ’, REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS, NO_INFOMSGS;
GO

• After repairing the database, set it to multi-user mode by using the below command:

ALTER DATABASE databasetest17  SET MULTI_USER

_Note: Repairing the database with the REPAIR_ALLOW_DATA_LOSS option may deallocate pages or a series of pages. This may result in some data loss._

Method 5: Repair Database using a Professional SQL Repair Tool

To avoid data loss and quickly repair the corrupt SQL database, you can use a reliable SQL database repair tool. Stellar Repair for MS SQL is one such MVPs-recommended tool to repair corrupt SQL database of any size. It recovers all the objects, including pages, PFS, triggers, procedures, etc. from damaged MDF/NDF file with complete precision and integrity. It can help resolve corruption-related errors, including the page allocation errors. The tool is compatible with SQL Server 2019, 2017, and earlier versions. It supports both Windows and Linux operating systems.

Conclusion

The “Incorrect PFS Free Space Information” error is one of the errors related to page corruption in SQL Server. The most reliable method is to repair the corrupt NDF/MDF file by using a MS SQL repair tool, such as Stellar Repair for MS SQL. It can repair corrupt database files and recover all the objects, including PFS, pages, and indexes, without any data loss. The tool supports all SQL Server versions.

How to Fix Data Corruption in MariaDB after Improper Shutdown?

Arun Kumar — Fri, 20 Dec 2024 05:22:59 +0000

If the MariaDB Server or system is improperly shutdown, it can interrupt the read/write process leading to corruption in the database file. When the database is corrupt, it prevents you from dumping the data and throws an error, like mysqldump: Error 1034: Index for table 'statistics' is corrupt; try to repair it when dump, MariaDB [mysql]> DROP FUNCTION IF EXISTS civicrm_strip_non_numeric; ERROR 1728 (HY000): Cannot load from MySQL.proc. The table is probably corrupted, etc. Sometimes, you even fail to open or access the database. In this article, we will learn how to repair and restore corrupt MariaDB database.

How to Detect Corruption in MariaDB Database?

First, you need to check the MariaDB database tables for corruption issues using the CHECK TABLE command. This command checks views, foreign keys, and other referenced tables in the MariaDB. It supports Aria, Archive, CSV, InnoDB, and MyISAM storage engines. Here is how to use the CHECK TABLE command:

CHECK TABLE tbl_name [, tbl_name] ... [option] ... option = {FOR UPGRADE | QUICK | FAST | MEDIUM | EXTENDED | CHANGED}
The command also supports partitioned tables. But to check partitioned tables, you need to add an ALTER statement to the CHECK TABLE command.

If the CHECK TABLE command detects any issue in the tables, the InnoDB engine will intentionally cause the MariaDB server to crash to prevent additional damage.

Resolve Data Corruption in MariaDB after Improper Shutdown

You can follow the below methods to repair and restore the corrupt MariaDB database.

Method 1: Restore MariaDB Database from Backup

If you have a valid, recent backup of the MariaDB database file, a simple option is to restore the backup file. For this, you can use the Mariabackup - an open source utility that restores databases in MariaDB. You can use the –copy-back command to restore the backup file. It restores the entire backup to the data directory. So, it is necessary to empty the data directory (--datadir) before performing the action. The configuration file of your system for the data directory is located at /etc/mysql/my. cnf. Follow the below steps to restore the backup:

• First, you need to stop the MariaDB server services. For this, run the below command:
mysql.server stop

• Then, run the below command to use the Mariabackup utility with the –copy-back option:
$ mariabackup --copy-back \ --target-dir=/var/mariadb/backup/

• Next, change the ownership of the data directory file using the below command:
$ chown -R mysql:mysql /var/lib/mysql/

• Now, run the below command to restart the services of MariaDB Server:
mysql.server start

Method 2: Repair Corrupt Tables

If the backup file is not available, then you can use the myisamchk command to recover all the data from corrupt tables, except unique keys. Before using this command, first stop the server using mysqld stop and then recover the data by executing the following command:

myisamchk –recover TABLE

Next, use the below command to restart the server:
mysqld start

Alternatively, you can use the REPAIR TABLE command to repair the corrupt data in MariaDB MyISAM tables. Here’s how:

• First, run the SHOW GRANTS command as given below to check the permissions on the table.
SHOW GRANTS [FOR user|role]

• Check the permissions and ensure that you have all the privileges on the tables, especially SELECT and INSERT privileges.

• Then, run the REPAIR TABLE command as given below:
REPAIR [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name [, tbl_name] ... [QUICK] [EXTENDED] [USE_FRM]

Method 3: Use the Dump and Reload Method

If you’re trying to repair the InnoDB tables in MariaDB, then you can use the Dump and Reload method. The InnoDB engine deliberately causes the MariaDB Server to crash if it finds corruption in tables. If the server crashes, then first restart the server using the –innodb-force-recovery=# option. Next, follow the below steps:

• Dump data from the affected MariaDB table using the SELECT command.
• Run the SHOW CREATE TABLE command (see the below example) to check the declaration and structure of the corrupt table.

SHOW CREATE TABLE table_name

• After this, use the same structure to create a new table by using the below command.

CREATE TABLE table_name ( column1 datatype, column2 datatype, );

• Save the data in the newly created table.
• Restart MariaDB by using the below command:
mysqld start

• Drop the table by using the DROP TABLE command as given below:
DROP [TEMPORARY] TABLE [IF EXISTS] [/*COMMENT TO SAVE*/] table_name [, table_name] ... [WAIT n|NOWAIT] [RESTRICT | CASCADE]
• Now, recreate the table and restore the dump.

Use Professional MariaDB Repair Tool

To quickly recover data from corrupt MariaDB database with complete precision, you can use an advanced MariaDB repair tool, like Stellar Repair for MySQL. This tool can repair MariaDB tables created in both InnoDB and MyISAM engines. It is compatible with Windows and Linux operating systems.

Key features of this powerful software are:

• Repairs corrupt MariaDB and MySQL database
• Recovers all the data, including unique keys, foreign keys, tables, etc., from corrupt MariaDB database
• Fixes all types of MariaDB corruption errors
• Intuitive and user-friendly GUI
• Saves repaired files in several formats –MariaDB, MySQL, SQL Script, CSV, HTML, and XLS
• Supports MariaDB database up to 11.6

To Conclude

MariaDB database may get corrupted after improper server or system shutdown and various other reasons. You can follow the methods mentioned in this post to repair and recover the corrupt MariaDB database. However, the easiest method is to use an advanced MySQL database repair tool, such as Stellar Repair for MySQL. This tool can quickly repair severely corrupt, large-sized MariaDB database with complete integrity and precision. It can recover all the data from the database and save it in a new MariaDB file. It supports database created in both InnoDB and MyISAM storage engines.

How to Repair Corrupt Tables in MariaDB Server after Unexpected MariaDB Crash?

Arun Kumar — Wed, 27 Nov 2024 03:56:57 +0000

The MariaDB Server may unexpectedly crash or stops responding due to various reasons, like hardware failure, bugs in the server code, sudden power failure, etc. After an unexpected server crash, you may face inconsistency issues in the MariaDB database or corruption in tables.

When the tables are corrupted, you may fail to open or access the tables or encounter errors when trying to open the tables. So, you need to repair the MariaDB tables as soon as possible to prevent any further harm or data loss. In this article, we will discuss the methods to repair the corrupt tables in the MariaDB Server.

Methods to Repair MariaDB Database

When MariaDB tables get corrupted, you can use native MySQL utilities to repair and recover the corrupt database tables. Here’s how:

Method 1 - Restore the Database from Backup

If you have taken backup of the MariaDB database file, then you can use the Mariabackup utility to restore the file from backup. You can use the –copy-back command to restore the database file. This command restores the backup to the data directory. So, before executing the –copy-back command, make sure the data directory (--datadir) is empty. You can confirm this by checking the configuration file on your system, which is usually located in /etc/mysql/my. cnf. Then, follow the below instructions:

• First, stop the MariaDB Server services by using the below command.
mysql.server stop
• Next, run the Mariabackup tool with the –copy-back option (see the below example):
$ mariabackup --copy-back \ --target-dir=/var/mariadb/backup/
• Now, change the ownership of the data directory file.
• After this, run the following command to restart the MariaDB Server services:
mysql.server start

If the backup file (dump file) is not available or updated, then follow the next methods to repair the MariaDB tables.

Method 2 - Dump and Reload the Table Data

If you’re using InnoDB search engine, then you can use the Dump and Reload method to repair the tables in the MariaDB database. The InnoDB engine causes the MariaDB Server to crash if it detects corruption in tables. If the MariaDB Server crashes, then you need to restart the MariaDB by using the –innodb-force-recovery=# option. Once you are able to restart the MariaDB, then follow the below steps:

• Run the Select command as given below to dump data from the corrupt MariaDB table:
SELECT * FROM customers
• After this, you can run the SHOW CREATE TABLE command to know the declaration of the corrupt table.
SHOW CREATE TABLE table_name
• Next, create a table with the same structure as the corrupt table. To do this, execute the CREATE TABLE command as given below:
CREATE TABLE table_name ( column1 datatype, column2 datatype, );
• After this, save the data in the newly created table.
• Now, use the below command to restart MariaDB:
mysqld start
mysqld start
• Drop the table by executing the DROP TABLE command as given below.
DROP [TEMPORARY] TABLE [IF EXISTS] [/*COMMENT TO SAVE*/] table_name [, table_name] ... [WAIT n|NOWAIT] [RESTRICT | CASCADE]
• Now, recreate the table and restore the dump.

Method 3 - Use REPAIR TABLE Command

You can also use the REPAIR TABLE command to repair the corrupted tables in MariaDB database. But, before using this command, ensure that you have all the permissions and privileges on the tables, like SELECT and INSERT privileges. To check this, you can run the SHOW GRANTS command as given below:
SHOW GRANTS [FOR user|role]
Now, run the REPAIR TABLE command as given below:
REPAIR [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name [, tbl_name] ... [QUICK] [EXTENDED] [USE_FRM]

If you want to repair partitioned tables using the REPAIR TABLE command, then you need to use the ALTER statement in it.

Method 4 - Use myisamchk Command

You can use the myisamchk command to repair MariaDB tables. It can help you recover all data from the tables, except unique keys. Here’s how to use this command:
• First, use the below command to stop the server.
mysqld stop
• Then, recover the tables by executing the below command:
myisamchk –recover TABLE
myisamchk –recover TABLE
• After this, restart the server:
mysqld start

An Alternative Solution - Use a Professional MariaDB Repair Tool

If you want to repair the MariaDB database quickly and without any data loss, then you can use an advanced MariaDB repair tool. Stellar Repair for MySQL is one such tool that can repair database created in both InnoDB and MyISAM storage engines. It can recover partitioned tables, indexes, unique keys, foreign keys, and other objects from corrupted MariaDB database with complete precision.

Some key features of Stellar Repair for MySQL:

• Repairs MySQL and MariaDB databases created using InnoDB and MyISAM storage engines
• Batch repairs multiple MariaDB databases in a single process
• Recovers all the database objects, including primary keys, foreign keys, tables, table properties, data types, views, and triggers
• Previews recoverable database objects before saving
• Supports repairing of partition tables
• Supports all MariaDB versions up to 11.3.2

Conclusion

The unexpected MariaDB crash can lead to MariaDB table corruption. In this article, we have discussed the methods to repair and restore corrupt tables after MariaDB Server crash. You can restore the database from backup. If the backup is not up-to-date, you can use the REPAIR TABLE and myisamchk commands to repair the tables. To save time and effort, you can use a professional MariaDB repair tool, like Stellar Repair for MySQL, to repair the damaged or corrupt MariaDB tables with complete integrity.

How to Repair Excel File Errors without Losing Data?

Arun Kumar — Tue, 01 Oct 2024 09:49:22 +0000

MS Excel is not free from issues and errors. Users sometimes face random error messages while trying to open the application or an Excel file, saving or editing an Excel file, etc. There are some errors that can even prevent the users from accessing the application or the Excel file, leading to a data loss situation. In this article, we will discuss some common Excel file errors and also provide solutions to resolve these errors without any data loss.

Some Common Excel File Errors

Here are some errors that you may experience while opening, editing, or saving Excel files:

Excel is not responding
Unspecified error message
Microsoft Excel cannot access the file
We’re sorry, but Excel has run into an error that is preventing it from working correctly
We found a problem with some content
File Error: Data may have been lost
Excel found unreadable content in . Do you want to recover the contents of this workbook? If you trust the source of this workbook, click Yes.
MS Excel is already running

The above error messages can occur due to different reasons, such as outdated MS Excel version, bugs in the application, faulty add-ins, damaged program files, and corruption in the Excel file. Let’s see how to resolve these common Excel File errors.

Methods to Resolve Excel File Errors

Here are some methods you can try to resolve the common errors in Excel.

Method 1: Disable Faulty Add-ins in MS Excel
Sometimes, conflicting or faulty add-ins can prevent you from performing several operations in Excel, leading to the errors. You can launch Excel in Safe Mode (press Windows + R, type excel /safe in Run dialog box, and press Enter) to check if the error is caused by any problematic add-ins. When you launch Excel in safe mode, it only uses necessary resources required for its operation and open without any third-party add-ins.
If you are able to launch MS Excel in safe mode without any issue, then it indicates the error was caused by conflicting/faulty COM add-ins. You can disable all the COM add-ins by following these steps:

In Excel safe mode, click on File.
Click on **Options **in the left pane.
Click on Add-ins in the Excel Options.
Expand the dropdown menu against Manage and click on COM Add-ins.
Click on Go.
In the COM Add-ins window, uncheck all the selected add-ins and click OK.

This will disable all the add-ins. Now, relaunch Excel normally and enable the add-ins one-by-one. This will help you to find out the problematic add-in/s. When found, you can permanently disable that add-in.

Method 2: Check if Excel.exe is in Use by Another Process
Sometimes, when you try to launch MS Excel or open a workbook, you may encounter the MS Excel is already running error message. This could happen if the Excel.exe is in use in the background or is being used by another process. You can find and close the Excel.exe process to resolve the issue. Here are the steps to do so:

Press CTRL + SHIFT + ESC to launch Task Manager.
Click on the Processes tab.
Look for Excel.exe or Microsoft Excel.
Right-click on the process and click on End Task. Now, open Excel to see if the issue is resolved.

Method 3: Update MS Excel Application
Outdated MS Excel application may develop some bugs or glitches that can cause various issues and errors. So, it is important to keep your Excel application updated. Here are the steps to check and update MS Excel:

Click on File in the Menu bar.
Click on Account.
Click the Update Options and then click on Update Now.

Method 4: Repair Microsoft Office
Damaged or corrupt program files can also create issues when working with Excel, causing random errors. As Excel is a part of MS Office suite, you can repair the Microsoft Office program. Follow the steps below to repair Microsoft Office:

Press Windows + I to open Settings. Click on Apps.
Click on Apps & Features and scroll down to locate Microsoft Office.
Select Microsoft Office and click on Modify.
When prompted, click Yes.
Select the Repair option and click on Continue.
Wait for the repair process to complete.

Method 5: Repair Excel File
One of the major reasons for errors in Excel file is corruption. If your Excel file is corrupted, you can use the Open and Repair utility in MS Excel to fix the corruption issues. Follow the steps mentioned below to repair corrupted Excel file using this utility:

Launch MS Excel (if it is opening).
Click on File.
Click on Open > Browse.

Select the problematic Excel file.
Click on the arrow next to the **Open **button.
Click on Open and Repair.

On the dialog box that appears, select the Repair option.

Once the file is repaired, click Close.

If the above utility fails to repair the corrupt Excel file, then you can use Stellar Repair for Excel – a powerful Excel repair tool for repairing severely corrupted or damaged Excel files (.xls, .xlsx, .xltm, .xltx, and .xlsm). It recovers all the data from the corrupted Excel file and saves it in a new file. It is a simple-to-use tool that doesn’t require any technical expertise to operate. It can also repair multiple Excel files in a batch with complete precision and integrity.

Conclusion

You may encounter several errors while working with Excel. There are different reasons and factors that can lead to Excel file errors. Corruption in Excel file is one of the major reasons for some common errors. If the Excel file is corrupted, the best and quick way to repair the corrupt Excel file is by using a professional Excel repair tool, like Stellar Repair for Excel. This tool can repair corrupt Excel files and recover all data in just a few simple steps.

How to Recover InnoDB MySQL Table Data from ibdata and frm Files?

Arun Kumar — Thu, 12 Sep 2024 11:09:07 +0000

MySQL Server uses two types of database storage engines – InnoDB and MyISAM. When InnoDB storage engine is used, MySQL Server stores the data and indexes in .ibdata file, and table schema in .frm file. In case of corruption in InnoDB tables, you can easily recover the InnoDB MySQL tables’ data from .ibdata and .frm files, instead of restoring the complete database backup. In this article, we will discuss how to recover data from .ibdata and .frm files in MySQL Server.

Stepwise Process to Recover InnoDB Tables from ibdata and frm Files

Here’s the step-by-step process to recover InnoDB tables’ data from .frm and .ibdata files in MySQL Server:

You need to first create a new MySQL database. For this, login into the PhpMyAdmin, click on the Databases option, type a database name (e.g. Clients), and then click Create.
Next, go to the folder of your XAMPP installation to check the newly created database. The default location is C:\xampp\mysql\data.
When you open the new database, you will find that it does not contain any tables. To create the table, you need the schema of table. If you have an updated backup file, then you can get the schema and name of the database. You can use the same name to create the table. But if you don’t have backup, then you can use the .frm file to extract the schema of the table. There are various reliable utilities available online that can help you to extract table schema.
Now use the same schema to create table in the newly created database.
Once you create the table, it will automatically create new .frm and .ibd files in the database folder.
Next, go to your XAMPP installation folder and delete the .ibd file.
Then, copy the original .ibd file and paste it into the new database.
Before copying the original .ibd file, execute the below query:
ALTER TABLE table_name DISCARD TABLESPACE;
Note: The DISCARD TABLESPACE command will break the link between the MySQL table and the tablespace, thus helps prevent inconsistencies and other issues.
Next, restore the link between MySQL table and Tablespace by using the below command:
ALTER TABLE table_name IMPORT TABLESPACE;
Note: You can restore data from a single table at a time by using .frm and .ibd files. If you need to restore multiple tables, then it will take a lot of time as you need to perform all the steps for each table manually.

Alternate Solution to Recover InnoDB MySQL Table

To restore multiple InnoDB tables at once from MySQL Server database quickly and easily, you can use a professional MySQL database recovery tool. Stellar Repair for MySQL is one such easy-to-use tool that can recover InnoDB tables and other data, such as primary keys, views, triggers, etc. from corrupted or damaged MySQL databases. The tool features a rich and interactive user interface that helps you to perform the repair and recovery operation quickly in just a few simple steps.

Key Features of Stellar Repair for MySQL

Here are some key capabilities of Stellar Repair for MySQL:

Supports MySQL Server 8.0.36 and lower versions
Supports all MariaDB versions up to 11.3.2
Restores all data from MySQL databases, including deleted records and partition tables
Repairs MySQL tables with complete precision
Provides an enhanced preview of repaired data before saving
Allows repairing of multiple databases at once
Allows you to save repaired MySQL database in multiple formats, like MySQL, MariaDB, SQL Script, CSV, HTML, and XLS
Compatible with both Windows and Linux operating systems, including CentOS 7 (64-bit) / Red Hat Enterprise Linux 7 (64-bit) and Ubuntu 16.04 (32-bit & 64-bit) / Ubuntu 18.04 & 19.10 (64-bit)

Conclusion

Above, we have explained the detailed step-by-step process to recover InnoDB MySQL table data from ibdata and .frm files. However, this is not suitable for restoring multiple tables as you need to perform all the steps manually for every table. Alternatively, you can use a professional MySQL database recovery tool, such as Stellar Repair for MySQL that can help you extract all the objects, including tables, primary keys, views, triggers, etc. from corrupted database files with complete integrity. The tool supports repairing of databases created using both InnoDB and MyISAM storage engines. It is designed to address a wide range of corruption-related errors in MySQL database. A free demo version of Stellar Repair for MySQL is also available that allows to scan the database file and preview the recoverable data.

How to Restore SQL Server Database from Backup?

Arun Kumar — Tue, 13 Aug 2024 10:28:19 +0000

Database backups in SQL Server are important as they help restore data in case of database corruption, virus attack, server issue, or any disaster. For example, if a virus damages the database, you can use the last created backup to restore the database. In this article, we will see how to restore SQL Server database from backup.

Restore SQL Database from Full Backup using SSMS

A full backup contains the entire database. Follow the below steps to restore the database from full backup in SQL Server using SQL Server Management Studio (SSMS).

• In the SQL Server Management Studio (SSMS), go to the Object Explorer, select the Databases node, right-click on it, and select the Restore Database option.

• Select the Device option on the General page and then press the Browse button.

• In Select backup devices, press the Add button.
• Select your backup file and press OK.

• If you need to relocate the files, go to the Files page and select the Relocate all files to folder option.

• On the Options page, select Overwrite the existing database (if you want to replace the previous one).
• If your database is under replication, you may need to select the Preserve the replication setting.
• You can also select the restrict access to the restored database option. This option is useful if you don’t want anyone to access the database while you are still working on the restoration.
• The Tail-Log will back up the tail log and try to restore it.
• Optionally, you can select Close existing connection to destination database. Then, click OK.

Restore SQL Server Database from Backup using T-SQL

Alternatively, you can use the T-SQL script to restore the database from backup. Run the following T-SQL code to restore the database backup:

USE [master] BACKUP LOG [stellardb] TO DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Backup\stellardb_LogBackup_2024-03-05_09-38-48.bak' WITH NOFORMAT, NOINIT, NAME = N'stellardb_LogBackup_2024-03-05_09-38-48', NOSKIP, NOREWIND, NOUNLOAD, NORECOVERY , STATS = 5 RESTORE DATABASE [stellardb] FROM DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Backup\stellardb.bak' WITH FILE = 1, NOUNLOAD, STATS = 5
GO

The above code will back up the tail log and then restore the database from the backup file.

What to do if the backup is damaged or corrupted?

Sometimes, you fail to restore the database. So, it is recommended to check your backup and test it before restoring it. The following command can help you to verify if your backup works:
RESTORE DATABASE StellarDB FROM DISK = N'C:\Backups\stellardb.bak' WITH VERIFYONLY;
If it is damaged, there is a way to recover your backup. The best option is to repair your corrupt backup file with a third-party software, such as Stellar Repair for MS SQL. There are 3 editions of this software. The Technician and the Toolkit editions include the option to repair backup database.
The first thing you need to do is install the Stellar Repair for MS SQL Technician software.
Secondly, select the Extract from MS SQL Backup option.

Thirdly, select the backup file. You have two options to select the backup file:
• If you know your backup file location, use the browse option and select your .bak file.
• If you do not know your backup file location, you can use the Find button to search for the backup file.

Once the backup is selected, press the scan button.

There are two options for scanning:
• The Standard Scan, which is the default option and the recommended one. It is the faster option to scan the file.
• The Advanced Scan, which is a slower option but it can be used in case the Standard Scan fails to recover the data.

Select the backup set to repair and press Next.

After repair, it will display all your database objects.

Select the database objects you want to recover and press the Save icon.

You can save the data in New database and have a new database with the data restores. In addition, you can restore the data in a current Live Database or export the data to Other Formats, like Excel, CSV, and HTML.

Conclusion

If the database gets corrupted, you can always recover the database using the most current backup. You can follow the above-mentioned ways to restore the SQL Server database from backup. However, make sure that your backup is not corrupt. To check this, you can use the verifyonly option. If the backup is corrupt, you can use Stellar Repair for MS SQL - Technician to recover your data from the backup file with complete integrity.

How to Repair MariaDB Database?

Arun Kumar — Wed, 31 Jul 2024 03:49:55 +0000

MariaDB, similar to MySQL, is an open source database that is used to store and organize data. MariaDB database, just like other databases, is also susceptible to corruption. The database can get corrupted due to several reasons, like system issues, sudden crashing of application or system hosting database, virus or malware attacks, hardware problems, etc. In this article, we will mention some effective methods to repair the MariaDB database.

How to Check if the MariaDB Database is Corrupted?

Before proceeding, first check if the MariaDB database is corrupted. For this, you can use the CHECK TABLE command. This command checks the MariaDB tables for any errors and issues. This command supports tables created in Archive, Aria, CSV, InnoDB, and MyISAM storage engines. Here’s the syntax of the CHECK TABLE command:

CHECK TABLE tbl_name [, tbl_name] ... [option] ... option = {FOR UPGRADE | QUICK | FAST | MEDIUM | EXTENDED | CHANGED}
The options, used in the above CHECK TABLE command, may vary according to the storage engines. Let’s take a look at them:

FOR UPGRADE: This option is used to check the database after upgrading the MariaDB's version. It checks incompatible table formats.
FAST: This option only checks the tables that were not closed properly or marked as corrupt. It only supports Aria and MyISAM engines.
QUICK: This option supports MyISAM and Aria storage engines. It does not check the delete link chain, thus, performs the checks quickly.
EXTENDED: This option performs a complete check on tables. It checks each row and its keys, and also index keys and its primary clustered keys. This option supports InnoDB engine on MariaDB 10.6.11 and later versions.
CHANGED: This option checks tables, which were modified since the last CHECK/REPAIR in MyISAM and Aria engines.
MEDIUM: This option is used to check and find errors in MariaDB tables. It scans the data files and checks integrity between the data and the ‘index files’ with checksum.
If the CHECK TABLE command finds any issue in the tables, it will directly report the error with description.

Methods to Repair MariaDB Database

If the MariaDB database is corrupted, then you can try to restore the database from backup. If you have been using mariadb-dump client to take backups of your data regularly, you can use the dump files to restore the data. If the backup file (dump file) is not available or updated, then follow the below methods to repair the MariaDB database.

1. Use REPAIR TABLE Command
You can use the REPAIR TABLE command to repair the tables in MariaDB database. You can directly run the REPAIR TABLE command on tables created in Archive, Aria, CSV, and MyISAM Tables.
Here is the syntax:
REPAIR [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name [, tbl_name] ... [QUICK] [EXTENDED] [USE_FRM]
Note: Before using the above command, make sure you have the SELECT and INSERT privileges on the table. To repair the partition tables, you need to add the ALTER option to the REPAIR TABLE command.
If you’re using InnoDB engine, then the engine will cause the MariaDB to crash if it detects corruption in table. To repair the InnoDB table, you need to first restart the MariaDB by using the --innodb-force-recovery=# option. Then, to recover the existing data,

Dump the data from corrupted table.
Save the table structure with the SHOW CREATE TABLE command. Restart MariaDB.
Next, drop the table with the DROP TABLE command.
Now, rebuild the table and restore the dump.

2. Use a Professional MariaDB Database Repair Tool
If the REPAIR TABLE command fails to fix the corrupted MariaDB database, then you can take the help of a professional MariaDB database repair tool to repair the database. Stellar Repair for MySQL is one such tool that can quickly repair the MariaDB database without any data loss. It can repair tables created in MyISAM and InnoDB storage engines. It also supports repairing of partition tables in the database. It can restore all the database objects, including tables, triggers, and indexes with complete precision.

Some Key features of Stellar Repair for MySQL:

Repairs InnoDB and MyISAM tables of the MariaDB database
Restores all the data from damaged MariaDB database with complete integrity
Supports repairing MariaDB database on both Windows and Linux
Supports MariaDB server up to 11.3.2
Allows to save the repaired file in multiple formats, like MariaDB, MySQL, CSV, etc.
Helps to resolve complex corruption-related errors.

Conclusion

If you’re having trouble opening MariaDB database tables or accessing the records, you can use the CHECK TABLE command to check corruption in MariaDB tables. If corruption is detected, then use the REPAIR TABLE command to repair the tables. If this didn't work, you can use a MariaDB database repair tool, like Stellar Repair for MySQL to repair the corrupt MariaDB database. This tool can restore all the data from the corrupt MariaDB database with 100% integrity. It can repair both InnoDB and MyISAM tables.