RAC vs. DB link on availability and performance
1002650May 4 2013 — edited May 7 2013My prod database is having big availability and performance issue, now it's just using single database instance.
One of major job for this database is to output log in a table, it's writing out 2 mill text message/record (255 characters) per business hour, for sure it's using tons of I/O and disk space.
To distribute this task for gaining better availability and performance, I'm wondering, whether setting up RAC or db link can help, and which is better?if using RAC, any configuration option to instruct database server such that for a log table, always use node 2, all other tables always use node 1?
--
Thanks.
John