Error 3403, Severity 22 During recovery initialization, page %ld was encountered. This page belongs to object %ld, not the log

When MS SQL Server crashes, it itself tries to recover without intervening the user. During this automatic recovery, server performs a comprehensive scan of transaction logs till the last page. If a page allocated to syslogs is found mismatching the page header object ID with that of syslogs, in that case, error 3403 is displayed and this is why recovery fails.

In order to resolve this error check the backup status. If in case there is an existence of a clean backup, then we suggest you to leave the corrupt database and start afresh by restoring the backup. However, if the backup does not exists, then you need to perform SQL Recovery with the help of some professional third party SQL Server Recovery software.

Kernel for SQL is an expedient tool that is designed especially for dealing SQL server errors and saving your vital data by restoring it from corrupt MDF databases.

SQL database corruption can make anyone worried, as it stores essential data. Identifying database table corruption can help to resolve the problem in a better manner. This post will discuss the basic symptom of SQL database corruption. You may encounter the following error in SQL Server error log while updating, deleting, or opening a database table if your SQL database table is corrupt.

• “Error: 644, Severity: 21, State: 5

• Could not find the index entry for RID ‘1613b1000000100′ in index page (1:189), index ID 7, database ‘TestDB’..

• Error: 8646, Severity: 21, State: 1

• The index entry for row ID was not found in index ID 7, of table 2009058193, in database ‘test644′.”

So whenever you encounter any of the above mentioned error messages, there is corruption in your SQL database table. However, do not get bothered, as there is solution of this problem and i.e. SQL recovery tool. SQL Recovery tool helps to repair the corrupt SQL database and recovers all available data from it. In fact, nothing can better work than this when corruption has occurred to your SQL database.

When a user works with MS SQL Server 2005 and creates a report, he may face technical problems. Windows server may restart due to power failure and the user gets a screen prompting for the reason and information for restart of Server. Due to this OS issue, the SQL database becomes inaccessible.

Moreover, when the user tries to attach the MDF manually, the following error message appears:

“An exception occurred while executing a Transact-SQL statement or batch. <database name>_db.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171).”

Or something like,

“C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDATABASE.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171)”

Cause

MDF file corruption is the main cause of the above error message. The above issue occurs when the MDF file header gets corrupted or due to insertion of some invalid information in the header file. All these situations result in inaccessibility of the SQL database.

Resolution

As a first step user needs to recover the SQL Server database from the latest backup. If backup copy is not available then use SQL recovery software. SQL recovery tools are third party products that ensure complete and accurate recovery from corrupt .MDF database file.

When you try to restore the Microsoft SQL Server database .MDF file from the sequence of transaction log backups, MS SQL Server database gets damaged. In such situations, you might have encountered the following event in the Application Event log of Microsoft SQL Server:

“Filestream corruption – missing files, error 7904

The corruption is detected on a database that was restored from a sequence of backup logs. The original database does not seem to be corrupted.

7904 16 2 Table error: The filestream file for “FileID” was not found.”

What happens in such situation is the occurrence of data loss situations.

Cause

Reason behind this abrupt behavior of MS SQL Server is the filestream corruption. When it happens, the SQL Server database gets damaged, and the .MDF database become inaccessible.

• The Filestream is a critical SQL Server database component that integrates SQL Server Database Engine with NTFS file system by storing the varbinary(max) BLOB (Binary Large Object) data as the files on file system. Win32 file system interfaces offer streaming access to data. It uses NT system cache for data caching.

Resolution

User can recover the damaged SQL Server database using SQL Recovery tool, which perform extensive scan of damaged .mdf database and extract all of the database objects such as tables, reports, forms, triggers and stored procedures.

]]> http://www.sqlrecovery.org/blog/file-stream-corruption-in-sql-server-database/feed/ 0 http://www.sqlrecovery.org/blog/error-while-accessing-sql-database-system-cannot-self-repair-this-error/ http://www.sqlrecovery.org/blog/error-while-accessing-sql-database-system-cannot-self-repair-this-error/#comments Mon, 08 Mar 2010 05:26:34 +0000 admin http://www.sqlrecovery.org/blog/?p=48 read full article]]]> DBCC checks the logical and physical consistency of the SQL database and is able to resolve a few detected error messages. However, at times some issues cannot be resolved using the DBCC commands. SQL database corruption majorly occurs due to corrupt metadata, corruptions in certain critical system base tables or hardware failure. In order to perform systematic recovery of SQL database, the user needs to perform effective SQL Recovery. The error message that appears when a user attempts to access SQL database is:

