Fixing “Page P_ID in database ID...” Error Message

A PFS (Page Free Space) page tracks the allocation status for every page and the amount of free space available on the page. The database engine uses the information stored in the PFS pages to allocate new pages. The page stores the information in the form of bytes, including a byte that indicates that the page is a mixed page. An IAM (Index Allocation Map) page, on the other hand is an array that stores all the mixed pages assigned to a particular index. The data stored in the database components becomes inaccessible if the page that is assigned a 'mixed page' byte in PFS page, not the same page does appear in the IAM page's array. This primarily occurs due to SQL database corruption. In such cases, the database becomes unmountable, further resulting into inaccessibility of its records. For complete accessibility of records in such situations, you will need to restore the data from an updated backup. But, if backup is not available, then you will need to use advanced MS SQL Recovery application.

As a practical case, the below error message pops up while attempting to access your SQL database records:

“Page P_ID in database ID DB_ID is allocated in the SGAM SGAM_P_ID and PFS PFS_P_ID, but was not allocated in any IAM. PFS flags 'PFS_FLAGS'.”

The same error message pops up every time you attempt to access the database records. The database records become inaccessible, once the above error message appears.

Cause:

The above error message pops up when the page P_ID in the database is allocated as mixed page byte in PFS page, but the mixed page does as IAM page or in an IAM page's array. This occurs due to corruption of database due to logical or physical crash.

Resolution:

The resolution for the above error message is discussed below:
If the corruption is caused due to physical damage of a system component, replace the system component.
If the error pops up due logical crash scenarios, then you will need to run DBCC CHECKDB command using correct repair clause.

However, if both the resolutions fail to resolve the issue and the error message pops up while mounting the database, then you will need to repair the database using SQL Database Recovery application. Such SQL Repair tools can be easily downloaded from the Internet.

DBCC CHECKDB unable to resolve SQL Database corruption

The logical and physical integrity of all SQL Server database tables is performed by DBCC CHECKDB command. The command performs and divides its operations in three different phases. The first phase checks the consistency of the allocation structures in disk space, the second phase checks the integrity of all pages and their structures, and the last phase checks the catalog consistency. If critical errors are found in any of the phases, the DBCC CHECKDB command terminates immediately. This happens when the SQL Server database is badly corrupted, and is beyond the repairing capabilities of DBCC CHECKDB command. In such cases, if you need to access the database records, then you will need to restore the database records from a valid backup. But, if no backup is available or backup falls short to restore the required amount of data, then you will need to repair the database by using advanced MS SQL Repair application.

Consider a practical scenario, where you receive the below error message when you attempt to access one of your table records:

“Table error: Object ID O_ID1, index ID I_ID1 cross-object chain linkage. Page P_ID1 points to P_ID2 in object IDO_ID2, index ID I_ID2.”

The above error message primarily results in inaccessibility of all the table records. Additionally, the error message pops up every time you attempt to access the table records.

Cause:

The above table error message occurs when the next page pointer of P_ID1 page points to different object. This can happen either due to logical corruption factors or physical crash of a system component.

Resolution:

The above error message can be resolved by the below steps:

Database table corruption, if caused due to physical damage, can be resolved by changing the damaged system component.
For logical table corruption reasons, run DBCC CHECKDB command with appropriate repair clause.

While the physical corruption issues can be resolved easily changing the system component, the probability of logical corruption problems being resolved by DBCC CHECKDB command is slightly less. In such cases, you will need to use advanced SQL Database Recovery application to repair the database table. A SQL Repair software can be easily downloaded from Internet.

MS SQL Database Unmountable Post Logical Corruption

Corruption in MS SQL database is categorized into two forms – Logical and Physical. While the physical database corruption scenarios include damage of system components, the logical corruption situations only relate to software issues. The outcome for database corruption caused due to either of the two reasons in most cases is, unmountability of the database. An unmountable database does not allow you to access the records stored in the database. In such cases, an up-to-date backup (usually maintained by all the database users) allows you to restore the data and continue with your work. However, there have been thousands of case studies where either the user forgets to create an adequate backup or backup file itself gets corrupt. For such situations, the user needs to search for an effective MS Recover SQL application (for logical corruption) and database repair services (for physical crash scenarios).

Some of the most common logical corruption scenarios after which the database becomes unmountable are mentioned below:

Metadata structure damage
Operating system malfunction
File system damage
Virus attack
Simultaneous modification of same database component
Human errors

To repair the database after it gets corrupted due to any of the above reasons, you will need to run DBCC CHECKDB command. This command allows you to identify the level of corruption. Next, you will need to execute the same command with an appropriate repair clause.

While the above command allows you to repair database corruption in most of the situations, it might fail to repair in case the database is severely corrupted. For such situations, in case of no backup availability, you will need to use advanced third-party SQL Database Repair application. A MS SQL Recovery tool instantly repairs corrupt databases post any logical corruption scenario. It uses intensive scanning methods to scan and repair corrupt MS SQL databases. The read only software do not overwrite, change, or delete the data stored in the original database. Built with highly interactive user documentation, these tools are easy to understand and implement.

Fixing “Incorrect PFS free space information...” Error Message

An MS SQL Server database file is divided into various PFS (Page Free Space) intervals, approximately 64 MB in size. The byte-map of the PFS page consists of at least one byte per page for every page that is included in the PFS interval. The information stored in the PFS interval is very critical because corruption of it can result into database error, which stops you from accessing the records stored in the database. In such situations, the database corruption can be surmounted by restoring the data from an updated backup. However, the possibilities of database users forgetting to create an adequate backup, or the location where the backup is saved always exits. In such cases, the database user needs to opt for a powerful third-party SQL Database Recovery utility that can easily repair the database.

Picture a scenario, where you receive the underneath error message with your MS SQL Server database:

“Incorrect PFS free space information for page P_ID, object ID O_ID, index ID I_ID, in database ID DB_ID. Expected value PFS_VAL1, actual value PFS_VAL2.”

The above error is marked as “Error 8914” in SQL Server log and is a “Severity Level 10” error message.

Cause:

The above error message pops up when the bits allocated in the PFS page conflict with the free space available on the page P_ID. This can either occur due to logical or physical damage of the database.

Resolution:

The resolutions for the above error message are discussed below:

To check for hardware damages, check the system's hardware by examining the log reports of SQL Server and Windows. Change the hardware component in case any component is damaged.
If the problem persists, run DBCC CHECKDB command (with repair clause) to repair the corrupt database.

However, there is a possibility of data loss after running the above command. To avoid such situations, you should repair your database using effective SQL Repair software. These SQL Repair tools perform a complete scan and restore the repaired database on new or old destination. Such tools are completely non-destructive in nature.

Check this sql related article :-
http://ezinearticles.com/?Troubleshooting-SQL-Server-Error-2579&id=2857699

http://www.thefreelibrary.com/Applying+CHECKDB+on+Tempdb+Cause+Data+Loss-a01073994023

Fixing “Database error...” post SQL Database Corruption

PFS (Page Free Space) pages in SQL Server database not only maintains free spaces, but a lot more than that. Every SQL database file is divided into various PFS intervals, each containing 8088 pages. A PFS page contains a byte-map, which stores one byte for every page included in the PFS interval. Corruption in PFS page results into damage in the stored bytes, further resulting in making your database unmountable. The database records saved in the database become inaccessible after it becomes unmountable. For easy accessibility of records and to save your valuable time, you will need to restore the data from a valid backup. However, in case of backup unavailability or corruption, you will need to use a third-party MS SQL Recovery tool, which provides systematic repair.

As a practical example, you receive the below error message while mounting your SQL database:

“Database error: Page P_ID1 is marked with the wrong type in PFS page P_ID2. PFS status 0xVAL1 expected 0xVAL2.”

The appearance of the above error message makes your database unmountable, further resulting into inaccessibility of its stored records.

Cause:

