Blogs

Home

News

Features

Network

Events

CXO

Technology

Entrepreneurship

Strategy

Education

Cities

Job Board

Editor's Picks

(1-4 of 8)

Social Engineering: Methods To Minimize Risks

Stuff Better To Know Before Hard Drive Rec...

The Advantage Of B2B Marketing Explained

4 Keys To Peace Of Mind In Times Of Trouble

Oracle Database Corrupt Post Upgradation To 9.2.0.8

Upgrading your Oracle database allows you to use all the new features provided in the upgraded version. To upgrade from Oracle 9.2.0.1 to 9.2.0.8 version, you just need to download the patch compatible with your operating system, shutdown your database, perform a cold backup, and install 9.2.0.8 batch. While the process seems to be simple, it can result into disastrous situations, if not done properly, mostly leading to corruption of the Oracle database. In such cases, the Database Administrator (DBA) is unable to mount the database that further renders to inaccessibility of its stored data. To overcome such situations, the DBA needs to restore the data from an updated backup. However, if no backup is available, then the DBA needs to repair the database using an advanced third-party Oracle Recovery application.

Consider a practical case, where you convert your database from Oracle 9.2.0.1 to 9.2.0.8. After doing so, when you try to mount the database, it does not mount. On viewing the alert.log file, you find the below information:

“Corrupt block relative dba: 0x0180000b (file 6, block 11)
Bad header found during buffer read
Data in bad block -
type: 35 format: 2 rdba: 0x0040000b
last change scn: 0x0000.00000000 seq: 0xff flg: 0x04
consistency value in tail: 0x000023ff
check value in block header: 0x551d, computed block checksum: 0x0
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x0180000b (file 6, block 11) found same corrupted data
Hex dump of Absolute File 6, Block 19 in trace file d:\oracle\admin\oracle9i\bdump\oracle9i_

smon_1100.trc”

Cause:

The database could not mount because it is corrupted. Corruption in this case primarily occurs due to improper upgradation.

Resolution:

To resolve the above issue and to access the database records, the DBA should run 'dbms_repair' command. However, if the command fails to resolve the problem, then s/he needs to use an effective DBF Recovery application.

An Oracle Recovery tool ensures complete repair of every logically corrupted Oracle database. A DBA just needs to download the software, browse to the corrupted file, and perform repair. These applications do not modify or overwrite the original records saved in an Oracle database.

Oracle Recovery software provides comprehensive repair of Oracle database, irrespective of their size. Compatible with Oracle 9i, the read only Oracle Recovery tool recovers objects like tables, indexes, views, sequences, and table spaces. It is designed for Windows XP and 2003 operating systems.