ASM_DISKSTRING
TheASM_DISKSTRING
initialization parameter specifies a comma-delimited list of strings that limits the set of disks that an Oracle ASM
instance discovers. The discovery strings can include wildcard characters. Only disks that match one of the strings are discovered. The same disk cannot be discovered twice.
The discovery string format depends on the Oracle ASM library and the operating system that are in use. Pattern matching is supported. Refer to your operating system-specific installation guide for information about the default
pattern matching.
For example, on a Linux server that does not use ASMLib, to limit the discovery process to only include disks that are in the/dev/rdsk/mydisks
directory, set theASM_DISKSTRING
initialization
parameter to:
/dev/rdsk/mydisks/*
The asterisk is required. To limit the discovery process to only include disks that have a name that ends indisk3
ordisk4
,
setASM_DISKSTRING
to:
/dev/rdsk/*disk3
,/dev/rdsk/*disk4
The?
character, when used as the first character of a path, expands to the Oracle home directory. Depending on the operating system, when you use the?
character
elsewhere in the path, it is a wildcard for one character.
The default value of theASM_DISKSTRING
parameter is aNULL
string. ANULL
value
causes Oracle ASM to search a default path for all disks in the system to which the Oracle ASM instance has read and write access. The default search path is platform-specific. Refer to your operating system specific installation guide for more information
about the default search path.
Oracle ASM cannot use a disk unless all of the Oracle ASM instances in the cluster can discover the disk through one of their own discovery strings. The names do not have to be the same on every node, but all disks must be discoverable
by all of the nodes in the cluster. This may require dynamically changing the initialization parameter to enable adding new storage.
For additional information about discovering disks, see"Oracle ASM Disk Discovery".
See Also:
-
Oracle Exadata documentationfor information about the Oracle ASM discovery string format for Oracle Exadata
-
Oracle
Database Referencefor more information about theASM_DISKSTRING
initialization parameter
Oracle ASM Disk Discovery
Disk discovery is the mechanism used to find the operating system names for disks Oracle ASM can access.
It is used to find all the disks that comprise a disk group to be mounted, the disks an administrator wants to add to a disk group, or the disks the administrator might consider adding to a disk group. This section contains the following topics:
For additional information about disk discovery and theASM_DISKSTRING
initialization parameter, refer to"ASM_DISKSTRING".
How A Disk is Discovered
When an Oracle ASM instance is initialized, Oracle ASM discovers and examines the contents of all of the disks that
are in the paths that you designated with values in theASM_DISKSTRING
initialization parameter.
Disk discovery also occurs when you:
-
Run the following SQL statements
-
Mount a disk group withALTER
DISKGROUP
...MOUNT
-
Online a disk withALTER
DISKGROUP
...ONLINE
DISK
-
Add a disk to a disk group withCREATE
orALTER
DISKGROUP
...ADD
DISK
-
Resize a disk in a disk group withALTER
DISKGROUP
...RESIZE
DISK
-
Query withSELECT
...FROM
V$ASM_DISKGROUP
orV$ASM_DISK
views
-
Run Oracle Enterprise Manager or Oracle ASM Configuration Assistant (ASMCA) operations that invoke the SQL statements previously listed
-
Run ASMCMD commands that perform the same operations as the SQL statements previously listed
After Oracle ASM successfully discovers a disk, the disk appears in theV$ASM_DISK
view. Disks that belong to a disk group, that is, disks that have a disk group name in the disk
header, show a header status ofMEMBER
. Disks that were discovered, but that have not yet been assigned to a disk group, have a status of eitherCANDIDATE
orPROVISIONED
.
Disks that previously belonged to a disk group and were dropped cleanly from the disk group have a status ofFORMER
.
ThePROVISIONED
status implies that an additional platform-specific action has been taken by an administrator to make the disk available for Oracle ASM. For example, on Windows computers,
the administrator might have usedasmtool
orasmtoolg
to stamp the disk with a header. On Linux computers, the administrator might have used ASMLib to prepare
the disk for Oracle ASM.
Example 4-10shows a SQL query onV$ASM_DISK
that
displays the header status of a group of disks.
Example 4-10 Querying V$ASM_DISK for header status
SQL> SELECT name, header_status, path FROM V$ASM_DISK
WHERE path LIKE '/devices/disk0%'
NAME HEADER_STATUS PATH
--------- ------------- ---------------------
FORMER /devices/disk02
FORMER /devices/disk01
CANDIDATE /devices/disk07
DISK06 MEMBER /devices/disk06
DISK05 MEMBER /devices/disk05
DISK04 MEMBER /devices/disk04
DISK03 MEMBER /devices/disk03
7 rows selected.
See Also:
Oracle Database Referencefor
information about the header status of an Oracle ASM disk that is displayed in the
V$ASM_DISK
view
Disk Discovery Rules
The rules for discovering Oracle ASM disks are as follows:
-
Oracle ASM can discover up to 10,000 disks. That is, if more than 10,000 disks match theASM_DISKSTRING
initialization parameter, then Oracle ASM discovers only the first 10,000.
-
Oracle ASM only discovers disk partitions. Oracle ASM does not discover partitions that include the partition table.
-
From the perspective of the installation, candidate disks are those that have theCANDIDATE
,PROVISIONED
, orFORMER
header
status. These disks with aCANDIDATE
,PROVISIONED
, orFORMER
status can be added to Oracle ASM disk
groups without using theFORCE
flag.
-
When adding a disk, theFORCE
option must be used if Oracle ASM recognizes that the disk was managed by Oracle. Such a disk appears in theV$ASM_DISK
view
with a status ofFOREIGN
. In this case, you can only add the disk to a disk group by using theFORCE
keyword.
-
MEMBER
disks can usually be added to a disk group by specifying theFORCE
flag, if the disks are not part of a currently mounted
disk group.
In addition, Oracle ASM identifies the following configuration errors during discovery:
-
Multiple paths to the same disk
In this case, if the disk is part of a disk group, then disk group mount fails. If the disk is being added to a disk group with theADD DISK
orCREATE
DISKGROUP
command, then the command fails. To correct the error, adjust theASM_DISKSTRING
value so that Oracle ASM does not discover multiple paths to the same disk. Or if you are using multipathing
software, then ensure that you include only the pseudo-device name in theASM_DISKSTRING
value. See"Oracle
ASM and Multipathing".
-
Multiple Oracle ASM disks with the same disk header
This can be caused by having copied one disk onto another. In this case, the disk group mount operation fails.
Improving Disk Discovery Time
The value for theASM_DISKSTRING
initialization parameter is an operating system–dependent value that Oracle ASM uses to limit the set of paths
that the discovery process uses to search for disks. When a new disk is added to a disk group, each Oracle ASM instance that has the disk group mounted must be able to discover the new disk using itsASM_DISKSTRING
.
In many cases, the default value (NULL
) is sufficient. Using a more restrictive value might reduce the time required for Oracle ASM to perform discovery, and thus improve disk group
mount time or the time for adding a disk to a disk group. Oracle may dynamically change theASM_DISKSTRING
before adding a disk so that the new disk is discovered through this parameter.
The default value ofASM_DISKSTRING
might not find all disks in all situations. If your site is using a third-party vendor ASMLib, then the vendor might have discovery string conventions
that you must use forASM_DISKSTRING
. In addition, if your installation uses multipathing software, then the software might place pseudo-devices in a path that is different from the operating system default.
See"Oracle ASM and Multipathing"and consult the multipathing vendor documentation for details.
Q131.
When starting up your ASM instance, you receive the followingerror:
What is the cause of the error?
A. The ASM_DISKGROUPS parameter is configured for three diskgroups: DGROUP1, DGROUP2, and DGROUP3. The underlying disks for these diskgroups have apparently been lost.
B. The format of the ASM_DISKGROUPS parameter is incorrect.It should reference the disk group numbers, not the names of the disk groups
C. The ASM_POWER_LIMIT parameter is incorrectly set to 1. Itshould be set to the number of disk groups being attached to the ASM instance.
D. The ASM_DISKSTRING parameter is not set; therefore 因此disk discovery is not possible.
E. There is insufficient information to solve this problem.
Answer: D
分享到:
相关推荐
Oracle_ASM_详解 Oracle_ASM_详解
oracle_asm_管理_中文
ORACLEASM_for_linux_AS5.8,包括3个文件,kmod、oracleasmlib和oracleasm-support的,为Redhat AS5.8版本安装ORACLEASMLIB用
ORACLEASM_for_linux_AS6.6,包括3个文件,kmod、oracleasmlib和oracleasm-support的,为Redhat AS6.6版本安装ORACLEASMLIB用
Oracle RAC系列之_10gR2 RAC(ASM) Data Guard容灾配置手册_mfkqwyc86.pdf
Oracle_10g_R2_RAC_ASM_for_Redhat_Linux_AS_4_u4安装文档
oracleasm-support、oracleasmlib、kernel-firmware、bfa-firmware、kmod-oracleasm及安装步骤
三个软件包,打包在一起,安装oracle创建asm磁盘组所用的软件 rpm -aq |grep oracleasm* oracleasm-support-2.1.8-1.el6.x86_64 oracleasmlib-2.0.12-1.el6.x86_64 oracleasm-2.6.18-308.el5-2.0.5-1.el5.x86_64
RAC_Oracle11g_asm_grid_openfile搭建集群环境
迁移Oracle数据库文件到ASM_数据库技术
oracle10g下asm管理中文教程,识别自动存储管理ASM的功能。为ASM和数据库实例设置初始化参数文件等,讲的比较详细。
Oracle_11gR2_RAC_+_ASM_on_AIX-6.1安装指导手册
\asm_11对话框
grid infrastructure 安装,oracle11gr2安装,asm磁盘管理方式, standalone方式的使用,aix操作系统的补丁升级。
Android Screen Monitor,asm_2_50.zip 用法: 解压后,将asm.jar放入sdk\platform-tools目录,运行java -jar asm.jar
c32asm_反汇编程序,供学习用,感谢吾爱破解,提供谢谢
rfdevice_asm_qm77040_hb_asm_data_ag_77040_源码.zip