Decode360's Blog

          業精于勤而荒于嬉 QQ:150355677 MSN:decode360@hotmail.com

            BlogJava :: 首頁 :: 新隨筆 :: 聯系 ::  :: 管理 ::
            397 隨筆 :: 33 文章 :: 29 評論 :: 0 Trackbacks
          PMON failed to acquire latch, see PMON dump
          ?
          ?
          ??? 今天在關閉數據庫的時候,shutdown immediate之后系統就hang住了,其他進程也連不上庫。查看了alert.log日志,發現大量出現“PMON failed to acquire latch, see PMON dump”這個錯誤,到網上查了一下,據說是個bug,在一篇博文上找到了解決的辦法:
          ?
          http://blog.chinaunix.net/u/6436/showart_1918697.html
          ?
          ***********************************************************************************
          ?
          To implement the solution, execute the following steps:

          1. In $ORACLE_HOME/network/admin/listener.ora, of the database where the Metadata Repository is to be loaded, add the line:
          INBOUND_CONNECT_TIMEOUT_LISTENER = 0

          2. In the Oracle Server 10g sqlnet.ora, add the line:
          SQLNET.INBOUND_CONNECT_TIMEOUT = 0

          3. Stop and restart the database and the listener for the changes to take effect
          ?
          這是metalink上的:
          ?
          Applies to:
          Oracle Server - Enterprise Edition - Version: 10.2.0.1.0 to 10.2.0.3.0
          ?
          This problem can occur on any platform.
          ?
          Symptoms
          Database Instance hangs and connections to database using 'sqlplus' are also not possible.

          Checking alert.log we see following messages

          PMON failed to acquire latch, see PMON dump
          Fri Oct 5 10:33:00 2007
          PMON failed to acquire latch, see PMON dump
          Fri Oct 5 10:34:05 2007
          PMON failed to acquire latch, see PMON dump
          Errors in file /dwrac/BDUMP/dwhp_pmon_1912834.trc:

          This will also dump a systemstate dump and the location will be mentioned in alert.log

          Also at OS level, we see that MMAN is consuming lot of CPU.

          Cause
          Currently this issue is being worked upon by development in
          ?
          ?
          Bug 6488694
          - DATABSE HUNG WITH PMON FAILED TO ACQUIRE LATCH MESSAGE
          ?
          ?
          Solution
          As of now only workaround is to disable Automatic Shared Memory Management (
          ?
          ASMM
          ) i.e Setting
          ?
          SGA_TARGET=0

          Also as per bug, you can can set following event and restart the instance

          EVENT="10235 trace name context forever, level 2"
          ?
          Development is suspecting memory corruption in this case. So with the above event, database might hit ORA-600 before spin. The trace file of ORA-600 would help investigate the issue. These trace files need to be sent to Oracle support for investigation.

          Note : - Event 10235 with level 2 or higher can impact latch contention.Though may not be quite critical. In case you see latch contention then unset the event

          References
          Bug 6488694
          - DATABSE HUNG WITH PMON FAILED TO ACQUIRE LATCH MESSAGE
          ***********************************************************************************
          ?
          ?
          ??? 最后沒辦法,hang住之后系統sys用戶都登不進,無法使用任何操作,只能重啟機器之后數據庫恢復正常。希望加了那兩個參數之后不要再發生這樣的Bug,雖然對數據庫的危害不大,但是需要重啟機器還是比較嚴重的。
          ?
          ?
          ?
          ?
          posted on 2009-06-23 21:42 decode360 閱讀(4570) 評論(0)  編輯  收藏 所屬分類: 07.Oracle
          主站蜘蛛池模板: 乡城县| 郑州市| 永康市| 通山县| 庐江县| 含山县| 原阳县| 临海市| 梁平县| 山阳县| 永平县| 泊头市| 沁源县| 和顺县| 陵川县| 古浪县| 新晃| 普陀区| 临猗县| 清水河县| 徐水县| 安泽县| 金沙县| 凭祥市| 伊春市| 澳门| 宁河县| 郑州市| 洮南市| 宣化县| 来凤县| 化德县| 儋州市| 滦南县| 文成县| 丹寨县| 涞水县| 侯马市| 杭州市| 邵武市| 清远市|