Internal Error ORA-07445:memset()+116] [SIGSEGV]

简介:

From Alert logfile ********************* Wed May 27 13:11:47 2009 Errors in file /u01/app/oracle/admin/proa021/udump/proa021_ora_9533.trc: ORA-07445: exception encountered: core dump [memset()+116] [SIGSEGV] [Address not mapped to object] [0] [] [] From Trace file ******************** Dump file /u01/app/oracle/admin/proa021/udump/proa021_ora_9533.trc Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production With the Partitioning option JServer Release 8.1.7.4.0 - Production ORACLE_HOME = /u01/app/oracle/product/817proa021 System name: SunOS Node name: v08k01 Release: 5.8 Version: Generic_117350-38 Machine: sun4u Instance name: proa021 Redo thread mounted by this instance: 1 Process Info ****************** Oracle process number: 117 Unix process pid: 9533, image: oracle@v08k01 (TNS V1-V3) Error ********* 2009-05-27 13:11:47.847 ksedmp: internal or fatal error ORA-07445: exception encountered: core dump [memset()+116] [SIGSEGV] [Address not mapped to object] [0] [] [] Current SQL(Current SQL statement for this session) *********************************************************************** : SELECT COUNT(PO_LINE_ID) FROM PO_LINES_INTERFACE WHERE PO_HEADER_ID = :b1 Call Stack functions ************************* ksedmp <- ssexhd <- sigacthandler <- memset ##################################################################################### From Alert logfile ********************* Wed May 27 13:18:39 2009 Errors in file /u01/app/oracle/admin/proa021/bdump/proa021_pmon_9584.trc: ORA-00600: internal error code, arguments: [1115], [], [], [], [], [], [], [] Wed May 27 13:18:56 2009 Errors in file /u01/app/oracle/admin/proa021/bdump/proa021_pmon_9584.trc: ORA-00600: internal error code, arguments: [1115], [], [], [], [], [], [], [] From Tracefile ******************* Dump file /u01/app/oracle/admin/proa021/bdump/proa021_pmon_9584.trc Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production With the Partitioning option JServer Release 8.1.7.4.0 - Production ORACLE_HOME = /u01/app/oracle/product/817proa021 System name: SunOS Node name: v08k01 Release: 5.8 Version: Generic_117350-38 Machine: sun4u Instance name: proa021 Redo thread mounted by this instance: 1 Process Info **************** Oracle process number: 2 Unix process pid: 9584, image: oracle@v08k01 (PMON) Error ******** 2009-05-27 13:18:39.766 ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [1115], [], [], [], [], [], [], [] Call Stack Functions: **************************** ksedmp <- kgeriv <- kgesiv <- ksesic0 <- kssdch <- ksuxds <- kssxdl <- kssdch <- ksudlp <- kssxdl <- ksuxdl <- ksuxda <- ksucln <- ksbrdp <- opirip <- opidrv <- sou2o <- main <- start CURRENT SESSION'S INSTANTIATION STATE ********************************************************* current session=8c8fdfbc ---- Cursor Dump ------ Current cursor: 0, pgadep: 0 Cursor Dump: End of cursor dump END OF PROCESS STATE ******************** Cursor Dump ************************ Current cursor: 0, pgadep: 0 Cursor Dump: End of cursor dump ksedmp: no current context area CAUSE DETERMINATION =================== This issue is caused by Bug 2028564 Abstract: DATABASE CRASHED WITH ORA-600 [1115] BECAUSE PMON FAILED TO CLEANUP SESSION. CAUSE JUSTIFICATION =================== ---- Customer's errors in alert log and trace file match with this issue. --- Customer's call stack trace in the trace file match with this issue. The cause can be justified by the followings: Bug 2028564 Abstract: DATABASE CRASHED WITH ORA-600 [1115] BECAUSE PMON FAILED TO CLEANUP SESSION. Note 2028564.8 Bug 2028564 - ORA-7445 or OERI 17114 errors possible after OERI:729 - PMON may die PROPOSED SOLUTION(S) ==================== 1. Apply one-off patch for Bug 2028564 according to your OS platform and version. OR 2. Upgrade to 9.2.0.4 or later version...for example 9.2.0.8. PROPOSED SOLUTION JUSTIFICATION(S) ================================== 1. One-off patch for Bug 2760836 has fixed this issue...so after customer apply the one-off patch...then this issue will be solved. OR 2. 9.2.0.4 or later version has fixed this issue...so after customer upgrade to at least 9.2.0.4 version...then this issue will be solved. The solution can be justified by the followings: Note 2760836.8 PMON cleanup of dead shared servers/dispatchers can crash instance (OERI 26599 / OERI 1115)



本文转自maclean_007 51CTO博客,原文链接:http://blog.51cto.com/maclean/1276683

相关文章
|
机器学习/深度学习 自然语言处理 数据挖掘
Python:简单、优雅且强大的编程语言
Python:简单、优雅且强大的编程语言
|
11月前
|
云安全 存储 运维
阿里云安全体检功能评测报告
阿里云安全体检功能评测报告
275 7
|
网络协议 算法 网络安全
如何在 Debian Wheezy 上使用 Postfix 安装和配置 DKIM
如何在 Debian Wheezy 上使用 Postfix 安装和配置 DKIM
387 0
|
安全 Linux 调度
xenomai+linux双内核下的时钟管理机制
clock是操作系统正常运行的发动机,系统利用时钟中断维持系统时间、促使任务调度,以保证所有进程共享CPU资源;可以说,“时钟中断”是整个操作系统的脉搏。那你是否好奇xenomai cobalt内核和Linux内核双内核共存的情况下,时间子系统是如何工作的?一个硬件时钟如何为两个操作系统提供服务的?本文将揭开xenomai双核系统时间机制
537 0
xenomai+linux双内核下的时钟管理机制
|
存储 数据管理 云栖大会
云栖大会全空间数据库Session
Ganos三维引擎针对三维数据管理提出创新解决方案,旨在解决传统技术栈中的数据分散与冗余问题。该引擎提供表面网格模型、体网格模型及实景模型三种存储结构,支持高效三维空间计算与大规模模型渲染。其ST_SnapToPolygon和ST_Loft函数可实现地形与路网无缝贴合,显著提升三维建模效率与精度。通过SQL操作,Ganos可在数秒内完成复杂三维模型生成与处理,适用于交通仿真等多种应用场景,推动数字孪生技术的“视算一体”发展。
209 1
|
机器学习/深度学习 人工智能 运维
运维自动化之路:从手动到智能的转变
【8月更文挑战第8天】在数字化转型的大潮中,运维工作由传统的手动操作逐步演变为自动化和智能化的实践。本文将探讨这一转变背后的原因、过程以及带来的影响,旨在为读者提供对现代运维工作的深入理解。
180 0
全排列----关于next_permutation()/prev_permutation() 函数的用法
全排列----关于next_permutation()/prev_permutation() 函数的用法
193 0
|
前端开发
巧用 CSS 构建渐变彩色二维码
巧用 CSS 构建渐变彩色二维码
584 0
巧用 CSS 构建渐变彩色二维码
|
存储 JSON JavaScript
【mysql】JSON 类型
【mysql】JSON 类型
315 1
【mysql】JSON 类型
|
机器学习/深度学习 人工智能 自然语言处理
最早2026?全球优质语言数据「存量」告急!网友:杞人忧天
最早2026?全球优质语言数据「存量」告急!网友:杞人忧天
207 0

热门文章

最新文章