Can be useful on servers with multiple databases.
config.ora can contain parameters that you may wish to be
common among all databases on the server.
e.g.
NAME VALUE VAL? MOD? MOD?
-------------------------
-------------------------------------------------- ---- ---- ----
audit_trail DB N N N
db_block_size 8192 N N N
db_files 1024 N N N
global_names FALSE N Y I
job_queue_interval 30 N N N
job_queue_processes 2 N N I
log_archive_start TRUE N N N
max_dump_file_size 10240 N Y I
max_enabled_roles 30 N N N
os_authent_prefix N N N
timed_statistics TRUE N Y I
Jared
"Fink, Dan" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/13/2002 09:48 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
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
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