The above error message appears when the below bits are improperly set:
PFS_IS_IAM_PG (0x10)
PFS_IS_MIXED_EXT (0x20)
PFS_IS_ALLOCATED (0x40)

Damage in PFS pages can occur either due to logical or physical reasons.

Resolution:

To read your database records and to resolve the error message, you will need to follow the below measures:
If the above error arises due to physical damages, then you need to swap the damaged system component with a new component.
However, if the message arises due to logical corruption, then you will need to run DBCC CHECKDB, with appropriate repair clause.

While the first resolution provides 100% guarantee to resolve all physical damages, the second falls short to prove successful in all logical corruption scenarios. For such cases, only a third-party SQL Repair application should be used. These SQL Repair utilities systematically scans a logically corrupted database and restores it on default or new destination. Such repair software are self-explanatory and can be easily used by even non-technical users.

You can view this related sql article :- http://ezinearticles.com/?Resolving-Table-Error---Object-Id-O-ID---Possible-Bad-Root-Entry-in-Sysindexes&id=3422084

SQL Server database corrupt post Unexpected Shutdown

Database corruption after unexpected system shutdown is a common scenario happened to almost all of us. The database becomes unmountable, further resulting in inaccessibility of records, after being corrupted. In most of these situations, you receive an error message that describes the exact cause of corruption, and sometimes its resolution too. However, if the resolution provided in the error message works, then there is no need to worry. But if in case, the resolution fails, then the best way to overcome database corruption is by restoring the data from an updated backup. Unavailability of a valid backup leaves you with no option, but to use advanced third-party MS SQL Recovery application to repair the database.

Consider a practical scenario, where your database unexpectedly stops and restarts again. On the restart, the database does not mount, and you view the below error messages in the error log file:

“DateTimeSPID Error: 602, Severity: 21, State: 30.
DateTimeSPID Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
DateTimeSPID Error: 9001, Severity: 21, State: 5.
DateTimeSPID The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
DateTimeSPID Error: 3449, Severity: 21, State: 1.
DateTimeSPID SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.”

Cause:

Unexpected shutdown could be caused when SQL Server is unable to handle duplicate partition Ids, which are produced in tempdb database.

Resolution:

To resolve database corruption, you will need to opt for advanced MS SQL Repair tool. These tools use advanced scanning methods to repair your database. Such SQL Repair tools do not require any technical skills to perform database repair.

Error Messages while restoring the MS SQL Server database

Restoration of data from an updated database backup allows you to overcome almost all SQL Server database corruption scenarios. It is therefore, always recommended to maintain a systematic database backup on some other storage media as well. While restoration of data is an easy process, it might result into an error message, which prevents you from restoration of the database. In such situations, an easy way is to restore the data from any other updated database backup. However if in case, no other backup is available or backup falls short to restore the data, then you will need to opt for advanced third-party SQL Recovery application.

Consider a practical scenario, where you encounter the underneath error message while restoration of data:

“Msg 8967, Level 16, State 216, Server , Line 2
An internal error occurred in DBCC which prevented further processing. Please contact Customer Support.
DBCC results for ''.
Msg 8921, Level 16, State 1, Server , Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.”

On viewing the your SQL Server log, you view another error message:

“2007-05-26 07:13:49.21 spid58 DBCC encountered a page with an LSN greater than the current end of log LSN () for its internal database snapshot. Could not read page (file id:page id), database '), LSN = (), type = 32, isInSparseFile = 1. Please re-run this DBCC command.”

While the restoration process halts, the data stored in the database becomes inaccessible.

Cause:

The above error message primarily occurs when the DBCC CHECKDB command is unable to serve the required checks that confirm the consistency of your database. These checks could not be performed due to numerous reasons, such as SQL Server database corruption, metadata structure damage, and more.

Resolution:

To resolve the above error message and to access the database records, you will need to use advanced SQL Database Recovery tool that provides comprehensive repair of corrupt database. Such SQL Repair tools are non-destructive in nature as they do overwrite or modify the original records of the database.