| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> BAARF - true life story
I just joined this site.
Less than 6 weeks ago they had a problem with one of their
Oracle DBs. It seems it was running on a RAID-5 volume.
A disk died. The hot spare got automagically included,
but nobody was notified or noticed this happening. Then
2nd disk failed. It was some time after this that errors
started and one of the *DBF had gotten corrupted. They
have been able to reload the records which had been
sitting on the bad block. So we think that from a logical
(data) standpoint the problem has been resolved. The DBV
utility no longer reports any bad blocks.
We now have to move this whole database (178GB) to a new system, with minimal downtime.
We have worries, doubts & concerns about just doing an OS copy from the old to the new system. Can there still be 1 or more bad blocks in the tablespace that just are not being used now? If the OS (Linux) has tagged & remapped bad blocks, will an OS copy allow them to be "left behind"? We doubt we have a big enough downtime window to allow for either an expotr/import to RMAN duplicate operation.
What would YOU do given this history & requirements?
 |
 |