Saturday, February 8, 2025

How to select/filter specific lines from the oracle database alert log?

Usually when verifying the alert log entries to troubleshoot any database specific issue, it will take a good amount of time if the alert log is huge like 10MB or 20MB etc.. During such situations, if we know the exact error time, to filter specific lines from alert log, please use below script.
awk '$0 >= "2025-01-19T00:00:00" && $0 <= "2025-01-25T00:00:00" {print $0; getline; print $0}' /u02/app/oracle/diag/rdbms/test1/TEST1/trace/alert_TEST1.log > selected_alert.txt
in the above command, selected_alert.txt contains your required output lines from the alert log.
reference article :
https://ermannkara.wordpress.com/2025/02/06/filter-a-specific-time-range-in-the-alert-log-and-write-the-results-to-a-txt-file/

Sunday, January 26, 2025

Oracle DB patching (single instance db's) with autoupgrade tool - livelabs session

As we all know opatch is old way of patching oracle db's and autoupgrade is emerging now a days, There is a good livelab session is there if we want to practice patching (single instance) with AUTOUPGRADE tool.
https://apexapps.oracle.com/pls/apex/dbpm/r/livelabs/view-workshop?wid=3740

Wednesday, January 22, 2025

Oracle database Features and Licensing information for all the database releases through 11.2.0.2 to 23ai

Sometimes we want to compare/verify the database feature(s) that is/are available in a perticular database version. During that time, we need to verify oracle documentation (or) some other resources available in the internet. Some times we did not get the details easily. In such cases, to save our time, use below link for database features and licencing information

Oracle database Features and Licensing information

Tuesday, January 7, 2025

Oracle database release schedule (updated till 23ai)

Please find the master note for Oracle database releases..
Schedule of Current Database Releases (Doc ID 742060.1)

Thursday, December 19, 2024

oracle "shutdown immediate" not getting completed due to active application sessions.

I faced a strange issue when i fired the command
 shut immediate 
on one of our running oracle database instances. When i fired this shutdown command, it took longer time and the database is not closed. instead the command rolled backed by oracle itself with below comments.
alert log
========== 
Active process 31928 user 'oracle' program 'oracle@sitdb2', waiting for 'single-task message'

Active process 20462 user 'oracle' program 'oracle@sitdb2', waiting for 'single-task message'

Active process 14219 user 'oracle' program 'oracle@sitdb2', waiting for 'single-task message'

SHUTDOWN: Active sessions prevent database close operation
          Shutdown did not complete in 60 minutes
Instance shutdown cancelled
2024-12-20T12:41:57.103353+07:00


shutdown command what i executed is..
even though i have not killed the session, oracle automatically killed the session after 60 minutes of wait time (as updated in alert log).

SYS@XLTABP1:SQL> shut immediate;

ORA-01013: user requested cancel of current operation
SYS@XLTABP1:SQL> 

Minimalistic Oracle: A SQL-centric and a session-centric way to query V...

Minimalistic Oracle: A SQL-centric and a session-centric way to query V... : Version 1: SQL-Centric  This version starts from V$SQL and...