Oraclebug caused by dropdatafile

Today, I encountered a bug with javasuard at 10gR2. In any case, I did perform a specific operation at a specific time and encountered a specific problem. This problem occurs in the 10gR2 version.

Today, I encountered a bug with javasuard at 10gR2. In any case, I did perform a specific operation at a specific time and encountered a specific problem. This problem occurs in the 10gR2 version.

Today, I encountered a bug with javasuard at 10gR2. In any case, I did perform a specific operation at a specific time and encountered a specific problem.

This problem occurs in a database in version 10.2.0.4.0 of 10gR2. During inspection, it is found that the tablespace usage is very high and you are ready to add some data files to fix this problem, it is also a common operation, and there is nothing to circle.

However, after adding the data file, after a while, I will receive an alarm saying that the slave database has encountered a problem and I am wondering what causes it, use dgmgrl to check the problem.

DGMGRL> show configuration;
Configuration
Name: test
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
Test-Primary database
Stest4-Physical standby database
Stest2-Physical standby database
Current status for "test ":
Warning: ORA-16607: one or more databases have failed

Through this, it is indeed found that the slave database has some problems, quickly connect to the slave database, the results view the data log, it is found that the original MRP process was stopped.
Fri Sep 11 17:58:53 2015
Errors in file/U01/app/Oracle/admin/test/bdump/test_mrp0_10953.trc:
ORA-00600: internal error code, arguments: [3689], [21], [], [], [], [], [], [], []
Errors with log/U01/app/oracle/flash_recovery_area/STEST4/archivelog/2015_09_11/o1_mf_7414_bz598mqc _. arc
MRP0: Background Media Recovery terminated with error 600
Fri Sep 11 17:58:55 2015
Errors in file/U01/app/oracle/admin/test/bdump/test_mrp0_10953.trc:
ORA-00600: internal error code, arguments: [3689], [21], [], [], [], [], [], [], []
Fri Sep 11 17:59:04 2015
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Fri Sep 11 17:59:04 2015

Seeing this error, it seems a bit strange to find the problem, because the associated ora error is a ora-600
With this question, the first thing that comes to mind is that you have encountered the problem that MRP cannot be started before. The problem of MRP cannot be started in dataguard is analyzed and solved.
For more information, see this link.
As a result, I made a similar analysis based on the current problem and found the problem.
Use the following statement to view the data file.
View in the slave database:
Select file #, df. name, df. ts #, ts. name, df. RFILE # from v $ datafile df, v $ tablespace ts
Where df. ts # = ts. ts #;
FILE # name ts # NAME
----------------------------------------------------------------------------------------------------
20/U01/app/oracle/oradata/test/test_new_data04.dbf 9 TEST_NEW_DATA
21/U01/app/oracle/oradata/test/test_new_index04.dbf 9 TEST_NEW_DATA
View master database

FILE # name ts # NAME
----------------------------------------------------------------------------------------------------
20/U01/app/oracle/oradata/test/test_new_data04.dbf 9 TEST_NEW_DATA
21/U01/app/oracle/oradata/test/test_new_index04.dbf 10 TEST_NEW_INDEX
We can find that the data files in the tablespace are inconsistent in the two databases.
At this time, the ora600 actually implies the meaning of 21 in the error.

ORA-00600: internal error code, arguments: [3689], [21], [], [], [], [], [], [], []

At this time, I suddenly realized that I accidentally added test_new_index04.dbf to the table space TEST_NEW_DATA. After the result is created, I found this problem,
Alter tablespace test_new_data drop datafile 'xxxxx' is used to delete the object, and a new data file test_new_data04.dbf is created.
This operation has no criticism, but it won't work in 10gR2 10.2.0.4.0, because there is a bug.
Bug 5623467-synchronized upt redo from alter tablespace drop datafile (Document ID 5623467.8)
Oracle does not provide any feasible suggestions for this bug. Apart from upgrading and patching, we recommend that you do not use the drop datafile command, but I have already run it. What do you do, only the standby database can be rebuilt.
Of course, I want to make some attempts in addition to the heavy work of rebuilding the slave database.
Since the data dictionary is not synchronized and the drop operation is not supported, I directly use alter database datafile 'xxxxxx' offline drop to solve this problem, the problem of the last MRP can be solved in 11 GB.
SQL> alter database datafile '/U01/app/oracle/oradata/test/test_new_index04.dbf' offline drop;
Database altered.