Ora-07445:[kghsrch () +128] [SIGSEGV] [Address not mapped to object] cryogenic treatment

Source: Internet
Author: User

Customer site, telecommunications-related 7*24h business, a province database two node alert constantly produce ORA-7445 error, and throw trace dump file, TRC file. One node alert does not have 7445 related errors, only the core file is generated. CRS, syslog and other logs no obvious alarm. Does not cause a restart and does not cause a business impact. Just constantly error, due to Oracle directory space 40G, in order to prevent the database instance rammer, the customer decided to resolve the error.

Customer host HP-UX b.11.31 ia64,oracle Release 10.2.0.5.0.

Node two alert:

Thu 18:27:38 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_17889.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:27:40 EAT 2016

Trace dumping is performing id=[cdmp_20161124182740]

Thu 18:28:29 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_18076.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:29:03 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_19496.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:43:22 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_12403.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:44:37 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_14293.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:46:41 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_17336.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:50:20 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_20339.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 18:50:22 EAT 2016

Trace dumping is performing id=[cdmp_20161124185022]

Thu 18:53:06 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_23424.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 19:06:40 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_18689.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 19:38:31 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_6449.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 19:38:33 EAT 2016

Trace dumping is performing id=[cdmp_20161124193833]

Thu 19:39:49 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_10964.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 19:39:53 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_9299.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 19:41:19 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_12404.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Thu 19:42:47 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/UDUMP/ESSBJ2_ORA_13863.TRC:

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []


Node One alert:

Fri 11:16:05 EAT 2016

Trace dumping is performing id=[cdmp_20161125111604]

Fri 12:00:05 EAT 2016

Thread 1 advanced to log sequence 34397 (LGWR switch)

Current log# 8 seq# 34397 mem# 0:/vgbj03/oradata/essbj/vgbj03_1_rd81.log

Current log# 8 seq# 34397 mem# 1:/vgbj04/oradata/essbj/vgbj04_1_rd82.log

Fri 12:00:51 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/BDUMP/ESSBJ1_J000_11783.TRC:

Ora-12012:error on auto Execute of Job 281

Ora-00031:session marked for Kill

Ora-06512:at "SYS. Kill_long_sql ", line 67

Ora-06512:at Line 1

Fri 12:17:15 EAT 2016

Trace dumping is performing id=[cdmp_20161125121714]

Fri 12:37:21 EAT 2016

Errors in FILE/ORACLE/ADMIN/ESSBJ/BDUMP/ESSBJ1_J000_5909.TRC:

Ora-12012:error on auto Execute of Job 281

Ora-00031:session marked for Kill

Ora-06512:at "SYS. Kill_long_sql ", line 67

Ora-06512:at Line 1

Fri 12:50:53 EAT 2016

Trace dumping is performing id=[cdmp_20161125125053]

Fri 13:33:53 EAT 2016

Trace dumping is performing id=[cdmp_20161125133352]


The TRC file generated in node two is reviewed and a SQL

Ksedmp:internal or fatal error

Ora-07445:exception Encountered:core Dump [Kghsrch () +128] [SIGSEGV] [Address not mapped to object] [0XFFFFFFFFFFFFFFF0] [] []

Current SQL statement for this session:

SELECT occupy_staff_id, occupy_depart_id from tf_r_tempoccupy WHERE res_no =: 1 and Res_type_code =: 2 and RSRV_TAG1 =: 3


It is intended to execute this SQL separately and Tail-f alert logs to see if the 7445 related bugs caused by the SQL problem are an error. Because the SQL has bound variables. We need to parse the value of the variable and execute the SQL statement.

Alter session Set Nls_date_format = ' Yyyy-mm-dd,hh24:mi:ss ';

Set Linesize 400

Col sql_id format A20

Col name format A20

Col datatype_string format A14

Col value_string format A20

Select Sql_id,name, datatype_string, last_captured,value_string

From V$sql_bind_capture where sql_id= ' &sql_id ' ORDER by last_captured,position;


No error occurred since the variable was executed in SQL alone. The most closely related documents in the trace file are found on MoS as follows:

Smon terminates with ORA-7445 [Kghsrch () +128] (document ID 1189894.1)
Bug 10036960:ora-07445[kghsrch] and ora-07445[kghlkremf] followed by INSTANCE CRASH.
ORA-07445 [Kghsrch] associated with Session kills (document ID 787914.1)
Instance termination with ORA-07445 [Kghsrch () +144], ORA-00600 [Kghfrh:ds] (document ID 2128933.1)
However, due to the current database is only an error, did not cause the consequences of the instance down, so the elimination of MOS document is identical to the bug. And the system itself the database version is already 10.2.0.5,bug described in the fix version is this version.

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/8A/EE/wKiom1g_g6KT6gDVAACakxBte8E147.jpg-wh_500x0-wm_3 -wmp_4-s_1950165466.jpg "style=" Float:none; "title=" mos1.jpg "alt=" Wkiom1g_g6kt6gdvaacakxbte8e147.jpg-wh_50 "/>

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/8A/EA/wKioL1g_g6Pjb1ynAACnkDpgYzM670.jpg-wh_500x0-wm_3 -wmp_4-s_725318753.jpg "style=" Float:none; "title=" mos2.jpg "alt=" Wkiol1g_g6pjb1ynaacnkdpgyzm670.jpg-wh_50 "/>

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/8A/EA/wKioL1g_g6ODO1s8AADYRGhnKkU297.jpg-wh_500x0-wm_3 -wmp_4-s_3752148690.jpg "style=" Float:none; "title=" mos3.jpg "alt=" Wkiol1g_g6odo1s8aadyrghnkku297.jpg-wh_50 "/>

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/8A/EE/wKiom1g_g6TAROGjAAD2vJete_c663.jpg-wh_500x0-wm_3 -wmp_4-s_1833915713.jpg "style=" Float:none; "title=" mos22.jpg "alt=" wkiom1g_g6tarogjaad2vjete_c663.jpg-wh_50 "/ >

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/8A/EE/wKiom1g_g6XgHUf9AACUtcIum08307.jpg-wh_500x0-wm_3 -wmp_4-s_2078979112.jpg "style=" Float:none; "title=" mos23.jpg "alt=" wkiom1g_g6xghuf9aacutcium08307.jpg-wh_50 "/ >


