Database Recovery Software | Database Diasaster Recovery Solutions

An insight into FileMaker database corruption and the possible remedies to overcome data loss

2012-01-24T22:48:00.000-08:00

FileMaker is a cross-platform relational database management system that has originated from a DOS application. It is an Apple Macintosh application specifically known for its interactive GUI-based interface that enables users to introduce new elements to their existing layouts, screens or forms in the database. It is much similar to the desktop database applications, but exceeds the storage capacity of most of these products. A FileMaker database typically faces corruption due to virus infection, hardware errors, abnormal system shutdown, etc. As a consequence, you lose access to all the valuable data stored in the database. To resolve this problem, you need to go for FileMaker pro recovery through a trusted third-party tool.

Let's assume a real time scenario. Suppose you are a database administrator. When you try to import your FileMaker database into an excel sheet, you may encounter the below given error on your screen:

"FileMaker Pro Error: Object not found"

Causes: The above error may occur if you perform the following course of actions:

On the ‘Data’ menu, you select ‘Get External Data’.
You click ‘Import form FileMaker Pro’.
You get all the data to a worksheet.

You can only import records up to a multiple of 500 rows. If you try to import records beyond that multiple of 500, you will receive the above specified error.

Resolution: To resolve this issue, you may try exporting the file as a text file and then using it in MS Excel:

Start FileMaker Pro and open the database that you wish to import into Excel.
Go to ‘File’ menu and select ‘Export Records’.
A dialog box appears. In the ‘Type’ section, click ‘Tab-Separated Text’ or ‘Comma-Separated Text’. Now, specify a new name and click ‘Save’.
Another dialog box appears. Choose the individual fields you need to export and then click ‘Export’.
Try to open the saved text file in MS Excel.

If the problem still persists, take help of a competent FileMaker repair tool. These third-party software are proficient in safely repairing corrupt FileMaker databases and retrieving precious tables and other valuable information in the database. Moreover, they support all Mac-Intel based computers with Mac OS X 10.5 and above.

Possible workaround for FileMaker database corruption

2012-01-11T03:09:00.000-08:00

It is difficult to make assumptions of what exactly went wrong when you are dealing with FileMaker database corruption. One might think of 'Compact, Optimize or Recover'. You might overcome a few cases with this technique and get away with the real problem of data loss. Let's find out various options through which you can effectively handle this type of problem.

Frequently, a FileMaker file gets damaged because of unwanted or unnecessary power surges. When ever the application closes unexpectedly, it s very likely that the file will get damaged. FileMaker 9 Server performs a consistency check that typically includes the following set of actions:

Verifies the block structures (4K blocks)
Checks if the next and previous blocks are present.

Now, use the following options to recover FileMaker database in the event of corruption:

Save a Copy As → Clone:

This command is not exactly to fix any corruption. Instead, it enables you to get the clone or an identical image of your file's structure without any data. The significance of this command is that it deletes or removes all the locale info from the file. The locale info includes all region specific data, such as dates, time, etc.

Save a Copy As → Copy:

This command would allow for creating a block by block copy of your file.

Save a Copy As → Compacted:

This command implements the 'Compact and Optimize' technique. This process is performed on a copy of the file, thus helping you to protect or safeguard the original data. You can also find the 'Compact' and 'Optimize' options in the 'File Maintenance' menu.

Recovery command:

This command will ensure that all the invalid blocks are removed from the file when it is recovered. It performs complete scanning of the file and then validates the data blocks. If it finds a corrupt block, it will simply skip the block. A valid block will have the below properties:

Each block will have a previous and next block containing data.
The block will have a length of 4K and should be in correct order.
The block should not be a duplicate of its preceding one.

SQL server Error Messages & their Solutions

2011-12-29T22:07:00.000-08:00

When MS SQL server 2000 founds any problem with the database then it writes a message from the system table to SQL server error log or sends a message to the database administrator depending upon the security level. An error message is combination of four information that is message number, security level, error state number and message. Message number identifies the error message, security level denotes the type of problem, state number denotes the source of problem while message suggest the problem and possible solution.

For detail information about error message, we will take an example. Suppose you try to access a table that is not exist in the SQL server database then MS SQL server 2000 database generates an error message.

Select * FROM Database Employee, in this example database administrator is trying the access Database employee table but Database employee table is not exist in the database then SQL server generates below error message

Server: Msg 208, Level 16, State 1
Invalid object name 'stellar employee'

Cause for Error Message: There are several causes for appearing error message in the SQL server database, some of them are virus attack, hardware problem, automatic system shutdown, user related problem, wrong SQL server syntax, insufficient space, log related problem and many more. Each cause generates unique error message with detail description about the error and suggested solution. Suggested solution helps for resolving the error message but sometime, it is not enough to solve the problem.

How to Fix Error Message: As we know that every solution depends upon the type of problem. If SQL server generates error message due to wrong syntax then correct the syntax and fix the problem. Most of the errors messages in the SQL server database are appear due to virus attack or power failure problem. If you have updated backup for the affected database then restore from it. In case, there is no any backup you should try any third party MDF repair software. MDF repair software uses advanced scanning algorithm to scan and repair corrupt SQL server database.

Features of FileMaker Pro database & FileMaker Recovery

2011-12-07T01:46:00.000-08:00

FileMaker is a cross platform relational database management system designed for Mac & Windows by FileMaker Inc. It offers an advanced graphical user interface that help in modification of database layout. Database administrator can drag new element to the database with the help of GUI. Some FileMaker versions are FileMaker Pro, FileMaker Pro Advanced, FileMaker server, FileMaker Server Advanced. Recently FileMaker Inc. has developed FileMaker Go for iPhone & iPad.

FileMaker Pro Starter Solutions: FileMaker Pro database comes with 30 build-in starter solutions that help to design database more professionally. You can design your important tasks in a minute by using of these starter solutions. Some of the starter solutions are as follows:

Contact Management: Manage your contact details with this feature. As you know that a good contact management always saves time & effort to retrieve data or records.

Manage Inventory Details: It is the best option for personal as well as for business users. You can easily manage your inventory details like price of product, product availability, pictures of products and many more.

Manage To Do List: Personally i like this feature most because it helps me to manage my to do list very efficiently. You can also organize your project to do list and work associated with it. It also helps in managing the priority of work, like low, medium, and high priority.

FileMaker Pro Corrupt, What to Do? FileMaker Pro database gets corrupt of damaged due to several reasons like virus attack, hardware problem, unexpected system shutdown and many more. You can restore corrupt database from updated backup. If you don't have backup of database then you have to recover corrupt database.

How to Recover? FileMaker Pro database offers an in-build utility for FileMaker Recovery that recover corrupt FileMaker database. For this go to the File Menu and click on the Recover button to recover.

How to Repair MySQL Database Error 1194

2011-11-08T03:10:00.000-08:00

Database administrators use MySQL database tables to store their personal as well as professional data or records. Sometimes, MySQL database throws a below error message:

“ERROR 1194 (HY000): Table 'table_name' is marked as crashed and should be repaired”
where “table_name” is your table table name.

Why this Happen? The first point comes in our mind that why have we got this error message? There are several reasons for this like virus attack, automatic system shutdown, power failure, hardware failure and many more.

Where to Start? To repair MySQL database table corruption, you can follow given below methods.

Method 1: The first method that you can try is Export/Import. To do this follow the below steps:

Export the corrupted or damaged MySQL table.
Delete it.
Import the exported MySQL table.
Repair it throgh “REPAIR_TABLE” syntax

“REPAIR [NO_WRITE_TO_BINLOG | LOCAL] TABLE
    tbl_name [, tbl_name] ...
    [QUICK] [EXTENDED] [USE_FRM]”

Optimize it through “OPTIMIZE_TABLE” syntax.

“OPTIMIZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE
    tbl_name [, tbl_name] ...”

Notification: Method 1 is available for those database administrators that have command line permission.

Method 2: Incase, if you don't have MySQL database command line permission then you can repair corrupt MySQL table through phpMyAdmin. It has repair table option.

Method 3: At last but not least, if above two methods fail to repair corrupt/damaged MySQL database table then you can try any third party MySQL database repair utility.

Why should backup Your Oracle database

2011-11-03T22:32:00.000-07:00

Backup is like second life for any database and it is the most important role of database administrator's job. We can replace corrupt software and hardware with new one but without backup, accessing corrupt oracle database is like nightmare. In some cases you can try any third party oracle database recovery software to recover corrupt/damaged oracle database.

“If you lose organization's data, may lose your job”

Schedule to get Backup: you can schedule your routine to get backup of oracle database on daily, weekly and monthly basis. Normally oracle database backup routine depends upon the below factors.

Value of data: High or Low
Transaction Rate
Number of Users
Database Availability
Many Other

Note: If possible, try to consult your database users before deciding a plan.

Methods for Backing-Up: Oracle database offers four methods for backing-up of an Oracle database.

Export/Import
Cold or offline backup
Hot or online backup
RMAN backup

Sometimes backup accomplished by one method is not able to fix the corruption so it is recommended to you to take backup of oracle database by two methods.

Recovery without Backup: Yes, it is possible to recover corrupt oracle database file and its objects without backup. For this, you can try any third party oracle database recovery tool. These tool use advanced scanning algorithm to scan and repair corrupt oracle database file and objects like tables, tablespaces, triggers, views, keys and many more.

Reasons for LOB data corruption and steps to perform MDF File recovery

2011-10-18T21:42:00.000-07:00

Most of the time, we face situations wherein we need to store large amount of data in an SQL Server table. Data isn’t always limited to characters, strings, or numbers. Large data can be categorized as documents, photos, videos, raw files, etc. SQL uses advanced data types for storing bulk of data. LOB data types generally include BLOB (Binary LOB), CLOB (Character LOB), and DBCLOB (Double-byte Character LOB). But, LOB data structures are prone to corruption. As a consequence, all valuable data stored in your SQL database becomes inaccessible. To overcome this problem, you need to go for SQL database recovery through a reliable third-party utility.

For instance, when you run a query that references LOB data, you may come across the following error message on your screen:

“Msg 7105, Level 22, State 6, Line 1
The Database ID 11, Page (255:177), slot 1 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE”

Causes:
Any of these reasons might have caused the above error message:

The query that you ran uses the ‘READ UNCOMMITTED ISOLATION LEVEL’ or the ‘NOLOCK’ query hint.
There is corruption in one of the database pages or the referenced LOB page structure.
An application or database engine error.

This could also lead to complete database inaccessibility. Try using an updated backup to resolve the issue. However, if the backup is unavailable, you should follow the below mentioned resolution steps.

Resolution:
The following steps may help you fix the error:

You can try using DBCC CHECKDB command to fix logical corruption in the database.
If DBCC CHECKDB indicates no problems, rerun the query.
If the problem still persists, download the latest service pack for MS SQL Server.

If the above resolution steps are unable to resolve the issue, take help of efficient SQL database recovery software. These software encapsulate advanced mechanisms to effectively repair corrupt SQL databases and retrieve all precious objects in any SQL database corruption scenario.

How to fix import error in filemaker database

2011-09-09T04:07:00.000-07:00

Filemaker is a cross platform relation database developed by filemaker industry. It offers very advanced graphical user interface that allow database administrator to modify database by dragging new element into the layouts, forms and screens. It also offers a facility for exporting and importing a database into a word file or excel sheet that helps users to maintain the filemaker database.

Let consider a scenario, wherein a database administrator is trying to import a filemaker database into a excel sheet and got an error message…

“FileMaker Pro Error: Object not found”

Cause for error: when a database administrator tries to import a filemaker database into excel sheet by below methods then above error message will be appear.

Click on the data menu and then click on get external data.
Database administrator select import from filemaker pro database.

Resolution: For filemaker pro recovery, export a file in filemaker pro database as a text file and use this text file in excel sheet. A database administrator can perform this operation by following the follow steps:

Go to the filemaker pro and open the filemaker pro database that you want to import.

Go to the file menu and click on the export records.
An export records to files dialog box will be appear.
Choose tab-separated text or comma-separated text.
Put your file name and click on save button.
Go to the specify field order for export dialog box.
Choose individual field under current file and move or select all and export.
Open the save text file in excel sheet and use this file as a filemaker database source.

How to resolve SharePoint Search Error?

2011-09-08T04:36:00.000-07:00

Are you getting bellow error message in windows sharepoint services 3.0?

“Your search cannot be completed because of a service error.
Try your search again or contact your administrator for more information.”

When you open application log on windows sharepoint services 3.0 then got following message descriptions:

Event Type:                 Error
Event Source:             Windows SharePoint Services 3 Search
Event Category:          Gatherer
Event ID:               2424
Date:           26/08/2011
Time:              10:22:30 AM
User:               N/A
Computer:       YourCompuetrName
Description:        The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context:        Application 'Search', Catalog 'index file on the search server Search'

Cause for Error: Above error message generates when service account for the windows sharepoint services search service is configured to use the network service account.

How to Fix: A database administrator can resolve above error message in a non SBS environment by using a configurable account for sharepoint search service account. To do this for sharepoint server recovery follow the given below steps:

Login to the windows sharepoint services 3.0 from an admin account.
Click on Start Button and goto administrative tools.
Click on sharepoint 3.0 central administration.
From central administration page, click on operations.
Goto the services and click on the windows sharepoint services search.
Goto configure windows sharepoint services search service settings on server: servername page and click on configurable.
Place a valid user id and password that has permission to access windows sharepoint services 3.0.
Press OK and done.

How to handle Error ORA-03113 in Oracle Database?

2011-08-22T02:36:00.000-07:00

Oracle database sends an error message ORA_03113 when it found some network problem between client software and oracle server. This error message could not by the SQL*Net.

Possible causes: ORA-03113 error message may be occur due to several reasons. The most possible reasons are:

Oracle server machine crashed.
Your server process was died at the operating system level.
Some network problems.
Oracle database internal problem.
Client handles multiple connection incorrectly.
And many more.

All the connection between client software and oracle server are created and managed by the oracle networking. It is a two connection between the client and server. After the completion of the connection, the above error message may be occur due to connection between client and server may be no longer available.

How to Resolve: A database administrator can fix the above error message by following the below steps:

Fix Oracle server error: If the above error message occurs after the completion of connection then it is a database server problem. In such circumstances, you can see the alert log and connect to the oracle database support team.

Fix Networking server error: This happens when server is not able to response client. It can be occurs due to lack of memory on the server machine or host operating system problem. In such circumstances restart listener using host operating system.

Fix Network connection failure error:This happens when connection through network protocol is no longer available. In such circumstances you can contact your network administrator or can change used protocol.

How to fix corruption in Master database of SQL server 2000?

2011-07-19T01:46:00.000-07:00

Master database is the backbone of SQL server database. It is also known as system database. The file extension for the master database is .MDF. It is not necessary to used .MDF as a file extension for the master database but Microsoft suggest used .MDF as a file extension for the user better understanding. Without master database SQL server does not start. Sometimes master database gets corrupted by the several reasons like meta data structure corruption, virus attach, power failure, hardware problem and many more. At this situation a database administrator is unable to start the SQL server. To start SQL Server database, you will have to restore or repair master database. If you have updated backup of SQL server data files then restore it from backup. If not, then use any advanced third party SQL server recovery software to repair corrupt mdf file.

A database administrator has three options to fix the corruption in master database.

Restore from backup
Rebuild master database
Try any third party recovery software for mdf

Restore from Backup: If you have maintain the backup of master database then restore the corrupt master database and fix the problem. If you don't have backup then go with second option.

Rebuild Master Database: MS SQL server 2000 has an utility to rebuild master database i.e. rebuilddm.exe. It rebuilds the master database in case of emergency. To build the master database follow the following steps:

Shutdown the sql server database
Run rebuilddm.exe from the window command promote
Go to Rebuild master and click browse
Select network directory and click OK
Go to the collation setting and verify the change in master database.
Click rebuild button in the rebuild master dialog box
Start the process

Note: Now you have a new master database. Set the database in emergency mode and attach the new master database to start the SQL server 2000 database.

Try any third party recovery software for mdf: If you are unable to rebuild the master database by second option, then you have another option i.e. third party recovery software for mdf. Most of the third party recovery software is advanced in nature and restore corrupt mdf file in safe location without touching the corrupt database.

How to recover suspect sql server database 2005?

2011-06-21T00:02:00.000-07:00

Microsoft has added a new feature in MS SQL server 2005 that is known as Microsoft SQL server management studio. It provides an integrated environment for the managing, accessing, developing, configuring all component of MS SQL server database. It works with all the SQL server component such reporting services, notification services, integration services. If MS SQL detects any corruption in SQL server management studio then put database in inaccessible mode and database administrator might got some error message like:

“Database ‘msdb’ cannot be opened. It has been marked suspect.”

Cause: When SQL server tries to start and found any of the data file for the database is unavailable then mark database in suspect mode. You can check SQL server error log to verify the cause for the database in suspect mode.

Resolution Options: You have three options for solving the above problem. First option is to restore suspect database second option is to repair database file with DBCC CHECKDB command and last one is to recreate suspect database.

1) Restore from Backup: It is the best option to restore your database which has gone in suspect mode. If you don’t have valid backup then go with second option.

2) Run DBCC CHECKDB: Run this command with repair_allow_data_loss. After running this command you may loss some data.

ALTER DATABASE DatabaseName SET EMERGENCY
GO
dbcc checkdb ('DatabaseName', REPAIR_ALLOW_DATA_LOSS)

If both the above option fails to restore your database, Recreate msdb is the best option for you:

3) Recreate msdb: if you don’t have database backup and DBCC CHECKDB is not working then recreating msdb is the best option for you. Create msdb by the given below methods:

1.Shutdown the server and go to bin folder of sql server in the program files and start sqlserver.exe -c – T3608.
2.Move the corrupt msdb files (master & log) into MSSQL directory.
3.Run instmsdb.sql command in the MSSQL directory.
4.Restart the sql server without T 3608.

Last Minute: Database recreation is not feasible all time. It takes time and money. If you want any other cheap solution for fixing suspect database then you should try any third party repair software for SQL. Third party SQL recovery software works even DBCC CHECKDB command fails and support MS SQL server 2005.

How to rebuild corrupt transaction log?

2011-05-31T02:54:00.000-07:00

In the previous article we have discussed about “how to restore MS SQL database without transaction log file”. In this article we have discussed about how to deal with error 9004 in Microsoft SQL server database. Error 9004 occurs when you try to attach SQL server database and the an error message appears look like

“Error: 9004, Severity: 21, State: 1.
An error occurred while processing the log for database 'employee'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.”

Cause for Error 9004: This error message is related to the corrupt transaction log. It is a general error message that indicates there is some corruption in the transaction log. There can be several possible cause for above error like hardware error, software malfunction, corrupt drivers, SQL server engine problem etc.

Possible Solution: when you got error 9004, you have three options to resolve this error message.

First solution: you can restore from the clean backup to recover SQL server from above problem.

Second solution: if you can not recover from the backup then you can rebuild the transaction log. For creating transaction log, you should follow the given below steps:

Create a new empty database with same name and physical file layout.
Shutdown the SQL server database.
Swap the files in empty database which you want to attach.
If database goes in suspect mode then set database in emergency mode.
Run run DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS.
Fix the issues.

Third solution: You can also try “CREATE DATABASE FOR ATTACH_REBUILD_LOG”. This command will run successfully when you have shutdown SQL server properly.

Note: second solution will pull data as much as possible from the corrupt transaction log but be sure there may be some data loss.

Restore MS SQL Database without Transaction log file

2011-05-30T22:32:00.000-07:00

Microsoft SQL server database is used by the variety of organization because of its advanced features and facilities. It stores all the data in the primary file which is also known as master database file and the file extension for the master database file is .mdf. SQL server also uses secondary database file (next database file) if the size of master database file is very large and the file extension for this is .ndf. All the modification related information is stored in the transaction log file. The transaction log file stores the data related to the modification of the database like insert, delete, update and many more. It is very helpful for the roll back of database if any corruption occurs in the database. Sometimes the transaction log file may be deleted by mistake or intentionally at this situation your database goes in halt situation and does not allow you to do any operation on the database.

you have a problem with your system and you take the backup of mdf file not the log file, and reinstall the SQL server database and try to restore or reattach the database and got an error message

“Can not open backup device.... Device error or device off-line. See the SQL server error log for more details. RESTORE database is terminating abnormally”.

Solution: some of the possible solution is given below

In the above problem looks like just copy the mdf file and try to restore which would no be right, you need to try ATTACH to restore your database.
Run sp_attach_single_file_db command in the query analyzer to attach the mdf. It will automatically create the transaction log file in the same location.
DBCC command for rebuilding transaction load file.

EXEC sp_configure 'allow updates', 1
RECONFIGURE WITH OVERRIDE
GO

BEGIN TRAN

UPDATE master..sysdatabases
SET status = status | 32768
WHERE name = 'MyDatabase'

IF @@ROWCOUNT = 1
BEGIN
COMMIT TRAN
RAISERROR('emergency mode set', 0, 1)
END
ELSE
BEGIN
ROLLBACK
RAISERROR('unable to set emergency mode', 16, 1)
END

GO

EXEC sp_configure 'allow updates', 0
RECONFIGURE WITH OVERRIDE
GO

-- Restart SQL Server at this point.

DBCC REBUILD_LOG('MyDatabase','C:\MyDatabase.ldf')

/*Perform physical and logical integrity checks at this point.
Bcp data out if your integrity checks demonstrate that problems exist.
*/

ALTER DATABASE MyDatabase SET MULTI_USER
GO

-- Set database options and recovery model as desired.
GO

Note: Always keep the copy of master database file in the safe location to avoid the database loss.

After performing the all above solutions and you are still not able to attach the database file that means there are some problem with your master database file, mdf file may be corrupt. At this situation restore your corrupt database from the updated backup. If there is no any updated backup then run DBCC CHECKDB command with proper repair clause if you understand the effect of DBCC CHECKDB. At last but not least you can try any third party SQL server recovery software to repair and restore your corrupt database.

Note: Always try demo version of any third party software first before downing the full version.

Restore Corrupt SQL Database from Replicated Database

2011-05-20T01:45:00.000-07:00

Cross posted on: SQL Recovery | SQL Server Recovery | SQL Database Recovery

Microsoft SQL server offers a technology for improving the database consistency that is known as Database Replication. A database replication is a set of technique for copying and distributing database objects from one database server to another database server. It also maintains synchronization between the databases to improve consistency. You can distribute database or database objects to different location to mobile or remote users by the use of wireless connection, local area network, wide area network or dial-up connection. There are mainly two operations in the database replication, one is writes operation and another is read operation. Database writes are operated at the master database server and then replicated to the slave database server. Database reads are used by the all servers thats improve the database's availability. In case of corruption at the master database server you can restore the database from the slave database server but sometimes slave database server is not able to restore the corrupted database objects. In such situation you should used an advanced SQL server recovery software to restore the corrupt database objects.

Types of Database Replication: There are three type of database replications, which are described below:

Transactional Database Replication.
Merge Database Replication.
Snapshot Database Replication.

Transactional Database Replication: It is basically used in server to server transaction scenarios where throughput is high.

Merge Database replication: This database replication is used in mobile or distributed server applications. Data exchange with mobile users and integration of database from different websites are some example of merge replication.

Snapshot Database Replication: It provides initial data sets for above two database replications.

With above three replication methods, MS SQL server offers flexible and powerful system for synchronization of database or database objects. As discussed above, sometimes these replication methods are not able to restore the corrupt database. In such cases you can use a Microsoft gold certified partner application to fix the problem.

Stellar Phoenix SQL Recovery software is a Microsoft gold certified partner that repairs database objects like tables, triggers, constraints, primary key, unique keys, foreign keys, views, indexes and many more. It supports MS SQL server 2000, 2005, 2008 & 7.0 and compatible with window 2000, 2005, XP, vista, 7.0.

Common Causes of Data Loss

2011-04-28T02:09:00.000-07:00

There is no single most effective way in which to ensure data is protected. The approach to backups and restores depends not only on the organization’s computer and networking resources, but also on the cause and, therefore, the extent of data loss.

The following are the most common causes of data loss.

User Error
Data Corruption
Hardware Failure
Disaster

