Recovery for Oracle

Frequently Asked Questions

Table Of Contents
Questions And Answers

Can Recovery for Oracle repair my Oracle database?

What limitations does the demo version of Recovery for Oracle have?

I have tried the demo. How do I decide whether to purchase the full version of Recovery for Oracle?

What are the differences between product licenses?

Why do results of recovery contain less data than the original Oracle database?

Running Recovery for Oracle from command line (through Windows Start -> Run menu).

After running Recovery for Oracle on the corrupted database, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new database?

Processing of sql scripts created by Recovery for Oracle does not rebuild the database and/or produce any error messages. What is the problem with?

Recovery for Oracle Error Messages

Recovery for Oracle Error: Internal Program Error message.

Recovery for Oracle Error: Not enough disk space.

Oracle Error Messages

ORA-01033

ORA-01043

ORA-01053

ORA-01073

ORA-01079

ORA-01099

Questions And Answers

 
Q: Can Recovery for Oracle repair my Oracle database?
A:

The effective way to find out if a Oracle database is recoverable is to try the demo version of Recovery for Oracle on it. Visit the Demo page for a free copy of the demo.

Product specifications with lists of items recovered and not recovered is available at the Product Information page.

Note: Always backup your original corrupted Oracle database before proceeding with any recovery activity!

 
Q: What limitations does the demo version of Recovery for Oracle have?
A: The demo version recovers a limited number of rows in each table of the corrupted database. The remaining rows will contain "demo" in text fields and null values in other types of fields. Full version of Recovery for Oracle will recover the demo-limited rows as well.

No additional records or tables or any other elements and features of the original database will be recovered by commercial version of Recovery for Oracle if not present in demo output.

 
Q: I have tried the demo. How do I decide whether to purchase the full version of Recovery for Oracle?
A:

Evaluating the results of demo recovery can help in making the decision.

 
Q: What are the differences between product licenses?
A:

Details of current licensing scheme are described at the Licensing page.

 
Q: Why do results of recovery contain less data than the original Oracle database?
A: This is normal. The damaged parts of your Oracle database will convert to zero size on output. The other common reason of file size decrease is when some of features of the original database are not supported and therefore absent from the recovered database.
Demo-recovered database is smaller because it mostly consists of demo placeholders than actual data.
 
Q: Running Recovery for Oracle from command line (through Windows Start -> Run menu).
A:

If your license type is Enterprise or Service, you can run Recovery for Oracle from command line and use these calls in your batch files. Standard version does not support command line. The format for command line call is:

ora.exe <original filename with path> "<path to directory to store the recovered file(s)>"
(without angle brackets).

Please note that the directory for recovered file(s) should be created before starting the recovery.

Command line mode supports patterns '*' (replaces group of symbols) and '?' (replaces one symbol).

 
Q: After running Recovery for Oracle on the corrupted database, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new database?
A:

To recreate database, process resulting sql scripts starting with schema.sql and following by dataNNNN.sql. The database will be recreated from scratch.

To make the import procedure more convenient for the end-user an appropriate batch file is automatically created and put in the same folder as sql script(s).

 
Q: Processing of sql scripts created by Recovery for Oracle does not rebuild the database and/or produce any error messages. What is the problem with?
A: In addition to script(s) the assisting batch file commit.bat is created to automate database rebuilding procedure. The following parameters should be passed as command-line arguments:
  1. Path to sqlplus.exe utility without file name (e.g., c:\oracle\ORA90\bin);
  2. User name to use for database creation (e.g., SYSTEM);
  3. Password;
  4. "Connect string" to the server where database rebuilding scripts will be executed.

Recovery for Oracle Error Messages

 
Q: Recovery for Oracle Error: Internal Program Error message.
A:

Run Recovery for Oracle in a logged mode and contact our support team with detailed description of the problem and the log file.

To create log file, please hold the SHIFT key while clicking the Recover button on the toolbar of Recovery for Oracle or selecting the Recover: item in the main menu. You can also press CTRL+SHIFT+R after launching Recovery for Oracle.

 
Q: Recovery for Oracle Error: Not enough disk space.
A:

To fix this problem you need to set temporary directory to the drive with free space available (2-3 times of the original database size). Fix the Windows environment variable to use it. Do the following:

  1. Open System in Control Panel.
  2. On the Advanced tab, click Environment Variables, then click the name of the user variable (TEMP or TMP) you want to change.
  3. Click Edit to change value.
  4. Set path to the location where temporary data should be stored (e.g., e:\).
  5. Restart computer for changes to take in effect.
  6. Run the software again.

You can also use the special environment variable called OFFICERECOVERY_TMP to set the directory where Recovery for Oracle should store its temporary files. Use the method shown above to add/edit environment variable.

Oracle Error Messages

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

Product Guide

Recovery for Oracle

Product Home

Product

Product information
Free demo version is available:
Download

Order

Place an order
Upgrade
Sales assistance
1-800-920-7713
Resellers
Licensing

Support

Request support
Frequently asked questions

Company

Profile
Products
Customers

I need recovery for... Use the product reference to locate a recovery solution for your application file, database, server or media.

Office and Windows

Email

Access

Exchange Server

Excel

Exchange OST

Money

Lotus Notes

QuickBooks

OneNote

PowerPoint

Outlook

Project

Outlook Express

Publisher

Undelete for Outlook

Word

Works

Windows Backup

Windows Registry

Servers

Databases

Active Directory

Access

BizTalk

FileMaker Pro

Exchange Server

Interbase / Firebird

Lotus Notes

MySQL

Project Server

Oracle

SharePoint

Paradox

PostgreSQL

SQL Server

Sybase

SQL Anywhere Server

Visual FoxPro

Other

Media

Zip

Flash Drive

PDF

Hard Drive

JPEG, GIF, TIFF, BMP, PNG or RAW

CD and DVD

Photo File

Diskette

Photoshop

Removable Disk

WordPerfect

Virtual Drive

Writer

Calc


No portion of this website may be reproduced without express written permission by Recoveronix
Copyright © 1998-2012 Recoveronix Ltd.