Company D's DBA failed to start OracleDatabase11gEnterpriseEditionRelease11.2.0.3.064bitProductionWiththePartitioning, AutomaticStorageManagement, OLAP, DataMiningandRealApplicationTestingopt
Company D's DBA accidentally deleted the TS $ data dictionary base table, causing the Database to fail to start Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 64bit Production With the Partitioning, Automatic Storage Management, OLAP, data Mining and Real Application Testing opt
Company D's DBA accidentally deleted TS $ data dictionary base table, causing the database to fail to start
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0-64bit Production With the Partitioning, Automatic Storage Management, OLAP, Data Mining And Real Application Testing options INSTANCE_NAME ------ ASMME SQL> SQL> SQL> select count (*) from sys. ts $; COUNT (*) ---- 5 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 scenario, it is very difficult to open the database normally because the data dictionary is damaged.
In this case, you can use PRM to extract data from the database. The procedure is similar to that in scenario 1. You only need to enter all the data files of the database. The procedure is as follows:
- Recovery Wizard
- Select Dictionary Mode
- Proper choice of Big or Little Endian
- Add the data file and click Load
- Restore table data as needed
Related posts:
- ORA-01173
- ORA-20001 error example
- An internal error in ORA-00600: [kclchkinteg_2] and [kjmsm_epc]
This article from: http://www.askmaclean.com, original address: http://www.askmaclean.com/archives/corrupted-oracle-dictionary-prm-dul.html, thanks to the original author to share.