User Error:- Users most frequently experience data loss limited to one or a few files, usually caused by deleting or overwriting files. If a user’s data is only on the local computer and is not backed up, there is no alternative other than to recreate the data. If the data is on a server, a backup may contain an earlier version of the file, which can be restored. (Mirroring data to another disk is not an effective solution for this problem, since the user’s error will also be replicated.) Unfortunately, locating and restoring single files from a tape backup is a time-consuming and costly process.

Data Corruption:- Software bugs or virus attacks can be limited to corruption of one or a few files, or can affect an entire application and its associated files. Regardless, recovery from this type of data loss requires restoring data and the application from a point in time before the problem. (As before, this precludes mirroring between disks as an option.)

Hardware Failure:- Hardware components (cables, power supplies, system boards, and disk drives) are all susceptible to failure. While some hardware losses simply render the data inaccessible, a disk failure can result in the loss of large amounts of critical data. (Similarly, notebooks are at high risk for complete data loss if stolen.) This type of data can be protected through hardware redundancy and mirroring, a method that not only has the advantage of keeping data available (since failover to the mirrored disk is automatic), but also up-to-date (since the mirrored disks remain synchronized until the point of failure). The disadvantages to this approach are the higher costs associated with hardware replication, as well as greater system administration complexity. For small and midsize organizations, the more common solution is to rely on tape backups and full restores of the disk’s data.

Disaster:- Although rare, losing a site to natural or man-made disaster is nevertheless a measurable risk. In the event of a site disaster, tape backups can provide the most effective means to restore data. Alternatively, if the capabilities exist, remote site replication of data is also an effective means of protection.

Read full article from here

Database Corruption Due to Incorrect Up-Gradation of MySQL Server and the Possible Resolution

2011-04-11T00:43:00.000-07:00

MySQL was developed realizing the need for an advanced database management system that could efficiently handle much bigger databases. Today, it is widely used in various large scale projects and applications. It is an open source database that is mostly used for developing web applications. It includes several distinguished features, such as meta-data locking within transactions, crash recovery, foreign key support etc. which make it a highly reliable and user-friendly database management system.

But users have faced various corruption issues while working with MySQL databases. The possible reasons behind database corruption are improper shutdown of the application, virus attacks, hardware failures etc. Sometimes, corruption can also occur while you try to upgrade your MySQL server to higher versions. Due to this corruption, you may not be able to access any database objects and tables stored in your database. To overcome this problem, you need to go for MySQL recovery through a reliable third-party utility.

For instance, you may receive the following error message while trying to upgrade the MySQL server running on InnoDB engine to MySQL 5.0.27:

"#1033 - Incorrect information in file 'file_name"

Cause: An improper or incomplete update of the MySQL server has resulted in the corruption of some InnoDB tables.

Corruption in some database tables may prevent you from accessing the whole MySQL database. Here, you can use an updated backup to recover database. In case, an updated backup of the database is not available, you should follow the below mentioned resolution steps.

Resolution: You may try these steps to resolve the above error-

Use the check table utility that will help to easily detect corruption and fix the structure of any corrupt InnoDB table.orc

You can also run innodb_force_recovery=4 command

If both the resolution steps fail to solve the problem, you should take help of an efficient MySQL database recovery software. These software repair corrupt database tables created in both InnoDB and MyISAM database engines. They are capable of recovering all the MySQL database components including tables, keys, constraints, views etc. They can also recover data from tables on which auto-increment properties are applied.

Stellar Phoenix MySQL Database Recovery is a comprehensive utility that repairs corrupt MySQL tables created in MySQL 3.x, 4.x, 5.x, and 6.x versions. It continuously writes a log of the recovery process to keep track of the changes made to the database. It compatible with Windows 7, Vista, Server 2003, XP, and 2000.

For more details about how to recover MySQL database visit this: http://www.mysql-database-recovery.com/

Article Source: http://EzineArticles.com/?expert=Mark_Willium

Article Source: http://EzineArticles.com/6075341

MySQL Table Corruption: Possible Causes and Measures to Perform MySQL Database Recovery

2011-03-30T22:47:00.000-07:00

MySQL RDBMS (or Relational Database Management System) provides users the choice of using a variety of storage engines according to their workload. These storage engines are capable of handling different types of tables. MyISAM is the default storage engine used in MySQL which handles non-transactional tables. It facilitates high-speed storage or retrieval and has full text searching capabilities. The MyISAM table is stored in three files on the system hard disk i.e. the data file (.MYD extension), index file (.MYI extension), and the file storing table format (.frm extension). Many times, a MyISAM table gets corrupt due to a number of reasons making all the data records stored there inaccessible. In such situations, you should go for MySQL recovery through a reliable third-party utility to recover back all your precious and invaluable data.

For instance, while trying to save, update, or access a MySQL table, you may encounter the following error message on your computer screen:

"#1034 - Incorrect key file for table; try to repair it"

Cause:
The following reasons may be responsible for the above error message-

An improper system shutdown may interrupt the read or write operation to the database.
A virus or malicious software infection may cause damage to the MySQL tables.
The internal structure of the table may get damaged due to some application errors.
A file system corruption issue may also result in database inaccessibility.

After the occurrence of the above error message, the MyISAM table becomes completely unusable and you will not be able to perform any operation on the table. In this case, you may use a backup to recover MySQL database. However, if the backup is unavailable, try to follow the below given resolution steps.

Resolution:
These steps may help you fix the problem-
Use the 'myisamchk' command line utility with the 'r' option.

'myisamchk -r tablename'
Use the 'mysqlcheck' command-line utility as follows:

'mysqlcheck -r databasename tablename'

If the problem still persists, you should take help of an efficient MySQL database recovery software. These software repair corrupt or damaged MySQL tables to restore various database objects including tables, views, indexes, user-defined functions, stored procedures etc. They create a log report to save all the details about the recovery process.

Stellar Phoenix MySQL Database Recovery is a powerful utility that repairs MySQL tables created in MySQL 3.x, 4.x, 5.x, and 6.x versions. Furthermore, it is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

My name is Mark Willium, currently doing research on how to repair and recover MySQL. MySQL database recovery software repairs corrupt MySQL database.

Article Source: http://EzineArticles.com/?expert=Mark_Willium

Article Source: http://EzineArticles.com/6058522

Oracle recovery software to deal with severe database corruption

2011-03-23T23:52:00.000-07:00

Sometimes, the Oracle database fails to mount and therefore all the data in the database becomes completely inaccessible. The reason can be a possible corruption to the database files because of any virus/malware attack, file system corruption, bad block allocation or any other problem in the structure of the database etc. Whatever be the reason, you need to point out the error location and try to repair Oracle database to get back your precious data. For this, you can take the help of any Oracle recovery software to repair and retrieve various inaccessible database objects.

You were working on some of the tables of your Oracle database and all of a sudden the system shut-down following an power outage. After that, when you tried to mount the database, you failed with a error message on the screen. The message that you received, can be read as below:

“DBV-00200: Block, dba 4289132, already marked corrupted
DBV-00200: Block, dba 4309228, already marked corrupted”

Cause: Though there can be a number of possible reasons behind the occurrence of the error, the most probable cause can be the allocation of a bad block to an Oracle database. Apart from this, the reason may be a serious damage to the database structure because of the power outage.

Resolution: In order to overcome the problem and gain access to your precious database files, you need to look into your backup server for any recent updated backup. You can restore the Oracle database from the valid backup. However, if the backup is old or could not be restored, then, the only way to bring the data back is to run any third-party Oracle database recovery software.

These recovery utilities are developed with innovative search algorithms to repair the troubled Oracle database and recover the views, tables, stored procedures, containers etc. with their original format being intact. Apart from this, these software are completely read-only in their operations and recover dbf without any alteration.

Stellar Phoenix Oracle Database Recovery is an advanced utility to repair the damaged Oracle database and recover various objects (tables, clusters, indexes, procedures. Containers, user defined functions, packages, package body etc.) efficiently. The software works on the files created with Oracle 9i, 10g, 11 g and is compatible with Windows Server 2003, XP. This wonderful Oracle recovery utility provides preview of all the recoverable files and offers you to recover selectively. With attractive graphical user interface and detailed instructions for each step, the software provides an absolute ease of usage.

Powerful MS SQL repair software to repair and recover your corrupt SQL database

2011-02-16T02:23:00.000-08:00

Sometimes, while working in Microsoft SQL, it issues warning messages. A possible database corruption is the reason behind such alarming messages. Though many users ignore such messages and start experimenting with the database, which results in harsher instance of data loss or inaccessibility. Therefore, when your valuable data is lying in the database, handle it with extreme care and it would be wise to use any reliable SQL repair utility to repair the database and recover the data back.

After encountering the error or warning message, which gets flashed every time you try to open the database, the tables in the MS SQL database becomes completely inaccessible. Moreover, repeated occurrence of the error may result in more complex corruption of the SQL database. The error message that you may have come around can be as read as below:

Warning: Page P_ID, slot S_ID in Object O_ID Index I_ID Column COLUMN_NAME value COLUMN_VALUE is out of range for data type "DATATYPE". Update column to a legal value.

Cause:
The above error message tells that the particular column contains an illegal value, which can be caused by any logical or physical corruption of the SQL database.

Resolution:
In order to resolve the above case of database corruption and recover the data back from it, you have to run the command ‘DBCC CHECKDB’ with the recommended repair clause.

However, with severe corruption, this command fails to repair the database and you need to restore the database from any previously created valid backup. But, if you do not have any valid backup available, still you can recover the data by repairing SQL database with the help of any mdf repair software.

These MS SQL repair utilities are innovatively developed applications to successfully repair the SQL database and recover all the data from it. These applications are absolutely read-only in nature and recover database keeping the integrity intact. Moreover, with highly interactive and easy-to-use user interface, any user even without much technical knowledge can use the software and repair SQL database.

Stellar Phoenix SQL Recovery is a heavily used and highly appreciated SQL server recovery utility for its safe and efficient recovery of data from any instance of database corruption. The software is compatible with SQL Server 2008, 2005, 2000 and recovers the database tables, containers, schema, stored procedures etc without even altering their original format. Above all, this wonderful utility incorporates absolutely easy-to-use functionalities and provides a lucid recovery experience.

Absolutely risk-free SQL recovery utility to deal with any instance of database corruption

2011-02-10T03:29:00.000-08:00

In SQL server database, the IAM or Index Allocation Map takes 4GB chunks of space from a single file and gives us the result. These 4GB chunks are called GAM intervals and a single IAM page tracks the spaces from it belongs to a single entity entirely. If files are more than the size 4GB or there are multiple files, then there comes the scene of multiple GAM intervals and the need of IAM chains. IAM chain is a linked-list of the IAM pages, which can track the space allocated to an entire large file. Sometimes, due to certain corruption in the database, the IAM pages can not exhibit the desired results. In such cases, you need to look for any SQL recovery utility to retrieve the SQL server database files back.

You may be at the receiving end of the below error message while working on your SQL Server 2000 database:

“Table error: Could not check object ID XXXX, index ID YYYY due to invalid allocation (IAM) page(s).”

Cause:

From the error message, it is quite evident that any of the IAM pages indicated by different ids has been corrupted.

Resolution:

Run the command DBCC CHECKDB to repair the troubled SQL Server database. Run it without putting any repair clause, so that you can be aware of the level of corruption. With respect to the corruption level, you can give the necessary repair clause.

If the above command fails to repair the database and you are still unable to access the same, then, you can try restoring the database from any previously taken valid backup. But, if backup is not updated or restoration from backup can not be performed because of some unresolved problems, you need to opt for a good MS SQL recovery software to do needful.

These SQL server recovery applications are designed with advanced algorithms to locate the corruption and repair the database efficiently. These mdf database recovery utilities are completely read-only in their operations and retrieves the database objects with their internal structure intact.

Stellar Phoenix SQL Data Recovery is an absolutely risk-free mdf recovery software to recover your SQL server database under any instance of corruption. The software works well on the databases created with SQL Server 2000, 2005, and 2008. Moreover, with efficiency and rich graphical user interface, the utility is compatible with all most all Windows operating systems, including Windows 7, Vista, Server 2003, XP, 2000.

Risk-free Sql Repair Utility To Retrieve Suspect Sql Database Issue

2011-02-06T21:58:00.000-08:00

Sometimes, the Microsoft SQL server can not be able to access one of its database and sets the corresponding bit as something other than normal in the status field of the 'sysdatabases' table. After this, the particular database appears as 'SUSPECT' in the Enterprise Manager of the SQL server. When any database is marked as 'SUSPECT', you may encounter error messages while accessing the same. Moreover, the mounting of the database is halted with the error messages and the database becomes completely inaccessible. Under such situations, in order to bring back your important data from the troubled database, you need to use any utility which can repair SQL.

There can be some sort of corruption to the SQL database which has triggered SQL server to mark it as SUSPECT. In such case, the error message that you receive may be as below:

