ORA-7445 [dbgrlrReadAlertMsg] on SELECT FROM X$DBGALERTEXT or a View Based On It

(Doc ID 1433214.1)

Last updated on OCTOBER 25, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 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:

ORA-07445: exception encountered: core dump [dbgrlrReadAlertMsg()+1107] [SIGSEGV] [ADDR:0x7] [PC:0x8D0C17B] [Address not mapped to object] []

The call stack reported in the incident trace file contains:

dbgrlrReadAlertMsg dbgrxae_alert_ex dbgrmqmif_internal_fetch dbgrmqmf_fetch_real dbgrmqmf_fetch dbgrip_fetch_record dbgrip_relation_iterator dbkrx_alertextcb qerfxFetch qersoProcessULS qersoFetch opifch2 kpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o opimai_real ssthrdmain main _start

The current SQL in the generated incident tracefile in this case looks similar to:

----- Current SQL Statement for this session (sql_id=dzkcu8f0wa0gw) -----

SELECT originating_timestamp "DATE TIME", message_text
FROM SYS.v_dbgalertext
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:

adrci> show alert

ADR Home = /mnt/oracle/diag/rdbms/xxx/yyy:
Abort (core dumped)

- OR -

adrci> show alert

DIA-48216: Field Len Exceeds Max Field Length [5] [0] [20] [20]


Some external event caused the log.xml to become corrupt.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms