| multiplexing to reduce I/O contention [message #288892] |
Wed, 19 December 2007 00:36  |
asangapradeep
Messages: 128
Registered: October 2005
Location: UK
|
Senior Member |
|
|
Hi,
What’s the best way to organize various files in a RAC environment with two ASM disk groups?
There are two disk groups created one disk group would be used for data files (named DATA) and other would be used as the flash recovery area (named FLASH). From what I read this is what oracle recommends (two disk groups) Question comes when it comes to multiplexing various files such as control files, online redo log files and even archive logs.
The SAN has two controllers managing all its disks and all disks from one controller are assigned to one data group.
By default online redo log files are multiplexed on the two disk groups. Wouldn’t this create contention between database writer process (dbwn) and the log writer process (lgwr) ?
If all online redo log files are multiplexed on one single disk group wouldn’t it defeat the whole purpose of multiplexing?
Another thing to be considered is where to put archive logs. Putting them in the FLASH disk group would create additional contention between lgwr and arc processes.
Archiving the logs locally on each RAC node would make it risky in case a node is completely lost and need to do recovery.
So I would like to know what would be the ideal configuration for a production system.
thank you.
|
|
|
|
|
|
|
|
| Re: multiplexing to reduce I/O contention [message #289947 is a reply to message #289028] |
Wed, 26 December 2007 17:11  |
 |
ebrian
Messages: 2794
Registered: April 2006
|
Senior Member |
|
|
|
ASM can be configured to be a form of SAME, however Oracle actually recommends that you use external RAID for data protection. The SAME methodology can be utilized to provide the redundancy for the disk and then ASM disk group would be configured with EXTERNAL REDUNDANCY.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
