数据库关闭Hang住，出现错误PMON failed to acquire latch, see PMON dump

在AIX5.3平台中，Oracle10gR2的版本Oracle10.2.0.1

在关闭shutdown  immediate数据库时，数据库不能正常关闭，

出现错误PMON failed to acquire latch, see PMON dump，数据库处于Hang状态。

 

如果再执行shutdown immediate命令出现：

SQL> shutdown immediate

ORA-24324: service handle not initialized

ORA-24323: value not allowed

ORA-01089: immediate shutdown in progress - no operations are permitted

SQL>

 

强制关闭出现：

SQL> shutdown abort

ORA-01031: insufficient privileges

 

这可能是Oracle版本的bug。

 

 

解决：

1、  临时解决

可多试几次shutdown  abort强制关闭数据库，如不行，重启系统。

 

2、  打上补丁

   METALINK:Bug 6488694

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

 

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

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/12778571/viewspace-695481/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/12778571/viewspace-695481/