How to disable all the trcings of oracle???

Hi,

I have set up our application environment with all default options of oracle. The application ran find for few days. One day suddenly it stopped responding. Then after checking, I came to see my harddisk is full because of the trace files generated by oracle in the bdump directory. I was surprised to see a file of size 18GB in the bdump directory. May I know how to disable all the tracing options of oracle???

Thanks in advance.

Raghu
raghudesamAsked:
Who is Participating?
 
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
Hi raghudesam,
  No, tracing cannot be disabled, it is considered to be essential part for Oracle.
  For example, if the folder for the trace doesn't exist, oracle refuses to start / stops immediately if running.

  The trace files should always be taken into account by the DBA, and a logroll+backup+cleanup to keep the trace file folders "small".

Cheers
0
 
ypwitkowCommented:
What is the name of the file?

Lucy
0
 
Rajkumar_SinhaCommented:
    You cannot prevent the information being written into the trace file. All background processes write to the trace file and alert log file when ever appropriate. This control is not available to user/DBA. But in case of trace information generated from LGWR, specifying initialization file parameter LOG_ARCHIVE_TRACE can control the amount of information writeen to trace file. This can have various values, the default being ZERO, which is to DISABLE the tracing. In this case, the normal operation of LGWR will not be logged, but the erroneous operation will still get logged into the trace file.
    Server processes can be prevented from writing nornmal operation information to trace file by setting Initialization parameter SQL_TRACE = FALSE. In this case only internal errors will get logged in.
    Another way of controlling the size of trace file is by setting the initialization file parameter           MAX_DUMP_FILE_SIZE that specifies the maximum size up to the entire trace file in combination, except Alert Log, can grow. Alert log has to be monitored manually and cleaned from time to time.

Thus writing to trace files cannot be prevented, however, amount of data being written can be controlled to an extent.
0
 
Rajkumar_SinhaCommented:
    You cannot prevent the information being written into the trace file. All background processes write to the trace file and alert log file when ever appropriate. This control is not available to user/DBA. But in case of trace information generated from LGWR, specifying initialization file parameter LOG_ARCHIVE_TRACE can control the amount of information writeen to trace file. This can have various values, the default being ZERO, which is to DISABLE the tracing. In this case, the normal operation of LGWR will not be logged, but the erroneous operation will still get logged into the trace file.
    Server processes can be prevented from writing nornmal operation information to trace file by setting Initialization parameter SQL_TRACE = FALSE. In this case only internal errors will get logged in.
    Another way of controlling the size of trace file is by setting the initialization file parameter           MAX_DUMP_FILE_SIZE that specifies the maximum size up to the entire trace file in combination, except Alert Log, can grow. Alert log has to be monitored manually and cleaned from time to time.

Thus writing to trace files cannot be prevented, however, amount of data being written can be controlled to an extent.
0
 
Rajkumar_SinhaCommented:
    You cannot prevent the information being written into the trace file. All background processes write to the trace file and alert log file when ever appropriate. This control is not available to user/DBA. But in case of trace information generated from LGWR, specifying initialization file parameter LOG_ARCHIVE_TRACE can control the amount of information writeen to trace file. This can have various values, the default being ZERO, which is to DISABLE the tracing. In this case, the normal operation of LGWR will not be logged, but the erroneous operation will still get logged into the trace file.
    Server processes can be prevented from writing nornmal operation information to trace file by setting Initialization parameter SQL_TRACE = FALSE. In this case only internal errors will get logged in.
    Another way of controlling the size of trace file is by setting the initialization file parameter           MAX_DUMP_FILE_SIZE that specifies the maximum size up to the entire trace file in combination, except Alert Log, can grow. Alert log has to be monitored manually and cleaned from time to time.

Thus writing to trace files cannot be prevented, however, amount of data being written can be controlled to an extent.
0
All Courses

From novice to tech pro — start learning today.