ASM – ora.asm error
11.2.0.3 RAC CRS 无法启动
[ohasd(25286)]CRS-2112:The OLR service started on node db-41.
2012-04-25 14:46:13.120
[ohasd(25286)]CRS-1301:Oracle High Availability Service started on node db-41.
2012-04-25 14:46:13.120
[ohasd(25286)]CRS-8017:location: /etc/oracle/lastgasp has 2 reboot advisory log files, 0 were announced and 0 errors occurred
2012-04-25 14:46:14.181
[/data/11.2.0/grid/bin/orarootagent.bin(25332)]CRS-5016:Process “/data/11.2.0/grid/bin/acfsload” spawned by agent “/data/11.2.0/grid/bin/orarootagent.bin” for action “check” failed: details at “(:CLSN00010:)” in “/data/11.2.0/grid/log/db-41/agent/ohasd/orarootagent_root/orarootagent_root.log”
2012-04-25 14:46:17.031
[gpnpd(25510)]CRS-2328:GPNPD started on node db-41.
2012-04-25 14:46:20.794
[cssd(25593)]CRS-1713:CSSD daemon is started in clustered mode
2012-04-25 14:46:22.520
[ohasd(25286)]CRS-2767:Resource state recovery not attempted for ‘ora.diskmon’ as its target state is OFFLINE
2012-04-25 14:46:40.715
[cssd(25593)]CRS-1707:Lease acquisition for node db-41 number 1 completed
2012-04-25 14:46:42.003
[cssd(25593)]CRS-1605:CSSD voting file is online: /dev/mapper/Vote03; details in /data/11.2.0/grid/log/db-41/cssd/ocssd.log.
2012-04-25 14:46:42.008
[cssd(25593)]CRS-1605:CSSD voting file is online: /dev/mapper/Vote02; details in /data/11.2.0/grid/log/db-41/cssd/ocssd.log.
2012-04-25 14:46:42.015
[cssd(25593)]CRS-1605:CSSD voting file is online: /dev/mapper/Vote01; details in /data/11.2.0/grid/log/db-41/cssd/ocssd.log.
2012-04-25 14:46:52.173
[cssd(25593)]CRS-1601:CSSD Reconfiguration complete. Active nodes are db-41 .
2012-04-25 14:46:54.177
[ctssd(25738)]CRS-2407:The new Cluster Time Synchronization Service reference node is host db-41.
2012-04-25 14:46:54.177
[ctssd(25738)]CRS-2401:The Cluster Time Synchronization Service started on host db-41.
[client(25843)]CRS-10001:25-Apr-12 14:46 ACFS-9391: Checking for existing ADVM/ACFS installation.
[client(25848)]CRS-10001:25-Apr-12 14:46 ACFS-9392: Validating ADVM/ACFS installation files for operating system.
[client(25850)]CRS-10001:25-Apr-12 14:46 ACFS-9393: Verifying ASM Administrator setup.
[client(25853)]CRS-10001:25-Apr-12 14:46 ACFS-9308: Loading installed ADVM/ACFS drivers.
[client(25856)]CRS-10001:25-Apr-12 14:46 ACFS-9154: Loading ‘oracleoks.ko’ driver.
[client(25913)]CRS-10001:25-Apr-12 14:46 ACFS-9154: Loading ‘oracleadvm.ko’ driver.
[client(25974)]CRS-10001:25-Apr-12 14:46 ACFS-9154: Loading ‘oracleacfs.ko’ driver.
[client(26099)]CRS-10001:25-Apr-12 14:46 ACFS-9327: Verifying ADVM/ACFS devices.
[client(26103)]CRS-10001:25-Apr-12 14:46 ACFS-9156: Detecting control device ‘/dev/asm/.asm_ctl_spec’.
[client(26107)]CRS-10001:25-Apr-12 14:46 ACFS-9156: Detecting control device ‘/dev/ofsctl’.
[client(26113)]CRS-10001:25-Apr-12 14:46 ACFS-9322: completed
2012-04-25 14:47:06.975
[ohasd(25286)]CRS-2807:Resource ‘ora.asm’ failed to start automatically.
[ctssd(25738)]CRS-2405:The Cluster Time Synchronization Service on host db-41 is shutdown by user
2012-04-25 14:51:25.852
[/data/11.2.0/grid/bin/orarootagent.bin(25523)]CRS-5016:Process “/data/11.2.0/grid/bin/acfsload” spawned by agent “/data/11.2.0/grid/bin/orarootagent.bin” for action “check” failed: details at “(:CLSN00010:)” in “/data/11.2.0/grid/log/db-41/agent/ohasd/orarootagent_root/orarootagent_root.log”
2012-04-25 14:51:35.716
[cssd(25593)]CRS-1603:CSSD on node db-41 shutdown by user.
2012-04-25 14:51:35.725
[ohasd(25286)]CRS-2767:Resource state recovery not attempted for ‘ora.cssdmonitor’ as its target state is OFFLINE
2012-04-25 14:51:36.224
[cssd(25593)]CRS-1660:The CSS daemon shutdown has completed
2012-04-25 14:51:38.144
[gpnpd(25510)]CRS-2329:GPNPD on node db-41 shutdown.
重建spfile ：
+ASM.asm_diskgroups=’DATA’,’ARCH’
*.asm_diskstring=’/dev/mapper/*’
*.asm_power_limit=1
*.diagnostic_dest=’/data/app/oracle’
*.instance_type=’asm’
*.large_pool_size=12M
#*.local_listener=’LISTENER_+ASM’
*.remote_login_passwordfile=’EXCLUSIVE’
eg: pfile 拉起 ASM instance mount data group
SQL>create spfile=’+DATA’ from pfile=’xxx’;
[grid@db-41 ~]$ sqlplus ‘/as sysasm’
SQL*Plus: Release 11.2.0.3.0 Production on Thu Apr 26 15:21:33 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production
With the Real Application Clusters and Automatic Storage Management options
SQL> show parameter spfile;
NAME TYPE
———————————— ———————————
VALUE
——————————
spfile string
+DATA/yhd-cluster/asmparameter
file/registry.253.781624261
SQL>
重新启动CRS OK
[client(2162)]CRS-10001:26-Apr-12 14:47 ACFS-9392: Validating ADVM/ACFS installation files for operating system.
[client(2164)]CRS-10001:26-Apr-12 14:47 ACFS-9393: Verifying ASM Administrator setup.
[client(2167)]CRS-10001:26-Apr-12 14:47 ACFS-9308: Loading installed ADVM/ACFS drivers.
[client(2170)]CRS-10001:26-Apr-12 14:47 ACFS-9154: Loading ‘oracleoks.ko’ driver.
[client(2227)]CRS-10001:26-Apr-12 14:47 ACFS-9154: Loading ‘oracleadvm.ko’ driver.
[client(2286)]CRS-10001:26-Apr-12 14:47 ACFS-9154: Loading ‘oracleacfs.ko’ driver.
[client(2415)]CRS-10001:26-Apr-12 14:47 ACFS-9327: Verifying ADVM/ACFS devices.
[client(2418)]CRS-10001:26-Apr-12 14:47 ACFS-9156: Detecting control device ‘/dev/asm/.asm_ctl_spec’.
[client(2422)]CRS-10001:26-Apr-12 14:47 ACFS-9156: Detecting control device ‘/dev/ofsctl’.
[client(2428)]CRS-10001:26-Apr-12 14:47 ACFS-9322: completed
2012-04-26 14:47:44.001
[crsd(2755)]CRS-1012:The OCR service started on node db-41.
2012-04-26 14:47:44.472
[evmd(2146)]CRS-1401:EVMD started on node db-41.
2012-04-26 14:47:46.297
[crsd(2755)]CRS-1201:CRSD started on node db-41.
2012-04-26 14:47:47.586
[/data/11.2.0/grid/bin/oraagent.bin(2880)]CRS-5016:Process “/data/11.2.0/grid/bin/lsnrctl” spawned by agent “/data/11.2.0/grid/bin/oraagent.bin” for action “check” failed: details at “(:CLSN00010:)” in “/data/11.2.0/grid/log/db-41/agent/crsd/oraagent_grid/oraagent_grid.log”
2012-04-26 14:47:47.592
[/data/11.2.0/grid/bin/oraagent.bin(2880)]CRS-5016:Process “/data/11.2.0/grid/bin/lsnrctl” spawned by agent “/data/11.2.0/grid/bin/oraagent.bin” for action “check” failed: details at “(:CLSN00010:)” in “/data/11.2.0/grid/log/db-41/agent/crsd/oraagent_grid/oraagent_grid.log”
2012-04-26 14:47:47.685
[/data/11.2.0/grid/bin/oraagent.bin(2880)]CRS-5016:Process “/data/11.2.0/grid/opmn/bin/onsctli” spawned by agent “/data/11.2.0/grid/bin/oraagent.bin” for action “check” failed: details at “(:CLSN00010:)” in “/data/11.2.0/grid/log/db-41/agent/crsd/oraagent_grid/oraagent_grid.log”
2012-04-26 14:47:47.832
[crsd(2755)]CRS-2772:Server ‘db-41’ has been assigned to pool ‘Generic’.
2012-04-26 14:47:47.833
[crsd(2755)]CRS-2772:Server ‘db-41’ has been assigned to pool ‘ora.user’.
2012-04-26 14:51:13.534
针对这个问题 可以提出这样的疑问 CRS 如何在 datagroup 还没有mount的时候 读取 spfile 而且CRS如何知道在哪去读 spfile 下面这篇精彩的文章 很详细的介绍了process读取的整个过程：
Oracle 11gR2 have many new futures in Grid Computing area. One of them is Oracle Local Repository (OLR), this repository designed to store information and profiles for local resources, resources that dedicated to particular node. It improves the performance of accessing local resources profile information, redundancy and manageability. In Grid Infrastructure RAC configuration there is usual one global shared OCR and OLR’s on each node. In Oracle Restart environment there is only OLR repository. In 11g R2 there is also new feature, Grid Plug and Play (GPNP), as the name implies, it helps to automate and simplify some of the aspects of grid administration. GPNP maintains profile, it is XML file that stores the configuration information of some components maintained by GPNP, for example vips and interconnect information is stored here.
But in this post, I wont to discuss another new feature of 11g R2, it is the possibility to store the server parameter file (spfile) on the ASM disks, also for ASM instance itself! And there is some reasonable questions arise:
1.How process can read the spfile from ASM disks, if they are not mounted yet
2.How process knows where to get spfile if there is no init.ora file in $ORACLE_HOME/dbs with spfile=[path to spfile] parameter
3.What about asm_diskstring parameter?
Third point is important for ASM instance because, before reading spfile from ASM disks, we need to identify them, to identify them we need spfile to get asm_diskstring parameter!
To make clear all this points I will use system calls tracing tools, to trace oracle processes. We can use tools like Dtrace, strace, truss and so on, it depends on platform, I will use strace because I am on Linux.
My environment is Oracle Grid Infrastructure 11g R2 (11.2.0.1.0) in Oracle Restart mode. I simulated ASM disks using loop devices, /dev/loop*, I have 5 disks
bash> /etc/init.d/oracleasm listdisks
DISK1
DISK2
DISK3
DISK4
DISK5
SQL> conn / as sysasm
Connected.
SQL> col path format a15
SQL> select a.name,a.state,b.name,b.path from v$asm_diskgroup a, v$asm_disk b where a.group_number=b.group_number order by b.name;
NAME STATE NAME PATH
—————————— ———– —————————— —————
DGROUP1 MOUNTED DISK1 ORCL:DISK1
DGROUP1 MOUNTED DISK2 ORCL:DISK2
DGROUP2 MOUNTED DISK3 ORCL:DISK3
DGROUP2 MOUNTED DISK4 ORCL:DISK4
DGROUP2 MOUNTED DISK5 ORCL:DISK5
As seen from the listing, I have two disk groups DGROUP1 and DGROUP2. My spfile is located on DGROUP1
SQL> show parameter spfile;
NAME TYPE VALUE
———————————— ———– —————————————————-
spfile string +DGROUP1/asm/asmparameterfile/registry.253.740659373
Lets make some tests
SQL> conn / as sysasm
Connected.
SQL> startup
ASM instance started
Total System Global Area 284565504 bytes
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL>
SQL> show parameter power
NAME TYPE VALUE
———————————— ———– ——————————
asm_power_limit integer 1
SQL> alter system set asm_power_limit=3;
System altered.
SQL> show parameter power
NAME TYPE VALUE
———————————— ———– ——————————
asm_power_limit integer 3
SQL>–We set asm_power_limit to 3 in spfile
SQL> shutdown immediate;
ASM diskgroups dismounted
ASM instance shutdown
SQL> !crs_stat -t
Name Type Target State Host
————————————————————
ora.DGROUP1.dg ora….up.type OFFLINE OFFLINE
ora.DGROUP2.dg ora….up.type OFFLINE OFFLINE
ora….ER.lsnr ora….er.type ONLINE ONLINE testdb03
ora.asm ora.asm.type OFFLINE OFFLINE
ora.cssd ora.cssd.type ONLINE ONLINE testdb03
ora.diskmon ora….on.type ONLINE ONLINE testdb03
SQL>– Lets start instance in nomount mode, it will not mount the diskgroups
SQL> startup nomount;
ASM instance started
Total System Global Area 284565504 bytes
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
SQL> show parameter spfile;
NAME TYPE VALUE
———————————— ———– —————————————————-
spfile string +DGROUP1/asm/asmparameterfile/registry.253.740659373
SQL> show parameter power
NAME TYPE VALUE
———————————— ———– ——————————
asm_power_limit integer 3
SQL> select * from v$spparameter;
select * from v$spparameter
*
ERROR at line 1:
ORA-15001: diskgroup “DGROUP1” does not exist or is not mounted
SQL> alter system set asm_power_limit=10;
alter system set asm_power_limit=10
*
ERROR at line 1:
ORA-32000: write to SPFILE requested but SPFILE is not modifiable
SQL> !asmcmd
ASMCMD> ls
ASMCMD> exit
SQL> !crs_stat -t
Name Type Target State Host
————————————————————
ora.DGROUP1.dg ora….up.type OFFLINE OFFLINE
ora.DGROUP2.dg ora….up.type OFFLINE OFFLINE
ora….ER.lsnr ora….er.type ONLINE ONLINE testdb03
ora.asm ora.asm.type ONLINE ONLINE testdb03
ora.cssd ora.cssd.type ONLINE ONLINE testdb03
ora.diskmon ora….on.type ONLINE ONLINE testdb03
So, what we see, we were able to start ASM instance without mounting the disks, our process picked up correct spfile. The command SHOW PARAMETER reads the parameter values from the memory, but if we try to read directly from spfile (select from v$spparameter) or write to it (alter system set) we will get errors, because diskgroups not mounted yet. It means that our process was read spfile directly from ASM disks. The design about from which disk to read it made based on information from disk header. I use ASMlib, and my asm_diskstring parameter is equal to default value null, ASM instance by default scans the /dev/oracleasm/disks/* on Linux, that is why process found my disks properly. But what if we use HP-UX and our disks is multipathing disks in /dev/rdisk/*, ASM will not scan them by default, we need to use asm_diskstring parameter, how our process will read asm_diskstring parameter before accessing spfile?
Lets start sqlplus, after we will connect as sysasm it will initialize server process, this process will do all job, that is why I will trace this server process
bash> sqlplus /nolog
SQL> conn / as sysasm
Connected.
SQL> !ps -aefH
.
.
oracle 15505 4255 0 13:26 pts/1 00:00:00 sqlplus
oracle 15507 15505 0 13:26 ? 00:00:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
.
.
SQL>
Our sserver process number is 15507, now I will use strace to trace it
bash> strace -o userproc.out -p 15507
start the instance with nomount option, OCSSD must be running, or instace will not start
SQL> startup nomount;
Total System Global Area 284565504 bytes
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
SQL>
Now we can analyze the contents of the userproc.out, I will not list all contents, just useful parts of it
First row is
read(9, “001\6\3\212\6\376\377\377\377\1\376\377\377\377\376\377\377\377″…, 8208) = 49
it is our “startup nomount” command transmitted to server process from sqlplus by socket
connect(6, {sa_family=AF_FILE, path=”/var/tmp/.oracle/sOCSSD_LL_testhost_”…}, 110) = 0
open(“/u01/oracle/product/grid11g/auth/css/testdb03/A6857753/84b0b692”, O_WRONLY|O_CREAT|O_EXCL, 0644) = 13
write(13, “\nS\336[“, 4) = 4
close(13)
from this lines we can see that our process connects to socket file of OCSSD /var/tmp/.oracle/sOCSSD_LL_testhost_ to communicate with it and authenticates itself. That is why it impossible to start instance without OCSSD, if process could not connect to this socket, it would fail. Then it establishes communication with OHASD (Oracle High Availability Services Deamon) through the socket file /var/tmp/.oracle/sCRSD_UI_SOCKET, after exchange messages with OHASD it will get information about the location of spfile and asm_diskstring parameter
access(“/var/tmp/.oracle/sCRSD_UI_SOCKET”, F_OK) = 0
connect(14, {sa_family=AF_FILE, path=”/var/tmp/.oracle/sCRSD_UI_SOCKET”…}, 110) = 0
open(“/u01/oracle/product/grid11g/auth/ohasd/testdb03/A4972914/5140f6df”, O_WRONLY|O_CREAT|O_EXCL, 0644) = 15
write(15, “\20\7\3519”, 4) = 4
close(15)
write(14, “4\2\2\1\1\1\1\3\1T\235\376\t”…, 52) = 52
write(14, “8\3\2\1\1\1\1\4\1T\235\376\t”…, 56) = 56
read(14, “8\3\2\1\1\1\1\3\1T\235\376\t”…, 32768) = 56
write(14, “\212\1PC\v\2\2\5\1T\235\376\t”…, 394) = 394
read(14, “\366\nPC\v\2\2\4\1T\235\376\t”…, 32768) = 2806
write(14, “0\2\20\1\1T\235\376\t”…, 48) = 48
write(3, “kggpnpSIHAGetItem 1 = +dgroup1/ASM/asmparameterfile/registry.253.740659373″…, 75) = 7
write(3, “kfspFileNameGet name=+dgroup1/ASSM/asmparameterfile/registry.253.740659373″…, 78) = 78
write(3, “kggpnpSIHAGetItem 2 = “, 23) = 23
write(3, “kgfspb_shallow_discover dscstr=\”\””…, 33) = 33
As we can see our process got spfile location (+dgroup1/ASM/asmparameterfile/registry.253.740659373) and asm_diskstring=”” which is null by default from OHASD. Now, lets see where OHASD itself gets this information. To identify that I traced the OHASD process, and I found this lines
open(“/etc/oracle/olr.loc”, O_RDONLY) = 4
read(4, “olrconfig_loc=/u01/oracle/produc”…, 4096) = 108
read(4, “”, 4096) = 0
close(4) = 0
open(“/u01/oracle/product/grid11g/cdata/localhost/testhost.olr”, O_RDONLY|O_SYNC|O_LARGEFILE) = 4
pread64(4, “\1\202VD\31\4\3OCR\226\361nA”…, 4096, 102400) = 4096
pread64(4, “\1\202\300I#\4\3OCR\226\361nA”…, 4096, 143360) = 4096
pread64(4, “\1\202VD\31\4\3OCR\226\361nA”…, 4096, 102400) = 4096
pread64(4, “\1\202hq\33\4\3OCR\226\361nA”…, 4096, 110592) = 4096
pread64(4, “\1\202\271\311#\4\20\3OCR\226\361nA”…, 4096, 4337664) = 4096
pread64(4, “\1\202\276\262$\4\20\3OCR\226\361nA”…, 4096, 4341760) = 4096
pread64(4, “\1\202VD\31\4\3OCR\226\361nA”…, 4096, 102400) = 4096
pread64(4, “\1\202hq\33\4\3OCR\226\361nA”…, 4096, 110592) = 4096
pread64(4, “\1\202\271\311#\4\20\3OCR\226\361nA”…, 4096, 4337664) = 4096
pread64(4, “\1\202\276\262$\4\20\3OCR\226\361nA”…, 4096, 4341760) = 4096
pread64(4, “\1\202\236\363%\4\2\3OCR\226\361nA”…, 4096, 4345856) = 4096
pread64(4, “\1\202\334\n&\4\2\3OCR\226\361nA”…, 4096, 4349952) = 4096
pread64(4, “\1\202\325\357-\4\2\3OCR\226\361nA”…, 4096, 4378624) = 4096
pread64(4, “\1\202VD\31\4\3OCR\226\361nA”…, 4096, 102400) = 4096
pread64(4, “\1\202hq\33\4\3OCR\226\361nA”…, 4096, 110592) = 4096
pread64(4, “\1\202\271\311#\4\20\3OCR\226\361nA”…, 4096, 4337664) = 4096
pread64(4, “\1\202\276\262$\4\20\3OCR\226\361nA”…, 4096, 4341760) = 4096
pread64(4, “\1\202\325\357-\4\2\3OCR\226\361nA”…, 4096, 4378624) = 4096
As one would expect OHASD reads this information from OLR, the path to it, it gets from /etc/oracle/olr.loc. I want to note that it is true for Oracle Restart mode, in Oracle RAC environment information is stored in GPNP profile and there is GPNPD process that maintains and manages this profile information. In Oracle Restart, as we can see OHASD process executes this role, and because there is no PGNP profile it stores information in OLR file. So, what next? Our process starts to scan all disks to identify ASM headers, after identifying them, it identifies which disks belongs to which diskgroups by information from header. There is many other metadata in the ASM diskheader that it reads, including pointers to spfile and votig disk file, it is kfdhdb.spfile, kfdhdb.spfflg (first block and number of blocks) and kfdhdb.vfstart, kfdhdb.vfend (begin block and end block). It is possible to read disk header using kfed utility from $ORACLE_HOME/bin directory. For example, lets read disk header of the /dev/loop1 which corresponds to ORCL:DISK1, spfile is on this disk.
shell> kfed read /dev/loop1 | more
kfbh.type: 1 ; 0x002: KFBTYP_DISKHEAD –Indicates that this is ASM disk header
.
kfdhdb.grptyp: 2 ; 0x026: KFDGTP_NORMAL –Indicates mirroring level, in my case it is NORMAL
kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER –Indicates that disk is the member disk of diskgroup
.
kfdhdb.dskname: DISK1 ; 0x028: length=5 –Disk name
kfdhdb.grpname: DGROUP1 ; 0x048: length=7 –Disk group name, to which this disk belongs
kfdhdb.fgname: DISK1 ; 0x068: length=5 –To which failure group this disk belongs
.
kfdhdb.secsize: 512 ; 0x0b8: 0x0200 –Disk sector size
kfdhdb.blksize: 4096 ; 0x0ba: 0x1000 –Disk block size
kfdhdb.ausize: 1048576 ; 0x0bc: 0x00100000 –Allocation Unit size, by default 1M
.
kfdhdb.vfstart: 0 ; 0x0ec: 0x00000000 –Begin block address of voting disk file
kfdhdb.vfend: 0 ; 0x0f0: 0x00000000 –End block address of voting disk file
kfdhdb.spfile: 59 ; 0x0f4: 0x0000003b –Begin block address of spfile
kfdhdb.spfflg: 1 ; 0x0f8: 0x00000001 –Number of blocks containing spfile
Now, lets see what will be next steps of our process
open(“/opt/oracle/extapi/32/asm/orcl/1/libasm.so”, O_RDONLY) = 17
read(17, “\177ELF\1\1\1\3\3\1000\v004″…, 512) = 512
close(17) = 0
open(“/dev/oracleasm/.query_version”, O_RDWR|O_LARGEFILE) = 17
write(17, “MSA\2\1\20”, 16) = 16
read(17, “MSA\2\1\20”, 16) = 16
close(17) = 0
open(“/dev/oracleasm/.get_iid”, O_RDWR|O_LARGEFILE) = 17
write(17, “MSA\2\2\30”, 24) = 24
read(17, “MSA\2\2\30\3”, 24) = 24
close(17) = 0
open(“/dev/oracleasm/.check_iid”, O_RDWR|O_LARGEFILE) = 17
write(17, “MSA\2\3\30\3”, 24) = 24
read(17, “MSA\2\3\30\3”, 24) = 24
close(17) = 0
open(“/dev/oracleasm/iid/0000000000000003”, O_RDWR|O_CREAT|O_LARGEFILE, 0770) = 17
open(“/dev/oracleasm/disks/DISK1”, O_RDONLY|O_LARGEFILE) = 18
read(17, “MSA\2\5 \22T/v\17\200-%\310”, 32) = 32
close(18) = 0
read(17, “MSA\2\7P@\364\311\20\320\301\225\277″…, 80) = 80
open(“/dev/oracleasm/disks/DISK2”, O_RDONLY|O_LARGEFILE) = 18
read(17, “MSA\2\5 \22T/v\17\200+%\310”, 32) = 32
close(18) = 0
read(17, “MSA\2\7P@\364\311\20\320\301\225\277″…, 80) = 80
open(“/dev/oracleasm/disks/DISK3”, O_RDONLY|O_LARGEFILE) = 18
read(17, “MSA\2\5 \22T/v\17\200!%\310”, 32) = 32
close(18) = 0
read(17, “MSA\2\7P@\364\311\20\320\301\225\277″…, 80) = 80
open(“/dev/oracleasm/disks/DISK4”, O_RDONLY|O_LARGEFILE) = 18
read(17, “MSA\2\5 \22T/v\17\200#%\310”, 32) = 32
close(18) = 0
read(17, “MSA\2\7P@\364\311\20\320\301\225\277″…, 80) = 80
open(“/dev/oracleasm/disks/DISK5”, O_RDONLY|O_LARGEFILE) = 18
read(17, “MSA\2\5 \22T/v\17\200)%\310”, 32) = 32
close(18) = 0
read(17, “MSA\2\7P@\364\311\20\320\301\225\277″…, 80) = 80
read(17, “MSA\2\7P@\364\311\20″…, 80) = 80
read(17, “MSA\2\7P@\364\311\20″…, 80) = 80
read(17, “MSA\2\7P@\364\311\20″…, 80) = 80
read(17, “MSA\2\7P@\364\311\20″…, 80) = 80
read(17, “MSA\2\7P@\364\311\20″…, 80) = 80
.
.
open(“/u01/oracle/diag/asm/+asm/+ASM/trace/alert_+ASM.log”, O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE, 0660) = 16
write(16, “Tue Jan 18 17:45:13 2011\n”, 25) = 25
write(16, “Starting ORACLE instance (normal”…, 33) = 33
write(16, “\n”, 1) = 1
close(16)
.
.
It opens /opt/oracle/extapi/32/asm/orcl/1/libasm.so library, reads it. Then it opens special files /dev/oracleasm/.query_version, /dev/oracleasm/.get_iid and /dev/oracleasm/.check_iid, this files is interfaces to ASM device manager. First one is used to get managers version, second one is used to get identifier of the ASM disk device manager instance (not ASM instance) and third for verifying of this instance identifier. In our case ASM device managers instance identifier is 0000000000000003. Then, our process opens /dev/oracleasm/iid/0000000000000003, in other words it establishes connection to the ASM device manager instance. Process will use this interface to read and write to ASM disks. Then it checks all disks from DISK1 to DISK5. After it gets all information about disks, i.e. groups, mirroring level, AU size, failure group and so on it starts reading ASM disk through established interface. I think in this step it reads the spfile. After it gets initialization parameters it starts to allocate memory structures and starting necessary background processes.
Now lets see what is stored in OLR regarding ora.asm resource
shell> cd $ORACLE_HOME/cdata/localhost
shell> strings testhost.olr | grep dgroup1/ASM/asmparameterfile/registry | sed ‘s/~/\n/g’
DEFAULT_TEMPLATE=PROPERTY(RESOURCE_CLASS=asm) ELEMENT(INSTANCE_NAME= %GEN_USR_ORA_INST_NAME%)
DEGREE=1
DESCRIPTION=Oracle ASM resource
ENABLED=1
GEN_USR_ORA_INST_NAME=+ASM
LOAD=1
LOGGING_LEVEL=1
NAME=ora.asm
NLS_LANG=
NOT_RESTARTING_TEMPLATE=
OFFLINE_CHECK_INTERVAL=0
PROFILE_CHANGE_TEMPLATE=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=60
SPFILE=+dgroup1/ASM/asmparameterfile/registry.253.740659373
START_DEPENDENCIES=hard(ora.cssd) weak(ora.LISTENER.lsnr)
START_TIMEOUT=900
STATE_CHANGE_TEMPLATE=
STOP_DEPENDENCIES=hard(ora.cssd)
STOP_TIMEOUT=600
TYPE=ora.asm.type
TYPE_ACL=owner:oracle:rwx,pgrp:dba:rwx,other::r–
UPTIME_THRESHOLD=1d
USR_ORA_ENV=
USR_ORA_INST_NAME=+ASM
USR_ORA_OPEN_MODE=mount
USR_ORA_OPI=false
USR_ORA_STOP_MODE=immediate
VERSION=11.2.0.1.0
We can found there information about spfile “SPFILE=+dgroup1/ASM/asmparameterfile/registry.253.740659373”, we also can see that ora.cssd is hard dependency resource, because OCSSD is responsible for synchronization between ASM and database instance. But what about asm_diskstring parameter, where is it?
shell> strings testhost.olr | grep ASM_DISKSTRING | sed ‘s/~/\n/g’
nothing, it is because my asm_diskstring parameter equals to null, default value, lets change it
SQL> alter system set asm_diskstring=’ORCL:DISK1,ORCL:DISK2′ scope=spfile;
System altered.
check OLR file again
strings testdb03.olr | grep ASM_DISKSTRING | sed ‘s/~/\n/g’
bASM_DISKSTRING
ACL=owner:oracle:rwx,pgrp:dba:rwx,other::r–
ACTION_FAILURE_TEMPLATE=
ACTION_SCRIPT=
AGENT_FILENAME=%CRS_HOME%/bin/oraagent%CRS_EXE_SUFFIX%
ALIAS_NAME=
ASM_DISKSTRING=ORCL:DISK1,ORCL:DISK2
AUTO_START=restore
BASE_TYPE=ora.local_resource.type
Now we can see that information about asm_diskstring is also stored in OLR profile. And next time, at ASM instance startup it will scan only specified disk strings. If we specify disks on which spfile not present, our instance will not start
SQL> alter system set asm_diskstring=’ORCL:DISK3,ORCL:DISK4,ORCL:DISK5′ scope=spfile;
System altered.
SQL> startup nomount force;
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file ‘+DGROUP1/asm/asmparameterfile/registry.253.740659373’
ORA-17503: ksfdopn:2 Failed to open file +DGROUP1/asm/asmparameterfile/registry.253.740659373
SQL>
You can also use the ocrdump utility to extract this entries on any platform in XML format:
shell> ocrdump -local -keyname SYSTEM.OHASD.RESOURCES.ora\!asm.CONFIG -xml -noheader
shell> more OCRDUMPFILE
同样 我们在11.2.0.3的OLR 文件中可以找到SPFILE 的位置：
这里需要说明一点 11.2.0.3 修改diskstring OLR 文件并没有出现对应的修改记录
另外针对 ASM_DISKGROUPS 需要一点说明：
SQL> create pfile=’/tmp/tmp.ctl’ from spfile=’+DATA/yhd-cluster/asmparameterfile/registry.253.781624261′;
File created.
[grid@db-41 ~]$ cat /tmp/tmp.ctl
+ASM1.__oracle_base=’/data/11.2.0’#ORACLE_BASE set from in memory value
+ASM.asm_diskgroups=’DATA’,’ARCH’
+ASM1.asm_diskgroups=’ARCH’#Manual Mount
*.asm_diskgroups=’ARCH’,’DATA’
*.asm_diskstring=’/dev/mapper/*’
*.asm_power_limit=1
*.diagnostic_dest=’/data/app/oracle’
*.instance_type=’asm’
*.large_pool_size=12M
*.remote_login_passwordfile=’EXCLUSIVE’
SQL> alter system set asm_diskgroups=’ARCH’,’DATA’ scope=both sid=’+ASM1′;
System altered.
SQL> create pfile=’/tmp/tmp.ctl’ from spfile=’+DATA/yhd-cluster/asmparameterfile/registry.253.781624261′;
File created.
[grid@db-41 ~]$ cat /tmp/tmp.ctl
+ASM1.__oracle_base=’/data/11.2.0’#ORACLE_BASE set from in memory value
+ASM.asm_diskgroups=’DATA’,’ARCH’
*.asm_diskgroups=’ARCH’,’DATA’
+ASM1.asm_diskgroups=’ARCH’,’DATA’
*.asm_diskstring=’/dev/mapper/*’
*.asm_power_limit=1
*.diagnostic_dest=’/data/app/oracle’
*.instance_type=’asm’
*.large_pool_size=12M
*.remote_login_passwordfile=’EXCLUSIVE’
针对这个问题 这篇文章也做过说明：http://comtmr.blogspot.com/2011/01/11gr2-mysteriously-changing.html
Reference:https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1059856.1
