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...
|
- Init.ora and Config.ora Fink, Dan
- Re: Init.ora and Config.ora Rachel Carmichael
- Re: Init.ora and Config.ora Jared . Still
- Re: Init.ora and Config.ora Tim Gorman
- Re: Init.ora and Config.ora Rachel Carmichael
- RE: Init.ora and Config.ora Mercadante, Thomas F
- RE: Init.ora and Config.ora Fink, Dan