Rman

Published on July 2016 | Categories: Documents | Downloads: 71 | Comments: 0 | Views: 277
of 2
Download PDF   Embed   Report

Comments

Content

RMAN> recover database; Starting recover at 27-NOV-11 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=225 devtype=DISK allocated channel: ORA_SBT_TAPE_1 channel ORA_SBT_TAPE_1: sid=150 devtype=SBT_TAPE channel ORA_SBT_TAPE_1: Data Protector A.06.20/370 starting media recovery archive log thread 1 sequence 17898 is already on disk as file /hrmsdata1/logs/1 _17898_651258629.dbf archive log thread 2 sequence 13606 is already on disk as file /hrmsdata1/logs/2 _13606_651258629.dbf archive log filename=/hrmsdata1/logs/1_17898_651258629.dbf thread=1 sequence=178 98 archive log filename=/hrmsdata1/logs/2_13606_651258629.dbf thread=2 sequence=136 06 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 11/27/2011 12:49:28 ORA-00283: recovery session canceled due to errors RMAN-11003: failure during parse/execution of SQL statement: alter database reco ver logfile '/hrmsdata1/logs/2_13606_651258629.dbf' ORA-00283: recovery session canceled due to errors ORA-12801: error signaled in parallel query server P000 ORA-00600: internal error code, arguments: [3020], [5], [153], [20971673], [], [ ], [], [] ORA-10567: Redo is inconsistent with data block (file# 5

1) Set _ALLOW_RESETLOGS_CORRUPTION=TRUE in init.ora file. 2) Startup Mount 3) Recover database 4) Alter database open resetlogs. 5) reset undo_management to manual in init.ora file. 6) startup database 7) Create new undo tablespace changed undo_management to AUTO and undo_tablespace to NewTablespace 9) Bounce database. (1) Take a Backup. (2) Shutdown the DB (2) Set UNDO_MANAGEMENT=MANUAL (3) Set parameter _OFFLINE_ROLLBACK_SEGMENT = (_SYSSMU1$, _SYSSMU2$...) etc for all the segments that were in the original UNDO tablespace. I checked v$rollname for the name of those active ones in the replacement UNDO TBS (they were number ed 11 - 20) so I put 1 - 10 in the offline_rollback_segment parameter. (4) Open the DB (5) Drop each RBS 1 - 10 individually using 'DROP ROLLBACK SEGMENT "seg_name". (6) Drop the UNDO tablespace. (7) Shutdown the DB (8) Comment out or remove the parameter _OFFLINE_ROLLBACK_SEGMENT (9) Set UNDO_MANAGEMENT back to AUTO (10) Ensure the UNDO_TABLESPACE is set to your new UNDO TBS name (11) Restart the DB

(12) Check the alert log for any errors - if all looks pukka then shutdown and t ake another backup. (You know it makes sense) _OFFLINE_ROLLBACK_SEGMENT is undocumented and support warn that its use should b e restricted to those occasions when support ask you to use it. Be warned!

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close