Custom Search
#header-wrapper { margin:0; padding: 0; background-color: #1d3146; text-align: left; } #header { margin: 0 2%; background-color: #1d3146; color: #ffffff; padding: 0; font: normal normal 210% Verdana, Arial, Sans-serif;; position: relative; } h1.title { padding-top: 38px; margin: 0 1% .1em; line-height: 1.2em; font-size: 100%; } h1.title a, h1.title a:visited { color: #ffffff; text-decoration: none; } #header .description { display: block; margin: 0 1%; padding: 0 0 40px; line-height: 1.4em; font-size: 50%; } /* Content ----------------------------------------------- */ .clear { clear: both; } #content-wrapper { margin: 0 2%; padding: 0 0 15px; text-align: left; background-color: #ffffff; border: 1px solid #cccccc; border-top: 0; } #main-wrapper { margin-left: 1%; width: 64%; float: left; background-color: #ffffff; display: inline; /* fix for doubling margin in IE */ word-wrap: break-word; /* fix for long text breaking sidebar float in IE */ overflow: hidden; /* fix for long non-text content breaking IE sidebar float */ } #sidebar-wrapper { margin-right: 1%; width: 29%; float: right; background-color: #ffffff; display: inline; /* fix for doubling margin in IE */ word-wrap: break-word; /* fix for long text breaking sidebar float in IE */ overflow: hidden; /* fix for long non-text content breaking IE sidebar float */ } /* Headings ----------------------------------------------- */ h2, h3 { margin: 0; } /* Posts ----------------------------------------------- */ .date-header { margin: 1.5em 0 0; font-weight: normal; color: #999999; font-size: 100%; } .post { margin: 0 0 1.5em; padding-bottom: 1.5em; } .post-title { margin: 0; padding: 0; font-size: 125%; font-weight: bold; line-height: 1.1em; } .post-title a, .post-title a:visited, .post-title strong { text-decoration: none; color: #333333; font-weight: bold; } .post div { margin: 0 0 .75em; line-height: 1.3em; } .post-footer { margin: -.25em 0 0; color: #333333; font-size: 87%; } .post-footer .span { margin-right: .3em; } .post img { padding: 4px; border: 1px solid #cccccc; } .post blockquote { margin: 1em 20px; } .post blockquote p { margin: .75em 0; } /* Comments ----------------------------------------------- */ #comments h4 { margin: 1em 0; color: #999999; } #comments h4 strong { font-size: 110%; } #comments-block { margin: 1em 0 1.5em; line-height: 1.3em; } #comments-block dt { margin: .5em 0; } #comments-block dd { margin: .25em 0 0; } #comments-block dd.comment-footer { margin: -.25em 0 2em; line-height: 1.4em; font-size: 78%; } #comments-block dd p { margin: 0 0 .75em; } .deleted-comment { font-style:italic; color:gray; } .feed-links { clear: both; line-height: 2.5em; } #blog-pager-newer-link { float: left; } #blog-pager-older-link { float: right; } #blog-pager { text-align: center; } /* Sidebar Content ----------------------------------------------- */ .sidebar h2 { margin: 1.6em 0 .5em; padding: 4px 5px; background-color: #ffd595; font-size: 100%; color: #333333; } .sidebar ul { margin: 0; padding: 0; list-style: none; } .sidebar li { margin: 0; padding-top: 0; padding-right: 0; padding-bottom: .5em; padding-left: 15px; text-indent: -15px; line-height: 1.5em; } .sidebar { color: #333333; line-height:1.3em; } .sidebar .widget { margin-bottom: 1em; } .sidebar .widget-content { margin: 0 5px; } /* Profile ----------------------------------------------- */ .profile-img { float: left; margin-top: 0; margin-right: 5px; margin-bottom: 5px; margin-left: 0; padding: 4px; border: 1px solid #cccccc; } .profile-data { margin:0; text-transform:uppercase; letter-spacing:.1em; font-weight: bold; line-height: 1.6em; font-size: 78%; } .profile-datablock { margin:.5em 0 .5em; } .profile-textblock { margin: 0.5em 0; line-height: 1.6em; } /* Footer ----------------------------------------------- */ #footer { clear: both; text-align: center; color: #333333; } #footer .widget { margin:.5em; padding-top: 20px; font-size: 85%; line-height: 1.5em; text-align: left; } /** Page structure tweaks for layout editor wireframe */ body#layout #header { width: 750px; } -->
PARAMETERS
--------------------------------------------------------------------------------------
BACKGROUND_DUMP_DEST
background_dump_dest specifies the directory (folder) where trace files of background processes are being written. It also specifies the location for the alert.log file.
It is also used for ORA-00600 errors.
Explain BACKGROUND TRACE FILES?

Background trace files are used to log errors that have been encountered by a background process, such are SMON, PMON, DBWn, and other background processes.

These files exist only when an error requires writing to the trace files.You use these files to diagnose and troubleshoot problems.

Naming convention for user trace file: sid_processname_PID.trc

Its location is defined by the BACKGROUND_DUMP_DEST initialization parameter.
What is an Alert_SID.log file?

Each Oracle Instance has an alert log file. If not already created, it is created during instance
startup.

The alert log file should be the first place you look when diagnosing dayto-day operations or errors. The alert log file also contains pointers to trace files for more detailed information.

The alert log file keeps a record of the following information:
• When the database was started or shut down
• A list of all non-default initialization parameters
• The startup of background processes
• The thread being used by the instance
• The log sequence number LGWR is writing to
• Information regarding a log switch
• Creation of tablespaces and undo segments
• Alter statements that have been issued
• Information regarding error messages such as ORA-600 and extent errors
--------------------------------------------------------------------------------------
USER_DUMP_DEST
The value of user_dump_dest specifies the destination where user processes will write trace files.
It is also used for ORA-00600 errors.
What is User Trace File?
User trace files contain statistics for traced SQL statements, which are useful for SQL tuning.
  • Naming convention for user trace file: sid_ora_PID.trc (Ex: db01_ora_23845.trc).
  • Produced by the user process
  • Can be generated by a server process
  • Contains user error messages
  • Created when a user encounters user session errors
  • Location is defined by USER_DUMP_DEST
  • Size defined by MAX_DUMP_FILE_SIZE

Enabling or Disabling User Tracing

Session level:
Using the ALTER SESSION command:

ALTER SESSION SET SQL_TRACE = TRUE

Executing DBMS procedure:

dbms_system.SET_SQL_TRACE_IN_SESSION

Instance level
Setting the initialization parameter:

SQL_TRACE = TRUE

Setting SQL_TRACE=TRUE at the instance level will produce a significant volume of trace data.

This option should be used with care.

--------------------------------------------------------------------------------------

No comments: