Oracle数据库数据恢复、性能优化

找回密码
注册
搜索
热搜: 活动 交友 discuz
Oracle数据库数据恢复、性能优化»论坛 › Oracle › Oracle数据库管理 › ora-01034错误如何解决
发新帖
check.ora

20

积分

1

好友

9

主题

[常规总体性能调优] ora-01034错误如何解决

1#
发表于 2015-4-24 10:24:57 | 查看: 8130| 回复: 5
环境oracle11.2.0.4
plsql登陆报错

ORA-01034: ORACLE not available
ORA-27102: out of memory
Linux-x86_64 Error: 12: Cannot allocate memory
Additional information: 26
Additional information: 1736708
Additional information: -2147483648
无论是使用plsql还是备份数据库，还有停止数据库应用都报此错误。关闭软件应用之前，应用程序可以使用。
是龙先学会盘着，是虎先学会卧着，等待时机，蓄势待发
2#
发表于 2015-4-24 14:46:55
ORA-01034: ORACLE not available
ORA-27102: out of memory
Linux-x86_64 Error: 12: Cannot allocate memory
Additional information: 26
Additional information: 1736708
Additional information: -214748364


需要诊断该库的alert.log ，一般该错误是在oracle实例发生问题后出现

回复 只看该作者 道具 举报

3#
发表于 2015-4-24 15:50:27
数据库停了，肯定报这个错误啊，你把数据库起起来

回复 只看该作者 道具 举报

4#
发表于 2015-4-27 10:31:21
Maclean Liu(刘相兵 发表于 2015-4-24 14:46
ORA-01034: ORACLE not available
ORA-27102: out of memory
Linux-x86_64 Error: 12: Cannot allocate m ...
  1. Deleted Oracle managed file /oraarch/fast_recovery_area/GOLDFINANCE/archivelog/2015_04_03/o1_mf_1_30_bktv4lfw_.arc
  2. Archived Log entry 86 added for thread 1 sequence 86 ID 0x795e2356 dest 1:
  3. Thu Apr 23 02:00:00 2015
  4. Closing scheduler window
  5. Closing Resource Manager plan via scheduler window
  6. Clearing Resource Manager plan via parameter
  7. Thu Apr 23 10:02:40 2015
  8. DM00 started with pid=32, OS id=17104, job GOLD.SYS_EXPORT_SCHEMA_01
  9. Thu Apr 23 10:02:41 2015
  10. DW00 started with pid=33, OS id=17195, wid=1, job GOLD.SYS_EXPORT_SCHEMA_01
  11. Thu Apr 23 10:25:13 2015
  12. DM00 started with pid=37, OS id=31611, job GOLD1.SYS_IMPORT_FULL_01
  13. Thu Apr 23 10:25:13 2015
  14. DW00 started with pid=38, OS id=31638, wid=1, job GOLD1.SYS_IMPORT_FULL_01
  15. Thu Apr 23 10:30:20 2015
  16. Thread 1 cannot allocate new log, sequence 88
  17. Private strand flush not complete
  18.   Current log# 3 seq# 87 mem# 0: /oradata/goldfinance/redo03.log
  19. Thread 1 advanced to log sequence 88 (LGWR switch)
  20.   Current log# 4 seq# 88 mem# 0: /oradata/goldfinance/redo04.log
  21. Thu Apr 23 10:30:24 2015
  22. Deleted Oracle managed file /oraarch/fast_recovery_area/GOLDFINANCE/archivelog/2015_04_03/o1_mf_1_31_bktvbcn5_.arc
  23. Archived Log entry 87 added for thread 1 sequence 87 ID 0x795e2356 dest 1:
  24. Thu Apr 23 11:31:24 2015


  27. ***********************************************************************

  29. Fatal NI connect error 12170.

  31.   VERSION INFORMATION:
  32.         TNS for Linux: Version 11.2.0.4.0 - Production
  33.         Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  34.         TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  35.   Time: 23-APR-2015 11:31:24
  36.   Tracing not turned on.
  37.   Tns error struct:
  38.     ns main err code: 12535
  39.    
  40. TNS-12535: TNS:operation timed out
  41.     ns secondary err code: 12560
  42.     nt main err code: 505
  43.    
  44. TNS-00505: Operation timed out
  45.     nt secondary err code: 110
  46.     nt OS err code: 0
  47.   Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.40.61.25)(PORT=1424))
  48. Thu Apr 23 11:31:29 2015


  51. ***********************************************************************

  53. Fatal NI connect error 12170.

  55.   VERSION INFORMATION:
  56.         TNS for Linux: Version 11.2.0.4.0 - Production
  57.         Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  58.         TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  59.   Time: 23-APR-2015 11:31:29
  60.   Tracing not turned on.
  61.   Tns error struct:
  62.     ns main err code: 12535
  63.    
  64. TNS-12535: TNS:operation timed out
  65.     ns secondary err code: 12560
  66.     nt main err code: 505
  67.    
  68. TNS-00505: Operation timed out
  69.     nt secondary err code: 110
  70.     nt OS err code: 0
  71.   Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.40.61.25)(PORT=1449))
  72. Thu Apr 23 12:30:02 2015
  73. DM00 started with pid=92, OS id=12462, job GOLD.SYS_EXPORT_SCHEMA_01
  74. Thu Apr 23 12:30:04 2015
  75. DW00 started with pid=93, OS id=12513, wid=1, job GOLD.SYS_EXPORT_SCHEMA_01
  76. Thu Apr 23 12:44:22 2015


  79. ***********************************************************************

  81. Fatal NI connect error 12170.

  83.   VERSION INFORMATION:
  84.         TNS for Linux: Version 11.2.0.4.0 - Production
  85.         Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  86.         TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  87.   Time: 23-APR-2015 12:44:22
  88.   Tracing not turned on.
  89.   Tns error struct:
  90.     ns main err code: 12535
  91.    
  92. TNS-12535: TNS:operation timed out
  93.     ns secondary err code: 12560
  94.     nt main err code: 505
  95.    
  96. TNS-00505: Operation timed out
  97.     nt secondary err code: 110
  98.     nt OS err code: 0
  99.   Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.40.61.27)(PORT=56169))
  100. Thu Apr 23 17:23:28 2015
  101. Warning: VKTM detected a time drift.
  102. Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
  103. Thu Apr 23 22:00:00 2015
  104. Setting Resource Manager plan SCHEDULER[0x32DC]:DEFAULT_MAINTENANCE_PLAN via scheduler window
  105. Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
  106. Thu Apr 23 22:00:00 2015
  107. Starting background process VKRM
  108. Thu Apr 23 22:00:00 2015
  109. VKRM started with pid=35, OS id=11763
  110. Thu Apr 23 22:00:02 2015
  111. Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
  112. Thu Apr 23 22:00:46 2015
  113. End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
  114. Fri Apr 24 00:30:02 2015
  115. DM00 started with pid=92, OS id=30870, job GOLD.SYS_EXPORT_SCHEMA_01
  116. Fri Apr 24 00:30:03 2015
  117. DW00 started with pid=93, OS id=30909, wid=1, job GOLD.SYS_EXPORT_SCHEMA_01
  118. Fri Apr 24 02:00:00 2015
  119. Closing scheduler window
  120. Closing Resource Manager plan via scheduler window
  121. Clearing Resource Manager plan via parameter
  122. Fri Apr 24 02:49:47 2015
  123. Process J001 died, see its trace file
  124. kkjcre1p: unable to spawn jobq slave process
  125. Errors in file /oracle/diag/rdbms/goldfinance/goldfinance/trace/goldfinance_cjq0_19593.trc:
  126. Fri Apr 24 02:50:08 2015
  127. Process m000 died, see its trace file
  128. Fri Apr 24 02:55:09 2015
  129. Process m000 died, see its trace file
  130. Fri Apr 24 02:56:36 2015
  131. Process J000 died, see its trace file
  132. kkjcre1p: unable to spawn jobq slave process
  133. Errors in file /oracle/diag/rdbms/goldfinance/goldfinance/trace/goldfinance_cjq0_19593.trc:
  134. Process J000 died, see its trace file
  135. kkjcre1p: unable to spawn jobq slave process
  136. Errors in file /oracle/diag/rdbms/goldfinance/goldfinance/trace/goldfinance_cjq0_19593.trc:
复制代码

回复 只看该作者 道具 举报

5#
发表于 2015-4-27 10:33:36
Maclean Liu(刘相兵 发表于 2015-4-24 14:46
ORA-01034: ORACLE not available
ORA-27102: out of memory
Linux-x86_64 Error: 12: Cannot allocate m ...

这个是trc文件4月24日内容
  1. *** 2015-04-24 02:00:00.007
  2. Closing Resource Manager plan via scheduler window
  3. Clearing Resource Manager plan via parameter

  5. *** 2015-04-24 02:49:47.474
  6. Process J001 is dead (pid=19534 req_ver=791 cur_ver=791 state=KSOSP_SPAWNED).

  8. *** 2015-04-24 02:56:36.950
  9. Process J000 is dead (pid=7706 req_ver=672 cur_ver=672 state=KSOSP_SPAWNED).

  11. *** 2015-04-24 02:56:42.954
  12. Process J000 is dead (pid=7861 req_ver=673 cur_ver=673 state=KSOSP_SPAWNED).

  14. *** 2015-04-24 02:56:44.957
  15. Process J000 is dead (pid=7918 req_ver=674 cur_ver=674 state=KSOSP_SPAWNED).

  17. *** 2015-04-24 02:56:46.960
  18. Process J000 is dead (pid=8443 req_ver=675 cur_ver=675 state=KSOSP_SPAWNED).

  20. *** 2015-04-24 02:56:48.963
  21. Process J000 is dead (pid=8496 req_ver=676 cur_ver=676 state=KSOSP_SPAWNED).

  23. *** 2015-04-24 02:56:50.966
  24. Process J000 is dead (pid=8551 req_ver=677 cur_ver=677 state=KSOSP_SPAWNED).

  26. *** 2015-04-24 02:56:52.969
  27. Process J000 is dead (pid=8603 req_ver=678 cur_ver=678 state=KSOSP_SPAWNED).

  29. *** 2015-04-24 02:56:54.972
  30. Process J000 is dead (pid=8660 req_ver=679 cur_ver=679 state=KSOSP_SPAWNED).

  32. *** 2015-04-24 02:56:56.974
  33. Process J000 is dead (pid=8870 req_ver=680 cur_ver=680 state=KSOSP_SPAWNED).

  35. *** 2015-04-24 02:56:58.977
  36. Process J000 is dead (pid=8922 req_ver=681 cur_ver=681 state=KSOSP_SPAWNED).

  38. *** 2015-04-24 02:57:00.980
  39. Process J000 is dead (pid=8977 req_ver=682 cur_ver=682 state=KSOSP_SPAWNED).

  41. *** 2015-04-24 02:57:02.983
  42. Process J000 is dead (pid=9029 req_ver=683 cur_ver=683 state=KSOSP_SPAWNED).

  44. *** 2015-04-24 02:57:04.986
  45. Process J000 is dead (pid=9084 req_ver=684 cur_ver=684 state=KSOSP_SPAWNED).

  47. *** 2015-04-24 02:57:06.980
  48. Process J000 is dead (pid=9136 req_ver=685 cur_ver=685 state=KSOSP_SPAWNED).

  50. *** 2015-04-24 02:57:08.984
  51. Process J000 is dead (pid=9188 req_ver=686 cur_ver=686 state=KSOSP_SPAWNED).

  53. *** 2015-04-24 02:57:10.988
  54. Process J000 is dead (pid=9241 req_ver=687 cur_ver=687 state=KSOSP_SPAWNED).

  56. *** 2015-04-24 02:57:12.982
  57. Process J000 is dead (pid=9293 req_ver=688 cur_ver=688 state=KSOSP_SPAWNED).

  59. *** 2015-04-24 02:57:14.987
  60. Process J000 is dead (pid=9350 req_ver=689 cur_ver=689 state=KSOSP_SPAWNED).

  62. *** 2015-04-24 02:57:16.991
  63. Process J000 is dead (pid=9877 req_ver=690 cur_ver=690 state=KSOSP_SPAWNED).

  65. *** 2015-04-24 02:57:18.984
  66. Process J000 is dead (pid=9929 req_ver=691 cur_ver=691 state=KSOSP_SPAWNED).

  68. *** 2015-04-24 02:57:20.987
  69. Process J000 is dead (pid=9982 req_ver=692 cur_ver=692 state=KSOSP_SPAWNED).

  71. *** 2015-04-24 02:57:22.990
  72. Process J000 is dead (pid=10036 req_ver=693 cur_ver=693 state=KSOSP_SPAWNED).

  74. *** 2015-04-24 02:57:24.985
  75. Process J000 is dead (pid=10091 req_ver=694 cur_ver=694 state=KSOSP_SPAWNED).

  77. *** 2015-04-24 02:57:26.989
  78. Process J000 is dead (pid=10597 req_ver=695 cur_ver=695 state=KSOSP_SPAWNED).

  80. *** 2015-04-24 02:57:28.993
  81. Process J000 is dead (pid=10649 req_ver=696 cur_ver=696 state=KSOSP_SPAWNED).

  83. *** 2015-04-24 02:57:30.986
  84. Process J000 is dead (pid=10702 req_ver=697 cur_ver=697 state=KSOSP_SPAWNED).

  86. *** 2015-04-24 02:57:32.989
  87. Process J000 is dead (pid=10756 req_ver=698 cur_ver=698 state=KSOSP_SPAWNED).

  89. *** 2015-04-24 02:57:34.992
  90. Process J000 is dead (pid=10811 req_ver=699 cur_ver=699 state=KSOSP_SPAWNED).

  92. *** 2015-04-24 02:57:36.985
  93. Process J000 is dead (pid=10863 req_ver=700 cur_ver=700 state=KSOSP_SPAWNED).

  95. *** 2015-04-24 02:57:38.988
  96. Process J000 is dead (pid=10915 req_ver=701 cur_ver=701 state=KSOSP_SPAWNED).

  98. *** 2015-04-24 02:57:40.993
  99. Process J000 is dead (pid=10970 req_ver=702 cur_ver=702 state=KSOSP_SPAWNED).

  101. *** 2015-04-24 02:57:42.986
  102. Process J000 is dead (pid=11022 req_ver=703 cur_ver=703 state=KSOSP_SPAWNED).

  104. *** 2015-04-24 02:57:44.989
  105. Process J000 is dead (pid=11077 req_ver=704 cur_ver=704 state=KSOSP_SPAWNED).

  107. *** 2015-04-24 02:57:46.991
  108. Process J000 is dead (pid=11497 req_ver=705 cur_ver=705 state=KSOSP_SPAWNED).

  110. *** 2015-04-24 02:57:48.984
  111. Process J000 is dead (pid=11547 req_ver=706 cur_ver=706 state=KSOSP_SPAWNED).

  113. *** 2015-04-24 02:57:50.987
  114. Process J000 is dead (pid=11600 req_ver=707 cur_ver=707 state=KSOSP_SPAWNED).

  116. *** 2015-04-24 02:57:52.991
  117. Process J000 is dead (pid=11652 req_ver=708 cur_ver=708 state=KSOSP_SPAWNED).

  119. *** 2015-04-24 02:57:54.984
  120. Process J000 is dead (pid=11707 req_ver=709 cur_ver=709 state=KSOSP_SPAWNED).

  122. *** 2015-04-24 02:57:56.987
  123. Process J000 is dead (pid=12083 req_ver=710 cur_ver=710 state=KSOSP_SPAWNED).

  125. *** 2015-04-24 02:57:58.989
  126. Process J000 is dead (pid=12135 req_ver=711 cur_ver=711 state=KSOSP_SPAWNED).

  128. *** 2015-04-24 02:58:00.992
  129. Process J000 is dead (pid=12188 req_ver=712 cur_ver=712 state=KSOSP_SPAWNED).

  131. *** 2015-04-24 02:58:02.995
  132. Process J000 is dead (pid=12240 req_ver=713 cur_ver=713 state=KSOSP_SPAWNED).

  134. *** 2015-04-24 02:58:04.998
  135. Process J000 is dead (pid=12295 req_ver=714 cur_ver=714 state=KSOSP_SPAWNED).

  137. *** 2015-04-24 02:58:07.001
  138. Process J000 is dead (pid=12508 req_ver=715 cur_ver=715 state=KSOSP_SPAWNED).

  140. *** 2015-04-24 02:58:09.004
  141. Process J000 is dead (pid=12560 req_ver=716 cur_ver=716 state=KSOSP_SPAWNED).

  143. *** 2015-04-24 02:58:11.010
  144. Process J000 is dead (pid=12615 req_ver=717 cur_ver=717 state=KSOSP_SPAWNED).

  146. *** 2015-04-24 02:58:13.004
  147. Process J000 is dead (pid=12667 req_ver=718 cur_ver=718 state=KSOSP_SPAWNED).

  149. *** 2015-04-24 02:58:15.007
  150. Process J000 is dead (pid=12722 req_ver=719 cur_ver=719 state=KSOSP_SPAWNED).

  152. *** 2015-04-24 02:58:17.011
  153. Process J000 is dead (pid=13089 req_ver=720 cur_ver=720 state=KSOSP_SPAWNED).

  155. *** 2015-04-24 02:58:19.014
  156. Process J000 is dead (pid=13141 req_ver=721 cur_ver=721 state=KSOSP_SPAWNED).

  158. *** 2015-04-24 02:58:21.018
  159. Process J000 is dead (pid=13195 req_ver=722 cur_ver=722 state=KSOSP_SPAWNED).

  161. *** 2015-04-24 02:58:23.021
  162. Process J000 is dead (pid=13247 req_ver=723 cur_ver=723 state=KSOSP_SPAWNED).

  164. *** 2015-04-24 02:58:25.014
  165. Process J000 is dead (pid=13302 req_ver=724 cur_ver=724 state=KSOSP_SPAWNED).

  167. *** 2015-04-24 02:58:27.018
  168. Process J000 is dead (pid=13676 req_ver=725 cur_ver=725 state=KSOSP_SPAWNED).

  170. *** 2015-04-24 02:58:29.022
  171. Process J000 is dead (pid=13728 req_ver=726 cur_ver=726 state=KSOSP_SPAWNED).

  173. *** 2015-04-24 02:58:31.015
  174. Process J000 is dead (pid=13787 req_ver=727 cur_ver=727 state=KSOSP_SPAWNED).

  176. *** 2015-04-24 02:58:33.019
  177. Process J000 is dead (pid=13848 req_ver=728 cur_ver=728 state=KSOSP_SPAWNED).

  179. *** 2015-04-24 02:58:35.023
  180. Process J000 is dead (pid=13921 req_ver=729 cur_ver=729 state=KSOSP_SPAWNED).

  182. *** 2015-04-24 02:58:37.017
  183. Process J000 is dead (pid=14292 req_ver=730 cur_ver=730 state=KSOSP_SPAWNED).

  185. *** 2015-04-24 02:58:39.020
  186. Process J000 is dead (pid=14345 req_ver=731 cur_ver=731 state=KSOSP_SPAWNED).

  188. *** 2015-04-24 02:58:41.024
  189. Process J000 is dead (pid=14400 req_ver=732 cur_ver=732 state=KSOSP_SPAWNED).

  191. *** 2015-04-24 02:58:43.018
  192. Process J000 is dead (pid=14452 req_ver=733 cur_ver=733 state=KSOSP_SPAWNED).

  194. *** 2015-04-24 02:58:45.021
  195. Process J000 is dead (pid=14505 req_ver=734 cur_ver=734 state=KSOSP_SPAWNED).

  197. *** 2015-04-24 02:58:47.023
  198. Process J000 is dead (pid=14876 req_ver=735 cur_ver=735 state=KSOSP_SPAWNED).

  200. *** 2015-04-24 02:58:49.026
  201. Process J000 is dead (pid=14928 req_ver=736 cur_ver=736 state=KSOSP_SPAWNED).

  203. *** 2015-04-24 02:58:51.038
  204. Process J000 is dead (pid=14981 req_ver=737 cur_ver=737 state=KSOSP_SPAWNED).

  206. *** 2015-04-24 02:58:53.041
  207. Process J000 is dead (pid=15033 req_ver=738 cur_ver=738 state=KSOSP_SPAWNED).

  209. *** 2015-04-24 02:58:55.024
  210. Process J000 is dead (pid=15088 req_ver=739 cur_ver=739 state=KSOSP_SPAWNED).

  212. *** 2015-04-24 02:58:57.029
  213. Process J000 is dead (pid=15462 req_ver=740 cur_ver=740 state=KSOSP_SPAWNED).

  215. *** 2015-04-24 02:58:59.032
  216. Process J000 is dead (pid=15514 req_ver=741 cur_ver=741 state=KSOSP_SPAWNED).

  218. *** 2015-04-24 02:59:01.339
  219. Process J000 is dead (pid=15579 req_ver=742 cur_ver=742 state=KSOSP_SPAWNED).

  221. *** 2015-04-24 02:59:03.342
  222. Process J000 is dead (pid=15631 req_ver=743 cur_ver=743 state=KSOSP_SPAWNED).
复制代码

回复 只看该作者 道具 举报

6#
发表于 2015-4-27 10:37:59
本帖最后由 check.ora 于 2015-4-27 18:20 编辑
Maclean Liu(刘相兵 发表于 2015-4-24 14:46
ORA-01034: ORACLE not available
ORA-27102: out of memory
Linux-x86_64 Error: 12: Cannot allocate m ...


两文件中一直这样报错，操作人重启后数据库恢复正常。服务器内存128G，memory_target和memory_max_target 均为100G  
df -h /dev/shm 容量为102G,操作系统日志 该时段信息为多条执行/etc/init.d/oracle status

该问题出现时间为2015-04-24

回复 只看该作者 道具 举报

返回列表
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

QQ|手机版|Archiver|Oracle数据库数据恢复、性能优化

GMT+8, 2024-12-20 19:30 , Processed in 0.050505 second(s), 20 queries .

Powered by Discuz! X2.5

© 2001-2012 Comsenz Inc.

回顶部
TEL/電話+86 13764045638
Email service@parnassusdata.com
QQ 47079569