Feed: Database Recovery Software | SQL Recovery | MySQL Repair - AggScore: 45.2

Last week, I had got an email from one of my friend with MS access database attachment. I had successfully downloaded Access database on my system. When I tried to open the database then got an error message “you can’t see this database, update your MS access database”. I want to tell you that am not an Access database geek so I searched on the Internet and found solution to fix the problem.

Here, I will share all the steps which I had tried to fix the problem.

1. Check the Version of my Access Database
2. Check the version of received Access database
3. Convert an Access 2000 database to .accdb file format

1. Check the version of my Access database that is MS Access 2000. You can check your Access database version by checking the registry for below key.

"HKEY_CLASSES_ROOTAccess.ApplicationCurVer", this will give you the following values:
Access.Application.8: that means: "Access 97", Access.Application.9: that means: "Access 2000", Access.Application.10 that means: "Access XP", Access.Application.11 that means: "Access 2003", Access.Application.12 that means: "Access 2007" & Access.Application.13 that means: "Access 2010"

2. Check the version of received Access database that is MS Access 2010. You can do this with the help of File-Format property. To do run this:

Set obj access = CreateObject( "Access.Application" )
Obj access. Open current database “c:scriptstest.mdb”
Int format = obj access.current project.file format
Select Case int Format
Case 8 Print "Microsoft Access 97", Case 9 Print "Microsoft Access 2000", Case 10 Print "Microsoft Access XP", Case 11 Print "Microsoft Access 2003", Case 12 Print "Microsoft Access 2003", Case 13 Print "Microsoft Access 2003"
End Select

Note: As we know that MS Access database is not backward compatible.

3. Convert an Access 2000 database to .accdb file format, I have followed below steps to fix Access database:

• Open Access database using Access 2010 and save then as .accdb file format.
• Go to the file menu, click on the open tab select Access 2000 database that I want to see.
• Go back to the file tab, select save & publish button and then select .accdb file format to save.
• Now select “save as” tab and enter the file name to save the received Access database.
• Now open the copied Access database.
• Successfully done.

Microsoft SharePoint is a web based platform, which is aimed at secure content manage among a specified group of persons. This innovation of Microsoft has a much broader aspect than web technology and can be used to provide a variety of solutions through the web. But, at times the SharePoint server gets corrupt and a he volume of precious data becomes inaccessible. If you encounter any such situations in your SharePoint implementation, you can use any reliable SharePoint database repair utility to repair the corrupt database and regain access to the data in it.

SharePoint is one of the popular products of Microsoft among the corporate, as according to sources around 78% of Fortune 500 firms use SharePoint and the company has already sold more than 36.5 million user licenses. SharePoint has given an easy to use platform for management as well as provisioning of secure intranet portals, websites, extranet portals, social tools, business intelligence, collaboration spaces, enterprise search, system integration, process integration, work-flow automation and many more.

Thus, each SharePoint Server contains huge volumes of valuable data in it. Though more than one organization can implement a SharePoint Server together and can work as a single server firm, SharePoint stores its data in a centralized SQL Server database. Sometimes, this internal SQL Server database gets corrupt and the entire SharePoint Server becomes completely inaccessible. Below are some of the instances of data inaccessibility from a SharePoint database (MDF database):

• The MDF database file got damaged because of virus/malware infection and thus, became completely inaccessible.
• The hard drive or the array used for housing the SharePoint Server database has been corrupt and as a result of this the MDF file has become corrupt.
• Incompatibility or existing bugs in the current version of the SharePoint Server is responsible for MDF file corruption.

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 database 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.

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

• Save a Copy As → Clone:

• Save a Copy As → Copy:

• Save a Copy As → Compacted:

• Recovery command:

• 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.

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 file repair software. MDF repair software uses advanced scanning algorithm to scan and repair corrupt SQL server database.

 

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.

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.

1. Value of  data: High or Low
2. Transaction Rate
3. Number of Users
4. Database Availability
5. 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.

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.

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.

• 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.

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.

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.