你在这里

You are here:

首页

博客

PDSERVICE的博客

Recover Database Can't be opened(corrupted System TABLESPACE or dictionary) using PRM-DUL

Posted by PDSERVICE on 11月 29, 2015 In

Case 3: Oracle Dictionary Corrupted, DB can not be open

DBA of company D deleted SYS.TS$ (A bootstrap Table) by mistake, this cause Oracle DB can not be open

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit ProductionWith the Partitioning, Automatic Storage Management, OLAP, Data Miningand Real Application Testing options

INSTANCE_NAME

—————-

ASMME

SQL>

SQL> select count(*) from sys.ts$;

COUNT(*)

———-

SQL> delete ts$;

5 rows deleted.

SQL> commit;

Commit complete.

SQL> shutdown immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

Database mounted.

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-01405: fetched column value is NULL

Process ID: 5270

Session ID: 10 Serial number: 3

Undo initialization errored: err:1405 serial:0 start:3126020954 end:3126020954 diff:0 (0 seconds)

Errors in file /s01/diag/rdbms/asmme/ASMME/trace/ASMME_ora_5270.trc:

ORA-01405: fetched column value is NULL

Errors in file /s01/diag/rdbms/asmme/ASMME/trace/ASMME_ora_5270.trc:

ORA-01405: fetched column value is NULL

Error 1405 happened during db open, shutting down database

USER (ospid: 5270): terminating the instance due to error 1405

Instance terminated by USER, pid = 5270

ORA-1092 signalled during: ALTER DATABASE OPEN…

opiodr aborting process unknown ospid (5270) as a result of ORA-1092

In this circumstance, data dictionary had been damaged; therefore it would be very hard to open the database.

Then, we can use PRM-DUL rescue data in DB. Following processes as below:

Recovery Wizard
Select Data Dictionary Mode
Choose Big or Little Endian , and input DB NAME
Click Load for database loading
Extract Tables