转:ORA-15186: ASMLIB error function = [asm_open], error = [1], 2009-05-24 13:57:38

http://space.itpub.net/471666/viewspace-406996

ORA-15186: ASMLIB error function = [asm_open], error = [1], mesg = [Operation not permitted]

参考 Metalink   Note:398622.1

Subject:    ORA-15186: ASMLIB error function = [asm_open], error = [1], mesg = [Operation not permitted]
     Doc ID:    Note:398622.1    Type:    PROBLEM
     Last Revision Date:    06-MAY-2008    Status:    PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0
This problem can occur on any platform.
Oracle Database ASM (Automatic Storage Management) instance
Oracle ASMLib
Raw devices
Symptoms
The Oracle Database ASM instance reports ORA-15186 error in the alert.log, for example:

ORA-15186: ASMLIB error function = [asm_open], error = [1], mesg = [Operation not permitted].

The error occurs periodically, most notably during ASM instance startup and as a result of V$ASM_... view queries, as well as during RMAN backup.

Despite the error, however, no adverse affects are observed.

Cause
By default, Oracle Database ASM instance parameter ‘ASM_DISKSTRING‘ is unset and therefore uses a default value of ‘*‘. This means that the ASM instance scans both/dev/raw/and/dev/oracleasm/disks/directories when searching for oracle ASM disks.

When using a combination of oracleasm disks (/dev/oracleasm/disks/*) with raw devices (/dev/raw/*), in particular where some raw devices are not owned by or accessible to the oracle user) as well as ASM instance parameter ‘ASM_DISKSTRING‘ with an unspecified value, error ORA-15186 is likely to occur.

Solution
The solution is to explictly set Oracle ASM instance parameter ‘ASM_DISKSTRING‘ such that it only scans for  oracleasm disks (e.g. with label ORCL:*) or to set the value to scan only intended oracleasm devices known to be oracleasm disks.

Explicitly setting ‘ASM_DISKSTRING‘ is recommended as it increases oracle ASM disk scan performance by restricting the number of devices scanned to only those marked with the default provisioned ‘ORCL:‘ label prefix or scanning only a given subset of devices.

Examples of setting ASM_DISKSTRING parameter include:

SQL> alter system set asm_diskstring=‘ORCL:*‘ scope=both;
...

SQL> alter system set asm_diskstring=‘/dev/raw/raw6,/dev/raw/raw7,/dev/raw/raw8‘ scope=both;
...

SQL> alter system set asm_diskstring=‘/dev/mapper/mpath0,/dev/mapper/mpath1,/dev/mapper/mpath2‘ scope=both;
...

Note: whilst limiting the ‘ASM_DISKSTRING‘ value to a specific list of disks ensures optimal ASM instance scan performance, the parameter value must be modified to include any new devices whenever oracleasm disks are added or removed.

References
Note 391136.1- New ASMLib / oracleasm Disk Gets "header_status=Unknown" - Cannot be Added to Diskgroup
Keywords
AUTOMATIC~STORAGE~MANAGEMENT; RAW~DEVICE; ORACLEASM; ASMLIB;

时间: 2024-10-28 21:29:11

转:ORA-15186: ASMLIB error function = [asm_open], error = [1], 2009-05-24 13:57:38的相关文章

complementary error function

首先正态分布的概率密度函数为: P{|X-μ|<σ}=2Φ(1)-1=0.6826,  P{|X-μ|<2σ}=2Φ(2)-1=0.9544,  P{|X-μ|<3σ}=2Φ(3)-1=0.9974 由于"小概率事件"和假设检验的基本思想 "小概率事件"通常指发生的概率小于5%的事件,认为在一次试验中该事件是几乎不可能发生的.由此可见X落在(μ-3σ,μ+3σ)以外的概率小于千分之三,在实际问题中常认为相应的事件是不会发生的,基本上可以把区间(μ-

升级 MySQL 至 5.5,报错 [ERROR] Plugin &#39;InnoDB&#39; init function returned error

MySQL 从 5.5 升级到 5.6,启动时报错: [ERROR] Plugin 'InnoDB' init function returned error. [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. [ERROR] Unknown/unsupported storage engine: InnoDB [ERROR] Aborting 原因:主要是没有正常关闭 mysqld 服务的情况下,对数据库参数进行改

ERROR: function @ Ordinal 1883 missing !!! Please Check your SYSGEN variable !!!

ERROR: function @ Ordinal xxx missing今天新定制了一个OS,测试以前的应用程序,程序无法运行,查看串口信息有如下错误提示:ERROR: function @ Ordinal 1883 missing!!! Please Check your SYSGEN variable !!! 这通常是系统缺少某个组件导致的. 查看\WINCE600\PUBLIC\COMMON\OAK\LIB\ARMV4I\RETAIL\coredll.def文件看到如下信息: ; @CE

[ERROR] Plugin &#39;InnoDB&#39; init function returned error

今天一大早到公司,计划把开发环境的mysql升级到5.7.15,干净关闭系统后,把目录从5.6指向到5.7,一切正常,重新指向5.6启动时,报下列错误: 2016-10-31 08:13:14 86998 [ERROR] Plugin 'InnoDB' init function returned error.2016-10-31 08:13:14 86998 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.2016

MySQL Plugin &#39;InnoDB&#39; init function returned error

. . 在MySQL的配置文件中,设定default-table-type=InnoDB,发现MySQL无法正常的启动,错误日志中给出了如下的信息: 150210 18:11:19 mysqld_safe mysqld from pid file /data/mysqldata/mysql.pid ended150210 18:15:20 mysqld_safe Starting mysqld daemon with databases from /data/mysqldata150210 18

LR接口性能测试提示Code - 60990 Error: Two Way Communication Error: Function two_way_comm_post_message / two_ (转载)

一.在做JAVA接口性能测试时,场景在运行中出现:Code - 60990 Error: Two Way Communication Error: Function two_way_comm_post_message /two_way_comm_post_message_ex failed.错误 及Code - 10343 Error: Communication error: Cannot send the message since reached the shared memory buf

机器学习 损失函数(Loss/Error Function)、代价函数(Cost Function)和目标函数(Objective function)

损失函数(Loss/Error Function): 计算单个训练集的误差 代价函数(Cost Function): 计算整个训练集所有损失之和的平均值 至于目标函数(Objective function),字面一些,就是有某个(最优化)目标的函数,比如最优化这个目的.没有找到定义,个人理解,目标函数是一个大类,包含损失函数.代价函数:损失函数.代价函数,属于目标函数. 原文地址:https://www.cnblogs.com/callyblog/p/8321795.html

解决ajax后台请求明明”前台语法,后台逻辑没错”但却一直走error:function(data)的问题

今天用ajax做了个登录,   前台语法,后台ssm框架都没问题,但却一直走error:function(data), 后面百度说把dataType:josn注释掉就可以,试了一下还是不行. 最后跟之前ajax请求成功的后台代码比较了一下才发现我在@RequestMapping注解里多加了produces属性,并且属性值是"text/html;charset=UTF-8",是为了防止中文乱码 然后我把这个属性去掉了果然可以,虽然不知道啥原因(哭笑) ,有知道原因的网友欢迎在我博客下方交

突然出现错误gdiplustypes.h(280): error C2059: syntax error : &#39;constant&#39;等未知错误

gdiplustypes.h(280): error C2059: syntax error : 'constant'gdiplustypes.h(280): error C2238: unexpected token(s) preceding ';'gdiplustypes.h(281): error C2059: syntax error : 'constant'gdiplustypes.h(281): error C2238: unexpected token(s) preceding '