Wednesday 10 August 2011

Diskmon cannot handle more than 13 instances - Exadata

Diskmon process is one of the background process in exadata environment and is a part of Oracle Clusterware ready services.This takes care of the I/O Fencing.

In 11.2.0.1/11.2.0.2 version, Diskmon can handle upto 13instances. Each instance has one diskmon(ora_dskm_<sid>) process.Oracle can fork upto 13 diskmon slaves.This is a limitation in these versions.The CRS startup will hang if the exadata server has more than 13 instances. We could find the below messages in the  instance's alert logfile which are failed to start.

ORA-00600: internal error code, arguments: [2116], [900], [], [], [], [], [], [], [], [], [], [] In the alert log and DISKMON logs show dskm_slave_thrd_creat1: no more slave table slots left!

Oracle has provided a patch  9790947  to support upto 62 instances  and later introduced another patch 9842238 to completely remove this limitation.Exadata Patch Bundle 4 has covered the latest patch.

2 comments:

  1. Hi colleagues, is there any other fastidious blog related to JavaScript articles,
    while this one is good for PHP programming.

    Here is my weblog fptester.com

    ReplyDelete
  2. This is a very good tips especially to those new to blogosphere,
    brief and accurate information… Thanks for sharing
    this one. A must read article.

    my blog: comitiv.it

    ReplyDelete

ZFS

Public Cloud tools comparison