Oracle 11g Recovery uard undo recovery

Oracle 11g restart uard undo restore environment: OS: centos5.5db: oracle11g datauardversion: 11.2.0.2.0 shrink data file size in primary ALTER DATABASE DATAFILE '/oracle/oradata/skatedb/undotbs03.dbf 'resize 1024 M; www.2cto.com will receive an alert message later. log on to the standby database and find it in alert. the following error occurs in logl ...... media Recovery Waiting for thread 1 sequence 17248 (in transit) Recovery of Online Redo Log: Thread 1 Group 8 Seq 17248 Reading mem 0 Mem #0: /oracle/oradata/skatedb/sdbyredo08.logThu Oct 11 13:59:06 2012 Archived Log entry 10938 added for thread 1 sequence 17247 ID 0xa47b04d0 dest 1: thu Oct 11 14:06:26 2012 Errors in file/oracle/app/diag/rdbms/skate04/skatedb/trace/skatedb_pr0d_25721.trc (incident = 40497): ora-00600: internal error code, arguments: [3020], [3], [160], [12583072], [], [], [], [], [], [], [], [] ora-10567: Redo is inconsistent with data block (file #3, block #160, file offset is 1310720 bytes) ora-10564: tablespace UNDOTBS1ora-01110: data file 3: '/oracle/oradata/skatedb/undotbs01.dbf' ora-10560: block type 'ktu smu header Block' Incident details in: /oracle/app/diag/rdbms/skate04/skatedb/incident/incdir_40497/skatedb_pr0d_25721_i40497.trcThu Oct 11 14:06:52 2012 ...... the standby database www.2cto.com cannot be applied to restart standby, and the database can be alter database mount standby database. However, when open read is only, the above error is always reported on standby, execute the following SQL statement or recover standby database. To solve this problem, we decided not to restore undotbs01.dbf and directly copy the file from primary (the master database is newer ), then, in the standby database, perform the following operations on www.2cto.com: to ensure data file consistency, freeze the TABLESPACE undo1.primary: SQL> ALTER TABLESPACE UNDOTBS1 BEGIN BACKUP; 2. standby: shutdown immediate
3. primary: copy the undotbs01.dbf file on primary to standby. After the copy is complete, it must be restored (if it is not restored, it will be hang when applying the standby database) SQL> ALTER TABLESPACE UNDOTBS1 END BACKUP; 4. standby: SQL> startup nomount; SQL> alter database mount standby database; SQL> alter database open read only; SQL> alter database recover managed standby database disconnect using current logfile; note, when operating the tablespace uard environment, pay special attention to the undo tablespace and data operations. Here is an example. Another example is www.2cto.com. To save space and decide to shrink the undo size, follow these steps: 1. create a new undotbs2 tablespace on primary and check and verify the tablespaces and corresponding data files on primary and standby. replace the online undo tablespace on primary. Run the following command SQL> alter system set undo_tablespace = undotbs2 scope = both; system alteredSQL> View SQL> show parameter undo NAME TYPE VALUE ------------------------------------------ -------------------------------- undo_management string AUTOundo_retention integer 900 undo _ Tablespace string UNDOTBS2, but on standby, check SQL> show parameter undoNAME TYPE VALUE =----------- unknown undo_management string AUTOundo_retention integer 900undo_tablespace string UNDOTBS1 www.2cto.com, so I want to change it to the spfile file, restart the database, and the result is wrong (restored using the mountain method). Theoretically, no error should be reported. Find the environment to continue the test.