Trace Files and the Alert Log-LGWR

Posted on June 8th, 2008 by admin

Each server and background process can write to an associated trace

file. When a process detects an internal error, it dumps information

about the error to its trace file. If an internal error occurs and

information is written to a trace file, the administrator should

contact Oracle support.

Each database also has an Alert log. The ALERT file of a database is

a chronological log of messages and errors.

 

Oracle does not consider a transaction as committed until LGWR

successfully writes you transactions redo entries and a commit

record to the transaction log.


Add your opinion - this will move the pointer
get dashboard plugin?

Filed under: DBA (DataBase Administrator), DataWarehousing, ERP, PL/SQL, SQL

Free Dashboards

Here are some more interesting Articles
  • Oracle architecture- background processes
  • How to deploy dashboard on Web – Server or intranet
  • How to deploy dashboard on Web – Server or intranet
  • How to deploy dashboard on Web – Server or intranet
  • How to deploy dashboard on Web – Server or intranet
  • How to deploy dashboard on Web – Server or intranet

    • Leave a Reply

    You must be logged in to post a comment.

    « ROWID UROWID »

    • About InfoPurple

      InfoPurple is an Oracle Digest that collects best articles from the best minds from entire blogosphere. We collect them and post an excerpt and point back to the main site. This allows for a consolidated view of Oracle Apps related topics. If you would like to add your website to be included then please email us (infopurple8888 AT gmail DOT com) your web url. If you would like to get your website removed then send us an email and we will remove it. -- infoK purple