Timeline for Oracle 11gR2 permit NOLOGGING but ensure non-corrupt backups
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2016 at 14:25 | comment | added | KevinKirkpatrick | Just realized - maybe simplest recovery: 1) recover db to backup 2) export TS D 3) recover db to time-of-failure (pprobably leaving many ORA-26040 in TS D) 4 Drop TS D, restore from export. Thoughts/improvements? Will update answer and accept once settled. | |
| Apr 8, 2016 at 14:25 | comment | added | atokpas | @KevinKirkpatrick Yes it waits for nologging operation to complete, my sentence gave wrong meaning may be. | |
| Apr 8, 2016 at 14:20 | comment | added | KevinKirkpatrick | Another comment indicates that FORCE_LOGGING will wait on running operations; I'll work out a way to trial this. If you're correct I'll run rman report unrecoverable after each backup (and instruct to app devs to avoid ETL during backup window). For TSPITR, it sounds like it rewinds... so I think I'd need TSPITR on D to "run it back" to the SCN of latest backup. But it seems both TSPITR or flashback table may balk at NOLOGGING op in archive logs - it sounds like recovery of TS D may just need to be done independent then imported. | |
| Apr 8, 2016 at 14:07 | history | edited | atokpas | CC BY-SA 3.0 |
added 50 characters in body
|
| Apr 8, 2016 at 13:59 | history | answered | atokpas | CC BY-SA 3.0 |