The system cannot self repair this error

After the occurrence of the above mentioned error message, the data saved in the SQL database becomes inaccessible to the user. The main reason behind the above error message in SQL database can be corrupt system database files, Page Free Space (PFS) page damage or corrupt metadata.

Other reasons for the above error message can be flawed hardware. In order to resolve the error message mentioned above, user needs to follow these steps:

1. Restore the database from last updated backup copy
2. User can run DBCC commands with repair option
3. For hardware issues, user should replace the hard drive

If the above measures fail to perform, then the user needs to recover the inaccessible data using quintessential SQL Recovery Software. The third party sql recovery application comprises of advanced and powerful scanning algorithms to recover the lost data.

In MS SQL Server 2000, the replication process usually runs without any issue for more than 377 days. But once these 377 days get over problem arises while accessing the Server. So when the user tries to run the SQL Server 2000 Transaction Replication, he gets an error message:

“The process could not execute ’sp_replcmds’ on ’servername’. An invalid datetime value was encountered. Value exceeds the year ####”.

Cause

It’s not hard and fast rule that this particular will come only after 377 days; rather this error can come even before 377 days time. This is basically a problem with the user’s log reader agent. The user can change the default profile settings for Query Timeout and ReadBatchSize to 1 for the log reader and then he can restart the log reader agent.

But, most of the times, even after restarting the LogReader, user get the above error message again. In such cases, it’s highly recommended that you must take help of third party tools to safeguard your SQL Server for any mishap and further corruption.

Resolution

If you want to eradicate the above mentioned error, using Kernel for SQL Recovery software would be of great help to you. It is one of the best and smartest utility available that strives hard to perform SQL recovery under any circumstance.

Data files and Transaction log files are the two basic elements in Microsoft SQL Server. All the committed or uncommitted transactions are recorded by or handled by transaction log files. So whenever there is unexpected shutdown of SQL Server, this particular uncommitted log is added to transaction log files. Now if the user restarts the Server, all the SQL transaction log files are analyzed. If the transactions are not run successfully, then the changes performed in the queries related to that transaction persist.

But that’s not the case all the time. Sometimes, this automatic process of recovery does not successfully ends and thus leaving the database in the corrupted state only.

During the SQL Server database corruption, the user encounters the below error message:
Error 3403, Severity 22 during recovery initialization, page %ld was encountered. This page belongs to object %ld, not the log

Cause

At MS SQL Server crash, firstly automatic recovery is performed by the Server. Automatic recovery involves a complete scan of transaction logs up till the last page. Error 3403 occurs whenever a page is found in Syslogs but its page header object ID does not match with that of Syslogs. It leads to failure of automatic recovery. Reasons for this error 3403 to occur are

• Bad write or page allocation

• User updates the allocation page and SQL Server goes down prior to the writing of the transaction log page.

Solution

For solving this issue, firstly look for any backup you are having. If there exists a clean backup with you, then immediately drop the damaged or corrupted database and load it from the backup. But in case no availability of backups, then you are bound to take help of a professional efficient SQL recovery tool. Kernel for SQL Recovery is an absolutely fruitful choice for repairing corrupt SQL database .MDF files and resolving 3403 error.

]]> http://www.sqlrecovery.org/blog/3403-error-in-sql/feed/ 0 http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/ http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/#comments Thu, 04 Feb 2010 05:51:06 +0000 admin http://www.sqlrecovery.org/blog/?p=36 read full article]]]>

Clustered indexes are often misunderstood and overlooked in MS SQL Server. Basically, clustered indexes are responsible for overall system performance and maintenance of the database as the size of database increases. Corruption in clustered indexes could land you in trouble as there is a fear of database crash.

Errors that crop up whenever there is corruption in clustered indexes are

Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1378
Expression: m_offBeginVar <>
SPID: 51
Process ID: 948
Connection Broken

Or

Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).

Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken

Reasons behind these error messages

One encounters these errors when he or she tries to insert a column to existing table through INSERT command.

