Hi!
I hit a bug 1083739 when restoring my 8.0.6 database. The fix is included in 8.1.7, but the db cannot be upgraded because of application running on it. The upgrade is planed in next half a year. I cannot survive without a properly restoring backup for such a long time...
The bug causes restore problems if SCNs are very high. They are.
Is there any way to reset the SCN to 0? How?
Did anybody experience this bug? How did you survived?
The offline backup (without using RMAN) is not possible as we lack of backup window and also a db is very large and must be backed up directly to tape using media manager software. We don't have enough space to run a backup to disks.
Thanks,
mewa
I hit a bug 1083739 when restoring my 8.0.6 database. The fix is included in 8.1.7, but the db cannot be upgraded because of application running on it. The upgrade is planed in next half a year. I cannot survive without a properly restoring backup for such a long time...
The bug causes restore problems if SCNs are very high. They are.
Is there any way to reset the SCN to 0? How?
Did anybody experience this bug? How did you survived?
The offline backup (without using RMAN) is not possible as we lack of backup window and also a db is very large and must be backed up directly to tape using media manager software. We don't have enough space to run a backup to disks.
Thanks,
mewa