96/11/18 10:48:32.60 kernel udopen: Operating System Error 32 (The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device,
C:\DATA\SQL\MSDB.DAT (or C:\DATA\SQL\MSDB.MDF)
96/11/18 10:48:32.60 kernel udactivate (primary): failed to open
device C:\MSSQL\DATA\MSDB.DAT (or C:\DATA\SQL\MSDB.MDF) for vdn 127

After the occurrence of the above error message, you will be unable to access the particular SQL database and the error pops up each time you try to access the database.

Apart from the database file corruption, it may be any missing device driver, renaming of the database, changing location of the database file, up-gradation of the operating system etc which can result in the inaccessibility of the database by the SQL server.

Resolution:

Below steps may help you in resolving the problem and help you access the troubled SQL database once again:
If it is the case of missing device driver file, ensure that the file is available.
If it is the case of a sure database corruption, below steps will guide you through the resolution process:
Drop all the indexes of the database and recreate them once again.
After the above step, copy every record from the original database table and paste them into a newly created one.
Update the statistics.
Run the command 'DBCC UPDATEUSAGE'.
Lastly, run the command 'sp_recompile'.

After performing all the above steps, if you are unable to resolve the issue and Enterprise Manager still shows the database as 'SUSPECT', then try to restore the data from any previously taken valid backup. However, if backup is unavailable, then, you need to opt for any SQL repair utility to repair SQL database and retrieve the data back.

Stellar Phoenix SQL Recovery is an absolutely risk-free utility to perform mdf repair from SQL Server 2008, 2005, 2000 and recover backup all your database components back safely. Moreover, this MS SQL repair software is compatible with almost all Windows OS and is very much simple to be used by any user without much technical knowledge.

How to perform SQL database recovery in case of MS SQL Server Error 9004

2011-01-27T02:30:00.000-08:00

A transaction log is an important component of database which is often ignored or overlooked as it is not regularly maintained or used by the database administrators or users. It keeps track of all the changes made to the database and maintains a separate data file to store the actual data. Transaction log backup and the corresponding data file backup can be used to perform database recovery in case of a corruption and restore the database to its original state. But the transaction log may get corrupt due to several reasons, such as installing wrong drivers, virus attack, hard drive failure, system table corruption etc. In such situations, the transaction log may become inaccessible and thus, you may not be able to restore your database. To overcome this problem, you need to go for SQL database recovery through a reliable third party utility.

While trying to access a corrupt transaction log, you may see the following error in ERRORLOG or Windows Application Event Log:

"Error: 9004, Severity: 21, State: 1.

An error occurred while processing the log for database 'mydb'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log."

Cause:

This error may have occurred due to any of the following reasons-

The file system is corrupt.
A hardware error
Damaged drivers
SQL Server Engine problem

The transaction log corruption may also lead to a corrupt database. To recover back your lost data in case of any corruption scenario, you need perform SQL recovery by following below mentioned resolution steps.

Resolution:

Try to restore the transaction log from a backup. If you are unable to recover it from a backup, you may try to rebuild the log and bring it on-line.

Rebuilding of the transaction log should be done carefully as it can result in transactional consistency loss in the database. In all these circumstances, you should take help of a reliable database recovery software in order to recover back your lost valuable data from the corrupt database. These software are capable of repairing those database files as well that are not repaired by the DBCC CHECKDB tool.

Stellar Phoenix MSSQL Database Recovery Software is a recovery utility that repairs and restores MS SQL Server databases from all scenarios of corruption. It supports MS SQL Server 7.0, 2000, 2005, and 2008. It can recover all database components including tables, views, rules, user defined functions, indexes, constraints etc. It performs SQL repair by allowing you to search for the corrupt MDF file in your system.

Resolving Table Error - Object Id O-ID - Possible Bad Root Entry in Sysindexes

2011-01-24T03:23:00.000-08:00

The metadata structure of SQL Server database comprises of numerous Index pages, which further consist of data pages. The data pages at each level of Index page are linked in a doubly-linked list. Inaccessibility of data stored in the data pages primarily occurs due to breaking of linked list (metadata structure corruption). Additionally, it also results in unmountability of the database. Few main reasons for metadata structure damage are improper system shutdown, virus hits, or physical damage. An easy solution to overcome the metadata structure corruption situation, you will need to restore the data from an updated database backup. However, with case studies proving that database users tend to forget to create an updated database backup, it is always handy to take help of third-party sql database repair applications.

Picture a scenario, where you receive the below error message while you attempt to mount your SQL Server database:

"Table error: Object ID O_ID, index ID I_ID. Page P_ID1 is missing references from parent (unknown) and previous (pageP_ID2) nodes. Possible bad root entry in sysindexes."

The result of the above error message is unmountability of your database, which further results in inaccessibility of database records.

Cause

The root cause for the occurrence of above error message is not linking of P_ID1 to the B-tree. The message can be caused either due to hardware or software issues.

Resolution

To resolve the above error message and to access the database records, you will need to follow the below steps:

Change the physically damaged system component with a new system component to resolve all physical damage problems.

Execute DBCC CHECKDB command to resolve logical corruption issues.

While the former resolution proves successful in resolving all physical corruption scenarios, the later fails to resolve all logical corruption issues. For resolving every logical corruption problem, you will need to use advanced SQL Database Repair software. These sql recovery tools repair corrupt SQL database by using advanced scanning and repairing algorithms. Additionally, these applications perform repair without deleting or modifying the original content of the database.

SQL Recovery comprehensively repairs and restores database created in SQL Server 2008, 2005, and 2000 versions. The sql database repair software is designed for Windows 7, Vista, XP, 2003, 2000 and NT operating systems. It repairs almost all database objects, including tables, stored procedures and views, and supports.

Source

Failing to restore SQL Server database backup with internal consistency error

2011-01-21T02:57:00.000-08:00

Here is one of the corruption issue that i came across on the database which was dettached after entering into suspect mode making it difficult to re-use the mdf and ldf file.
Even the database backup they had was taken from SQL 7.0 instance which had corruption. This backup was taken post the database was corrupt.
Below im sharing the information on all the steps that I tried and finally getting the backup work with minimal data loss.

Failing to restore SQL Server database backup with internal consistency error.

ERROR
======
5 percent restored.
10 percent restored.
15 percent restored.
Server: Msg 3270, Level 16, State 1, Line 1
An internal consistency error occurred. Contact Technical Support for assistance.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

Troubleshooting
===============
-- Customer had SQL 7 backup and trying to restore the database and failing to restore and giving some internal consistecny error.
-- It passes all the checks (Verify Header and Filelistonly) however when trying to restore.
-- CU do not have the DB anymore in production.
-- They have mdf and ldf but they were dettached after the database went into suspect mode.

-- Ran Restore headeronly from disk = backup file name, this came with below output.

BackupName BackupType ExpirationDate Compressed Position DeviceType UserName ServerName DatabaseName DatabaseVersion DatabaseCreationDate BackupSize
--------------- ---------- ------------------ ---------- -------- ---------- ------------------------- -------------- ----------------- --------------- ---------------------------------- ----------------------
NULL 1 NULL 0 1 2 515 2009-01-02 13:54:13.000 2516844032

-- Restore Verifyonly -- Gave Valid backup Set.
-- restore filelistonly -- Gave the result.
-- This was giving indication that the backup is good but still it was giving some inconsistency issue.
-- Looks like the Database backup was taken post the database encoutnered corruption.
-- Connected to SQL 2005 instance and try restoring the database from the backup here.
-- We saw that everytime we try to restore the DB using the back file, we saw the DB files getting created but it was failing to complete the restore.
-- Ran the restore using WITH CONTINUE_AFTER_ERROR paramter, this continued file with no errors.
-- This completed fine but it detected inconsistency error below:

5 percent processed.
10 percent processed.
15 percent processed.
20 percent processed.
25 percent processed.
30 percent processed.
35 percent processed.
40 percent processed.
45 percent processed.
50 percent processed.
55 percent processed.
60 percent processed.
65 percent processed.
70 percent processed.
75 percent processed.
80 percent processed.
85 percent processed.
90 percent processed.
95 percent processed.
Processed 307200 pages for database 'DBName', file 'DBName_Data' on file 1.
Processed 1 pages for database 'DBName', file 'DBName_Log' on file 1.
100 percent processed.
Damage to the backup set was detected.
RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible.
RESTORE DATABASE successfully processed 307201 pages in 142.521 seconds (17.657 MB/sec).

-- Checked SQL Server error from file.

2010-03-15 11:41:57.15 spid63 Starting up database 'DBName'.
2010-03-15 11:41:57.20 spid63 The database 'DBName' is marked RESTORING and is in a state that does not allow recovery to be run.
2010-03-15 11:41:58.79 spid63 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2010-03-15 11:42:02.09 spid63 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2010-03-15 11:42:02.24 spid63 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2010-03-15 11:42:32.23 spid63 Error: 3183, Severity: 16, State: 1.
2010-03-15 11:42:32.23 spid63 RESTORE detected an error on page (0:0) in database "DBName" as read from the backup set.
2010-03-15 11:44:12.56 spid63 Starting up database 'DBName'.
2010-03-15 11:44:12.58 spid63 The database 'DBName' is marked RESTORING and is in a state that does not allow recovery to be run.
2010-03-15 11:44:13.22 Backup Database was restored: Database: DBName, creation date(time): 2009/01/02(13:54:13), first LSN: 12375:571:29, last LSN: 12375:582:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\DIR\Backup\DBName_20100310_214921.bak'}). Informational message. No user action required.

-- In SSMS the status of the DB was restoring.
-- Ran --> Restore database with recovery, but failed with below error:

Server: Msg 4323, Level 16, State 2, Line 1
The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

-- Stopped SQL 2005 instabnce.
-- Copied the mdf and ldf file for this restoring state Database.
-- Dropped the DB in restoring state.
-- Tried to CREATE DATABASE DBNAme ON (Filename ='D:\File.mdf') FOR ATTACH_FORCE_REBUILD_LOG
-- This again failed with below error.

File activation failure. The physical file name "F:\Database\DBName\DBName_Log.LDF" may be incorrect.
New log file 'D:\MSSQL\SQL2005\Logs\DBNAme_log.LDF' was created.
Msg 1824, Level 16, State 1, Line 1
Cannot attach a database that was being restored.

-- Here I noticed that the log file was getting created on F Drive and we did not had Drive: F on the box.
-- Mapped another drive with letter F: and created the folder structure, but same error.

-- Tried EXEC sp_attach_single_file_db but failed with

File activation failure. The physical file name "F:\Database\DBName\DBName_Log.LDF" may be incorrect.
The log cannot be rebuilt because the database was not cleanly shut down.
Msg 1813, Level 16, State 2, Line 1
Could not open new database 'DBNameDBName'. CREATE DATABASE is aborted.

-- Now tried the sp_attach_db command but failed again.

EXEC sp_attach_db @dbname = N'AdventureWorks',
@filename1 = N'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\AdventureWorks_Data.mdf',
@filename2 = N'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\AdventureWorks_log.ldf';

Msg 1824, Level 16, State 1, Line 1
Database cannot be restored.

-- Copied the original Data and Log files.
-- And tried attaching the files here.

Msg 1813, Level 16, State 2, Line 1
Could not open new database 'DBName'. CREATE DATABASE is aborted.
Msg 9004, Level 21, State 1, Line 1
An error occurred while processing the log for database 'DBName'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.

RESOLUTION
==========
-- Finally resorted back to Restoring the database from SQL 7.0 backup taken with CONTINUE_AFTER_ERROR paramter.
-- Then ran sp_reset status follwoed by restore with recovery this got the DB in accessible mode and was able to read the table.
-- Ran CHECKDB and this showed inconsistency on user Table.
-- Ran repair and this fixed the corruption, however there was some data loss which could not be recovered.

Article Source

MySQL Server Crash Leads to Database Corruption

2011-01-18T04:01:00.000-08:00

MySQL is a popular and advanced RDBMS (Relational Database Management System) that offers efficient reliability of your precious data. However, in some situations, MySQL server might crash due to some database problems and encounter severe data loss. Corruption renders your database unusable and inaccessible. Application cannot recognize the database. At this point, you need to restore your significant data from the most recent backup. However, if backup is not available, MySQL database recovery becomes need of hour.

When MySQL application crashes, the database becomes un-mountable. At this point, server throws numerous error messages that help you identify the cause of this issue. As a practical example of this problem with MySQL database management system, you might encounter the below error message when you try to mount the database-

"Version: '5.0.20-nt' socket: '' port: 3306 MySQL Community Edition (GPL)

InnoDB: Error: page n:o stored in the page read in is 2719, should be 3383!

InnoDB: Error: page n:o stored in the page read in is 2720, should be 3384!

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 3384.

InnoDB: You may have to recover from a backup.

060725 6:59:18 InnoDB: Page dump in ascii and hex (16384 bytes):"

When this error occurs, you cannot access any of the database records. The issue most frequently occurs with the databases based on InnoDB storage engine and you need to repair MySQL database to get your data recovered.

Root of the issue

You may encounter this behavior of MySQL Server due to database corruption. Corruption might occur due to various reasons, which include virus infection, improper system shutdown, operating system malfunction, user errors, and application crash.

Solution

Try out the below MySQL repair methods to recover MySQL database in such cases-

As stated in the above error message, you can restore database from the most recent backup. It is the most efficient MySQL recovery technique.

In case an adequate and updated backup is not in place, you are required to opt for alternative MySQL database recovery solution, which is to use MySQL repair software.

MySQL recovery software are designed to thoroughly scan entire database and recover MySQL database to a working state. They enable you to repair MySQL database in an easy and safe way with interactive user interface and read-only design.

Stellar Phoenix Database Recovery for MySQL is the most effective solution to repair and restore damaged databases of both InnoDB and MyISAM storage engines.

Resource Taken from: http://www.americanchronicle.com/articles/view/209848

System Table Corruption Causes Data Loss in SQL Server

2011-01-17T04:27:00.000-08:00

Microsoft SQL Server is a reliable and advanced database management system that provides you various database management and SQL database recovery algorithms. DBCC CHECKDB is one of the most advanced SQL Server commands that helps you repair corrupt database. However under some situations, this command fails with an error and cannot repair damaged database. This behavior leads to critical data loss and requires SQL Server recovery to be fixed.

DBCC CHECKDB command may not recover SQL Server database due to various reasons, such as metadata structure corruption, system table damage, and faulty database index. For instance, consider the following error message that occurs when you try to perform MS SQL recovery using DBCC CHECKDB command-

"Database MyDB: Check Data and Index Linkage...

Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8921: [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is corrupt. Check previous errors.

Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in database 'MyDB'.

Microsoft][ODBC SQL Server Driver][SQL Server]repair_fast is the minimum repair level for the errors found by DBCC CHECKDB (MyDB )."

The above error occurs with every parameter of DBCC CHECKDB command, including REPAIR_FAST.

Since the database remains corrupt due to DBCC CHECKDB failure, its records also remain inaccessible.

Cause:

You may encounter this problem if SQL Server database or MDF file has severe logical corruption. DBCC CHECKDB command cannot handle serious corruption and perform MDF recovery.

Solution:

In order to sort out this problem and extract your precious data from inaccessible data, go through the below SQL recovery steps-

Restore MDF file from an updated and valid backup.

If backup is not current, use commercial MS SQL repair software to ensure absolute MDF file recovery.

Such efficient SQL database recovery applications are particularly designed to repair MDF file using advanced SQL recovery algorithms. The MDF recovery software do not demand sound technical skills to repair SQL database as of their interactive MS SQL recovery user interface.

You need not to worry about integrity of your database as MS SQL recovery applications perform safe recovery with read-only conduct. You can use free demo version of these applications to check out their features and functionalities.

Stellar Phoenix SQL Recovery software helps you perform SQL Database recovery for Microsoft SQL Server 2008, 2005, 2000, and 7.0.

Recover Corrupted Oracle Database by Using Data Recovery Advisor

2011-01-13T03:25:00.000-08:00

Latest version of Oracle 11g database come up with a new feature for Database Backup and Recovery. This feature is called Data Recovery Advisor. It is also known as DRA . This new feature helps us to recover the oracle database without any trouble alogwith few RMAN commands.

What is Data Recovery Advisor?
Data Recovery Advisor (DRA) is an oracle database tool that automatically check the loss of data or corruption in the oracle database, it also find the suitable repair options to execute repair at the user's demand. This process reduces the complexity of recovery, therefore the Mean Time To Recover atoumatically reduced.

Given below RMAN commands are used to perform Data Recovery Advisor in oracle database.
List Failure
Advise Failure
Repair Failure
Change Failure
Validate

List Failure:
List failure command gives us information about all failures and the effect of these failures on oracle database operations. Each failure denoted by unique failure number.

Advise Failure:
Advise failure command gives us advise for how to deal with different failures. It also gives us solution for particular failure.

Repair failure:
This Repair failure command gives us rman generated scrits, which restore & recover database from latest oracle database backup.

Change failure:
Change failure command is RMAN command which is used to change the failure priority or status.

Validate: Validate command is used to data integrity checks, block corruption of files and backups in the V$DATABASE_BLOCK_CORRUPTION view.

After performing all the operation of data recovery advisor and still you are unable to start your corrupted oracle database. At this point i would suggest to you try an advanced third party oracle database recovery tool to recover your database.

Stellar Phoenix Oracle Recovery is an advanced dbf recovery software that repairs and recovers dbf file of oracle database. This oracle recovery software recovers indexes, roles, schemas, sequences, synonyms, triggers, table, tablespace and views. Compatible with Windows Server 2003, XP, Vista and Windows 7.

Table Corruption in MySQL Database

2010-12-31T01:41:00.000-08:00

A Request Tracker (RT) enables you to keep a record of all the operations performed in MySQL database. RT creates a session by using a MySQL database, a PERL (Practical Extraction and Report Language) based main engine and front-end web and mail interfaces. However, if RT is unable to store your transactions made into the MySQL component, chances are that your MySQL component is either corrupt or missing. Corruption of MySQL database component can occur due to MySQL database server malfunctioning, operating system failure, malicious software like virus and more. In such situations, you need to recover the MySQL database component by restoring it from the latest backup. But, if you have not maintained any backup or backup falls short of providing the required data, then you should repair your corrupted MySQL component to extract data from it. To do so, you need to use advanced MySQL Database Repair application.

Consider a practical scenario where you encounter the below error message when you attempt to save some changes in session_data table:

“RT couldn't store your session. This may mean that that the directory '/extra/requesttracker/current/var/session_data' isn't writable or a database table is missing or corrupt.”

Cause:

The root cause behind occurrence of above error message is that the session_data table is either missing or corrupt.

Resolution:

To resolve the above error message and access the session_data table, you can follow these steps:

Create a new directory and move the MySQL database to that directory. To do so, follow these steps:

mkdir /extra/var mkdir /extra/var/lib mv /var/lib/mysql /extra/var/lib/mysql ln -sn /extra/var/lib/mysql /var/lib/mysql

Next, you need to restart the MySQL database by using the below command:

service mysqld restart

If you find the table corruption even after moving the database files, then you need to follow these steps to repair the table:

Check the mysql database for the table named “RT4” by using the below command:

mysqlcheck -u root -h localhost RT4 -p

After checking, fix the mysql database table “RT4” by using this command:

mysqlcheck -r -u root -h localhost RT4 -p

Finally, recheck the mysql repaired table “RT4” by using the following command:

mysqlcheck -u root -h localhost RT4 -p

However, if you encounter the same error message even after following the above steps, then you should use advanced MySQL Database Repair software. Such MySQL Repair tools use advanced scanning methods to repair and restore MySQL database objects. With easy-to-use interface and illustrated plus user-friendly documentation, these repair tools are easily to implement. For more details visits:- http://www.repair-mysql-database.com

Article Source: http://www.articlesbase.com/software-articles/table-corruption-in-mysql-database-884040.html

Different error messages that indicate database corruption in MySQL and how to fix them

2010-12-23T03:26:00.000-08:00

The MySQL database is the most used open database in the world as it is fairly reliable, secure, and fast enough to be considered as one of the best database for Web-based applications. Its use in some of the Web sites with most traffic such as Yahoo!, Alcatel Lucent, Flickr, etc is the best testimony one could get. Still, at times these MySQL databases get corrupt due to different issues such as virus infections, several users accessing and modifying the database at the same time, etc. You should use MySQL repair mechanisms to overcome such issues. In the event, it is not possible then you should use a third-party MySQL recovery software to resolve such issues.

When the MySQL table that you are using is corrupt, it may display abnormal symptoms and you would encounter different kinds of error messages. Some of them are:

tbl_name.frm is locked against change
Can't find file tbl_name.MYI (Errcode: nnn)
Unexpected end of file
Record file is crashed
Got error nnn from table handler

Cause:

These error messages indicate that the MyISAM table has damaged and, therefore, unable to function properly. The database corruption could have happened due to the reasons mentioned earlier in this article.

Resolution:

To overcome such database corruption problems, you can perform the following methods one after the another:

Using Check Table: You should use the Check Table command with appropriate parameters to check the validity of the table in question. For this, you can use the following syntax:
CHECK TABLE tbl_name [, tbl_name] ... [option] ...

option = {FOR UPGRADE | QUICK | FAST | MEDIUM | EXTENDED | CHANGED}
Using Repair Table: After detecting errors in the MyISAM table, you should repair the damaged table using the Repair Table command. For this, you can use the following syntax:
REPAIR [NO_WRITE_TO_BINLOG | LOCAL] TABLE
tbl_name [, tbl_name] ...
[QUICK] [EXTENDED] [USE_FRM]

Both of the MySQL in-built methods would be able to check and repair the integrity issues in the MyISAM table. However, if the issues are persisting then you would need to repair MySQL database using a third-party MySQL repair software. The best features of these read-only tools is risk-free database recovery using a rich user interface.

The most recommended MySQL recovery software that recovers data from MyISAM and InnoDB database engines is Stellar Phoenix Database Recovery for MySQL. With the ability to recover different kinds of MySQL files such as .myd, .frm, .ibdata, etc, this MySQL repair utility recovers tables, primary keys, views, etc. In addition, it is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Read More: http://www.articlecompilation.com/Article/Different-error-messages-that-indicate-database-corruption-in-MySQL-and-how-to-fix-them/1060451

Using professional MySQL recovery tool to solve table corruption in MySQL database

2010-12-17T03:10:00.000-08:00

The MySQL database is extensively used as part of the LAMP (Linux, Apache, MySQL, and PHP/Python/Perl) stack. All these applications are very popular because these are freely available, fast, very reliable and secure. For these reasons the applications made on the LAMP stack are hugely preferred for the Web-based applications. But as they say, nothing is perfect in this world. These applications too can get stuck because of table corruption in MySQL databases thereby making all the concerned data inaccessible and insecure. Such instances can appear because of various causes such as abrupt system shutdown, virus infections, file header corruption, etc. You can try out several table repair methods to fix the problem. If you do not succeed in MySQL recovery, then the best option is to use a third-party MySQL repair software.

To relate with this matter, consider a scenario in which you are working on a MySQL table. In this, you try to run a query but it fails to execute. The following error message is displayed after this problem happens:

"MySQL server has gone away"

Cause:

The main causes of this problem are:

The MySQL connection is closed because of server time out.

The query is too large or complex to execute.

You are trying to run the query on the closed connection.

The connection on the client side is closed.

The MySQL table is corrupt.

Resolution:

You can perform the following methods to fix the problem:

Try to establish the connection again with the server and try that query again to ensure whether this is a server-related problem.

Run Optimize Table command. If it shows the following error message, then you should perform the steps given after the error message:

ERROR 1030 (HY000): Got error 28 from storage engine

Add the following line to the my.cnf file:

innodb_force_recovery=4

Stop the MySQL server and restore the backup to the "mysql" folder.

Now restart the MySQL server and try that query again.

It should work fine now.

Well, if the query does not work even now, then there must be a more serious corruption with the MySQL table. In such cases, I would suggest you to take the services of a third-party MySQL repair software to repair MySQL database. These tools use non-destructive algorithms to safely recover MySQL database.

One such efficient tool is Stellar Phoenix Database Recovery for MySQL that repairs various types of MySQL database files. Designed to support MyISAM and InnoDB database engines, this MySQL recovery tool is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

About The Author:

My name is Mark Willium, I have done Ph.D in computer science and currently doing research on how to recover and repair corrupted MySQL database. You can have more information about MySQL database recovery tool by visiting here http://mysql-database-recovery.blogspot.com/

Recover Master File from SQL Server database by SQL Recovery Software

2010-12-08T02:59:00.000-08:00

Structured query language (SQL) is a database computer language designed for managing data in RDBMs developed by Microsoft corporation. It has two primary query languages, ANSISQL and T-SQL. It offers the facility to access SQL Server database from anywhere, be it from your desktop or data center. It also provides combined services to search, query, report synchronize and analyze the database records. Sometimes it may happen that the SQL Server is unable to run. It may possible that the master database of SQL Server has gone damaged. This can be possible because of several reasons such as human errors, virus infections, power outages while SQL Server was open. In that case, you should replace the damaged database with its clean and backup. However, if the backup is not clean and updated then you should use an advanced sql recovery software to recover SQL database.

Consider a case wherein you have Microsot SQL Server installed on your machine. When you try to log on to the SQL Server, you are unable to do and an error message is appered, that is:

"Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online."

Cause:

The possible cause for the above mentioned error message is that the SQL Server database is unable to start the master database. If the tempdb or master database can not be mounted, SQL Server can not run. It is possible that the master database of SQL Server has gone damaged because of various above mentioned reasons.

Resolution:

To solve the above issue, you should first of all, check there is a clean and updated backup of the master database. If yes, then you should replace updated backup with the damaged master database. However, if the database is not clean and updated then you should use a SQL repair tool to perform sql recovery of the damaged master database.

Stellar SQL Database Recovery software is an advanced SQL Recovery tool that repairs and restores corrupted mdf as well ndf files of SQL Server database. This software is able to repair various database components such as tables, stored procedure, defaults, triggers, rules, and views. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Repairing Corrupt SQL Database in MS SQL Server 2000 in Case of Error 8946

2010-12-03T04:15:00.000-08:00

A page header in a database page is the first 24-bytes of the page that contains the general information about the page such as the details about the free space pointers. It is, thus, a significant part of the database page, which can pose problems if it gets damaged. The page header damage is possible in different circumstances such as virus infections, unplanned system shutdown when the database is open, power outages, etc. In such cases, you should repair SQL database using appropriate corrective measures. However, if these methods do not work for the database then you should use a third-party MS SQL repair software to perform SQL database recovery.

Let us consider a situation wherein you are getting the following error message while working on the MS SQL Server 2000 database:

"Table error: Allocation page P_ID has invalid PAGE_TYPE page header values. Type is TYPE. Check type, object ID and page ID on the page."

Cause:

The most possible cause of this problem is that the specified page has an invalid page header, which is raising the mentioned error.

Resolution:

To overcome this problem, you should perform the following methods, preferably in the given sequence:

Addressing the hardware-related issues: Lot of times, such errors are caused due to database corruption due to hardware malfunctioning. You can fix these issues using the following measures:

Fixing the errors that come up after running hardware diagnostics

Checking the Application logs and SQL Server error logs to check if the error has occurred due to hardware corruption.

Swapping the hardware components to isolate the actual reason of corruption.

Installing the operating system after formatting the hard disks to get a fresh system.

Using backup of the damaged database: If the hardware is perfectly in place, then check the status of the database backup. If it is updated and clean, then restore the database using the backup.

Running DBCC CHECKDB: If the previous method does not solve the problem, then you should repair MDF file using DBCC CHECKDB utility with the recommended repair clause.

If you still are not able to fix the error, then you should use a third-party MS SQL repair software to repair the damaged database. These MDF file repair tools use fast and sophisticated scanning mechanisms to repair SQL database without overwriting the existing database.

The most recommended SQL recovery software that recover SQL databases created in MS SQL Server 2008, 2005, 2000, and 7.0, is Stellar SQL Recovery. With the capability to repair SQL databases to recover tables, collations, NDF files, defaults, triggers, etc, this .MDF repair software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

Source: http://www.americanchronicle.com/articles/view/201617

Fixing Error 8947 by recovering damaged MS SQL Server 2000 database

2010-12-02T03:11:00.001-08:00

An IAM (Index Allocation Map) is a page in the database that stores one bit per extent in all the GAM (Global Index Map). A set bit is used to point out that the extent is allocated to that particular index. At times, this convention is not followed as two IAM pages refer to the same GAM interval. Lot of times, this problem is caused due to database corruption, which in turn, can occur because of virus infections, database header corruption, abrupt or unplanned system shutdown, etc. There are several methods that can be used to achieve MDF file recovery. However, if you fail to do so then you should use a third-party SQL recovery software to do the needful.

Let us assume a situation in which you are getting the following error message while working on the MS SQL Server 2000 database:

“Table error: Multiple IAM pages for object ID O_ID, index ID I_ID contain allocations for the same interval. IAM pages P_ID1 and P_ID2.”

Cause:

The root problem of this error is that the IAM chain for the specified index has two IAM pages, P_ID1 and P_ID2, that cover the same GAM interval.

Resolution:

To overcome from such situation, you should perform the following methods, preferably in the given order:

If you still get the same error, then you should recover MDF file with the help of a third-party SQL database recovery software. These tools use highly advances scanning mechanisms to safely recover database without any modifications.

The MS SQL Server recovery software that is recommended by most recovery experts is Stellar Phoenix SQL Data Recovery, which recovers SQL databases created in MS SQL Server 2008, 2005, 2000, and 7.0 versions. Recovering tables, stored procedures, NDF files, collations, defaults, etc, this master database file recovery software is compatible with Windows 7, Sever 2008, Vista, Server 2003, XP, and 2000.

Referrence: http://article-this.com/fixing-error-8947-by-recovering-damaged-ms-sql-server-2000-database/15797

Some Oracle 9i Database Corruption Errors and Tips to Repair Them

2010-11-24T03:45:00.000-08:00

Oracle 9i is a version of the Oracle database wherein the 'i' denotes 'Internet', which means that Oracle 9i is 'Internet Ready'. Because of this characteristic, the Oracle 9i databases provide excellent base for the OLTP (online transaction processing) applications as these are efficient, reliable, and provide secure data management. In addition, this new generation database engine provides the capability to read and write XML statements. All the data is stored in a datafile called a DBF file. Although it is a very secure and robust database system, it may sometimes get corrupt due to various reasons such as file system corruption, media block corruption, operating system corruption, etc. In such scenarios, you should use in-built database repair methods to recover DBF file. If you are not able to fix the problem, then you should use a third-party Oracle recovery software to do the needful.

Consider a scenario wherein you get the following error messages while working on an Oracle 9i database:

ORA-01073: fatal connection error: unrecognized call type
ORA-01079: Oracle database was not properly created, operation aborted
ORA-01099: cannot mount database in SHARED mode if started in single process mode
ORA-01043: user side memory corruption
ORA-01053: user storage address cannot be read

Cause:

The root cause of the aforementioned error messages is that the DBF file may have got corrupt due to the reasons discussed in the introductory paragraph.

Resolution:

To resolve these errors, you should perform several of the repair methods to repair dbf database. They are:

DBVerify: It is used to validate the offline and backup datafiles.
ANALYZE.. VALIDATE STRUCTURE: It is used to verify every data block in the analyzed object.
DB_BLOCK_CHECKING: It is used to check the consistency of the data block.
DBMS_REPAIR: It is used to detect and repair the corruption in the data block.

However, if you are not able to solve the problem even after performing the aforementioned methods then you should use a third-party dbf database repair software. Such read-only tools are able to recover Oracle database without overwriting the original database.

Stellar Phoenix Oracle Database Recovery is a DBF recovery software that is able to repair database from all instances of corruption. It is specifically designed to recover Oracle database created in Oracle 9i. This dbf recovery software is able to various Oracle database components such as tables, views, table spaces, cluster tables, schemas, synonyms, roles, indexes, and sequences. In addition, this oracle recovery tool is able to preserve primary and foreign keys associated with the database tables. It is compatible with Windows Server 2003 and XP.

Anurita Singh work as a freelancer and researcher oracle database repair & repair oracle database software.

Article Source: http://EzineArticles.com/?expert=Anurita_Singh

Tips to Resolve "Page %s-pgid is Allocated" Error Message

2010-11-22T02:53:00.000-08:00

DBCC CHECKALLOC is a common command that is used by database users to check the consistency of disk space allocation. The command comprehensively examines the use and allocation of all pages in your specified database. However, if examining the pages, the command displays an error message, then it means that your database pages have been corrupted or damaged. Furthermore, the data stored in the database becomes inaccessible after the error message appears. An ideal way to access your data in such situations is by restoring the data from an updated backup. But if in case, your database backup has been corrupted or damaged, then you will need to use advance SQL Repair application to repair your database.

As a practical instance, you encounter the below error message when you run DBCC CHECKALLOC command:

"Table error: Page %S_PGID is allocated to object ID %d, index ID %d, not to object ID %d, index ID %d found in page header."

After the above error message appears, the data stored in the database becomes inaccessible.

Cause

The root cause for the occurrence of the above error message is that DBCC CHECKALLOC statement has detected a mismatch in the Object ID between sysindexes and extents. This primarily occurs due to metadata structure corruption.

Resolution

To resolve the above error message, you will need to follow the below mentioned underneath steps:

1.Check the index ID connected with the page number highlighted in the error message to find the error occurred on the index or on table data.

2.Next, restore the database after analyzing the underneath situations:

If the Object ID in the error message contains a value less than or equal to 100, then the system table is corrupted. In such situations, restore the database from a clean backup.

In case, the value is greater than 100, the error is in user table. Restore only the table in such situations.

If the index ID contains a value equal to 1, then you will need to restore the database from an updated backup.

However, if the above steps fail to resolve your issue and the error message still persists, then you will need to use advanced third-party sql repair software to access your database. Such SQL Database Repair applications provide comprehensive database repair by using powerful scanning methods.

SQL Recovery is an impressive sql database repair tool to repair damaged SQL Server 2008, 2005, and 2000 databases after all kinds of logical crash. The read only software provides risk-free recovery of lost components by storing them on a new database file, leaving the original database file untouched.

Adishree Singh work as a freelancer and researcher repair sql & database repair software software. This tool helps to damaged SQL Server 2008, 2005, and 2000 databases after all kinds of logical crash.

Article Source: http://EzineArticles.com/?expert=Adishree_Singh

Table Error Post Metadata Structure Corruption

2010-11-15T03:36:00.000-08:00

MS SQL Server database is build up of various metadata structure components like, pages, extent, etc. Pages are the smallest unit of data storage that store actual data. A combination of 8 adjacent pages makes an Extent. Corruption or damage in metadata structure primarily results in inaccessibility of records stored in your database. In most of the database corruption situation, you encounter an error message stating the cause for the error. For successful access of records stored in your database and overcoming hazards created by error message, an easy way is to restore the database records from an updated backup. But if in case, your backup file has been corrupted, damaged, or unreadable, then you will need to use advanced repair software that can comprehensively repair MDF files.

Consider a practical case, where you encounter the below error message when you attempt to access the records stored in your MS SQL Server database:

"Table error: Extent P_ID object ID O_ID, index ID I_ID is beyond the range of this database."

The above table error message primarily results in inaccessibility of records stored in your database. Furthermore, the error message reappears each time you attempt to access the database.

Cause:

The fundamental reason for the occurrence of the above error message is corruption of metadata structure (in this case, Extents). Extent corruption can occur due to various reasons, such as, improper system shutdown, virus attack, human error, and more. Te corruption can also occur due to various physical damages in your hard drive, like accidental dropping of hard drive, natural disasters, power spikes, and more.

Resolution:

To stop the error message from occurring and to make your records accessible, you will need to use follow underneath steps:

In case of metadata structure corruption due physical crash of hardware, change the old hardware with new one.
For metadata structure corruption caused due to logical crashes, run DBCC CHECKDB command (with recommended repair clause).

After using the above measures, there is a very dim possibility for popping of above error message. However, if it does, you will need to use a powerful mdf repair software to repair your database. These MDF Repair tools are extremely user-friendly as they are built with highly graphical user-interface.

Stellar Phoenix SQL Recovery is a fantastic application to repair mdf file corrupted after any logical crash. The software supports SQL Server 2008, 2005, and 2000 and provides access to all your lost database components, such as, views, triggers, stored procedures, etc.

Adishree Singh work as a freelancer and researcher repair sql & sql repair software.

Article Source: http://EzineArticles.com/?expert=Adishree_Singh

Fixing "Table Error: ... offset 0xADDRESS overlaps with the prior row" Error

2010-11-09T03:43:00.000-08:00

You must have encountered the table error messages while accessing the MS SQL Server database tables. These errors occur because of some integrity issues in the database tables. Sometimes, the integrity issues can take place because of having a corrupt database. And a database can get corrupted because of various internal and external issues such as virus attacks, human errors like improper system shutdown especially when the database is open, sudden power fluctuations, data integrity issues due to mishandling the database such as changing the structure of the database, multiple users trying to change the database table simultaneously, etc. Because of the table errors you can face various problems such as partially or completely inaccessible database, retrieving corrupt records, regularly displaying error and warning messages, and so on. These problems are bound to pose serious threats especially when you are working on a real-time environment. To counter such situations, you can restore the database by overwriting it with its updated backup. However, if the backup is not the updated one then you will have to use the advanced SQL Database Recovery application to repair the corrupt database.

Consider a practical situation wherein you have created a table called "Accounts" in a database. However, when you open the table the following error message is displayed:

"Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, offset 0xADDRESS overlaps with the prior row."

The records in the "Accounts" table become inaccessible once the aforementioned message is displayed.

Cause:

The aforementioned error message occurs when the offset of the S_ID slot is not equal to or greater than the end of the previous slot. And the reason for this is that there is a 'test' table in which the value of the sorted[i].offset is not equal to or greater than the expected value.

Resolution:

To address the mentioned error and in turn, successfully access the "Accounts" table, you can perform the following methods:

Check the SQL Server Error Log to find out if there is any hardware issues that is causing this problem. If it is so, replace the damaged hardware. If it is not a hardware issue, then you need to run the DBCC CHECKDB command without using any repair clause. This way, you can find out the exact repair clause that needs to be applied for the database repair. Then, you can run the DBCC CHECKDB command with that repair clause. However, performing the previous method can result in data loss. So, to avoid any data loss you should take the help of a sophisticated SQL Repair tool. These tools use safe and robust algorithms to repair almost all kinds of corrupt database components.

The Stellar SQL Database Recovery tool recovers and repairs the SQL tables and other components in three steps. The SQL Database Repair tool can be used to recover database components created in MS SQL Server 2008, MS SQL Server 2005, and MS SQL Server 2000. The recovery tool is compatible with various Windows operating systems such as Windows 7, Windows Vista, Windows XP, Windows NT, etc.

About the Author

My name is Mark Willium, I have done Ph.D in computer science and currently doing research on how to recover and repair corrupted SQL database. You can have more information about about SQL recovery software by visiting clicking here http://www.database-recovery-software.blogspot.com/

How to repair Error 8926 in a corrupt MS SQL Server database

2010-10-28T03:32:00.000-07:00

Are you facing problems while working on a particular MS SQL Server 2000 database? If yes, then you should see if the same problem is reproducing on other databases as well. If not, then there are very strong chances that the database is corrupt. It could have become corrupt owing to miscellaneous reasons such as virus infections, malfunctioning of the hardware components, abrupt system shutdown while the database is open, etc. In such cases, you should fix the error by repairing SQL database failing which you should use a third-party SQL repair software.

Let us take a case in which you are getting the following error while working on the MS SQL Server 2000 database:

"Table error: Cross object linkage: Parent page P_ID1, slot S_ID1 in object ID O_ID1, index ID I_ID1, and page P_ID2, slot S_ID2 in object ID O_ID2, index ID I_ID2, next refer to page P_ID3 but are not in the same object."

Cause:

The problem in this case is due to the corruption in the page definitions in the SQL database.

The next page pointers of P_ID1 and P_ID2 pages are pointing each other in an incorrect manner leading to the error.

Resolution:

To address this problem, you would need to repair MDF file. To do this, you shold perform the follwoing methods preferably in the given order:

Fix hardware related issues: As is seen in many instances, such errors occur due to hardware malfunctioning. This can be addressed using the following measures:

Run the hardware diagnostics and try to repair the errors that you

Check the Windows Application log and MS SQL Server Error log to see whether the error has occurred because of any hardware-related problem.

Swap the hardware components to check and find out the exact reason for corruption.

If nothing else works out, then you can reinstall the operating system after formatting the hard disks.

Restore from backup: If the issues is not hardware-related, then you should restore the database from its clean and updated backup.

Run DBCC CHECKDB: In the end, you can choose to repair SQL database using the DBCC CHECKDB command using the appropriate repair clause.

If the problem is persisting, then you should repair the damaged SQL database using a third-party MDF file repair software. These read-only tools are able to repair and restore SQL components without inflicting any damages to the original database file.

The .MDF repair software that is recommended by most of the database recovery experts is Stellar Phoenix SQL Data Recovery. Able to recover SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008, this MS SQL repair software restores tables, NDF files, stored procedures, triggers, etc. In addition, this software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.

My name is Mark Willium, I have done Ph.D in computer science and currently doing research on how to recover and repair corrupted SQL database. You can have more information about about SQL recovery software by visiting my blog http://solution-mdf-file-corruption.blogspot.com/

Access Database corruption Post Software Conflicts

2010-10-26T03:35:00.000-07:00

A program that is installed in your system to interact with host application and perform a specific function is known as a Plug-in, Snap-in, or Add-in. MS Access users use this program to add custom commands and specialized features to save and maintain their database effectively. While installing a plug-in provides lots of benefits, incorrect or incomplete installation can also result into corruption of MS Access database. In such situations, you receive an error message that stops you from accessing the records stored in the database. For systematic access of your database records, a standard way is to restore the records from an updated backup. But, in absence of an updated backup or backup falling short to restore the required data, you will need to opt for an advanced third-party Access Recovery software.

To illustrate this, consider an example where you install a new third party plug-in to improve the performance of MS Access. However, after installing the plug-in, when you attempt to view the records saved in the database, they become inaccessible. Furthermore you also encounter an error message stating the cause for inaccessibility of database records.

Cause:

Few main reasons for the inaccessibility of database records are discussed below:

* Installing a faulty plug-in.
* Improper installation of a plug-in.
* Incomplete installation of a plug-in

Resolution:

To resolve the above error message and to access the database records, you will need to repair the corrupted database using the inbuilt repair utility known as “Compact and Repair”. While the repair utility completely repairs your corrupted database in most of the situations, it fails to repair under below two situations:

* Access database is too large
* Access database is badly corrupted or damaged

If your database remains corrupted due to any of the above situations, then you will need to use a powerful Access Recovery application to repair your database. Such utilities use high end scanning mechanisms to repair your database after any kind of logical crash. These Access Database Repair tools are completely non-destructive in nature and ensure safe recovery of database components.

Recovering Error 136 in MySQL 5.1 in case of index file corruption

2010-10-12T03:53:00.000-07:00

Of the MySQL tables, the MyISAM table is the default table type, which consists of three different types of files: .frm, .myd, and .myi. The MYI file is an important file that is very helpful in keeping the structure of the table. If this file gets damaged or gets full, then you are unable to add more records in the table. You can use appropriate methods to address both types of cases. In case, the table is corrupt then you should use a third-party MySQL repair database to resolve the issue.

Assume a practical situation in which you are working on a MySQL 5.1 (MyISAM) table. There is a power outage and the system shuts down abruptly. After the power is restored, you run a query to add some records in the table. But the query did not run displaying the following error message:

“MySQL error code 136 = No more room in index file”

Cause:

Such errors can occur because of the following reasons:

* The index file (.MYI) file of the MyISAM table has reached its defined limit. Because of this, you are unable to add any further data in the table.
* The MyISAM table is corrupt thereby disabling you from working on the records of the table. It may have damaged because of the abrupt system shutdown.

Resolution:

To perform MySQL recovery of the MyISAM table, you should perform either of the following methods according to the exact reason:

* Use ALTER TABLE command: If the table has reached the stipulated number of records, then you should alter the structure of the table using the 'ALTER TABLE' command. For this purpose, the following syntax can be used:

ALTER TABLE tbl_name MAX_ROWS=xxx AVG_ROW_LENGTH=yyy;

* Use myisamchk tool: If the table has corrupted because of the mentioned reason, then you should use the 'myisamchk' tool to check and repair MySQL table structure. To perform both check and repair in a single command, you can use the following syntax:

shell> myisamchk --silent --force --fast --update-state \

--key_buffer_size=64M --sort_buffer_size=64M \

--read_buffer_size=1M --write_buffer_size=1M \

/path/to/datadir/*/*.MYI

On most occasions, the MyISAM table is recovered using the respective method. However, if the issue is not sorted, then there is a strong case of using a third-party MySQL repair software. With the use of read-only mechanisms and rich user interface, such MySQL database recovery tools make the repair easy and safe.

One of most recommended MySQL repair software is Stellar Phoenix Database Recovery for MySQL, which supports MySQL 3.x, 4.x, 5.x, and 6.x versions. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this database recovery tool repairs MySQL database to recover various objects including tables, views, primary keys, etc.

Source: http://hubpages.com/hub/Recovering-Error-136-in-MySQL-51-in-case-of-index-file-corruption

How To Resolve The Error 2533 In Ms Sql Server 2008 Database

2010-10-06T03:35:00.000-07:00

Are you facing problems while working on an MS SQL Server 2008 database? If yes, then there are chances that there may be some corruption issues in the database itself. These corruption issues can occur due to various issues such as virus infections, human errors, improper and abrupt system shutdown, etc. When you face such problems, you should try to find out the exact cause of corruption and try to resolve the problem. If you are unable to resolve it using any which way, then you should use a third-party MDF recovery software to recover SQL database.

Consider a scenario wherein you encounter the following error message while working on an MS SQL Server 2008 database:

Table error: Page P_ID allocated to object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) was not seen. Page may be invalid or have incorrect alloc unit ID in its header.

Cause:

The root cause of this problem is that a page is allocated to the A_ID allocation unit ID, which does not have the same allocation unit ID in its header.

Resolution:

To resolve this problem, you should recover MDF file. To do this, you should perform the following methods in the given order:

There are the following methods that you can perform to rectify this error message:

Resolve the hardware issues: You should run hardware diagnostics and check the error logs to verify whether this error is hardware related. Try to swap the hardware components or reinstalling the operating system.

Restore from backup: If the problem is not hardware related, then you should check the backup. If it is clean and updated, then you should restore the database from the backup.

Run DBCC CHECKDB: If the backup is not clean or updated, then you should use the DBCC CHECKDB command, first without the repair clause to determine the level of corruption. Then, run it again with the suggested clause. This tool would deallocate the page and rebuild it.

However, if the problem is not solved, then you should use a third-party SQL database recovery software to perform MDF file recovery. Such SQL recovery tools are read-only in nature that do not overwrite the existing database.

Stellar Phoenix SQL Data Recovery is an MS SQL Server recovery software that recovers corrupted SQL databases created in MS SQL Server 2008, 2005, 2000, and 7.0. It recovers SQL database objects such as tables, triggers, records, queries, stored procedures, NDF files, collations, etc. This master database file recovery utility is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Source: http://www.articlesnatch.com/Article/How-To-Resolve-The-Error-2533-In-Ms-Sql-Server-2008-Database/1368247

Basic Overviews of SQL Server

2010-09-22T04:17:00.000-07:00

The smallest unit of database that SQL Server works with is 8Kilobyte (KB). This 8Kilobyte chunk of database is called pages. SQL Server stores data on the disk in pages form. In Memory also SQL Server database manipulates those same 8 Kilobyte (KB) chunks.

Whole record or row must fit within 8KB chunk (page) when data is written to the disk. Sometime a single page can share more than one row. A row cannot span multiple pages. For Example: If an employee table has employee name, address, city, street, house, state, zip, phone then all that combined data must be written in less than a page or 8kilobyte (KB). Few data types like Binary data, LOB of text files and many more which store pointer to the real data can be spread across multiple pages or even in file. All these data are gathered in to the data files on the disk which has either .MDF or .NDF as file extension.

When a SQL (structured query language) is written in the query analyze of SQL Server database then SQL Server's internal query optimizer looks at that query and constructs an execution plan for executing that structured query. SQL Server uses numerous techniques to execute those different queries. Once SQL Server has the plan for execute a particular query, then it executes it and retrieves the needed data information off of the disk. If the data is requested from the client side then the data is sent over the network.

In case of any modification SQL server use modification query (DML) to modify that query. SQL Server firstly modifies the pages of that data in the memory. After the modification has done, it does not write those updated pages (information) directly to the disk, but SQL server makes a copy of the modification query result in a log file called transaction log file. Transactional log file is that file which keeps track of every transaction in the database. Transactional log file has .LDF extension. If SQL sever writes on disk after every modification is fired on the table then it would increase the system load time to write records on to the disk.

Sometimes SQL server database gets corrupted due to some reasons and backup is not updated then whole SQL server database is inaccessible. At that you have to use third party SQL server database recovery software to recover SQL server database.

Resource: http://hubpages.com/hub/Basic-Overviews-of-SQL-Server

Fixing Error 8930 to recover SQL database in MS SQL Server 2000

2010-09-16T05:12:00.000-07:00

The DBCC CHECKDB utility is a useful tool in MS SQL Server databases that enables you to find and repair any kind of issues in the MDF files. There are several kinds of repair clauses that help in repairing different types of problems. However, at times, some of the problems are so rigid that DBCC CHECKDB is unable to repair them. In such cases, you should opt for other MDF file recovery techniques failing which you are advised to use a third-party SQL recovery software to recover MDF file.

Let us assume a situation in which you are running DBCC CHECKDB in an MS SQL Server 2000 database and getting the following error message:

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

Cause:

The primary cause of this problem is that the P_ID1 page is referring to the P_ID2 page in a different page.

Resolution:

To overcome this erroneous situation, the following resolutions can be used, preferably in the given order:

Resolve the hardware related errors: You should, first of all, look for the hardware related errors as most of these errors appear due to hardware malfunctioning. For this, you can perform the following tasks:

◦ Analyzing the error logs to check if the error has occurred due to hardware parts corruption.

◦ Running hardware diagnostics and address the errors that appear.

◦ Swapping the hardware components to isolate on the exact cause of error.

◦ Formatting the hard disks and reinstalling the operating system

Check the database backup and use it: If the hardware parts are absolutely fine, then you should restore the database from the backup provided it is updated and clean.

Run DBCC CHECKDB again: You should run DBCC CHECKDB again with the suggested repair clause to repair the damaged SQL database.

If the problem appears again even after using the aforementioned methods, then this is an obvious case of using a third-party SQL data recovery software. Having a rich user interface and the use of highly advanced scanning mechanisms ensure that the .MDF recovery is safe and secure.

The MS SQL Server recovery software with the best recovery results in the business is Stellar Phoenix SQL Data Recovery, which is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000. Able to recover MDF objects like NDF files, tables, stored procedures, defaults, triggers, collations, etc, this master database file recovery software recovers SQL databases created for MS SQL Server 7.0, 2000, 2005, and 2008.

Resource: http://www.americanchronicle.com/articles/view/185408

Repairing MySQL database when Error 1146 indicates table corruption

2010-09-09T05:18:00.000-07:00

MySQL database is one of most used open-sourced database, which is used by numerous users over the world. Being a free, reliable, secure, and fast-paced database system, it is highly preferred as the backend support for numerous high-traffic and popular web-based applications such as Flickr, Google, You Tube, Yahoo!, etc. For different types of storage needs, it offers different kinds of database engines such as InnoDB, MyISAM, etc. However, at times these tables do get corrupt due to various reasons including virus infections, abrupt system shutdown, bugs in the current MySQL version, etc. In such cases, there can be different methods to provide the workaround. If these methods do not work, then you should use a third-party MySQL repair software to repair MySQL database.

Consider a situation in which you start the MySQL 5.1 server by starting the 'mysqld' process. However, the following error message is displayed and the server does not start:

"Default storage engine is not available."

You reinstall the MySQL server without removing the data directory. Next time, when you try to access any MySQL database table, you are unable to do so. The following error message is displayed this time around:

"ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist"

Here, 1146 refers to the error code.

42SO2 refers to the five-character SQL state.

Cause:

Such erroneous situation occurs when the MySQL table that you are using is corrupt.

Resolution:
AdsSpy: 28 sites by this AdSense ID

To repair MySQL database in such case, you should perform either of the following methods:

Use updated backup: First of all, you should check if there is any clean and updated backup of the MySQL table. If yes, then restore the table with the backup.

Use Repair Table tool: If the backup is not up-to-date, then you should try to repair MySQL table using the Repair Table tool with either 'QUICK' or 'EXTENDED' repair clause. This tool can be used in the following syntax:

REPAIR [NO_WRITE_TO_BINLOG | LOCAL] TABLE

tbl_name [, tbl_name] ...

QUICK] [EXTENDED] [USE_FRM]

The situation will be resolved using the aforementioned solution, however if the problem persists then this situation calls for the use of a third-party MySQL recovery software. These MySQL repair tools are highly interactive and the use of non-destructive repairing mechanisms enable easy and safe recovery of MySQL tables.

In such situations, I would suggest you to use Stellar Phoenix Database Recovery for MySQL, which works for MySQL 3.x, 4.x, 5.x, and 6.x versions. With the ability to repair MySQL database created for various database engines including MyISAM and InnoDB, this MySQL repair utility recovers several objects like tables, views, primary keys, etc. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this MySQL recovery software recovers MySQL files including .ibdata, .ibd, .myd, .myi, and .frm.

Source taken from here: http://www.americanchronicle.com/articles/view/183620

Application Or Server Crash Causes Mysql Database Corruption

2010-09-07T03:01:00.000-07:00

Every version of MySQL RDBMS is launched after testing on various platforms. However, it can not be guaranteed that it does not have any bug. The application may have various bugs that are pretty difficult to discover. You may see various symptoms of these bugs, which include frequent application crashing and system freezing. Application crash like problem may damage the precious data in your database and lead to severe data loss. In such situations, MySQL recovery becomes need of hour to get your precious data back.

The very first step that you need to take to find out the cause of application crash is, check whether the mysqld server dies or the problem is associated with the client. You can also check how long the server remains up when you execute the mysqladmin version. If mysqld server is dead and rebooted, you can identify the root of this problem by examining error log of the server.

Cause of MySQL Server Crash:

Most of the server crashes are generally caused by the damaged index files of the database or the database itself. MySQL updates files on the hard drive with write() system call after executing any SQL statement and before client is notified regarding the results. Generally server crash doesn't cause database corruption if any of the below conditions are true:

The MySQL server update was killed halfway.

There is a bug in the mysqld server that kills the update.

External applications are manipulating the index files or data files simultaneously to the mysqld without properly locking the tables.

There is a crashed index or data file that holds damaged information which lead to a confused mysqld server.

Data storage code has some bugs. Though unlikely, it is possible. Here you may try changing the database storage engine with the help of ALTER TABLE command.

When database corruption occurs, you have to recover MySQL database from an updated and valid backup to get your mission-critical data back. However, if there is a clean and current backup in place, MySQL repair software becomes need of the hour.

These applications repair MySQL database by thoroughly scanning it using high-end scanning techniques. With simple and attractive graphical user interface, they do not demand sound technical skills to extract corrupt data from MySQL database.

Stellar Phoenix Database Recovery for MySQL is the best database recovery software which ensures perfect recovery of corrupt MySQL database. The software works well with MySQL 5.x and 4.x. It recovers both MyISAM and InnoDB storage engine-based databases.

Resource taken from here: http://www.articlesnatch.com/Article/Application-Or-Server-Crash-Causes-Mysql-Database-Corruption/1360140

Getting table Error 8925 while working on MS SQL Server 2000 database?

2010-09-01T03:10:00.000-07:00

Are you getting some table errors while working on MS SQL Server 2000 database? At times, these errors appear because of database corruption, which can be caused due to various reasons including header corruption in the MDF (Master Database File) file, virus infections, etc. Such corruption issues can make the SQL database vulnerable and may make it inaccessible. In such cases, you should use a third-party SQL database recovery software if you are unable to recover SQL database using any workaround.

Let us have a look at a practical situation in which you are getting the following error message while working on a database table in MS SQL Server 2000:

“Table error: Cross object linkage: Page P_ID1, slot S_ID1, in object ID O_ID1, index ID I_ID1 refers to page P_ID2, slot S_ID2, in object ID O_ID2, index ID I_ID2.”

Cause:

The root cause of this problem is that the P_ID1 page points to a P_ID2 in a different object.

Resolution:

To address this erroneous situation, you should look to recover MDF file. This could be done by doing either of the following methods preferably in the given order:

Fixing the hardware related problems: You should try to resolve the reasons due to which the hardware parts may have become faulty. For this intent, the following measures can be taken:

Checking the error logs to confirm that some error has not occurred because of any hardware related problem.

Checking if write-caching is not enabled for the hard disks. If yes, then contact your hardware provider to the solutions.

Installing the operating system again after formatting the hard disk.

Replacing updated backup with database: If the hardware parts are in perfect situation, then you should use the clean and updated backup to replace the database.

Running DBCC CHECKDB: Lastly, you should run the DBCC CHECKDB utility to recover SQL database with the suggested repair clause.

If the problem is persisting and you are still getting the table errors, then there is a need of recovering the SQL database. For this purpose, I would recommend using a third-party MDF file recovery software. Use of fast and sophisticated scanning algorithms, non-destructive SQL recovery, and rich user interface are some of the salient features of these tools.

Stellar Phoenix SQL Data Recovery is one of the most efficient master database file recovery software, which is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000. With the ability to recover SQL components such as tables, collations, triggers, defaults, NDF files, stored procedures, etc, this MS SQL Server recovery software recovers MDF files created in MS SQL Server 2008, 2005, 2000, and 7.0.

Source: http://hubpages.com/hub/Getting-table-Error-8925-while-working-on-MS-SQL-Server-2000-database

How to recover corrupted SQL Server 2008 database from Error 8974

2010-07-13T05:28:00.000-07:00

Are you using SQL Server 2008 in your organization to carry out enterprise solutions? If yes, then are you experiencing problems in using the database on a regular basis? If this is so, then there are chances that the database may have corrupted because of various reasons. Such reasons could be virus infections, power outages, abrupt system shutdown when the database is open, hardware malfunctioning, etc. In such cases, you should use appropriate corrective measures to repair SQL database. If you are not able to provide any solution, then you should use a third-party MS SQL repair software to do the needful.

Consider a scenario wherein you get the following error message while working on an SQL Server 2008 database:

“Table error: Object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE). The off-row data node at page P_ID1, slot S_ID1, text ID TEXT_ID is pointed to by page P_ID2, slot S_ID2 and by page P_ID3, slot P_ID3.”

Cause:

The root cause of this erroneous situation is that two index records have listed an off-row node as their child node whereas any node can have only one parent node.

Resolution:

To resolve this problem, you should repair SQL database by performing any of the following methods, preferably in the given order:

Check for hardware-related problems: You should check the error logs to find out whether the problem has occurred because of any malfunctioning hardware component. In addition, you can swap the hardware components to isolate the actual cause of error. Lastly, you can also consider to format the hard disks and reinstall the operating system.

Restore from backup: If the problem is not hardware related, then you should restore the database with its clean and updated backup.

Run DBCC CHECKDB: If the backup is not updated, then you should run the DBCC CHECKDB command without any repair clause to determine the corruption level. Then, run it again with the recommended repair clause. This command will delete the off-row data node from P_ID1 and, also, its references from P_ID2 and P_ID3.

After performing these methods, you would not get the similar error. However, if you still find yourself in a similar situation, then you should use a third-party MS SQL repair software to fix the error. Such MDF database repair tools are read-only in nature that do not overwrite the existing database during scanning.

Stellar Phoenix SQL Database Recovery is an SQL Server repair software that repairs SQL databases created in MS SQL Server 7.0, 2000, 2005, and 2008. It is able to recover various database components such as tables, NDF files, stored procedures, queries, triggers, defaults, etc. In addition, this SQL database repair software preserves the relationships among the database tables. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Out-Of-Range and Invalid Data Causes Errors in SQL Server Database

2010-07-08T05:24:00.000-07:00

Are you getting out-of-range or invalid data errors while accessing Microsoft SQL Server database? When you create a table in MS SQL Server, you need to specify the data types, size, and type of values that you can store in particular table. In case you store invalid data in any table, you may face this problem. The problem can also occur if database table is damaged and SQL Server application is unable to read it. This behavior causes data inaccessibility and data loss. At this stage, you are required to opt for SQL server recovery to work around the problem.

Out-of-range or invalid data might get stored in Microsoft SQL Server database table in the older versions for any of the below reasons:

Invalid data is passed by RPC (Remote Procedure Call) event calls made to MS SQL Server.

Invalid data is presented in source when you use bulk-insert mechanisms, like bcp tool.

Other possible reasons of data corrupt has left the table values in invalid sate.

In case you have out-of-range, invalid, or corrupt data in any column of SQL Server database table, you may come across issues depending upon type of the operations you perform against invalid data. But, it is possible to hide invalid data. It is not discovered until the DBCC CHECKTABLE or DBCC CHECKDB command is not executed on Microsoft SQL Server database. Continue from here: http://ezinearticles.com/?Out-Of-Range-and-Invalid-Data-Causes-Errors-in-SQL-Server-Database&id=4591532

Rectifying Error 8906 and repairing corrupt database in SQL Server 2000

2010-07-03T04:22:00.000-07:00

An IAM (Index Allocation Map) page consists of eight page Ids, collectively called mixed page array, and holds the pages that are allocated to the index. The IAM pages are used to optimize the tables by allocating and deallocating storage space. Sometimes the IAM page is not able to perform as expected. Such corruption instances can occur because of various reasons such as hardware malfunctions, virus infections, power outages, abruptly exiting SQL Server, etc. To resolve such situations, you should use appropriate corrective measures. In case, you are not able to recover SQL database then you should use a third-party SQL database repair software to do so.

Consider a scenario wherein you encounter the following error message while working on an SQL Server 2000 database:

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

Cause:

The root cause of this error is that a page that is not reflecting as an IAM page and also not seen in the mixed page array of IAM page. This is quite contradictory as this page has mixed page bit set in its PFS byte.

For resolution of this corruption click here: http://www.programmersheaven.com/user/markwillium/blog/5546-Rectifying-Error-8906-and-repairing-corrupt-database-in-SQL-Server-2000/

Rectifying Error 2578 and recovering corrupted database in SQL Server 2000

2010-07-01T00:24:00.000-07:00

Are you facing problems while working on your SQL Server 2000 database? Are you getting lot of error messages for some tasks that worked fine previously? Or the database is responding too slowly? If all your answers are in YES, then chances are that the database has corrupted. It may have corrupted due to various reasons such as virus infections, power outages, hardware malfunctioning, etc. To resolve such issues, you can perform in-place resolving techniques. If you are not able to address the situation, then you should use a third-party repair sql software to repair SQL database.

Consider a scenario wherein you encounter the following error message while working on the SQL Server 2000 database:

"Minimally logged extents were found in GAM interval starting at page P_ID but the minimally logged flag is not set in the database table."

Cause:

The root cause of this error is that a page of ML_MAP_PAGE was found in the GAM extent. However, in the DBTABLE, the DBT_MINIMAL_LOG_IN bit was not set.

Resolution:

To resolve this error, you need to recover SQL database. To do this, perform the following methods preferably in the given order:

Resolve the hardware issues: You should run hardware diagnostics and check if the problem is because of any faulty hardware component. You can also check the error logs to ascertain this. In addition, you can swap the hardware components to zero in on the actual cause of the problem. If nothing works out, then you can reformat the hard disks and reinstall the operating system to get an altogether fresh system.

Restore from backup: If the problem is not hardware related, then you should check if the backup is clean and updated. If yes, then restore the database from its backup.

Use DBCC CHECKDB: As a last resort, you should run the DBCC CHECKDB command: first without any repair clause to know the extent of corruption and then with the suggested repair clause.

After performing the aforementioned methods, check if you are still getting the same error. In most of the cases, it would not. However, if the error is still not resolved then you should use a third-party SQL database recovery software. Such SQL recovery tools recover SQL database using fast yet sophisticated scanning algorithms.

Stellar Phoenix SQL Data Recovery is an MS SQL recovery software that is able to recover SQL databases from all instances of corruption. It is specially designed to perform SQL recovery for databases created in SQL Server 2000, 2005, and 2008. This SQL repair software successfully recovers various database objects such as tables, queries, stored procedures, defaults, triggers, etc. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

How to recover SQL Server 2000 database from Error 2512

2010-06-30T04:56:00.000-07:00

MS SQL Server 2000 is used to provide enterprise solution in many reputed organizations. The primary reasons behind this are that it is simple to use, scalable for huge databases, provides strong support for demanding situations, etc. However, having said that, the database tables may sometimes become corrupt thereby disabling you to use it properly. Such issues can occur due to virus infections, power outages, damaged hardware components, etc. You should inquire for the cause of the corruption and try to recover SQL database. If you are not able to resolve the issue, then you should use a third-party SQL database recovery software to perform SQL MDF recovery.

Consider a scenario wherein you encounter the following error message while working on an SQL Server 2000 database.

"Table error: Object ID O_ID, Index ID I_ID. Duplicate keys on page P_ID1 slot SLOT1 and page P_ID2 slot SLOT2."

Cause:

The primary cause of this error message is that there are two slots on the database table that share the same keys, including the unique identifiers.

Resolution:

To resolve this erroneous situation, you should recover SQL database. You can do this using the following methods:

Resolving the hardware issues: You should check the hardware components by running the hardware diagnostics. The error logs can also be checked in this method, and you can also consider swapping the hardware components to narrow down on the actual cause. If nothing works out, then you can reformat the hard disks and reinstall the operating system.

Checking the database backup: If it is not a hardware related issue, then you should check the database backup. If it is clean and updated, then you should replace the corrupted database with the backup.

Running DBCC CHECKDB: If the backup option does not work out, then you should run the DBCC CHECKDB command without any repair clause to know the extent of corruption. Then, run it again with the recommended repair clause.

The database would now be fine after using the mentioned methods. However, if you still are facing similar issues then you should use a third-party SQL database recovery software to recover SQL database. Such SQL recovery tools are able to repair corrupted databases without overwriting the existing ones.

Stellar Phoenix SQL Data Recovery is an MS SQL recovery software that recovers logically corrupted SQL databases from all instances of corruption. It recovers various database objects such as tables, queries, stored procedures, triggers, etc. This SQL MDF repair utility is designed to recover SQL databases created in SQL Server 2000, 2005, and 2008. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

SQL Server Database Corruption on Network Storage

2010-06-23T05:11:00.000-07:00

Microsoft usually recommends you to use a SAN (Storage Area Network) or locally attached hard drives to store your MS SQL Server database (MDF or Master Database File) because it optimizes the reliability and performance of Microsoft SQL Server. Use of the network database files (the files stored on NAS [Network Attached Storage] or networked server) isn't enabled for MS SQL Server. However, this configuration may damage your SQL Server database in some cases of system failure. In such situations, you must have an absolute backup of your significant database to extract inaccessible data from it. In the other case, you need to go for master database file recovery solutions to get your valuable data back.

Although, network file support is not enabled by default in Microsoft SQL Server, you can manually configure MS SQL Server to store all your database files on NAS storage server or networked server. The servers, which you employ for this configuration, must fulfill MS SQL Server requirements for write-through guarantees and data write ordering.

When you try to store SQL Server database on UNC or mapped network location can result into any of the below mentioned error messages:

5105 “Device Activation Error.”

5110 “File 'file_name' is on a network device not supported for database files.”

This behavior of Microsoft SQL Server is expected. The Trace file 1807 go around the check and enables you to configure MS SQL Server to store databases on network-based storage devices. Microsoft SQL Server uses the transaction location and related recovery logic to insure transaction database consistency in case of an improper system shutdown or system failure.

SQL Server recovery protocols are based on the capability to write data directly to hard drive so that when database manager receives operating system I/O (Input/Output) write request, recovery system can guarantee that write operation is successful. But, any failure due to hardware or software reasons can cause in total or partial data loss and severe database corruption in case of system failure.

In the event of database corruption, you must employ MDF Recovery solutions to repair and restore the corrupt Microsoft SQL Server database.

You can easily, quickly, and successfully recover MDF file using commercial recovery tools, known as SQL Server recovery software. They offer absolute recovery in all database corruption scenarios, using high-end scanning techniques.

Stellar Phoenix SQL Recovery is the most advanced and efficient utility to repair and restore corrupt MDF and NDF files of MS SQL Server database. The software works well with Microsoft SQL Server 2008, 2005, 2000, and 7.0. It restores all database objects like tables, reports, macros, triggers, stored procedures, and constraints.

How to resolve Error 7984 to repair SQL Server 2008 database

2010-06-17T04:31:00.000-07:00

The DBCC CHECKDB command in SQL Server databases is used to check and repair any inconsistency in the databases. There are many extensions for this command that you can apply in various kinds of situations. However, at times when you this command finds any error on the system tables then it ends abruptly. Such cases can arise due to corruption in the database tables. In such situations, you should employ certain in-built workarounds to get the database repaired. If you are not able to recover the database using these methods, then you should use a third-party SQL database recovery software to recover SQL database.

Consider a scenario wherein you encounter the following error message while working on an SQL Server 2008 database:

"System table pre-checks: Object ID O_ID. Page P_ID has unexpected page type PAGETYPE. Check statement terminated because of an irreparable error."

Cause:

This error occurs during the first phase of the DBCC CHECDB command on the database table. In this phase, a page is found having a different type than the DATA_PAGE type. In the first page, this command does basic checks on the data pages of the system tables.

Resolution:

You can try out different methods to repair the database. They are:

Check for hardware issues: You should check the hardware components and run the hardware diagnostics to ascertain whether the error has occurred because of any hardware malfunctioning. If the problem is quite persisten, then you should swap the hardware components to narrow down on the actual problem. As a last resort, you should try to reformat the hard disk and reinstall the operating system. However, before doing this you should take a complete backup of all your valuable data.

Restore from backup: If the problem is not hardware related, then you should check the backup of the database. If the backup is clean and updated, then you should replace the corrupted database with its backup.

The aforementioned methods will be able to repair the corrupted database and it will able to function as desired. However, if you are still facing the similar symptoms then you should use a third-party SQL Server recovery software. Such read-only tools are able to recover SQL database from all instances of corruption using safe scanning algorithms.

Stellar Phoenix SQL Database Recovery is an MS SQL recovery software that is able to recover SQL databases created in SQL Server 2000, 2005, and 2008. It repairs various database objects such as tables, queries, stored procedures, defaults, triggers, etc. In addition, this ms sql repair software preserves the relationships between database tables. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

How to Resolve 'Error 823' While Accessing SQL Server Database?

2010-06-14T22:19:00.000-07:00

Are you getting 'Error 823' while accessing an SQL Server database or modifying the database? Are you getting various database inconsistency errors while querying SQL Server database? Well, the problem may take place if your SQL Server database is either inconsistent or damaged. In such critical situations, you must have a complete backup to restore data from it. However, the situations may become worse if there is no current backup in place. At this point of time, you have to opt for SQL recovery tools to get your valuable data recovered.

You may come across the below errors in Windows Application Event Log or MS SQL Server ERRORLOG while performing any operation on MDF (Master Database File) of SQL Server:

"2010-03-06 22:41:19.55 spid58 Error: 823, Severity: 24, State: 2. 2010-03-06 22:41:19.55 spid58 The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x000000a72c0000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\my_db.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online."

2009-12-09 04:53:49.170 spid25s Error: 823, Severity: 24, State: 2. 2009-12-09 04:53:49.170 spid25s The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000132000 in file 'D:\tempdb\tempdb_data.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Cause:

The Error 823 may occur due to either SQL Server database corruption or I/O errors in the database. The error usually indicates that that there are some inconsistency in file system or the database file is corrupt.

Resolution:

To recover SQL server database, use any of the below methods:

Run Chkdsk to find file system inconsistency issues and resolve it.

Use DBCC CHECKDB utility to try repairing the damaged database.

If the above methods can not perform MS SQL recovery, You need to use third party applications to repair and restore the damaged database. The MDF Repair software performs safe, quick, easy, and absolute recovery in all MDF corruption situations.

Stellar Phoenix SQL Recovery is the most advanced and efficient utility to ensure absolute recovery of damaged database. The software is designed for Microsoft SQL Server 2008, 2005, and 2000. It restores all the objects of MDF file, such as tables, reports, forms, macros, triggers, constraints, and stored procedures.

Resource: http://www.programmersheaven.com/user/markwillium/blog/5372-How-to-Resolve-Error-823-While-Accessing-SQL-Server-Database/

Resolving Error 5171 in SQL Database

2010-05-24T03:09:00.000-07:00

SQL database corruption can occur due to SQL Server malfunctioning, virus infection, improper system shutdown, hardware failure and many more. Once the MS SQL database gets corrupted, the SQL database become inaccessible. In such situations, use you backup, if there is no backup, the user needs to repair mdf file by using advanced SQL MDF Repair application. Consider a practical scenario, where a user is working on SQL Server 2005 and creating a report. While doing so, the Windows restarts due to power failure. When user restart the system, the SQL database becomes inaccessible. When the user tries to attach the MDF manually, he encounters the below error message:

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

“C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDATABASE.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171)” In such circumstances, the database administrators recommend to attach a single file. However, when the user uses sp_attach_single_db Stored Procedures, the user encounters the following error message:

“Server: Msg 5172, Level 16, State 15, Line 1 The header for file path……\.mdf is not a valid database file header. The PageAudit property is incorrect.”

The above error message encounters due to MDF file corruption. The above issue occurs when the MDF file header gets corrupted or some invalid information is inserted in the header file. All these situations result, inaccessibility of the SQL database. To ensure accessibility of the SQL database, the user needs to recover it by using the latest backup. But sometime user has not created any backup of its database or mdf file, then he needs to perform MDF repair. To do so, user needs to use efficient and effective MDF repair application. Such mdf file repair applications incorporate advanced and powerful scanning algorithms to repair the corrupted MDF file. The mdf recovery software perform systematic scan of corrupted MDF files, repair and restore them in their original format without altering any information.

Resource Link: http://www.goarticles.com/cgi-bin/showa.cgi?C=1973872

Stellar Phoenix SQL Recovery

2010-05-19T04:07:00.001-07:00

Check out this SlideShare Presentation:

Stellar Phoenix SQL Recovery

View more presentations from David Poul.

Tips to resolve “Table error: Object O_ID... page P_ID was not encountered.” Error

2010-05-17T23:00:00.000-07:00

The records in Microsoft SQL Server database can be placed and located in the form of a B-tree. These records are divided into various pages (child pages), each having a unique index page, which is one level up in hierarchy from the child page. Corruption in the hierarchical tree structure (metadata structure corruption) primarily results in loosing the reference of the child page from the Index page. In such situations, the data stored in the database becomes inaccessible. For accessing the data stored in the database, an ideal way is to restore it from an updated database backup. But if in case of absence of an valid database backup, you will need to use advanced MS SQL Database Recovery application to repair your database.

Consider a practical scenario, where you receive the below error message when you attempt to access the records stored in table:

“Table error: Object ID O_ID, index ID I_ID. Parent node for page P_ID was not encountered.”

The above error message makes the data stored in table inaccessible. Moreover, the error message repeatedly repeats every time you attempt to access the records stored in the table.

Cause:

The root cause for the occurrence of the above error message is SQL database corruption due to metadata structure damage.

Note: SQL database can be corrupted either due to logical or physical factors.

Resolution:

To resolve the above error message and to access the table records, you will need to follow the below measures:

To solve all the corruption issues caused due to physical damage, swap the corrupt system component with a new component.
To solve all the corruption issues caused due to logical damage, run DBCC CHECKDB command with correct repair clause.

The first measure is competent enough to resolve all the physical damage issues. The second measure, however, fails to resolve all logical corruption problems. For such situations, the database table can be repaired by using advanced MS SQL Database Repair software. These SQL Server recovery utilities employ effective scanning methods to completely repair the corrupt table after all logical database corruption scenarios.

Resource: http://ezinearticles.com/?Tips-to-Resolve-table-Error---Object-O_id-Page-P_id-Was-Not-Encountered-Error&id=3451876

MySQL Database Table corrupt after running a Procedure

2010-05-17T05:07:00.000-07:00

A procedure is a group of specific set of actions and operations to perform a particular task. These actions consist of various queries that fetch data from various tables connected to a database. While creating and running a procedure makes your work easy, it can also result into corruption of a database table. This occurs when either of the queries in the procedure is fetching records from two tables, one of which is corrupted due to virus infection. In such situations, an ideal way is to delete the virus infected database table and restore the table from an virus-free and latest database backup. However, if in case the database backup is unable to restore the required table or the backup is corrupted/damaged, then you will need to use a third-party MySQL Database Repair application to repair the corrupt table.

Picture a scenario, where you have created a below script to perform certain operation:

· Create Procedure
· Run Procedure
· Drop Procedure

However, after the above script runs, you find that one of your table always gets corrupted. Furthermore, the records stored on that table become inaccessible after it gets damaged.

Cause:

The table gets corrupted if there is query that relates it with another table, which is virus-infected. To prevent the table from being corrupted, you should always scan your database components with an up-to-date anti-virus software.

Resolution:

To resolve the above error message and to repair the table, you will need to run the “myisamchk” command. While the above command repair the table in most cases, it fails to repair the tables in case of severe corruption. For repairing such tables, you will need to use an advanced MySQL Repair application.

Easily downloaded from the Internet, these MySQL Repair applications can repair MYSQL database tables, regardless of their extent of corruption. These tools are primarily incorporated with an interactive user-documentation so that even a novice user can perform the repair task. Such repair utilities use high-end scanning methods to repair the corrupt table and also allow you to restore the repaired table on your desired location.

Ghost Records in MS SQL Server

2010-05-11T21:54:00.000-07:00

The background process of “Ghost Cleanup” in MS SQL database is primarily used to improve the performance of Delete command. This record count of total number of the ghosted records is stored in the header. However, if the record count in the header does not match with the exact number of ghosted records, then you receive an error message. The cause for the error message is corruption of your SQL database records. In such situations, it is always advisable to restore the data from an updated database backup. But if in case, you have not maintained any backup, or the database backup is corrupt, then you will need to repair the database by using advanced SQL Database Repair application.

Consider a practical scenario, where you encounter the below error message while attempting to access your database table:

“Object ID O_ID, index ID I_ID: The ghosted record count (HG_COUNT) in the header does not match the number of ghosted records (G_COUNT) found on page P_ID.”

The same error message appears every time you attempt to access the table records.

Cause:

The root cause for the above error message, as stated in the message, is that the number of ghosted records found on a particular page P_ID is not matching ghosted record count in the header. This mismatch primarily occurs due to SQL database corruption due to logical or physical reasons.

Resolution:

The resolution for the above error message is categorized in two steps:

· In case the SQL database corruption has occurred due to any physical damage of a component, then you will need to replace the component with a new one.

· In case of logical corruption of SQL database, you will need to repair the database using 'DBCC CHECKDB' command, with an appropriate repair clause.

The repair command ensures repair of corrupt database in almost every situation. However, if the command is unable to repair the database, then you will need to use powerful third-party SQL Database Repair application. Such SQL Repair tools repair the corrupt database by using effective repairing procedures. These tools are downloadable from the Internet.

Resource Link: http://www.articlesnatch.com/Article/Ghost-Records-In-Ms-Sql-Server/942477

MySQLD Read/Write Process Interrupted

2010-04-28T21:42:00.000-07:00

MySQL Server (MySQLD) is an important program that executes practically all operations during a MySQL installation. Server is also responsible for managing and accessing records that are saved in MySQL data directory. The MySQL data directory contains all the necessary information, such as, databases, tables, log files, and status files that are required by the user. Interruptions in MySQLD process while it is performing read or write operation on any MyISAM table results into corruption of table. In such cases, the user meets an error message while accessing the table, further resulting in inaccessibility of data saved in that table. To overcome such table corruption error messages, you need to restore your data from an updated backup. However, if no backup of the table is available, then the user needs to repair the table using repair command or by advanced MySQL Repair utility.

Consider a practical scenario, where you run an update command on a MyISAM table. While the MySQLD was performing the updates, it crashed in between due to power outage or some other reasons. However, next time you try to open that table, you encounter below error message:

“Incorrect key file for table: '...'. Try to repair it”

The error message means that the MyISAM table is corrupt. The message repeatedly occurs each time you try to access the database.

The main cause of corruption is killing of MySQLD process while performing a write operation.

To resolve MyISAM table corruption and to access the data saved in it, you need to:

Run 'CHECK TABLE' command to verify the health of MyISAM table.
Next, run 'REPAIR TABLE' command to repair the corrupt MyISAM table.

While the above steps successfully repair most corrupted MyISAM tables, there are still some situations where these steps fail to repair. For such scenarios, you need to opt for an effective third-party MySQL Repair application. A MySQL Database Repair utility provides complete MyISAM table repair using advanced repair algorithms.

Database And Common Database Corruption Reasons

2010-04-19T22:18:00.000-07:00

A database is an integrated collection of the data and records in structured way. The data in a database is organized according to a database model. The most commonly database model is relational model.

There are two types of database systems: relational and flat-file. In flat file database the user specifies the data attributes for one table at a time, storing data independently from application. While relational database, along with the flat file approach, allows the user to specify the information about multiple tables and the relationships among the tables, and often declarative controls over, which bind the table to obey them, particularly called constraints.

The DBMS implementing the relational database approach is called Relational Database Management System (RDBMS). Now at the marketplace there is a range of relational database management systems available such as MS Access, MS SQL Server and MySQL.

MS Access is a RDBMS which uses the relational MS Jet Database Engine. This Microsoft product is used within departments of large and small corporations. MS SQL is also a Microsoft product which implements the query language SQL (Structured Query Language). MySQL has been developed by MySQL AB and offers all the advanced features of a relational database management system.

The advantages like application-data independence, enhanced data integrity, improved security, reduced data redundancy and inconsistency etc. have lead the users to store more and more data on these databases. But side by side the complications to these databases are also growing with the fast pace which are resulting into the database corruption. This is increasing the need of database repair. Some of the common database corruption reasons include:

· Interruptions or crashes during the writing of data.
· Virus hit
· Application malfunction
· Unreliable network connections and hardware
· Hard disk error
· Too many users attempting for editing the database at the same time
· Poor structuring of the software that interfaces with the database

All these reasons have a common impact viz. database corruption and the data loss. The database repair is demanded at the peak level of importance in this case. For mostly all the organizations, they must keep track of the information including their employees, dealers, shareholders, creditors, debtors etc. and the database allows you to mange and use an incredible variety of information easily.

The database allows you to maintain order in what could be a very chaotic environment and possess most of the relevant information of the organization. So corruption of any of the database may result into big loss for the organization and hence an immediate database repair is required in either of the database corruption scenario.

Fortunately, technology has availed us the remedy to this database corruption in the name of database repair software. These software are designed so as to scan the corrupted database and retrieve the data intact. As relationships play the most important role in the relational model, therefore while choosing the database repair software, one should be sure that the software is not going to perform any write operation. Based on the RDBMS you are using, go for the relevant database repair software.

Resource: http://www.database-repair-software.com/blog/database-and-common-database-corruption-reasons/

Resolving Error 8904 in SQL Server

2010-03-24T00:15:00.000-07:00

In SQL Server database, few pages are used to store allocation structures. A GAM (Global Allocation Map) page is the one that has an individual bit for each extent included in the file interval that GAM page maps. Whereas, SGAM (Shared GAM) has similar structure as of GAM but has little difference like in SGAM, each of set bits resembles to an extent, where each of the pages is independently allocated to IAM pages for different indexes. An IAM page also maintains the similar structure as of GAM page, but has one devoted bit for an amount that is allocated to the index (here, the discussed index is the one of which IAM page is a part). But sometimes, you get table corruption errors that show that two different IAM pages have been allocated the same extent. In such situations, you are recommended to immediately restore your data from backup or use third-party SQL Recovery applications to scan and repair such databases.

You might receive the below error with your SQL Server database:

Server: Msg 8904, Level 16, State 2

Extent E_ID in database ID DB_ID is allocated to more than one allocation object.

You might also get error 8913 explaining the details of indexes involved.

The above error indicates that the bits are in state 2 in the specified table, but with two different IAM pages while the same extent is assigned to both of them. These conditions usually arise due to hardware failure reasons.

Solution

· It is suggested to first check your system for hardware failures. To do so, you should run hardware diagnostics, check the application and Windows error logs for the related hardware failure errors.

· To cope up with database issues, use your recent data backup

· If no clean backup is available, you should run DBCC CHECKDB command without using any repair clause. This will determine the extent of corruption and repair clause that should be used. Again run DBCC CEHCKDB but with using suggested repair clause. But the process can delete the corrupted database items while making it error-free.

· To perform safe and effective database repair, you need to use commercial SQL Database Repair utilities. These are designed as read-only applications that you can use to get complete SQL Recovery results.

Resolving “Microsoft Access has detected corruption…” Error Message in MS Access

2010-03-15T03:08:00.000-07:00

Corruption in MS Access database primarily happens due to MS Office malfunctioning, file system damage, operating system malfunction, malicious software like virus and more. Once the database gets corrupted, the data stored in it becomes inaccessible. In such situations, an up-to-date and valid data backup acts as a boon to restore your lost data. But, if you have not maintained any backup or it fails to restore the required data, then you need to repair the corrupted Access database. To do so, you need to opt for advanced Access Database Repair application.

Consider a practical scenario, sometime when you attempt to mount an Access database you meet the below error message:

"Microsoft Access has detected corruption in this file. To try to repair the corruption, first make a backup copy of the file. Then, on the Tools menu, point to Database Utilities and click Compact and Repair Database. If you are currently trying to repair this corruption then you will need to recreate this file or restore it from a previous backup."

After the occurrence of the above error message, the database becomes unmountable making the data saved in the database inaccessible. In addition, you encounter the same error message each time when you attempt to mount the database.

The root cause behind the above error message is database corruption.

To resolve the error message and access the data stored in the database, you need to follow below steps:

1. Create a blank database = “C:\ Recover_db.mdb”
2. Close and exit.
3. Create another blank database and navigate to Modules Tab
4. Click on New and Paste the code provided below:
Dim db As DAO.Database
Set db = DAO.OpenDatabase("C:Corrupt_db.mdb")
Dim xtable As TableDef
For Each xtable In db.TableDefs
If Mid(xtable.Name, 1, 4) <> "MSys" Then
rSQL = "SELECT * INTO [" & xtable.Name & "] IN " & _
"'C:Recover_db.mdb'" & _
" FROM [" & xtable.Name & "]"
db.Execute rSQL
End If
Next xtable
MsgBox "Process Complete."
End Function
5. Go to Menu Tools, select References, and scroll down and Select "Microsoft DAO 3.6 Object Library"
6. Click OK
7. In Module Window Click on Recover_db() Function
8. Check database file names, after proper setup and press the F5 button
9. Tables and data from corrupt database is recovered to new database

Another way to resolve the problem (as stated in the error message) is by using an inbuilt repair utility known as “Compact and Repair.” However, if the inbuilt repair utility fails to repair the database, then you need to use advanced Access Repair application. Such Access Database Repair tools employ powerful scanning algorithms to comprehensively recover and restore all Access (.accdb and .mdb) database files.

Clustered Index Corruption in SQL Server Database

2010-02-24T04:14:00.000-08:00

You may receive the following error messages in SQL Server:

Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1378
Expression: m_offBeginVar < m_SizeRec
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

These error messages mostly receive when the user attempts to insert a column to the existing table through INSERT command. If the applied transaction also retains the foreign key reference to the column, which has been affirmed as the exclusive clustered or non-clustered index key on the table, then this could be the reason of this problem. In this situation, the clustered index gets corrupted or damaged. When the added column attempt gets failed, the clustered index can get damaged and all of the data may become inaccessible.

If the clustered index got corrupt, then, no report will be generated by running the DBCC CHECKDB, but the access performance of the database gets degraded and hence you need an instant SQL recovery through the trustworthy tool and choose the best sql database repair software for better results.

The best way out to repair SQL, is to make use of the third party applications which are well suited for this situation. In fact, they avail a secure MDF recovery and so are recommended for the best part. With the intuitive user interface, this MDF repair utility helps you to work with its easy process.

List Of Few MySQL Error

2010-02-04T02:30:00.000-08:00

1000 -SQLSTATE: HY000 (ER_HASHCHK) hashchk
1001 -SQLSTATE: HY000 (ER_NISAMCHK) isamchk
1002 -SQLSTATE: HY000 (ER_NO) NO
1003 -SQLSTATE: HY000 (ER_YES) YES
1004 -SQLSTATE: HY000 (ER_CANT_CREATE_FILE) Can’t create file ‘%s’ (errno: %d)
1005 -SQLSTATE: HY000 (ER_CANT_CREATE_TABLE) Can’t create table ‘%s’ (errno: %d)
1006 -SQLSTATE: HY000 (ER_CANT_CREATE_DB) Can’t create database ‘%s’ (errno: %d)
1007 -SQLSTATE: HY000 (ER_DB_CREATE_EXISTS) Can’t create database ‘%s’; database exists
1008 -SQLSTATE: HY000 (ER_DB_DROP_EXISTS) Can’t drop database ‘%s’; database doesn’t exist
1009 -SQLSTATE: HY000 (ER_DB_DROP_DELETE) Error dropping database (can’t delete ‘%s’, errno: %d)
1010 -SQLSTATE: HY000 (ER_DB_DROP_RMDIR) Error dropping database (can’t rmdir ‘%s’, errno: %d)
1011 -SQLSTATE: HY000 (ER_CANT_DELETE_FILE) Error on delete of ‘%s’ (errno: %d)
1012 -SQLSTATE: HY000 (ER_CANT_FIND_SYSTEM_REC) Can’t read record in system table
1013 -SQLSTATE: HY000 (ER_CANT_GET_STAT) Can’t get status of ‘%s’ (errno: %d)
1014 -SQLSTATE: HY000 (ER_CANT_GET_WD) Can’t get working directory (errno: %d)
1015 -SQLSTATE: HY000 (ER_CANT_LOCK) Can’t lock file (errno: %d)
1016 -SQLSTATE: HY000 (ER_CANT_OPEN_FILE) Can’t open file: ‘%s’ (errno: %d)
1017 -SQLSTATE: HY000 (ER_FILE_NOT_FOUND) Can’t find file: ‘%s’ (errno: %d)
1018 -SQLSTATE: HY000 (ER_CANT_READ_DIR) Can’t read dir of ‘%s’ (errno: %d)
1019 -SQLSTATE: HY000 (ER_CANT_SET_WD) Can’t change dir to ‘%s’ (errno: %d)
1020 -SQLSTATE: HY000 (ER_CHECKREAD) Record has changed since last read in table ‘%s’
1021 -SQLSTATE: HY000 (ER_DISK_FULL) Disk full (%s); waiting for someone to free some space…
1022 - SQLSTATE: 23000 (ER_DUP_KEY) Can’t write; duplicate key in table ‘%s’
1023 -SQLSTATE: HY000 (ER_ERROR_ON_CLOSE) Error on close of ‘%s’ (errno: %d)
1024 -SQLSTATE: HY000 (ER_ERROR_ON_READ) Error reading file ‘%s’ (errno: %d)
1025 -SQLSTATE: HY000 (ER_ERROR_ON_RENAME) Error on rename of ‘%s’ to ‘%s’ (errno: %d)
1026 -SQLSTATE: HY000 (ER_ERROR_ON_WRITE) Error writing file ‘%s’ (errno: %d)
1027 -SQLSTATE: HY000 (ER_FILE_USED) ‘%s’ is locked against change
1028 -SQLSTATE: HY000 (ER_FILSORT_ABORT) Sort aborted
1029 -SQLSTATE: HY000 (ER_FORM_NOT_FOUND) View ‘%s’ doesn’t exist for ‘%s’
1030 -SQLSTATE: HY000 (ER_GET_ERRNO) Got error %d from storage engine
1031 -SQLSTATE: HY000 (ER_ILLEGAL_HA) Table storage engine for ‘%s’ doesn’t have this option
1032 -SQLSTATE: HY000 (ER_KEY_NOT_FOUND) Can’t find record in ‘%s’
1033 SQLSTATE: HY000 (ER_NOT_FORM_FILE) Incorrect information in file: ‘%s’
1034 -SQLSTATE: HY000 (ER_NOT_KEYFILE) Incorrect key file for table ‘%s’; try to repair it
1035 -SQLSTATE: HY000 (ER_OLD_KEYFILE) Old key file for table ‘%s’; repair it!
1036 -SQLSTATE: HY000 (ER_OPEN_AS_READONLY) Table ‘%s’ is read only
1037 -SQLSTATE: HY001 (ER_OUTOFMEMORY) Out of memory; restart server and try again (needed %d bytes)
1038 -SQLSTATE: HY001 (ER_OUT_OF_SORTMEMORY) Out of sort memory; increase server sort buffer size
1039 -SQLSTATE: HY000 (ER_UNEXPECTED_EOF) Unexpected EOF found when reading file ‘%s’ (errno: %d)
1040 -SQLSTATE: 08004 (ER_CON_COUNT_ERROR) Too many connections
1041 -SQLSTATE: HY000 (ER_OUT_OF_RESOURCES) Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use ‘ulimit’ to allow mysqld to use more memory or you can add more swap space
1042 -SQLSTATE: 08S01 (ER_BAD_HOST_ERROR) Can’t get hostname for your address
1043 -SQLSTATE: 08S01 (ER_HANDSHAKE_ERROR) Bad handshake
1044 -SQLSTATE: 42000 (ER_DBACCESS_DENIED_ERROR) Access denied for user ‘%s’@'%s’ to database ‘%s’
1045 -SQLSTATE: 28000 (ER_ACCESS_DENIED_ERROR) Access denied for user ‘%s’@'%s’ (using password: %s)
1046 -SQLSTATE: 3D000 (ER_NO_DB_ERROR) No database selected
1047 -SQLSTATE: 08S01 (ER_UNKNOWN_COM_ERROR) Unknown command
1048 -SQLSTATE: 23000 (ER_BAD_NULL_ERROR) Column ‘%s’ cannot be null
1049 -SQLSTATE: 42000 (ER_BAD_DB_ERROR) Unknown database ‘%s’
1050 -SQLSTATE: 42S01 (ER_TABLE_EXISTS_ERROR) Table ‘%s’ already exists
1051 -SQLSTATE: 42S02 (ER_BAD_TABLE_ERROR) Unknown table ‘%s’
1052 -SQLSTATE: 23000 (ER_NON_UNIQ_ERROR) Column ‘%s’ in %s is ambiguous
1053 -SQLSTATE: 08S01 (ER_SERVER_SHUTDOWN) Server shutdown in progress
1054 -SQLSTATE: 42S22 (ER_BAD_FIELD_ERROR) Unknown column ‘%s’ in ‘%s’
1055 -SQLSTATE: 42000 (ER_WRONG_FIELD_WITH_GROUP) ‘%s’ isn’t in GROUP BY
1056 -SQLSTATE: 42000 (ER_WRONG_GROUP_FIELD) Can’t group on ‘%s’
1057 -SQLSTATE: 42000 (ER_WRONG_SUM_SELECT) Statement has sum functions and columns in same statement
1058 -SQLSTATE: 21S01 (ER_WRONG_VALUE_COUNT) Column count doesn’t match value count
1059 -SQLSTATE: 42000 (ER_TOO_LONG_IDENT) Identifier name ‘%s’ is too long
1060 -SQLSTATE: 42S21 (ER_DUP_FIELDNAME) Duplicate column name ‘%s’
1061 -SQLSTATE: 42000 (ER_DUP_KEYNAME) Duplicate key name ‘%s’
1062 -SQLSTATE: 23000 (ER_DUP_ENTRY) Duplicate entry ‘%s’ for key %d
1063 -SQLSTATE: 42000 (ER_WRONG_FIELD_SPEC) Incorrect column specifier for column ‘%s’
1064 -SQLSTATE: 42000 (ER_PARSE_ERROR) %s near ‘%s’ at line %d
1065 -SQLSTATE: HY000 (ER_EMPTY_QUERY) Query was empty
1066 -SQLSTATE: 42000 (ER_NONUNIQ_TABLE) Not unique table/alias: ‘%s’
1067 -SQLSTATE: 42000 (ER_INVALID_DEFAULT) Invalid default value for ‘%s’
1068 -SQLSTATE: 42000 (ER_MULTIPLE_PRI_KEY) Multiple primary key defined
1069 -SQLSTATE: 42000 (ER_TOO_MANY_KEYS) Too many keys specified; max %d keys allowed
1070 -SQLSTATE: 42000 (ER_TOO_MANY_KEY_PARTS) Too many key parts specified; max %d parts allowed
1071 -SQLSTATE: 42000 (ER_TOO_LONG_KEY) Specified key was too long; max key length is %d bytes
1072 -SQLSTATE: 42000 (ER_KEY_COLUMN_DOES_NOT_EXITS) Key column ‘%s’ doesn’t exist in table
1073 -SQLSTATE: 42000 (ER_BLOB_USED_AS_KEY) BLOB column ‘%s’ can’t be used in key specification with the used table type
1074 -SQLSTATE: 42000 (ER_TOO_BIG_FIELDLENGTH) Column length too big for column ‘%s’ (max = %d); use BLOB instead
1075 -SQLSTATE: 42000 (ER_WRONG_AUTO_KEY) Incorrect table definition; there can be only one auto column and it must be defined as a key
1076 -SQLSTATE: HY000 (ER_READY) %s: ready for connections. Version: ‘%s’ socket: ‘%s’ port: %d
1077 -SQLSTATE: HY000 (ER_NORMAL_SHUTDOWN) %s: Normal shutdown
1078 -SQLSTATE: HY000 (ER_GOT_SIGNAL) %s: Got signal %d. Aborting!
1079 -SQLSTATE: HY000 (ER_SHUTDOWN_COMPLETE) %s: Shutdown complete
1080 -SQLSTATE: 08S01 (ER_FORCING_CLOSE) %s: Forcing close of thread %ld user: ‘%s’
1081 -SQLSTATE: 08S01 (ER_IPSOCK_ERROR) Can’t create IP socket
1082 -SQLSTATE: 42S12 (ER_NO_SUCH_INDEX) Table ‘%s’ has no index like the one used in CREATE INDEX; recreate the table
1083 -SQLSTATE: 42000 (ER_WRONG_FIELD_TERMINATORS) Field separator argument is not what is expected; check the manual
1084 -SQLSTATE: 42000 (ER_BLOBS_AND_NO_TERMINATED) You can’t use fixed rowlength with BLOBs; please use ‘fields terminated by’
1085 -SQLSTATE: HY000 (ER_TEXTFILE_NOT_READABLE) The file ‘%s’ must be in the database directory or be readable by all
1086 -SQLSTATE: HY000 (ER_FILE_EXISTS_ERROR) File ‘%s’ already exists
1087 -SQLSTATE: HY000 (ER_LOAD_INFO) Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld
1088 -SQLSTATE: HY000 (ER_ALTER_INFO) Records: %ld Duplicates: %ld
1089 -SQLSTATE: HY000 (ER_WRONG_SUB_KEY) Incorrect sub part key; the used key part isn’t a string, the used length is longer than the key part, or the storage engine doesn’t support unique sub keys
1090 - SQLSTATE: 42000 (ER_CANT_REMOVE_ALL_FIELDS) You can’t delete all columns with ALTER TABLE; use DROP TABLE instead
1091 -SQLSTATE: 42000 (ER_CANT_DROP_FIELD_OR_KEY) Can’t DROP ‘%s’; check that column/key exists
1092 -SQLSTATE: HY000 (ER_INSERT_INFO) Records: %ld Duplicates: %ld Warnings: %ld
1093 -SQLSTATE: HY000 (ER_UPDATE_TABLE_USED) You can’t specify target table ‘%s’ for update in FROM clause
1094 -SQLSTATE: HY000 (ER_NO_SUCH_THREAD) Unknown thread id: %lu
1095 -SQLSTATE: HY000 (ER_KILL_DENIED_ERROR) You are not owner of thread %lu
1096 -SQLSTATE: HY000 (ER_NO_TABLES_USED) No tables used
1097 -SQLSTATE: HY000 (ER_TOO_BIG_SET) Too many strings for column %s and SET
1098 -SQLSTATE: HY000 (ER_NO_UNIQUE_LOGFILE) Can’t generate a unique log-filename %s.(1-999)
1099 -SQLSTATE: HY000 (ER_TABLE_NOT_LOCKED_FOR_WRITE) Table ‘%s’ was locked with a READ lock and can’t be updated
1100 -SQLSTATE: HY000 (ER_TABLE_NOT_LOCKED) Table ‘%s’ was not locked with LOCK TABLES

Killing INSERT … SELECT Can Corrupt MySQL Table on MyISAM

2010-01-29T23:01:00.000-08:00

The MySQL INSERT … SELECT command allows you to insert several rows into a table from various tables. But at times, when you kill the command on MyISAM, you observe that the table gets corrupt. Such type of errors usually occur with large data sets. When you run CHECK TABLE command to check the table for consistency, it reports that the table is unusable as it is corrupt. The table thus corrupted should be restored from backup or you can alternatively use MySQL repair tools that are competent products to allow safe repair of database and its objects.

To illustrate the same, consider that you use a table with name 'a' on MyISAM storage engine'. You execute INSERT … SELECT command and kill it while it is running. After this, you use CHECK TABLE command to perform the sanity check of the table and come across errros similar to:

Table Op Msg_type Msg_text
test.a check warning Table is marked as crashed and last repair failed
test.a check warning Size of indexfile is: 1337344 Should be: 1024
test.a check error Record-count is not ok; is 92522 Should be: 0
test.a check warning Found 92522 key parts. Should be: 0
test.a check error Partition pMin returned error
test.a check error Corrupt

Cause

The error indicates that the table has got corrupt. When you kill the INSERT … SELECT statement, which is being applied on the table with indexes and contains large amount of data, it might get corrupt. This occurs when we disable the indexes for the purpose of fast insert. After the bulk_insert operation is completed, indexes are tried to be re-enabled. While MySQL is re-enabling the indexes, killing the query results into aborting the repair table operation and hence the table gets corrupt.

Solution

Use any of these methods to repair the corrupted MyISAM table:

· You can use the following command to repair:

REPAIR TABLE table_name

Where, table_name is the name of corrupted table

· Use MySQL Recovery tools for achieving best and safe repair results. MySQL Recovery tools are fully-competent database recovery utilities built with powerful scanning technology and easy to use interface.

Tips to resolve Run Time Error 3800 message in MS Access 2002

2010-01-26T21:51:00.000-08:00

Tables in MS Access database are the primary storage components to store user's records. While this database component is easy to open, there are possibilities that when you attempt to open the tables, an error message pops up. This error message does not allow you to access any records saved in the tables. In such situations, an ideal way is to restore the tables from an updated backup. But if in case, no backup is available or backup falls short to restore the records, then you will need to use advanced access repair software.

As a practical example, you encounter any of the below error messages when you attempt to view records saved in Finance table:

“Error 3800: AOIndex is not an index in this table.”

Or

“Run-Time Error '3058' Index or
Primary key cannot contain a null value”

You encounter the same error message every time you attempt to open the Finance table. Furthermore, the data stored in the Finance table becomes inaccessible after the above error message appears.

Cause:

The above error message primarily occurs due to damage or corruption of index in system table.

Resolution:

To resolve the above run time error message, you will need to repair the Finance table by using an inbuilt repair utility named “Compact and Repair”. Below are the steps that enable you to repair the table:

1. You will need to select Database utilities on the Tools menu, and then click Compact and Repair Database.
2. Next, click the database in the ‘Database to Compact From’ dialog box, and then click Compact.
3. Lastly, you will need to select a correct folder location for the new file in the ‘Compact Database Into’ dialog box, type a unique name for the file, and then click on Save.

But, if in case the above utility falls short to resolve your problem, Access Repair software comes to rescue. Such access database repair utilities incorporate advanced scanning algorithms to repair corrupted or damaged Access database components. These tools are built with highly graphical user-interface and easily understandable even by a home user.

How to Resolve SQL Server Error 8961?

2010-01-17T20:51:00.000-08:00

The rows of a SQL Server table are divided into partitions that are numbered from 1 to n. By default all rows are consisted in a single partition, however one can also define the size of partition. All rows of partition are stored as a B-tree or heap structure. The actual data is stored in leaf nodes of leaves (called text data node), while rest other nodes (called text index nodes) are used to store index values for leaf node. But sometimes, you observe table inconsistencies because of mismatch between one or more child nodes and their corresponding parent nodes. As a result, you receive table corruption errors. Such situations need to be resolved using DBCC CHECKDB command, backup or commercial SQL recovery utilities.

You might encounter the following error with your SQL Server database table:

Server: Msg 8961 , Level 23, State

Table error: Object ID O_ID. The text, ntext, or image node at page P_ID1, slot S_ID1, text ID TEXT_ID does not match its reference from page P_ID2, slot S_ID2.

Where, ‘state_number’ might be 1, 2 or 4.

Cause

SQL Server displays error 8961 when it finds mismatch between child node and parent node and corruption in a text object. Specifically, you might infer the exact cause of error message by the ‘state_number’ it is displaying:

State 1: It occurs when timestamps in node and parent don’t match with each other.

State 2: The child node is text data node and has greater size as what is supposed by its parent. It might also occur if the child node is text index node and has different size as what is supposed by its parent.

State 4: The child node is actually a text index node, but its parent supposes it to be a text data node or vice-versa. This might also occur due if the level of child node is different from what is supposed by its parent.

Solution

In order to solve such problems, you should follow these steps:

• Check your system for possible hardware problems

• Restore database from clean backup, if available

• Execute DBCC CHECKDB command without using repair clause if no valid backup is available. Again run DBCC CHECKDB but with the repair clause suggested by the previous check

• Running DBCC CHECKDB causes data loss. Thus, for safe SQL Repair, use third-party database repair applications. These SQL Recovery tools are built with powerful technology to safely scan and repair a damaged SQL Server database.

For More Information Visit: http://sqlrecoverydatabase.blogspot.com/2009_07_01_archive.html

Troubleshooting Sql Server Error 2579

2009-12-30T22:49:00.000-08:00

SQL Server database pages are 8 KB in size, each designated with a specific ID. The application uses extents as the basic unit to allocate space for tables and indexes. If these structures suffer any sort of corruption related concerns, you can run DBCC CHECKDB command to detect it. You can deduce the exact cause of the problem from SQL Server log that records all the results of running the command. However, to restore the corrupted table, you will need to use your current backup. But at times, you find issues while restoring from backup because it doesn't exist in valid state. You need to use SQL repair software in such problems to repair the corrupt database and its objects.

Consider an instance, you run DBCC CHECKDB command to check database consistency and come across the below error message in SQL Server error log:

“Table error: Extent P_ID object ID O_ID, index ID I_ID is beyond the range of this database.”

This entry is marked with error ID 2579 and severity level 16.

Cause

Each page ID is referenced in the form- fileId:pageInFile. In the error message above, P_ID is the ID of the affected page in the table. Error 2579 occurs if pageinfile of the extent is found to be greater than the expected physical size of the file with ID fileID specified in the database. The error indicates that the extent has been allocated in an IAM page for the indicated index ID or object.

Solution

Following are the solutions to fix the above problem:

Such errors might be frequent due to hardware related problems. So, you should diagnose the system for the same and remove or replace the faulty hardware.
Restore the database table from backup.
Execute DBCC CHECKDB command to determine the repair clause that should be run to repair the database table. Next, run the suggested repair clause with DBCC CHECKDB command
If applying the above measures is not feasible, you need to use third-party SQL Recovery software. SQL Repair products are commercial tools embedded with high-end scanning algorithms and graphically rich user interface to allow safe and efficient database repair.

SQL Recovery is a premier and popular tool to repair damaged SQL databases that is supportive to SQL Server 2008, 2005 and 2000. With self-descriptive and exceptionally realistic interface, advanced repair options and non-destructive design, it is a fully-featured SQL Recovery utility to repair all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.

Index File Crashed in MySQL Table and Recovery

2009-12-29T01:55:00.000-08:00

In MySQL databases, an index refers to the copy of one part of a table. Because of indexes when you perform an operation on tables, you get fast results. You can create these indexes on one or more table columns. But at times, these indexes get corrupt due to software or hardware faults. Such issues make the critical information stored in the MySQL database inaccessible. In such cases, you need to repair the MySQL database table. However, if the repair attempt fails and you don’t have a valid data backup, you need to use powerful MySQL repair utilities.

You might encounter the below error message with your MySQL database:

“126: Index file is crashed / Wrong file format”

After the occurrence of this error message, you face issues while accessing the table.

Cause

The above error message gets encountered due to the corruption of index file. As a result of which, when you attempt to run any query, it aborts unexpectedly as it can’t find the path to proceed. Index corruption can occur due to improper table locking, unexpected shutdown, application errors and other similar reasons.

Solution

To solve this issue, you need to follow these steps in sequence:

* First, you need to check MySQL table corruption. You can use CHECK TABLE statement, mysqlcheck command-line utility or myisamchk command-line utility. The latter two utilities can only be used with MyISAM tables and not with InnoDB tables. The basic syntax of these commands is as follows:

CHECK TABLE tablename

mysqlcheck dbname tablename

myisamchk dbname tablename

You can use appropriate options with them.

* If you experience errors related to table corruption, you need to repair the affected table. To accomplish the same, you can use REPAIR TABLE command as below:

REPAIR TABLE tablename

You can also use mysqlcheck or myisamchk command-line utilities, but only for MyISAM tables.

* If you continue to receive the same error messages, repair is beyond the scope of above utilities. Thus, you need to use an updated data backup to restore the complete database. But if no backup is available or the present backup is not valid to restore the lost data, you need to repair the damaged database with MySQL recovery applications. These are special tools that use powerful scanning algorithms to safely repair and restore MySQL database components.

Resource Link: http://www.repair-mysql-database.com/blog/

Module Corruption in MS Access database

2009-12-21T23:14:00.000-08:00

Modules in Microsoft Access are the storage components that store all the code required to perform different functions in your database. These Modules are primarily created by the programmers for making their routine tasks re-usable. In most cases, these MS Access modules are associated with reports and forms. Although compiling the code saved in Modules is a trouble-free task, corruption in database might occur when you attempt to edit the code while the Module is running. In such situations, the data stored in the database becomes inaccessible. To surmount the dangers created due to Access database corruption, a standard way is to restore the data from an updated backup. However, if the backup is corrupted or backup falls short to restore the required data, then you will need to use an advanced access database repair software to repair the corrupted database.

For example, you created a module and while compiling (in break mode) it, you changed its code. The compilation process halts and you encounter an error message. The error message indicates MS Access database corruption.

Cause:

The error message occurs because the MS Access gets confused between the below categories of your code:

Text-version of the code
Text-version of the temporary copy
Actual version of the code that is running

Note: Please avoid changing the Module code while it is running.

Resolution:

To resolve MS Access database corruption, compact and repair your database using below steps:

Choose “Database Utilities” on the Tools menu. Click on Compact and Repair Database option.
Choose the database file in the ‘Database to Compact From’ dialog box that you want to repair. Click on Compact.
Select a new folder destination for the new file in the ‘Compact Database Into’ dialog box.
Assign a unique, valid, and new name for the database file. Finally, click on Save.

The above steps repair your database in most situations. However, if database corruption persists and you are not able to access the database records, then you will need to search for powerful access recovery application. These Access Database Repair tools are competent enough to resolve corruption and provide accessibility to all your Access database objects.

Resource Link: http://www.progtalk.com/viewarticle.aspx?articleid=1147

Preventing usage of "SELECT *..."

2009-12-04T03:30:00.000-08:00

By Raghuram (AJ),

We know the possible pitfalls of "SELECT *..." in programmable objects and often DBAs discourage users or developers from using it in their queries. However it's hard to enforce that in code. Here's one way to make sure users do not use "SELECT * FROM..."

If you create a dummy column in the table and deny SELECT permissions on this new column to the user, this user can select the rest of the columns but cannot perform a "SELECT * FROM..." on that table. Let's try it out...

Let's first create a new login, database & database user

USE MASTER
GO
CREATE LOGIN test_user WITH PASSWORD = 'test_user_pwd';
GO
CREATE DATABASE DenySelectStar;
GO
USE DenySelectStar
GO
CREATE USER test_user FROM LOGIN test_user WITH DEFAULT_SCHEMA = DenySelectStar;
GO
EXEC sp_addrolemember N'db_datareader', N'test_user'
GO

Next we create a new table with the dummy column, named "dummycolumn". We insert a few rows and deny select on this dummycolumn to test_user.

CREATE TABLE dbo.Table_1(
IdentityKey INT IDENTITY(1,1) PRIMARY KEY CLUSTERED
,ColumnOne INT NULL
,DummyColumn CHAR(1) NULL
);
GO

INSERT INTO dbo.Table_1 (ColumnOne)
SELECT 1
 UNION
SELECT 2
 UNION
SELECT 3
 UNION
SELECT 4
 UNION
SELECT 5;
GO

DENY SELECT ON OBJECT:: dbo.Table_1(DummyColumn) TO test_user;
GO

Now open a new query window and login using the newly created test_user and try the following queries...

USE DenySelectStar
GO
SELECT * FROM dbo.Table_1;

--Result
Msg 230, Level 14, State 1, Line 1
The SELECT permission was denied on the column 'DummyColumn' of the object 'Table_1", database 'DenySelectStar', schema 'dbo'.

As you see above results, SELECT * was not allowed. The following query is the recommended way to select columns:

USE DenySelectStar
GO
SELECT IdentityKey, ColumnOne FROM dbo.Table_1;

--Result
IdentityKey ColumnOne
----------- -----------
1           1
2           2
3           3
4           4
5           5

(5 row(s) affected)

There is however a catch (ah...I knew it!?). There are a few things that this user cannot do such as: COUNT(*), COUNT(1) or even SELECT 1 from this table. But there is a way around it. Replacing the * or 1 with the primary key on that table gives the desired results. Let's see the examples...

USE DenySelectStar
GO
SELECT COUNT(*) FROM dbo.Table_1;
SELECT COUNT(1) FROM dbo.Table_1;

--Result
Msg 230, Level 14, State 1, Line 1
The SELECT permission was denied on the column 'DummyColumn' of the object 'Table_1", database 'DenySelectStar', schema 'dbo'.
Msg 230, Level 14, State 1, Line 2
The SELECT permission was denied on the column 'DummyColumn' of the object 'Table_1", database 'DenySelectStar', schema 'dbo'.

USE DenySelectStar
GO
SELECT COUNT(IdentityKey) As TotalRows FROM dbo.Table_1;

--Result
TotalRows
-----------
5

(1 row(s) affected)


USE DenySelectStar
GO
IF EXISTS (SELECT * FROM dbo.Table_1)
PRINT 'Has Rows'
IF EXISTS (SELECT 1 FROM dbo.Table_1)
PRINT 'Has Rows'

--Result
Msg 230, Level 14, State 1, Line 1
The SELECT permission was denied on the column 'DummyColumn' of the object 'Table_1", database 'DenySelectStar', schema 'dbo'.
Msg 230, Level 14, State 1, Line 3
The SELECT permission was denied on the column 'DummyColumn' of the object 'Table_1", database 'DenySelectStar', schema 'dbo'.


USE DenySelectStar
GO
IF EXISTS (SELECT IdentityKey FROM dbo.Table_1)
PRINT 'Has Rows'

--Result
Has Rows

I agree it seems too much work to make sure that the users don't use SELECT *, but if you really want to enforce it, here's one way to go about it.

Here is the cleanup for your database that you can run:

USE MASTER
GO
DROP DATABASE DenySelectStar;
GO
DROP LOGIN test_user;
GO


Resource Link:http://www.sqlservercentral.com/articles/SELECT+*/68324/

Rectifying Error Message “Unsupported Extension Used For Table” in MySQL Database

2009-11-23T02:12:00.000-08:00

To take the advantages of the new privileges added in the new version of MySQL database, most of us upgrade our MySQL tables to new version. The utility available for upgradation of MySQL tables is known as mysql_upgrade. While upgradation has various advantages, it can also result in complete or partial loss of data from the tables. In such situations, backup enables you to restore the lost data. But, if there is no backup available or it fails to restore the required data, then you need to repair the corrupted table(s). To do so, you need to use advanced MySQL database Repair applications.

Consider a practical scenario, where you upgraded your MySQL database from rev 4.0.13 to rev 4.0.14. After the upgradation is complete, you discover that some of your important tables are corrupted. In addition, when you attempt to open those tables, you encounter the below error message:

“e-systemusr/local/mysql/bin# ./myisamchk -a
/usr/local/mysql/var/centralf/postscobe1.MYI

myisamchk: error: 138 when opening MyISAM-table
‘/usr/local/mysql/var/centralf/postscobe1.MYI’

e-systemusr/local/mysql/bin#…….”

The data saved in the MySQL tables becomes inaccessible after the occurrence of the above error message.

The main cause behind corruption of MySQL tables is improper or interrupted upgradation of MySQL database.

To repair the corrupted MySQL tables and access their data, you will need to follow these steps:

Use the below command to check and analyze the corruption in MySQL table:
Check Table tablename
Next, run the below command to repair MySQL table:
Repair Table tablename
You can also run the following command:

REPAIR TABLE TABLENAME USE_FRM

Though, it won’t be useful here, as it will show the tables as empty.

However, if all the above measures fall short of repairing the corrupted tables, then you will need to use advanced MySQL Repair tools. Such MySQL Database Repair utilities incorporate high end scanning methods to completely repair and restore the data stored in MySQL tables. With self-descriptive and largely graphical user interface, such repair utilities serve as user-friendly solutions that do not require any sound technical skills.

Data Corruption in SQL Server and MDF Recovery

2009-11-15T20:43:00.000-08:00

In MS SQL Server, you use SSMS (SQL Server Management Studio) to query character data from the SQL Server database which uses a non-Unicode data type. For instance, the SQL Server uses the char, varchar or the text data type.

The code page of client computer differs form code page of database.

In such circumstances, the character data may be represented incorrectly. For instance, you may face any of the following issues:

The characters are represented as the question mark. You might come across this issue if you have inserted or updated character data as non-Unicode data type prior to querying character data.

The characters are represented as corrupted. The characters of code page A are stored in non-Unicode column of code page B. Furthermore, the characters are not translated.

In such circumstances, the MDF file becomes inaccessible due to corruption and might lead to the data loss.

This crisis occurs as the characters of code page are stored in non-Unicode column of page B. In addition, the characters are not translated properly.

In SQL Server, when you use the string literal of non-Unicode data type, the string literal is changed by using the default code page of the database which is derived from collation of the database. Storing the character data of code page in a column of B code page might result into database corruption and data loss.

To stop the database corruption and work around this issue, you may attempt the following:

Try a Unicode data type in place of non-Unicode data type

Try appropriate collation for SQL database

Try binary or varbinary data type

Try a diverse tool for storing and accessing data and disable data Translate parameter

These fixes will stop the database corruption but won’t be able to repair the corrupted database. To do so, you need to use third party SQL recovery software.

MS Access Data Loss after modifying data in some other application

2009-11-09T20:53:00.000-08:00

The data saved in the MS Access database files (.mdb and .accdb) contains critical data in the forms of tables, views, forms and more. In most of the cases of opening the database files in other applications, the database becomes corrupt or inaccessible. To conquer such data loss situations, a perfect way is to restore the data from an updated backup. But, in case of absence of an updated backup, you will need to use advanced access repair application that can completely repair the corrupted Access database.

As a practical scenario, you open an .mdb file in the excel application. After making some changes in the MDB file, you save the database at the desired location. However, when you try to open your database, it shows an error message. In addition, the data saved in the Access database becomes inaccessible.

The core cause for microsoft access database inaccessibility is corruption of database due to opening it in another application. To avoid corruption of Access database, you will avoid opening of your database to other application.

To resolve the corruption of MS access database, you will need to use inbuilt repair utility named “Compact and Repair.” To use inbuilt utility, you will need to follow these steps:

1. Go to the Tools menu and select Database Utilities and then click Compact and Repair Database.

2. Locate and then click the database in the ‘Database to Compact From’ dialog box, and then click Compact.

3. Select an appropriate folder location for the new file in the ‘Compact Database Into’ dialog box, type a unique name for the file and then click on Save.

However, if Compact and Repair utility fails to repair the database, then you need to go for efficient Access Repair application. These access database repair applications use advanced scanning mechanisms to scan and repair the corrupted and damaged MS access database files.

Clustered Index Corruption in SQL Server Database

2009-11-04T05:48:00.000-08:00

MS SQL Server is the most usual and commonly used RDMS, developed by Microsoft Corporation. It is used by number of organizations to competently and professionally manage their important data. Sometimes you may face error in sql database. Corrupt database is one of most DBA(database administrator) most awful nightmares.

The error messages in SQL Server:

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

These error messages encounters when the user try to insert a column to existing table through INSERT command. If the transaction also retains the foreign key reference to the column, which has been confirmed as the exclusive clustered or non-clustered index key on the table, this could be the reason for this error. In this situation, the clustered index gets corrupted. When added column gets failed, clustered index can get corrupted and all the data become inaccessible.

If the clustered index got corrupt, then no report will be generated by running the DBCC CHECKDB, but the access performance of the database gets contaminated. No need to panic and don’t detach the database. No need to restart the SQL. First try to find out the root cause of this problem then try to repair it. If you got the success than its good else use your recent backup. If you don’t have the recent backup than you need an instant SQL recovery and choose the best sql database repair software for better results.

The best way out to repair SQL is to use third party applications which are well suited for this situation. In fact, they reward a secure MDF recovery and so are recommended for the best part. With the instinctive user interface, this MDF repair utility helps you to work with its easy process.

Rectifying “error Signature…” Error Message In Ms Access 2002

2009-10-13T23:26:00.000-07:00

When MS Access database does not get mounted, an error message gets displayed at the startup. So, the data becomes inaccessible that are saved in Access database. The main cause for corruption of MS Access database is due to operating system failure, MS Office malfunctioning, virus infection and other such reasons. Under such situations, you need to use backup for complete restoration of the lost data. In case, no backup is available, you need to use advanced access recovery applications.

Sometime you may face any of the below error messages when you attempt to mount Access database:

“Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience”
Or

“Error Signature
AppName: msaccess.exe
AppVer: 10.0.6501.0
ModName: msjet40.dll
ModVer: 4.0.8618.0
OffSet: 0008fcdf”

The above error messages also appear when you try to open a new database. Data saved in database becomes inaccessible after appearance any of the above error messages.

The above error messages occurs due to the two reasons they are:

• Redirecting the Application Data folder to a different folder on the computer system by using a Group Policy
• Access database corruption

To troubleshoot and resolve the above error messages, you need to follow these measures:

• Use the Application Data folder name in the folder redirection path for the Application Data folder.
• In case of Access database corruption, use inbuilt repair utility known as “Compact and Repair.”

However, if the inbuilt repair utility fails to repair the database, then you need to use advanced access recovery applications. Such access database repair tools use high end scanning methods to recover and restore all Access database objects. These tools can completely recover and restore inaccessible Access database files.

Unexpected SQL Server Connection Termination

2009-10-08T21:56:00.001-07:00

MS SQL Server is the popular relational model database server used to create, edit and maintain databases. SQL Server is available in various editions, like SQL Compact Edition, SQL Evaluation Edition, SQL Developer Edition and others such. But sometimes when you work with it, you observe that SQL Server looses its connection without giving any error message. The connection terminates unexpectedly may be due to database corruption and hence to restore the lost information and to repair sql database, you should use your recent data backup.

Consider a practical scenario; you start the system and SQL terminates the connection, with or without displaying an error message. You cannot rebuild the connection in subsequent attempts.

SQL Server terminates the connection if any of the conditions is true:

• SQL process has suffered an execution error, for example, it is trying to access an illegal memory address or SQL encounters assertion error or stack overflow
• A protocol error has occurred in the communication between SQL and client library. It could occur due to bugs in client library or SQL Server, hardware issues, network problems, resource problems, SQL Server database corruption and so on.

To solve these problems, you need to consider these methods:

• Try reinstalling SQL server
• Reinstall client library
• Troubleshoot hardware problems. You need to use hardware diagnostic utility to detect malfunctioned hardware
• Detect and correct networking problems.
• To correct resource issues, ensure that sufficient RAM and disk space are available
• If database is corrupt, run DBCC CHECKDB command to check. If it reports corruption, use REPAIR_DATA_LOSS command. But it deletes all the damaged information. Thus for safe repair, use third party SQL Repair applications. These SQL Recovery software employ advanced scanning algorithms to analyze the damaged database and repair them intact.

'Duplicate unique key or constraint on write or update' MySQL Error and Recovery

2009-09-22T02:56:00.000-07:00

Storage engines that are supported by MySQL work as handlers for its various table types. MySQL tables are components used to relate and store data in databases. But some times, you observe corruption issues with tables that can occur due to improper locking of tables, application code errors, storage engine faults and other similar reasons. In such cases, use your updated database backup to retrieve lost data. However, if backup seems to be invalid or is not available, you need to repair the damaged table by using MySQL Recovery software.

You might encounter the below error message with your MySQL database table:

"141: Duplicate unique key or constraint on write or update"

• In MySQL tables, unique key is the constraint that is responsible for uniquely identifying each row in the table

The basic reason for the occurrence of this error message is inconsistencies of MySQL database table. It can happen due to unexpected shutdown and other similar causes.

To solve this issue, you need to follow these steps:

• First, you need to check the affected table for corruption. You can run CHECK TABLE command as follows:

CHECK TABLE tablename

The server must be running for the command to run. You can also use mysqlcheck or myisamchk command-line utility to check MySQL tables.

• If table check reports corruption, you need to repair it. You can use

REPAIR TABLE tablename

mysqlcheck or myisamchk command-line utilities can also be used.

• If you still receive the same error message or the table is inaccessible, you can use recent data backup to restore the entire database. However, if no backup is available or gives certain errors during restoration, third-party MySQL Repair applications can be used to repair and restore all the lost information.

MySQL Database Recovery tools are special utilities that can scan damaged MySQL databases and restore all their objects.

"Unexpected Error 35012" When You Open a Database.

2009-09-15T21:11:00.000-07:00

We always store office work in form of database. For maintaining and creating database, MS access is best software utility. As it is easy to use but sometimes when we try to open an existing MS Access Database, you may get an error message:

“Unexpected error 35012”

Due to this error your database closes unexpectedly. You face this error due to the corruption in the Microsoft Access Database or mdb file. These corrupted objects may include one or more database forms of reports.

As Microsoft has provided compact and repair utility to repair access database and several other utility is form of patch to resolve this problem such as jet compact utility. One more method is there to repair the corrupt database i.e import the corrupted .mdb file or object in a new file. For importing corrupted database, follow following steps:

* Create a new Access database
* In file menu, select Get External Data option
* Select Import from Get External Data
* Select all the database objects in the file and import in newly created database

If you again face "Unexpected error 35012" when you import a specific object, try the 2nd step again. If you fail to import this time also, you will need to restore the corrupt object from backup.

But it helps only when your database is less corrupted. If it is critically corrupted then compact and repair utility or jet compact utility doesn’t help you. Even you can’t import database. In case if you fail to import the database and you don’t have any backup, then you can’t repair your database without using 3rd party access repair tools. In these situations, your entire database may become inaccessible. Access recovery softwares are the powerful data recovery programs that can search and locate your corrupted access database and can repair them.

Resolving SQL Server Error 2511

2009-09-09T01:53:00.000-07:00

SQL Server stores data in b-tree format. It is the general method of locating and placing data in database. Sometimes, SQL Server reports keys being out of order for a particular page in a table. Such errors generally indicate table corruption, which are required to be restored by using backup. On the other hand, the unavailability or invalid state of backup requires you to use commercial SQL recovery applications.

As an example, you might face the below error message when you are using MS SQL Server database:

Server: Msg 2511, Level 16, State 2
Table Corrupt: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d.
Table error: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d.

As the error message suggests, it occurs when two specified slots are in incorrect order or not in accordance to comparison of their keys. Here, P_ID represents the index page and data page.

You need to follow these steps in order to correct the above issue:

• First need to ensure that system is free from hardware errors. For this, you should run hardware diagnostics and correct the problem, if exists. You can also check Windows, application and SQL Server error.
• Restore the damaged database from your most recent backup. In case of backup concerns, you should run DBCC CHECKDB command without using any repair clause, which will determine the repair clause that should be applied. Next, run DBCC CHECKDB command with the suggested repair clause.
If the above step can't helps you, then for safe database repair, you should use third-party SQL Repair tools. These are graphically rich SQL Recovery software designed to achieve complete SQL database repair results.

Rectifying Error Message "Table is crashed and last repair failed" in MySQL database

2009-08-31T21:19:00.000-07:00

MySQL database tables act as the primary storage components for the data stored in your database. These tables can be updated, modified or deleted as per your requirement. Corruption in MySQL database tables primarily occurs due to insufficient disk space, improper mysqld (MySQL Server) shutdown, usage of external program (like myisamchk) on a live table, malicious software like virus, faulty memory and more. In most of the table corruption cases, you face an error message. Such error messages make the data inaccessible. In such situations, you backup acts as a boon to restore your data. But, in case of unavailability of an updated backup, you need to opt for advanced MySQL Database Repair software.

As a practical scenario, you run the below query to analyze your XYZ table:

mysql>ANALYZE TABLE `XYZ`;

You face the below error message after running the above query:

"Table 'XYZ' is marked as crashed and last (automatic?) repair failed"

Data stored in the XYZ table becomes inaccessible after the above error message appears.

To successfully repair the corrupted XYZ table and access its data, follow these steps:

• Use the below command to check and analyze the corruption of XYZ table:

Check Table XYZ

• Run any of the below commands to repair XYZ table: REPAIR TABLE `XYZ` USE_FRM; Or mysqlcheck -r -u username -ppassword d60476544 XYZ

It repair your table and you are able to access your data but if you encounter the below error message:

"error : Not enough memory for blob at 15946608 (need 182026713)"

The error message means that the repair commands were unsuccessful in repairing the XYZ table. For systematic repair of XYZ table, you will need to use powerful MySQL Repair applications.

These MySQL Repair tools perform in-depth scan and repair of corrupted MySQL tables by incorporating advanced scanning algorithms. Designed with self descriptive and interactive interface, these tools work as user-friendly applications to repair and restore all corrupted business critical database components.

How to repair corrupted access mdb file

2009-08-25T22:59:00.000-07:00

Databases are normally made by the users using MS Access application and those files get saved with the extension .mdb. These databases contain critical information which is needed for the proper working of any organization. So any corruption in these databases could be a mind shaking experience for few and requires an urgent access database repair. There are many of the symptoms which indicate that the mdb files are corrupted:

• The file fails to open and no loading happens when you try.
• File opens but with the unreadable characters.
• A screen seeking password appears, although it has not been set.

You encounter some of the error messages like:

1. “Unrecognized Database Format”
2. “Unexpected error 35012 (opening file)”
3. “The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time”
4. “This database is in an unexpected state; Microsoft Access can't open it...”
5. “Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.”
6. “Operation failed - too many indexes - reduce the number and try again”
7. “You do not have the necessary permissions to open this object. Please contact your system administrator.”
8. “The Microsoft Jet database engine could not find the object MSysCompactError”
9. “This object needs a newer version of the Microsoft Jet database module”

And the list goes on.

The reason for the database corruption could be any like: improper shutdown of the computer system, application malfunctioning, virus attack, missing of some application related files, improper exit from the application, hardware or network problem etc.

Some of the problems of Access repair are sorted according to the cause of the error and you can get the clue from the error message itself like for the error message:

“This object needs a newer version of the Microsoft Jet database module”

You can try out installing the newer version of the Jet database module. Some of the problems related to the incorrect registry settings or some of the specific system file corruption, and then you can try out renaming the registry files and repairing the corrupted files.

While many of the corrupted files finds no solution and the data in them may remain intact. Then the most secure and safe solution to do Access repair is to have an Access repair software.

MDF Corruption Due to OS Errors or I/O Check Failure

2009-08-18T21:35:00.000-07:00

Sometimes you may face system or hardware problems while writing data to or reading from the SQL Server 2000 database. These issues can make your database inaccessible and cause serious data loss. In such situations, you need to opt for SQL Database Recovery.

While reading from or writing to the SQL Server database, you might encounter the below error message:

“Error 823
I/O error <error> detected during at offset in file ''”

This error message may occur every time when you start SQL Server and access the MDF file.

MS SQL Server 2000 displays this message when any of the below given conditions are true:

Operating system problem: A read Windows API (Application Programming Interface) call or write API call isn’t successful and MS SQL Server encountered operating system error which is related to API call.

I/O logical check failure: This behavior may occur if the read API or write API is successful but particular logical checks on database are unsuccessful. This situation prevents SQL Server to access data from MDF file.

MDF Corruption: This problem may occur if your MDF file is corrupted and thus SQL Server can not recognize the file and access data from it. This behavior causes serious data loss.

There are three possible solutions of this issue:

If the problem is due to operating system error then you need to fix the Windows API issue. It may require repair or reinstall.
Use DBCC CHECKDB command to check any logical errors in the database. It is an in-built command in SQL Server to fix application level errors.
Use SQL Database Recovery software to scan the corrupted database and recover all the inaccessible data from it.

This software is specifically designed to Recover SQL database in most of the corruption scenarios. This software come equipped with interactive graphical user interface and thus allow you to have ‘Do It Yourself’ recovery. This software can recover all the MDF file objects including tables, reports, triggers, stored procedures, constraints, indexes, views etc. They provide absolute results with their read-only and non-destructive design.

‘can't Find File: .myi’ Mysql Error And Recovery

2009-08-12T00:18:00.000-07:00

MyISAM is standard storage engine used for MySQL that is based on older ISAM code. MyISAM table is made of three files: .frm, .MYI and .MYD. MYI (MYIndex) is the index file that MyISAM uses to store table indexes. But at times, you observe that system is unable to open the .MYI file. As a result, you can’t access the database and hence need to restore lost information from backup. In such situations, if you find your database backup as invalid or no backup, then MySQL Database Recovery applications can be used for repairing and restoring the database.

You might receive the below error message with your MyISAM table:

“can't find file: .MYI”

Cause

The index file (.MYI) of table is damaged or corrupted. It can get corrupt due to unexpected shutdown, improper locking of table, errors in MyISAM code, network errors, hard disk issues and similar other reasons.

Solution

Perform these steps in order to rectify the above issue:

• First, you need to check the database table for corruption using one of the following commands with valid options:

CHECK TABLE tablename
myisamchk *.MYI
mysqlcheck *.MYI

• If the above commands detect corruption, you need to repair the database. To accomplish the same, you can use following command:

REPAIR TABLE tablename
myisamchk *.MYI
mysqlcheck *.MYI

Take the backup before you try to repair the table.

• If you still receive the same corruption error messages, you should delete the damaged database table and restore the lost data from latest backup. But if you observe that database backup is not up to the mark, you need to use MySQL Recovery tools.

MySQL Database Recovery software are effective applications that are designed to scan and repair damaged MySQL databases. These MySQL repair tools perform in-depth scan and repair of corrupted MySQL tables by incorporating advanced scanning algorithms and offer advanced repair options, to-the-point documentation, interactive interface and different support options.

Repair a damaged Access 2000

2009-07-30T02:06:00.000-07:00

MS Access is the best tool for creating database. When creating MS Access Forms for your database application, there you may face some error messages when user interaction takes place. Sometimes error messages in MS Access may appear completely unpredictably or at sometime due faulty network, interrupted write operation or saving a database file in another program.

Due to error you can lost your important database file. You get error message from MS access such as record is deleted, conflict error, file not supported. In this case your data become completely inaccessible.

For getting rid from this type of data loss you must have a data backup. In case, if you don’t have backup then you have to repair access file. You can do it with the help of compact and repair utility in tool section of MS access. This repair utility works in most of the database corruption cases .But if this utility doesn’t work and still you are not able to repair access file then you need some special access repair software to repair your damaged Access database files.

This software has enhanced data repair capabilities that helps you to recover queries, forms, reports, macros and Visual Basic module of corrupted database. This software are user friendly. Access database repair software provides a cool and simple user interface to their users.

Data Corruption in SQL Server and MDF Recovery

2009-07-20T23:00:00.000-07:00

In MS SQL Server, you use SSMS (SQL Server Management Studio) to query character data from the database which uses a non-Unicode data type. For example, the SQL Server uses the char, varchar or the text data type.

The code page of client computer differs from code page of database. In such position, the character data may be represented inaccurately. For instance, you may face any of the following issues:

The characters are represented as question mark. You may come across this matter if you have inserted or updated character data as non-Unicode data type earlier to querying character data.

The characters are represented as corrupted. The characters of one code page are stored in another code page in non-Unicode column. Furthermore, the characters are not translated.

In such situation, the MDF files get corrupted and are not accessible and might lead to the data loss.

Reasons of the trouble

This malfunction occurs as the characters of code page are stored in non-Unicode column of other page. In addition, the characters are not translated properly.

When using the string literal of non-Unicode data type in SQL Server, the string literal is changed by using the default code page of the database. Storing the character data of code page in a column of other code page might result into database corruption and data loss.

Resolution

To stop the database corruption and work around this issue, you may try the following:

Use binary data type
Use appropriate collation for SQL database
Use a Unicode data type in place of non-Unicode data type
Use a diverse tool for storing and accessing data and disable data Translate parameter

These things will help to stop the database corruption but won’t be able to repair the corrupted database. To repair the corrupted database, you need to use SQL recovery software. With SQL recovery Software, you can repair & recover your most precious SQL database in just 2 clicks. SQL database recovery tools include advanced scanning algorithms to widely recover and restore all database components.

Resolving Error Message "Can't locate the wtlicensemanager.dll file"

2009-07-14T22:15:00.000-07:00

Tables are the most common form of storing data in MySQL database. Corruption of tables primarily occurs due to unexpected shutdown of MySQL Server, operating system corruption, DLL (Dynamic Link Library) file damage, file system corruption, virus and more. Once a table is corrupted, the data stored in the table becomes unreadable. With the help of updated backup you can restore the affected data. But in certain scenarios, you have backup but not updated or face application errors while data restoration. In such cases, you need to use advanced MySQL Database Repair tools for complete repair and restoration of corrupted data.

Consider a practical example, where you were modifying a particular MyISAM table stored on the Webtrends log server. While modifying the table, the server shuts down unexpectedly due to power outage. When the server gets restarted, you encounter the below error message:

"Can't locate the wtlicensemanager.dll file"

After the above error message appears, the data stored in the table becomes inaccessible. In addition, you encounter the same error message when you try to open table.

Cause:

The root cause for the above error message is the corruption of MySQL database table due to improper server shutdown.

Resolution:

To resolve the above error and access the Accounts table, you need to repair the table by using below steps:

1. Enter the MySQL database as Administrator. Enter the password if prompted. To do so, type the below command:

mysql -u Administrator -p

2. Now, repair the corrupted table by using the following command:

use wtmaster

repair table Accounts:

3. Exit from the database by typing 'exit' and press Enter.

However, if the server still encounters the error message and the table remains inaccessible, you need to repair the table by using advanced MySQL Database Repair utilities. Such MySQL Repair applications include powerful scanning algorithms to repair and restore MySQL database components. With highly interactive user interface, these repair tools are easily understandable without any sound technical knowledge.

Access Database Error” Unrecognized Database Format”

2009-07-07T21:29:00.000-07:00

Sometimes when we open our old MS access database or .mdb file, ms access report following error message:

“Unrecognized database format or format not supported”

Due to this error you are not able to open your access database, even you can’t access your database file.

Following reasons may responsible for this problem.

1. If you're accessing the Access 2000 database using ADO or the ADO Data control, you can get a run-time error -2147467259 "Unrecognized Database Format".

2. If you are trying to open older version database in earlier version. As you are accessing access database 2002 file from access 97, You may get this error.

3. One more prospect is your access database may be corrupt.

If problem occurs due to accessing older database file from earlier version then you can easily fix this problem. For fixing this problem, open database in same version of access it was developed. Now convert the database file with help of tool option in access 2002 window.

In case if you still get the error message then your database file is corrupted. If you don’t have backup copy of your database then it’s a big problem. For fixing this problem we recommend you to repair your access file. To repair your database you need a repair or recovery tools for your database. We recommend you to download access repair tool (.MDB Repair).

With Access Database Repair Software, you can repair & recover your most precious access file in just 2 clicks. Access Database Repair tools include advanced scanning algorithms to widely recover and restore all database components. It is easy to use, compatible with all file versions (Access 97, 2000, 2002, 2003 and 2007), fast and Secure recovery.

SQL Recovery after Logical Database Corruption

2009-06-25T21:56:00.000-07:00

MS SQL Server is the most accepted and commonly used RDMS, developed by Microsoft Corporation. It is used by a number of organizations to efficiently and professionally manage their valuable data.

Though, it is considered as a reliable way to store important business data, but sometimes you may face problem in your SQL Server database due to system malfunction, virus attack and so on. After corruption, the entire database becomes inaccessible and you may fall in need to SQL recovery.

SQL database corruption can be categorized in two different forms: logical corruption and physical corruption.

The logical corruption is where something has modified due to which some data and a data relationship has got broken. Practical reasons of logical database corruption are as follows:

Ø Application bug- Sometimes the application malfunction can delete some inbuilt data and may lead to corruption. Improper use of database constraint could also cause the application fault and finally database corruption. Improper use of roll back function could also be the reason of same.

Accidental deletion of important system files such as transaction log files.
Virus attack to the database
Improper use of database repair commands or consistency check functions.

In case of logical database corruption, the MDF recovery is only possible with the help of third party software known as SQL recovery software.

SQL recovery software are specially designed to meet different users MDF recovery related requirements. SQL repair software are applicable to most of the MDF corruption cases and can repair and restore all of the objects of corrupted MDF file. SQL recovery software are fully automated and thus does not require any user interaction to carry out MDF recovery. The SQL Recovery Software is a powerful software tool that recover your data as much as possible, so to minimize the loss in file corruption and for making your organizational or personal operations productive.

Table Corruption in MySQL Database

2009-06-18T22:00:00.000-07:00

Request Tracker enables you to keep a record of all the operations performed in MySQL database. Request Tracker creates a session by using a MySQL database, a PERL based main engine and front-end web and mail interfaces. However, if Request Tracker is not capable to store your transactions made into the MySQL component, chances in MySQL component is either corrupt or missing. Corruption of MySQL database component can take place due to MySQL database server malfunctioning, operating system failure, virus and more. In such situations, you need to recover the MySQL database component by restoring it from the latest backup. But, if you don’t have any backup or backup falls short of providing the required data, then you should repair your corrupted MySQL component to extract data from it. To do so, you need to use advanced MySQL Database Repair application.

Consider a practical scenario where you encounter the below error message when you attempt to save some changes in session_data table:

“Request Tracker couldn't store your session. This mean that the directory '/extra/requesttracker/current/var/session_data' isn't writable or database table is missing or corrupt.”

Cause:

The reason behind occurrence of above error message is that the session_data table is either missing or corrupt.

Resolution:

To resolve the above error message and access the session_data table, you can follow these steps:
• Create a new directory and move the MySQL database to that directory. To do so, follow these steps:
mkdir /extra/var
mkdir /extra/var/lib
mv /var/lib/mysql /extra/var/lib/mysql
ln -sn /extra/var/lib/mysql /var/lib/mysql

• Next, you need to restart the MySQL database by using:
service mysqld restart

If you find the table corruption even after moving the database files, then you need to follow these steps to repair the table:

• Check the mysql database for the table named “RT4” by using the below command:
mysqlcheck -u root -h localhost RT4 -p

• After checking, fix the mysql database table “RT4” by using this command:
mysqlcheck -r -u root -h localhost RT4 -p

• Finally, recheck the mysql repaired table “RT4” by using the following command:
mysqlcheck -u root -h localhost RT4 -p

However, after following the above steps you again face the same error message then you should use advanced MySQL Database Repair software. Such MySQL Repair utilities use advanced scanning methods to repair and restore MySQL database files with easy-to-use interface and illustrated plus user-friendly documentation, these repair tools are easily to implement.

Rectifying “Input Output Error” in Microsoft Access

2009-06-12T01:39:00.000-07:00

Registry settings for Microsoft Access facilitate you to alter the title, icon, startup screen and help file of the database appliance. Corruption in registry settings first and foremost occurs due to incompatible hardware or software, software bugs and additional. In most cases of corruption in registry settings of Access database, you face an error message that makes the data inaccessible stored in your database. To repair the inaccessible data, you need to have an updated backup. But, if you don’t have backup or the backup fails to restore the data, then you need to use advanced Access Database Repair tools.

You might face or encounter any of the below given error messages:

“An unexpected error occurred - I/O Error 0”

Or

“An unexpected error occurred - I/O Error 6”

Or

“ found an error it cannot correct.”

After appearance of any above error message the data stored in the Access database becomes inaccessible.

Cause:

The above error messages mainly occur due to the corruption in Access settings stored in the registry.

Resolution:

To resolve the above error messages, you need to revise the registry. To do so, you need to follow these steps:

Delete the HKEY_CURRENT_USER\Software\Microsoft\Office\X.0 Key
Reset the Open Dialog Box Settings
Delete the HKEY_LOCAL_MACHINE\Software\Microsoft\Office\X.0 Key

However, a single erroneous change made in the registry can result as serious issues. In such situations, you need to reinstall the MS Office suite on your system. The data loss while reinstallation might occur under these two conditions:

Installing an incompatible version of Microsoft Office
Interruption while importing a Microsoft Access database

If your data is lost due to any of these reasons, then there is a single way to recover lost data is by using powerful Access Repair applications. Such Access Database Repair tools include advanced scanning algorithms to widely recover and restore all database components. With highly graphical and interactive user interface, these recovery tools work as self-explanatory tools without the need of sound or prior technical skills. These tools can generally recover and restore inaccessible Access (.accdb and .mdb) database files.

Database Inconsistency and Invalid File Header Problems in Mdf

2009-06-05T04:42:00.000-07:00

RAID servers are considered as the most trusted and reliable storage medium. But sometimes, they may also lose all the hard drives, which contains your important data, backups and other files.

Most of the organizations use RAID for storing their important SQL Server databases. When they fail, normally you may lose all of your data.

In such situations, you can save your data by restoring the database from your backup. But sometime, when you try to restore backups, you may receive the following error message:

“Msg 3270, Level 0, Sev 16.

An internal consistency error occurred. Contact Technical Support for assistance.”

In this case, when you attempt to detach the database using sp_detach_db stored procedure and then attempt to attach the database again with the help of sp_attach_db stored procedure, you may get the flowing error message:

“Server: Msg 5172, Level 16, State 15, Line 1.

The header for file ‘d:\pubs.mdf' is not a valid database file header. The PageAudit property is incorrect.”

After this error message, the restoration process gets halted and you can not access anything from your SQL Server database.

Grounds of the trouble

As stated in the above error messages, this problem is either due to inconsistent state of the database or due to invalid header entry for the database. In both of these cases, the database may get corrupted and then you are not able to access even a single data from it.

In such situations, you need to perform SQL recovery to repair the damaged database and retrieve all of your data from it. SQL recovery can be carried out using the SQL Database repair software.

SQL Database repair software are easy to use, which allow you to have quick and trouble-free MDF repair in each and every case of MDF corruption. To ensure complete and successful SQL repair, always use effective SQL database recovery software like Stellar Phoenix SQL Database Recovery software.

Phoenix SQL database Repair software works well in all MDF corruption posers. This MDF repair software can effectively repair and restore all of the SQL Server database objects including tables, reports, forms, triggers, stored procedures, defaults, user defined data types and likewise.

Resolving “Old database file” Error Message in MySQL database

2009-05-28T03:30:00.000-07:00

MyISAM tables (extensions .myi and .myd) in MySQL database form an essential part of storing data in the most efficient and effective way. Corruption in these tables primarily occurs due to unexpected MySQL Server shutdown, operating system malfunctioning, software bugs and more. In most of these situations, you encounter an error message which further makes the data saved in MyISAM table inaccessible. To recover the lost data from MyISAM table, you need to restore it from the latest backup. But, if you have not created any backup, then you need to repair the MyISAM table by using advanced MySQL Database Repair application.

Consider a scenario, where you are making certain modifications in the Marketing table. While doing so, you encounter a power outage and your system shuts down unexpectedly. After you switch on your system and try to open the table, you got the error message:

“Table is crashed and last repair failed”

The data saved in the Marketing table becomes inaccessible after the error occurrence.

Cause:

The reasons behind the above error message are:

• The table handler is unable to find Marketing.myi file.
• Unexpected end of the file due to power failure
• Some of the records in the Marketing.myi file have been crashed.

Resolution:

To resolve the above error message, you will need to repair Marketing.myi table by using these steps:

1. To check and analyze the corrupted table, use either of the two commands:
myisamchk Marketing.myi

Or

Check Table Marketing

2. To repair the corrupted table, use either of the two commands:
myisamchk -r -q Marketing (-r -q means “quick recovery mode”)

Or

Repair Table Marketing

But these commands are helpful to repair normal corrupted file. If the file is badly corrupted, you need to repair the table by using MySQL Repair software. Such MySQL Database Repair applications integrate advanced scanning algorithms to repair and restore the data stored in MyISAM tables. The repair tools also create a secure link with MySQL Server while repairing the corrupted MyISAM table.

File Sharing

Access Database Repair Software By Stellar

2009-05-11T05:17:00.000-07:00

Database is an important part of any business organization. It needs to store and manage information in organized way. Access is a “file system” relational database management system from Microsoft, storing every part of the database —tables, queries, forms, reports, etc.—inside one MDB file. The information may be about people, orders, products, employees and so on. A database file can get corrupted when the storage space of database maximizes, virus infection, which increases the chance of database corruption.

There are lots of reasons that will cause your Access MDB file corrupted or damaged. Some of the most important causes are:

• Application Malfunctioning.
• Exit the application improperly.
• Improper System Shutdown.
• Virus attack and so on.

Keeping in mind the above problems, Stellar Information Systems Ltd technically advanced Data Recovery Company launch the software called Stellar phoenix Access Recovery which recover and repair damaged and corrupted Ms Access file with table, Queries, forms, report, macros & modules in almost all data corruption situations like when you cannot open files and instead come across error messages such as:

* Unrecognized database format.
* Enter Password (even though no password has been given).
* The Microsoft Jet Database Engine cannot open the file.
* Microsoft Access has encountered a problem and needs to be closed

Our engineers try hard to make this Recovery Tool easy and safe for users so that Recover Data for Access can be used with better.

With Stellar phoenix Access Recovery you are just a small number of steps away to recover your very important, essential and confidential data from corrupt access database. No need to take your system anywhere. Just install Stellar phoenix Access Recovery and enjoy the retrieval of lost database. Stellar phoenix Access Recovery is available at http://www.repair-access-file.com/download-access-file-recovery.php

The trial or Demo version of Stellar phoenix Access Recovery would scan and repair corrupted Access files & objects but restricts the File saving option.

For More Information Visit:
http://www.repair-access-file.com

Minimize Your Data Loss Even if .MDB Databases are Corrupt!

2009-05-08T03:23:00.000-07:00

Everyone who is familiar with Microsoft Access and .MDB databases knows the importance of .mdb file and they also know, if the .MDB files are corrupt or damaged then Access can neither open the files nor distinguish any data in them. That can sustain significant data loss, as lots of important objects, including records, tables and relations that are stored in files. The question arises what to do in this case! They have already tried Access Recovery 3.0 and got persuaded by its extraordinary performance. It uses the most advanced scanning procedures to methodically scan MDF file and extract all data from it.

Access Repair and Recovery is based on wide-ranging understanding of the Access MDB database format. The advanced algorithm of this powerful tool allows recovering every possible item in the MDB database files, because the recovery process does not rely on the structure of the original corrupt or damaged MDB database file. Sometimes the structure is completely damaged and cannot be recognized, but Access Recovery is still able to analyze the MDB database file byte by byte and recover most of the data. It works even when other comparable tools would fail! Even if there is no corrupted file, it’s reasonable to have a Stellar Phoenix Access Recovery 3.0 - just to be on the safe side and to use it immediately if required.

Stellar Phoenix Access Recovery 3.0 can be used to successfully repair Microsoft Access including Access 97/2000/2002/XP/2003/2007. This software recovers Reports, Forms, Modules and Macros, constraints applied on the table, queries. It provides a number of benefits, because it covers abundant features that are not available or partially existing in other repair tools.

If your database is corrupted and you are in search of Access Database Repair and Recovery software that can supports Access 2007 then download Stellar Phoenix Access Recovery 3.0 and recover your entire database in just few minutes.

For More Information Visit:

http://www.repair-access-file.com

MS Access Error Message - “Record Is Deleted”

2009-04-22T05:08:00.000-07:00

Sometimes when you try to open a table, query, form, report or a data access page you may find the following error message:

“Record is deleted.”

Now, in the case of a table or a query the error message displayed may be in the form:

“Msaccess can't open the table in datasheet view.”

While if you are deal with a report the error message may take the following form:

“Unable to carry out the command.
There was an error executing the command.”

This behavior publicized by the MS Access in the multi user environment while the database is stored on the network. When the LAN is spread in a building or a more wide area, then it is a universal practice take up by the users to save an Access database on the network so that it can make them easy to keep an eye that the work is going in the right direction or not.. These databases generally hold some important company or organization related information which can not be lost at any cost. So it is required that no data loss may take place and the data will remain safe.

The above mention error messages arise if either the object or the whole of the database is corrupted or damaged. The problem occur when the similar record in the database is being modified by two or more users all together and in the mean time if any of the user forces the Access to close by shutting down his/her computer.

To resolve this problem Microsoft has recommended repairing the database using Compact and Repair utility tool. But there is a downslide to it, this tool didn’t work so, at last database remains damaged or corrupted. In this case the only option left to repair the database is to imply good access database repair software. This software is read only software and repairs your database without changing the original content of the database.

Stellar Phoenix Access Recovery software has marked a great performance in repairing the Access databases irrespective of the amount of damage occurred to the database. The software is found to be compatible with all the file versions of MS Access including Access 2000, 2002, 2003 and 2007. This can also repair databases containing queries, forms, reports, or tables. This is the best access database recovery software with all the repairing facility to repair every single damaged or corrupted part of the access database. And the interesting part is that the user needs not to be technically savvy to operate the software.