Skip to main content

alert.log File in 11g - New dump dest in 11g

In oracle 11g, alert file is saved in 2 location, one is in alert directory ( in XML format) and other in old style alert file in trace directory . Both contains the same information.

These logs are used when you are using the ADRCI . (Automatic Diagnostic Repository Command Interface)



Beginning with Release 11g, the alert log file is written as XML formatted and as a text file (like in previous releases). The default location of both these files is the new ADR home (Automatic Diagnostic Respository, yet another new dump dest in 11g).

The ADR is set by using the DIAGNOSTIC_DEST initialization parameter. If this parameter is omitted, then, the default location of ADR is, 'u01/oracle/product/ora11g/log' (depends on ORACLE_HOME settings).

The location of an ADR home is given by the following path, which starts at the ADR base directory: ADR_BASE/diag/product_type/product_id/instance_id

If environment variable ORACLE_BASE is not set, DIAGNOSTIC_DEST is set to ORACLE_HOME/log.

Within the ADR home directory are subdirectories:
alert - The XML formatted alertlog
trace - files and text alert.log file
cdump - core files

The XML formatted alert.log is named as 'log.xml'



eg:
/u01/app/oracle/diag/clients/user_oracle/host_1813406375_11/alert
log_998.xml



[oracle@gr host_1813406375_11]$ pwd
/u01/app/oracle/diag/clients/user_oracle/host_1813406375_11
[oracle@gr host_1813406375_11]$ ls
alert  cdump  incident  incpkg  lck  metadata  stage  sweep  trace

Comments

Popular posts from this blog

Building Continuous Data Trust with Oracle GoldenGate Veridata 26c

Today I'll discus on how we can build continuous data trust with Oracle GoldenGate Veridata 26c! As we accelerate towards hybrid and multi cloud architectures , one challenge keep coming up. That is "H ow do you trust your data across all these platforms?" With increasing data movement, replication, and transformation, even small changes can lead to major business risks. This is where Oracle GoldenGate Veridata 26c comes in handy! Rather than just validating data occasionally, the focus now is on continuous data trust . What is Veridata? It is a tool to compare data across different systems. It ensures source and target databases are in sync. It works during , Data migration, Replication setups, Ongoing operations. What’s new in Veridata 26c? 1. Support for Modern Architectures Built for hybrid, multi-cloud, and lakehouse environments with support for heterogeneous databases. 2. Continuous Data Validation Enables ongoing validation to detect data drift and inconsisten...

Bring AI to Data , A Smarter Way with Oracle!

  “Bring AI to Data” is a term I recently heard during the Oracle AI World in Singapore last week and it really caught my attention. It sounded simple but the idea behind it is quite powerful. So I thought it’s worth exploring a bit more! Normally, working with data and AI meant one thing, which is, moving data around. We would extract data from databases, send it to external tools or platforms, build machine learning models and then push the results back into the database. But this approach adds complexity, increases costs and introduces security risks. But now, Oracle is changing that model by bringing AI to where the data already is ! The concept of “Bring AI to Data” is straightforward but powerful. Instead of moving large volumes of data across systems, Oracle allows you to run AI and machine learning directly inside the database. This means that data do not have to leave its secure environment. This results faster processing, reduced data duplication, improved security ...

Top 5 Performance Tuning Tricks Every Oracle DBA Should Know!

Performance tuning in Oracle Database often focuses on obvious areas like indexes, SQL rewrites etc. But some of the most impactful improvements can come from lesser known techniques. Here are 5 such tuning tricks that can make a real difference in production environments.   Use SQL Plan Baselines to Stabilize Performance Even properly tuned queries in Oracle Database can suddenly degrade when execution plans change due to statistics refreshes or system upgrades. Using SQL Plan Baselines helps maintain stable and efficient execution plans, preventing unexpected performance regressions especially in highly changing workloads. SELECT * FROM DBA_SQL_PLAN_BASELINES; So, don’t just capture baselines, but periodically change them to allow the optimizer to adopt better plans when appropriate. Use Automatic Indexing Automatic Indexing is a useful feature in Oracle Database that can improve performance with minimal effort.  It was introduced in Oracle Database 19c and enhance...