Skip to main content

Shell Script to Read Oracle Database Alert Log and Report ORA Errors

Shell Script to Read Oracle Database Alert Log and Report ORA Errors

In this post, I will share shell script to check and read my alert log file based in timestamp and provide me ORA  errors from last check timestamp. The script will capture data after last checked timestamp.

Assumption:
You need to know your alertlog file path


Script:
#!/bin/bash
#set -x
# Oracle environment variables (adjust as necessary)
#export ORACLE_SID=your_sid
#export ORACLE_HOME=/path/to/oracle_home
#export PATH=$ORACLE_HOME/bin:$PATH
. ~/.bash_profile
# Paths to alert log and timestamp file
ALERT_LOG="/u01/db/TRAIN/12.1.0/admin/TRAIN_ebstraining/diag/rdbms/train/TRAIN/trace/alert_TRAIN.log"
TIMESTAMP_FILE="/tmp/last_checked_timestamp.txt"
REPORT_FILE="health_check_report.html"

# Function to validate the database alert log and identify ORA error codes
check_alert_log_for_errors() {
  echo "<h3>Database Alert Log Errors</h3>" >> $REPORT_FILE
  echo "<table style=\"border-collapse: collapse; width: 100%;\" border=\"1\">" >> $REPORT_FILE
  echo "<tr><th>Timestamp</th><th>Error Message</th></tr>" >> $REPORT_FILE

  # Get the last checked timestamp
  if [ -f "$TIMESTAMP_FILE" ]; then
    last_checked=$(cat "$TIMESTAMP_FILE")
  else
    last_checked="Sat May 11 00:00:00 2024"
  fi
# Update the timestamp file with the current time
  current_time=$(date '+%a %b %d %H:%M:%S %Y')
  echo "$current_time" > "$TIMESTAMP_FILE"

  # Convert last checked timestamp to seconds since epoch for comparison
  last_checked_epoch=$(date -d "$last_checked" '+%s')

  # Initialize a variable to keep track of the current log timestamp
  current_log_timestamp=""

  # Search for ORA errors in the alert log since the last checked time
  while IFS= read -r line; do
    # Check if the line contains a timestamp
    if [[ $line =~ ^[A-Za-z]{3}\ [A-Za-z]{3}\ [0-9]{2}\ [0-9]{2}:[0-9]{2}:[0-9]{2}\ [0-9]{4}$ ]]; then
      current_log_timestamp=$line
      current_log_epoch=$(date -d "$current_log_timestamp" '+%s')
    fi

    # If the current log entry is after the last checked timestamp, check for ORA errors
    if [[ -n $current_log_timestamp && $current_log_epoch -ge $last_checked_epoch ]]; then
      if [[ $line =~ ORA-[0-9]{5} ]]; then
        error_message=$line
        echo "<tr><td>$current_log_timestamp</td><td>$error_message</td></tr>" >> $REPORT_FILE
      fi
    fi
done < "$ALERT_LOG"
  echo "</table>" >> $REPORT_FILE
}

# Main script execution
echo "<html><body>" > $REPORT_FILE
check_alert_log_for_errors
echo "</body></html>" >> $REPORT_FILE

Output Format
It will generate an HTML report.


Execution of Script:

sh alert_log_check.sh





Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more