This content has been marked as final. Show 10 replies
You are right about that "*DML generates REDO*" but "only" not correct. Because If "*DELAYED BLOCKS CLEANOUTS*" have in your DB that REDO will produce with "SELECT". If you want, you can check "http://coskan.wordpress.com/2010/05/27/flashback-log-generation-with-select-statements/".
If I've any mistake about that , please inform me...
I know most of you have experienced in production implem of standby and dataguard. For me I only done it on test theory and not yet on production becuaseYou are using noarchivelog mode on production database ? Once I have seen how after power failure and database restart, crash recovery was using some of archivelogs. But theoretically crash recovery does not require archivelog mode.
it generats lots of logs and also affects performance.
I can only afford to setup standby as I do not have money to buy dataguard :(
Please can you enlighten me how can I recover my standby if my source database crashed and not recoverable anymore, like theres a bomb explode in my prod server while production is going on.
So there have been archive logs which lately committed and are current that is not yet transferred to the standby site. And I wonder how dataguard be able to address this?
Thanks a lot,
If you are using Standard Edition you can setup a poor man's Data Guard. There's a very good note on it here :
You can switch the TNSNAMES if the primary does crash as one option.
If you are really not using archivelog mode you should fix this ASAP.