ORA-07445: Exception Encountered: Core Dump [PGOSF544_upduaw()+3395] on DML Statements with Triggers Enabled
(Doc ID 2014421.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Alert log reports error like below:
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x0] [PC:0x414E0BD, __PGOSF544_upduaw()+3395]
ORA-07445: exception encountered: core dump [PGOSF544_upduaw()+3395] [ACCESS_VIOLATION] [ADDR:0x0] [PC:0x414E0BD] [UNABLE_TO_READ] []
ORA-07445: exception encountered: core dump [PGOSF544_upduaw()+3395] [ACCESS_VIOLATION] [ADDR:0x0] [PC:0x414E0BD] [UNABLE_TO_READ] []
The main incident trace file shows trigger list information like:
--------Dumping Sorted Master Trigger List --------
Trigger Owner : 'Trigger Owner'
Trigger Name : 'Trigger Name'
Trigger Owner : 'Trigger Owner'
Trigger Name : 'Trigger Name'
Trigger Owner : 'Trigger Owner'
Trigger Name : 'Trigger Name'
Trigger Owner : 'Trigger Owner'
Trigger Name : 'Trigger Name'
The incident detail trace file reports an update statement and a call stack that includes functions like:
... PGOSF544_upduaw kdusru kauupd updrow qerupFetch updaul updThreePhaseExe updexe opiexe opipls opiodr ...
Cause
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
Symptoms |
Cause |
Solution |