1. The existing 07445 problems of the system are only partially consistent with the information provided by Oracle.
2. The solution provided does not match the current environment of the database (such as the proposed upgrade from 10GR2 to 10.2.0.4 or 10.2.0.5, but the current production database itself is 10.2.0.5);
3. The database does not appear as the bug mentioned instance crash, etc., does not affect the normal operation of the business.

Therefore, the exception may be thrown in connection with a business Access object in an in-memory structure, and since it constantly generates trace files and cdump files, it is recommended that the client restart the problem instance (instance 2) before continuing with the business. Then see if there is a corresponding 7445 error generated. The client is given a time window to restart the instance.

Tue Nov 21:38:37 EAT 2016

ALTER DATABASE OPEN

Block change tracking file was current.

Picked broadcast on commit scheme to generate SCNS

Tue Nov 21:38:38 EAT 2016

Sending CIC to internal enable redo thread

Tue Nov 21:38:38 EAT 2016

Lgwr:starting ARCH PROCESSES

ARC0 started with pid=33, OS id=14097

Tue Nov 21:38:38 EAT 2016

Arc0:archival started

Arc1:archival started

Lgwr:starting ARCH PROCESSES Complete

ARC1 started with pid=34, OS id=14099

Tue Nov 21:38:38 EAT 2016

Thread 2 opened at log sequence 32257

Current log# seq# 32257 mem# 0:/vgbj03/oradata/essbj/vgbj03_1_rd121.log

Current log# seq# 32257 mem# 1:/vgbj04/oradata/essbj/vgbj04_1_rd122.log

Tue Nov 21:38:38 EAT 2016

Arc0:becoming the ' no FAL ' ARCH

Arc0:becoming the ' no SRL ' ARCH

Tue Nov 21:38:38 EAT 2016

Successful open of Redo thread 2

Tue Nov 21:38:38 EAT 2016

Arc1:becoming the Heartbeat ARCH

Tue Nov 21:38:38 EAT 2016

Starting background Process CTWR

CTWR started with pid=35, OS id=14101

Block Change tracking service is active.

Tue Nov 21:38:38 EAT 2016

Smon:enabling Cache Recovery

Tue Nov 21:38:39 EAT 2016

Successfully onlined Undo tablespace 4.

Tue Nov 21:38:39 EAT 2016

smon:enabling TX Recovery

Tue Nov 21:38:39 EAT 2016

Database Characterset is ZHS16GBK

Opening with internal Resource Manager plan

Replication_dependency_tracking turned off (no async multimaster replication found)

Starting background Process QMNC

QMNC started with pid=36, OS id=14127

Tue Nov 21:38:43 EAT 2016

Completed:alter DATABASE OPEN

Tue Nov 21:38:52 EAT 2016

ALTER SYSTEM SET service_names= ' essbj_db ' scope=memory sid= ' essbj2 ';

Tue Nov 21:48:47 EAT 2016

ALTER SYSTEM SET service_names= ' essbj_db ', ' essbj ' scope=memory sid= ' essbj2 ';

Wed Nov 00:16:10 EAT 2016

ALTER SYSTEM ARCHIVE LOG

Wed Nov 00:16:10 EAT 2016

Thread 2 advanced to log sequence 32258 (LGWR switch)

Current log# 4 seq# 32258 mem# 0:/vgbj04/oradata/essbj/vgbj04_1_rd41.log

Current log# 4 seq# 32258 mem# 1:/vgbj03/oradata/essbj/vgbj03_1_rd42.log

Wed Nov 00:16:15 EAT 2016

ALTER SYSTEM ARCHIVE LOG

Wed Nov 00:16:17 EAT 2016

Thread 2 advanced to log sequence 32259 (LGWR switch)

Current log# 3 seq# 32259 mem# 0:/vgbj04/oradata/essbj/vgbj04_1_rd31.log

Current log# 3 seq# 32259 mem# 1:/vgbj03/oradata/essbj/vgbj03_1_rd32.log

Wed Nov 02:00:27 EAT 2016

Thread 2 advanced to log sequence 32260 (LGWR switch)

Current log# 5 seq# 32260 mem# 0:/vgbj03/oradata/essbj/vgbj03_1_rd51.log

Current log# 5 seq# 32260 mem# 1:/vgbj04/oradata/essbj/vgbj04_1_rd52.log

Wed Nov 06:13:11 EAT 2016

Thread 2 advanced to log sequence 32261 (LGWR switch)

Current log# seq# 32261 mem# 0:/vgbj03/oradata/essbj/vgbj03_1_rd101.log

Current log# seq# 32261 mem# 1:/vgbj04/oradata/essbj/vgbj04_1_rd102.log

There is no related error.




This article is from the Yang Junfeng blog, so be sure to keep this source http://yangjunfeng.blog.51cto.com/539796/1878374

Ora-07445:[kghsrch () +128] [SIGSEGV] [Address not mapped to object] cryogenic treatment

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.