>> > What happens to the logs if they suddenly tell you that you have to
>> > go to the past?
>> >
>> > That is my question.
>>
>> An hour off is pretty serious. If it's really that bad, you have a
>> problem. Least intrusive: jump it at 02:00, or jump it in maybe five
>> minute intervals once or twice a day. I'd lean towards the former.
>
> That could be even worse. My biggest concern would be the effect on redo
> logs. I don't know how oracle handles time jumps into the past but my
> fear would be if you ever had to apply those redo logs then they could be
> applied in the wrong order so recovery from backup would be impossible for
> any time span that contained a backward jump.
Yeah, you're probably right. I think the best answer would be to halt
Oracle, then jump the time, then bring Oracle back up. Even then, you'd
probably want to wait an hour before bringing it up.
<snip>
I'm curious: how did production boxes get to be a whole hour off?
mark
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
