Re: recover uncommited data

Satheesh Babu.S wrote:
> My suggestion should work for few tables, it may not be possible with
> entire db. Also note if you need to do rollback, you need to implement
> some more logic to delete from the mirror table.
>
> Thanks and Regards,
> Satheesh Babu.S

You're suggesting, then, the OP double his schema to allow him to recover 'uncommitted data', and then implement additional logic to rollback any changes the user decides to not commit. I notice you haven't provided this 'more logic to delete from the mirror table' and since Oracle doesn't provide before rollback triggers I'm wondering how you'd provide such functionality. Certainly using DBMS_JOB or DBMS_SCHEDULER to run a procedure to delete unmatched records at a designated period during the day or night could work, but that's effort better spent on other things, in my opinion, like designing and implementing a proper backup/recovery strategy. Worrying over uncommitted data is not a task with which a DBA should be concerned. And I would not want to intentionally duplicate data for such a reason; most certainly the process of 'recovering' said 'data' would be more resource intensive than having the users re-enter the transactions which were in process at the time of a crash.

Your suggestion is worth nothing more than as an academic exercise. Yes, it can be done. However, I cannot recommend it should be done, and I expect I am not alone in that assessment.

David Fitzjarrell Received on Mon May 01 2006 - 21:15:40 CDT