Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you an analysis of how to crash ASM instances caused by ORA-4031 errors. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

An ORA-4031 error occurred in the ASM instance of the database, which caused the database instance to crash.

The detailed error message is:

Wed Jul 25 08:03:45 2012

Errors in file / u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_asmb_34668994.trc (incident=808023):

ORA-04031: unable to allocate 3432 bytes of shared memory ("shared pool", "unknown object", "sga heap (1meme 0)", "ASM file")

Incident details in: / u01/app/oracle/diag/rdbms/orcl/ORCL1/incident/incdir_808023/ORCL1_asmb_34668994_i808023.trc

Wed Jul 25 08:03:47 2012

Trace dumping is performing id= [cdmp _ 20120725080347]

Errors in file / u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_asmb_34668994.trc:

ORA-15064: communication failure with ASM instance

ORA-04031: unable to allocate 3432 bytes of shared memory ("shared pool", "unknown object", "sga heap (1meme 0)", "ASM file")

ASMB (ospid: 34668994): terminating the instance due to error 15064

Wed Jul 25 08:03:47 2012

ORA-1092: opiodr aborting process unknown ospid (29819058)

Wed Jul 25 08:03:48 2012

Errors in file / u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_q002_25886884.trc:

ORA-15064: communication failure with ASM instance

Wed Jul 25 08:03:47 2012

Errors in file / u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_arc3_36503776.trc:

ORA-15064: communication failure with ASM instance

Wed Jul 25 08:03:47 2012

Errors in file / u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_q001_32374808.trc:

ORA-15064: communication failure with ASM instance

Errors in file / u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_arc3_36503776.trc:

ORA-15064: communication failure with ASM instance

Master archival failure: 15064

Wed Jul 25 08:03:48 2012

ORA-1092: opiodr aborting process unknown ospid (1205898631)

Wed Jul 25 08:03:49 2012

ORA-1092: opitsk aborting process

Wed Jul 25 08:03:49 2012

License high water mark = 334

Instance terminated by ASMB, pid = 34668994

USER (ospid: 35914002): terminating the instance

Instance terminated by USER, pid = 35914002

It is obvious that the crash of the database instance is caused by an error in the ASM instance. According to Oracle's recommendation, if you use the MEMORY_TARGET parameter in 11g, then MEMORY_TARGET should allocate at least 256m, and as the capacity of DISK GROUP increases, so does the space required by SHARED_POOL. Therefore, for ASM instances with large disk group space, it is obviously not enough to use the default parameter as MEMORY_TARGET.

For the current environment, this error can be avoided by simply adjusting the MEMORY_TARGET parameters of the ASM instance to more than 500m.

The above is the analysis of how ASM instances crashed due to ORA-4031 errors. If you happen to have similar doubts, please refer to the above analysis for understanding. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.