Troubleshooting ORA-10567

I. Scenario Description

Database Version: 11.2.0.1 64bit active partition uard

Operating system version: centos 5.8 64bit

In the morning, the database routinely checks and finds that the undo tablespace data file is too large. After querying the largest block, it is found that only a few hundred megabytes are actually used. So it is assumed that alter database datafile 'xxxx' resize 3G; everything is OK! Before that, we were able to deal with this situation, and there were no problems! I do not like creating undo tablespace and changing the default undo tablespace.

Ii. Problems

It wasn't long before the mobile phone received the monitoring alarm information, from the read only with apply status to the read only status, and the mrp process died! Alert Log alerts are as follows:

Errors in file /u01/app/oracle/diag/rdbms/db2/xxxx/trace/xxxx_mrp0_7844.trc:ORA-00600: internal error code, arguments: [3020], [3], [10232], [12593144], [], [], [], [], [], [], [], []ORA-10567: Redo is inconsistent with data block (file# 3, block# 10232, file offset is 83820544 bytes)ORA-10564: tablespace UNDOTBS1ORA-01110: data file 3: '/u01/app/oracle/oradata/xxxx/undotbs01.dbf'ORA-10560: block type 'KTU SMU HEADER BLOCK'MRP0: Background Media Recovery process shutdown (xxxx)

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/22411Q301-0.jpg "title =" 1.jpg"/>

Iii. Problem Analysis

The db_lost_write_protect parameters of the master-slave database are set to typical.

SQL> show parameter protec;

NAME TYPE VALUE

---------------------------------------------------------

Db_lost_write_protect string typical

I guess the undo tablespace data file shrinking operation will lead to the loss of writing from the undo data file in the database. I don't know if this is an oracle bug!

Iv. troubleshooting

1: Shut down the slave database instance

2: Enable the undo tablespace to enter the Hot Backup state on the master database.

Alter tablespace undotbs01 begin backup;

3: Use the scp command to copy the data file to the specified location of the slave database. Rename the original file.

4: Start the mrp process from the database instance to the read only status. No error message is reported in the alert Log.

5. The hot backup status of the undo tablespace is disabled in the master database.

Alter tablespace undotbs01 end backup;

6. Delete the original undo tablespace data file backup from the database.

This article is from the "Bo Yue" blog and will not be reproduced!