If the transaction retains the foreign key reference to the column, which has been confirmed as the exclusive clustered or non-clustered index key on the table, then this leads to the above mentioned errors. Because in such a situation the clustered index gets corrupt. Also when the added column gets failed, clustered index also gets corrupt and the entire database become inaccessible.

Solution

When the clustered index gets corrupt, no report is generated by running the DBCC CHECKDB. The database gets contaminated and hence it gets corrupt too.

In such a situation there is no need to detach the database. No need to restart the SQL even. Try to restore the database using recent backup. But if you don’t have backup then you are left with a choice to go for professional SQL Recover software. They are efficient in dealing with any kind of errors and rectify the same.

In SQL Server, a database called tempdb is allocated for worktable / #temp table usage. Sometimes when the tempdb exceeds its maximum size limit, it starts behaving in weird manner. Possibilities of database corruption are very high when size of tempdb is larger than it should be, as when size is above the defined limit, the user experiences following problems:

• He finds an error message in event log saying “The log file for database “tempdb’ is full. Back up the transaction log for the database to free up some log space”.

• An error message in Query Analyzer saying “Could not allocate new page for database ‘TEMPDB’. There are no more pages available in filegroup DEFAULT. Space can be created by dropping objects, adding additional files, or allowing file growth.”

To solve these issues and avoid SQL database corruption caused by them, shrinking tempdb database is must.

Shrinking tempdb databas : SQL Recovery

For shrinking tempdb, you will need to restart MS SQL Server. Follow below mentioned steps to restart and shrink tempdb database:

• Stop SQL Server. Open a command prompt, and then start SQL Server by typing the following command:

sqlservr -c -f

The -c and -f parameters cause SQL Server to start in a minimum configuration mode with a tempdb size of 1 MB for the data file and 0.5 MB for the log file.

• Connect to SQL Server with Query Analyzer, and then run the following Transact-SQL commands:

ALTER DATABASE tempdb MODIFY FILE

(NAME = ‘tempdev’, SIZE = target_size_in_MB)

–Desired target size for the data file

ALTER DATABASE tempdb MODIFY FILE

(NAME = ‘templog’, SIZE = target_size_in_MB)

–Desired target size for the log file

• Stop SQL Server by pressing Ctrl-C at the command prompt window, restart SQL Server as a service, and then verify the size of the Tempdb.mdf and Templog.ldf files.

The best way to avoid a tempdb database from growing is not setting maximum size for it. But when it exceeds the maximum size you can shrink it using above mentioned procedure and avoid corruption and other errors and issues.

SQL Server is most preferred server, which is the resident of all the data maintained by your organization, company on day-to-day basis. SQL Server provides an effective way to manage the objects and data within the SQL database.

Importing and exporting data in and out of SQL Server is a common scenario.

Retrieving information from external sources into MS SQL Server is called the Importing of data in SQL Server. For example, there is an ASCII text file and you are inserting it into SQL Server tables. Now this is referred as importing data in SQL Server. When you set up SQL Server database, importing of data from some other external source is usually the foremost step, as you have raw SQL Server (with no data within to perform anything). Once data is imported to your SQL Server instance, you are ready to work with the database.

Most of the times, Importing of data into an instance of SQL Server is only one-time event i.e. when you need to start up a new SQL Server database. Once the initial migration is complete, the SQL Server database is used directly for all data-related tasks. There is no need for further data imports. Sometimes, importing can be a regular ongoing activity. Suppose SQL Server database is maintaining executive reporting purposes. You would be requiring updated reporting data from a numerous business applications into the SQL Server database on a regular basis.

Exporting is the opposite of above importing of data. The process of extracting data from an instance of SQL Server to some other user- defined format is known as Exporting of data from SQL Server. For example, you are copying particular content instance from SQL Server table to a MS Access database. This is known as exporting data from SQL Server.

SQL Server comes with special tools and features that let you connect applications such as MS Access or MS Excel to SQL Server, for manipulating the data directly in them. It’s better than copying all the data from an instance of SQL Server to the tool before manipulating. Therefore, the data to be manipulated can be exported to a text file on an ad hoc basis. For example, you can extract data from an instance of SQL Server into an Excel spreadsheet running on a portable computer.

Well, there are tools available with SQL Server for importing and exporting data to and from data sources, including text files, Oracle databases, Sybase database, other instances of SQL Server, ASCII text files, and Excel spreadsheets.

Free download demo version of Kernel for SQL Recovery Software.