3-2-1 InitializeFebruary 21st, 2008 — ddelmoli
A while ago I went on a crusade within my organization to review and clean up our init.ora files. Many of them had been around since versions 7.3 and 8.1 of Oracle and were simply added to over time. I still like the text-based init.ora files that I can check into source code control and liberally comment. I’m liking the fact that you can comment on parameters in spfiles too — they even have the comment fields displayable in DB Console and Grid Control.
I’m constantly amazed at the places I go where I still see the following text in their init.ora files:
# Use the following table to approximate the SGA size needed for the
# three scenarios provided in this file:
# ——-Installation/Database Size——
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
I’m guessing the init.ora file isn’t being reviewed at those places.
Anyway, I started doing this when I realized that many of the default values for particular parameters were higher / better than the ones we had “set”. And we didn’t have any documented reasons for setting them. I ended up with 2 goals:
- When the default values provided by Oracle are greater than or “better than” the values we had “set”, remove the parameter from the file
- When we need to set a parameter, we need to include a comment as to why for each and every parameter
End result was a lot more clarity around our settings and why we needed them. We also were able to basically make an init.ora template for ALL databases, since we made such heavy use of defaults.
What’s your policy for init.ora files? Do you even have one?