Oracle 9i Database Administration in 10 Minutes
CH1: Understanding the Oracle Environment | CH2: Understanding the Oracle Instance | CH3: Understanding the working of Oracle Instance | CH4: Understanding Oracle Database | CH5: Oracle 9i Software Installation | CH6: Oracle 9i Database Design using DBCA | CH7: Enabling Other Computers to Access Oracle Server | CH8: Oracle Enterprise Manger | CH9: Oracle Backup & Recovery -Simple Technique | CH10: Oracle Performance Tuning
Chapter 10: Oracle Performance Tuning
If we have two Database Writer processes (DBW0, DBW1) then you may see
one more trace file sidDBW1.trc besides sidDBWR0.trc, this applies to
Archiver Process too. Similarly for Checkpoint Process (CKPT) it is
sidCKPT.trc whereas in Unix environment the trace files pertaining to
each of these processes would include the name of that process in the
file names e.g. for PMON the trace file name would be PMON_nnnn.trc etc.
Remember that user trace file will get generated when there is an error
in user’s server process which contains the details regarding that
error. We can limit the size of User trace file by specifying the
MAX_DUMP_FILE_SIZE init.ora parameter e.g. specifying the value of this
parameter as follows in init.ora file will the user trace file size to
20MB.
MAX_DUMP_FILE_SIZE=20M
Chapter 10: Oracle Performance Tuning
CH1: Understanding the Oracle Environment | CH2: Understanding the Oracle Instance | CH3: Understanding the working of Oracle Instance | CH4: Understanding Oracle Database | CH5: Oracle 9i Software Installation | CH6: Oracle 9i Database Design using DBCA | CH7: Enabling Other Computers to Access Oracle Server | CH8: Oracle Enterprise Manger | CH9: Oracle Backup & Recovery -Simple Technique | CH10: Oracle Performance Tuning
Share with others: