ORA-7445 [dbgrlrReadAlertMsg] on SELECT FROM X$DBGALERTEXT or a View Based On It
(Doc ID 1433214.1)
Last updated on MARCH 09, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168.0 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 24-Oct-2013***
A query on X$DBGALERTEXT (or any view based on this fixed table) results in:
The call stack reported in the incident trace file contains:
The current SQL in the generated incident tracefile in this case looks similar to:
SELECT originating_timestamp "DATE TIME", message_text
WHERE originating_timestamp > (select last_run_date from db_admin.alert_message_control) AND message_text LIKE '%ORA-%'
ORDER BY originating_timestamp
The issues seem related to a corrupted log.xml file. You could see a variety of issues depending on what and where the problem is within the log.xml file. The following are examples of what you might see when issuing "show alert" from within the ADRCI command prompt:
Some external event caused the log.xml to become corrupt.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document