Skip to main content

ORA-07445: exception encountered: core dump [kglIsOwnerVersionable()]

Hi all,

We have received a mail from customer to investigate above error reported in the database's alert log.
Please find the details below.

Can you please investigate below error against EBSPRD and let me know the next course of action?

Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x24] [PC:0x2587EB9, kglIsOwnerVersionable()+123] [flags: 0x0, count: 1]
Errors in file /sw/oraebs/EBSPRD/db/tech_st/11.2.0/admin/EBSPRD_ebsprddb01/diag/rdbms/ebsprd/EBSPRD/trace/EBSPRD_ora_17713.trc  (incident=624688):
ORA-07445: exception encountered: core dump [kglIsOwnerVersionable()+123] [SIGSEGV] [ADDR:0x24] [PC:0x2587EB9] [Address not mapped to object] []
Incident details in: /sw/oraebs/EBSPRD/db/tech_st/11.2.0/admin/EBSPRD_ebsprddb01/diag/rdbms/ebsprd/EBSPRD/incident/incdir_624688/EBSPRD_ora_17713_i624688.trc
Non critical error ORA-48913 caught while writing to trace file "/sw/oraebs/EBSPRD/db/tech_st/11.2.0/admin/EBSPRD_ebsprddb01/diag/rdbms/ebsprd/EBSPRD/incident/incdir_624688/EBSPRD_ora_17713_i624688.trc"

Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached


As per MOSC doc “Bug 9003145 - Dump (kglIsOwnerVersionable) / "library cache: mutex X" waits (Doc ID 9003145.8)”,
A dump can occur in kglIsOwnerVersionable . Also "library cache: mutex X" waits may be seen for location kglIsOwnerVersionable if such a dump does occur.

Symptoms:
·         Process May Dump (ORA-7445) / Abend / Abort
·         Mutex Contention
·         Performance Affected (General)
·         Dump in or under kglIsOwnerVersionable
·         Waits for "library cache: mutex X"

We must prove to the customer that it is a bug in our database. So i have tracked the session details,sql_id and wait_event for the time when the error generated using dba_hist_active_sess_history.

(I'll give you sql query later to find the below output)

Output:


The above output proves that sql_id '8dx678sfn9zru' was waited for library cache: mutex X

Solution:

This issue is fixed in
  • 11.2.0.2 (Server Patch Set)
  • 11.2.0.1 Bundle Patch 3 for Exadata Database
  • 11.2.0.1 Patch 9 on Windows Platforms

Comments

Post a Comment

Popular posts from this blog

Export and import multiple schema using expdp/impdp (Data Pump utility)

Use the below sql query to export and import multiple schema: expdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp exclude=statistics logfile=expdpschemas120514.log impdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp logfile=impdpschemas120514.log sql query to export and import a schema: expdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp exclude=statistics logfile=expdpschema120514.log impdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp logfile=expdpschema120514.log Parameter STATISTICS=NONE can either be used in export or import. No need to use the parameter in both. To export meta data only to get ddl of the schemas: expdp schemas=schema1,schema2,schema3 directory=TEST_DIR dumpfile=content.dat content=METADATA_ONLY exclude=statistics To get the DDL in a text file: impdp directory=TEST_DIR sqlfile=sql.dat logfile=sql.log dumpfil...
3 comments
Read more

Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan

Deal all, Below post content is not my own. It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Hence we had implemented the same mentioned in the title "Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan". Introduction The "cost-based optimizer (CBO or just optimizer) is the part of database software that determines the most efficient means of accessing the specified data (or at least what it "calculates" as the most efficient). The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints. Some changes in those conditions may affect the calculations of the plan...
9 comments
Read more

Metrics Process Limit Usage percentage (%) is critical or warning in OEM or Cloud Control 12c or Cloud Control 13c

Please run the below queries to trace details during Metric alert "Process Limit % is >= 75" in OEM or Cloud Control 12c or Cloud Control 13c To check the Metrics Process Limit Usage (%): ***************************************************** set lines 300 col INITIAL_ALLOCATION for a17 col LIMIT_VALUE for a12 select resource_name,current_utilization,max_utilization, INITIAL_ALLOCATION,LIMIT_VALUE,((current_utilization*100)/(INITIAL_ALLOCATION)) as "Process limit %" from v$resource_limit where resource_name in ('processes'); The below query will give you all connected sessions (ACTIVE and INACTIVE) to instance: ******************************************************************************************************* set pages 100 set lines 1000 col SPID heading 'PID' for a06 col SID for 99999 col SERIAL# heading 'serial' for 999999 col SQL_ID for a14 col USERNAME for a10 col PROGRAM for a20 col MODULE for a18 col OSU...
Post a Comment
Read more