As I was searching the Internet for articles on Database Administration I came across an interesting question posted by Earle Shaffer.
Oracle on Windows – any first-hand advice?
Hi – I am looking for tips, tricks, and gotchas about running Oracle on the Windows platforms. Specifically regarding RAM and IO monitoring.
In my experience Oracle DBA’s fall into one of two camps.
- They are windows Operating system haters
- They are Windows operating systems tolerant.
I am not saying this if right. It’s so how they intially respond. I think it come from too much Oracle corporation brainwashing. So when I saw this question posed, I was curious what I might see for answers. What I saw was a wonderful dialogue full of very useful information.
So in this blog entry I will take the time to share with you some of what I saw.
James Rice an Oracle DBA at Abbott laboratories responded:
Make sure that you are buying I/O cards for the machine and not using the I/O on the motherboard – not enough throughput – and you should use multiple I/O cards for maximum spread. If you are using external disk then you need to make sure the storage if properly LUN’d to spread out the I/O as you have very little visibility as to how the disk are spread out. If you can buy the MKS Unix toolkit for windows so you can use unix scripts to manage your db as windows scripting can be weak. As for RAM – use a 64 bit os and you don’t have issues but if you can’t then remember a 2gb sga is about it – you can make it bigger but you will suffer. Hope this helps.
James response is loaded with nuggets of gold and a lot of common sense.
The slowest operation most computers do is I/O. Anything you can do minimize I/O is usually a step in the right direction. I/O bottlenecks will kill database performance very quickly. When it comes to database, you are delaing with a major hog of I/O resources. This is just plain good common sense, especially as it pertains to windows operating system.
I loved the MKS Unix toolkit for windows suggestion. Oracle DBA’s love to make windows look like Unix. Let me say that again, Oracle DBA’s love to make windows look like Unix.
The comment on 64Bit Operating system is also great advice. For those windows shops not using 64 bit, then remember a 2gb SGA is about it. I would take the commentone step further. Never let the SGA be more than 50% of the available memory on the box. You need to leave enough memory for the operating system to do its job.
What is very clear from all the comments. 64 Bit Operating system on windows for Oracle is not a nice to have, its a must have.
Martin Millstam of Oracle Corporation provided some useful links:
Oracle Database on Windows and .NET FAQ
Oracle Database Search Results: windows
Oracle Database Architecture on Windows
Administering a Database on Windows
Vendors like Oracle and Microsoft publish lots of great information. Take the time to read it. This was an excellent suggestion.
Jeff Wong DBA at AON
windows powershell is possibly the best way to go if you’re in a windows environment – it’s distributed now as standard with win2k8 server I believe. Otherwise you could try cygwin for unix shell compatibility.
Once again an Oracle DBA telling you another way to help it work like Unix.
Tuning Windows to Optimize Oracle Database
Make sure you are buying I/O cards for the machine and not using the I/O on the motherboard.
If you are using external disk then you need to make sure the storage if properly LUN’d to spread out the I/O as you have very little visibility as to how the disk are spread out.
As for RAM – use a 64 bit os and you don’t have issues but if you can’t then remember a 2gb sga is about it – you can make it bigger but you will suffer.
UWIN if you want a Unix Like environment on windows
the MKS Unix toolkit for windows so you can use unix scripts to manage your db
try cygwin for unix shell compatibility
Founder & CEO, Ntirety
My Personal Twitter Account: Michael_Corey
Ntirety Corporate Twitter Account: Ntirety