Dan,
 
I agree with Rachel.  I have one init.ora file for each database instance.  I personally *HATE* the "ifile" business.  All that it does is make me go searching in another directory to see what the parameters are set to.
 
I like to go to one directory/one file to set/review my init params.  I can see everything in one place, and I don't have to go searching/remembering where things are.
 
I also keep  this file in the ORACLE_HOME/dbs or database directory (depending on OS).  Frig the pfile directory.  Another lousy idea from somebody.
 
hope this helps.
 
Tom Mercadante
Oracle Certified Professional
-----Original Message-----
From: Tim Gorman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 1:49 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Init.ora and Config.ora

I always thought it was for separating instance-specific parameters from database-specific parameters in an OPS environment.  At least, that's one place where it is very useful to have separate files.  Of course, it was a matter of style whether "config.ora" was the database-level one or vice-versa...
 
Also, somewhere back in the mists of time, any ".ora" file for initialization parameters had to be less than 10,000 characters in size;  anything beyond that boundary was simply not used (I kid you not!).  So, having multiple files related by "ifile=" was the workaround, especially for those neurotic souls who insisted on leaving comments for documentation...
----- Original Message -----
From: Fink, Dan
Sent: Thursday, June 13, 2002 10:48 AM
Subject: Init.ora and Config.ora

Beware...DBA heresy below...
 
I am in the process of cleaining up parameter files and wonder why we still maintain an init.ora and config.ora. The original rational was that one contained the database configuration/creation parameters while the other was used for tuning.
 
Is there a good reason why we have 2 files instead of a single file?

Daniel W. Fink
Sr. Oracle DBA
MICROMEDEX
303.486.6456

 

Reply via email to