ORA-7445 [qmxsaxCreateDocTypeXob()+199] When Creating Enterprise Manager Repository
(Doc ID 1550305.1)
Last updated on APRIL 12, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Following error is reported in trace file when creating EM repository:
ORA-07445: exception encountered: core dump [qmxsaxCreateDocTypeXob()+199] [SIGSEGV] [ADDR:0x18] [PC:0x2BAD291] [Address not mapped to object] []
Failing statement:
** 2013-04-19 17:12:01.807
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=dp5hxgsszdnuk) -----
BEGIN dbms_registry.loaded('EM'); END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x936f79c8 145 package body SYS.DBMS_SQLTUNE_INTERNAL
0x936f79c8 12085 package body SYS.DBMS_SQLTUNE_INTERNAL
0x936f79c8 12719 package body SYS.DBMS_SQLTUNE_INTERNAL
0x936f79c8 17400 package body SYS.DBMS_SQLTUNE_INTERNAL
0x64e55a20 6926 package body SYS.DBMS_STATS_INTERNAL
0x90771a68 20779 package body SYS.DBMS_STATS
0x90771a68 21676 package body SYS.DBMS_STATS
0x90771a68 22918 package body SYS.DBMS_STATS
0x90771a68 23649 package body SYS.DBMS_STATS
0x90771a68 24145 package body SYS.DBMS_STATS
0x90771a68 24788 package body SYS.DBMS_STATS
0x90771a68 27322 package body SYS.DBMS_STATS
0x90771a68 27402 package body SYS.DBMS_STATS
0x959438b0 1093 package body SYS.DBMS_REGISTRY_SYS
0x949844a0 578 package body SYS.DBMS_REGISTRY
0x9359dd38 1 anonymous block
----- Call Stack Trace -----
qmxsaxCreateDocTypeXob qmxsaxElementDecl LpxmAddElement LpxFSMParseElementDecl LpxFSMParseProlog LpxFSMParseDocument LpxParse LpxStreamParse qmxuParseXobDoc_int qmxManifest0
Internally, the issue occurs when calling dbms_stats as can be seen in error stack above.
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 |
References |