ora-凯发app官方网站

凯发app官方网站-凯发k8官网下载客户端中心 | | 凯发app官方网站-凯发k8官网下载客户端中心

沧海拾贝

凯发app官方网站首页　| 　博文目录　| 　关于我

brjl

  • 博客访问： 3502668
  • 博文数量： 718
  • 博客积分： 1860
  • 博客等级： 上尉
  • 技术积分： 7790
  • 用 户 组： 普通用户
  • 注册时间： 2008-04-07 08:51
个人简介

偶尔有空上来看看

文章分类

全部博文（718）

文章存档

2024年（4）

2023年（74）

2022年（134）

2021年（238）

2020年（115）

2019年（11）

2018年（9）

2017年（9）

2016年（17）

2015年（7）

2014年（4）

2013年（1）

2012年（11）

2011年（27）

2010年（35）

2009年（11）

2008年（11）

我的朋友
最近访客
推荐博文
相关博文
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
ora-4030 lms 进程占用内存很高 实例重启

分类： oracle

2022-09-17 09:33:26

补丁不生效例子

aix 7202 11.2.0.4 rac 180417 psu
实例2 例行重启，实例1发生了意外重启

实例1告警日志
   
  1. fri sep 16 00:34:57 2022
  2.  set master node info
  3.  submitted all remote-enqueue requests
  4.  dwn-cvts replayed, valblks dubious
  5.  all grantable enqueues granted
  6. fri sep 16 00:34:59 2022
  7. minact-scn: master returning as live inst:2 has inc# mismatch instinc:0 cur:8 errcnt:0
  8. fri sep 16 00:36:16 2022
  9. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms2_38732932.trc (incident=1488512):
  10. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  11. incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_1488512/orcl1_lms2_38732932_i1488512.trc
  12. use adrci or support workbench to package the incident.
  13. see note 411.1 at my oracle support for error and packaging details.
  14. fri sep 16 00:36:17 2022
  15. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms0_19269850.trc (incident=1488496):
  16. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  17. incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_1488496/orcl1_lms0_19269850_i1488496.trc
  18. use adrci or support workbench to package the incident.
  19. see note 411.1 at my oracle support for error and packaging details.
  20. fri sep 16 00:36:18 2022
  21. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms1_5505754.trc (incident=1488504):
  22. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  23. incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_1488504/orcl1_lms1_5505754_i1488504.trc
  24. use adrci or support workbench to package the incident.
  25. see note 411.1 at my oracle support for error and packaging details.
  26. fri sep 16 00:36:25 2022
  27. dumping diagnostic data in directory=[cdmp_20220916003625], requested by (instance=1, osid=19269850 (lms0)), summary=[incident=1488496].
  28. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms0_19269850.trc (incident=1488497):
  29. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  30. incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_1488497/orcl1_lms0_19269850_i1488497.trc
  31. use adrci or support workbench to package the incident.
  32. see note 411.1 at my oracle support for error and packaging details.
  33. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms2_38732932.trc (incident=1488513):
  34. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  35. incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_1488513/orcl1_lms2_38732932_i1488513.trc
  36. use adrci or support workbench to package the incident.
  37. see note 411.1 at my oracle support for error and packaging details.
  38. fri sep 16 00:36:27 2022
  39. sweep [inc][1488513]: completed
  40. sweep [inc][1488512]: completed
  41. sweep [inc][1488504]: completed
  42. sweep [inc][1488497]: completed
  43. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms1_5505754.trc (incident=1488505):
  44. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  45. use adrci or support workbench to package the incident.
  46. see note 411.1 at my oracle support for error and packaging details.
  47. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms1_5505754.trc (incident=1488506):
  48. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)
  49. use adrci or support workbench to package the incident.
  50. see note 411.1 at my oracle support for error and packaging details.
  51. errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms1_5505754.trc (incident=1488507):
lms2、lms0、lms1三个进程都突然发生ora-4030异常，内存不足，看相关trc文件

  1. dump file /u01/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_1488512/orcl1_lms2_38732932_i1488512.trc
  2. oracle database 11g enterprise edition release 11.2.0.4.0 - 64bit production
  3. with the partitioning, real application clusters, automatic storage management, olap,
  4. data mining and real application testing options
  5. oracle_home = /u01/app/oracle/product/11.2.0/db_1
  6. system name:    aix
  7. node name:    db1
  8. release:    2
  9. version:    7
  10. machine:    00fb76794c00
  11. instance name: orcl1
  12. redo thread mounted by this instance: 1
  13. oracle process number: 15
  14. unix process pid: 38732932, image: oracle@db1 (lms2)


  17. *** 2022-09-16 00:36:16.929
  18. *** session id:(1892.1) 2022-09-16 00:36:16.929
  19. *** client id:() 2022-09-16 00:36:16.929
  20. *** service name:(sys$background) 2022-09-16 00:36:16.929
  21. *** module name:() 2022-09-16 00:36:16.929
  22. *** action name:() 2022-09-16 00:36:16.929
  23.  
  24. dump continued from file: /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms2_38732932.trc
  25. ora-04030: out of process memory when trying to allocate 195248 bytes (kjc pga smbuf,kjc pga send buffer)

  27. ========= dump for incident 1488512 (ora 4030) ========
  28. ----- beginning of customized incident dump(s) -----
  29. =======================================
  30. top 10 memory uses for this process
  31. ---------------------------------------

  33. *** 2022-09-16 00:36:22.939
  34. 99% 31 gb, 172610 chunks: "kjc pga send buffer "       <--------------这里很异常
  35.          kjc pga smbuf ds=110733230 dsprt=110005120
  36.  1% 213 mb, 172724 chunks: "free memory "
  37.          pga heap ds=110005120 dsprt=0
  38.  0% 149 mb, 145 chunks: "permanent memory "
  39.          pga heap ds=110005120 dsprt=0
  40.  0% 75 kb, 3 chunks: "permanent memory "
  41.          session heap ds=1109d66e0 dsprt=11011f5d8
  42.  0% 54 kb, 1 chunk : "free memory "
  43.          top call heap ds=11011f3b8 dsprt=0
  44.  0% 38 kb, 1 chunk : "fixed uga "
  45.          fixed uga heap ds=1108bad28 dsprt=110005120
  46.  0% 20 kb, 2 chunks: "free memory "
  47.          session heap ds=1109d66e0 dsprt=11011f5d8
  48.  0% 16 kb, 7 chunks: "permanent memory "
  49.          diag pga ds=1107324d0 dsprt=110005120
  50.  0% 16 kb, 2 chunks: "dbgeinitprocessctx:invctx "
  51.          diag pga ds=1107324d0 dsprt=110005120
  52.  0% 16 kb, 1 chunk : "kgh stack "
  53.          pga heap ds=110005120 dsprt=0
  54.  
  55. =======================================
  56. private memory summary for this process
  57. ---------------------------------------
  58. ******************************************************
  59. private heap summary dump
  60. 32 gb total:
  61.     31 gb commented, 149 mb permanent
  62.    213 mb free (0 kb in empty extents),
  63.       32 gb, 1 heap: "kjc pga smbuf " 212 mb free held
  64. ------------------------------------------------------
  65. summary of subheaps at depth 1
  66. 31 gb total:
  67.     31 gb commented, 98 kb permanent
  68.     31 kb free (0 kb in empty extents),
  69.       31 gb, 172610 chunks: "kjc pga send buffer "

  71. *** 2022-09-16 00:36:23.380
  72.  
  73. =========================================
  74. real-free allocator dump for this process
  75. -----------------------------------------
  76.  
  77. dump of real-free memory allocator heap [0x1109a4810]
  78. mag=0xfefe0001 flg=0x5000003 fds=0x0 blksz=65536
  79. blkdstbl=0x1109a4820, iniblk=521216 maxblk=524288 numsegs=320
  80. in-use num=172723 siz=4028628992, freeable num=1 siz=65536, free num=310 siz=20316160
  81.  
  82. ==========================================
  83. instance-wide private memory usage summary
  84. ------------------------------------------
  85.  
  86. dumping work area table (level=1)
  87. =====================================
  88.  
  89.   global sga info
  90.   ---------------
  91.  
  92.     global target: 115507 mb
  93.     auto target: 11333 mb
  94.     max pga: 2048 mb
  95.     pga limit: 4096 mb
  96.     pga limit known: 0
  97.     pga limit errors: 0
  98.  
  99.     pga inuse: 102955 mb
  100.     pga alloc: 105793 mb
  101.     pga freeable: 742 mb
  102.     pga freed: 43967956 mb
  103.     pga to free: 0
  104.     broker request: 0
  105.  
  106.     pga auto: 41 mb
  107.     pga manual: 0 mb
  108.  
  109.     pga alloc (max): 105793 mb
  110.     pga auto (max): 5444 mb
  111.     pga manual (max): 1 mb
  112.  
  113.     # workareas : 43
  114.     # workareas(max): 224
  115.  
  116.  
  117.  
  118. ================================
  119. per-process private memory usage
  120. --------------------------------
  121.  
  122. private memory usage per oracle process
  123.  
  124. -------------------------
  125. top 10 processes:
  126. -------------------------
  127. (percentage is of 103 gb total allocated memory)
  128. 31% pid 13: 32 gb used of 32 gb allocated (128 kb freeable)
  129. 31% pid 14: 32 gb used of 32 gb allocated
  130. 31% pid 15: 32 gb used of 32 gb allocated (64 kb freeable) <= current proc
  131.  0% pid 12: 14 mb used of 113 mb allocated (98 mb freeable)
  132.  0% pid 10: 45 mb used of 56 mb allocated (7680 kb freeable)
  133.  0% pid 86: 42 mb used of 45 mb allocated
  134.  0% pid 87: 42 mb used of 45 mb allocated
  135.  0% pid 89: 42 mb used of 45 mb allocated
  136.  0% pid 973: 42 mb used of 43 mb allocated (1024 kb freeable)
  137.  0% pid 1029: 42 mb used of 43 mb allocated (1024 kb freeable)
  138.  
  139. -------------------------
  140. all processes:
  141. -------------------------
  142. (session detail when over 5290 mb allocated)
  143.  
  144. pid 2: 2119 kb used of 2350 kb allocated
  145. pid 3: 1060 kb used of 1182 kb allocated
  146. pid 4: 1056 kb used of 1182 kb allocated
  147. pid 5: 1066 kb used of 1182 kb allocated
  148. pid 6: 6161 kb used of 6494 kb allocated (128 kb freeable)
  149. pid 7: 2121 kb used of 2718 kb allocated (320 kb freeable)
  150. ...

三个进程每个都32g，搜索mos，发现有个bug很像

检查当前的补丁，opatch lsinv|grep 18316692 已经包含了此修复，但是lms的pga还是很大，看来没有解决。

怎么办呢？

监控，发现内存占用太大就重启实例（lms进程杀不得）

  1. select pid,spid,program,pga_used_mem,pga_alloc_mem,pga_freeable_mem,pga_max_mem from v$process where program like '%lms%';

lms进程的工作机制



参考：
  1. https://orainternals.files.wordpress.com/2008/03/riyaj_battle_of_nodes_rac_perf_myths_ppt.pdf


阅读(976) | 评论(0) | 转发(0) |
0

上一篇：达梦逻辑导出备份简易参考

下一篇：达梦的disql 直接执行脚本

给主人留下些什么吧！~~
| | | | |

凯发app官方网站 copyright 2001-2010 chinaunix.net all rights reserved 北京皓辰网域网络信息技术有限公司. 凯发k8官网下载客户端中心的版权所有

感谢所有关心和支持过chinaunix的朋友们
")); function link(t){ var href= $(t).attr('href'); href ="?url=" encodeuricomponent(location.href); $(t).attr('href',href); //setcookie("returnouturl", location.href, 60, "/"); }
网站地图