Cannot identify ASM disks

Hi All,
I am getting this error [FATAL] [INS-30508] Invalid ASM disks. The environment is as below
HP-UX Itanium
11.2.0.2
Volume group ownership:
drwxr-xr-x 2 root sys 8192 Apr 21 14:09 vg1_x_ks_r1_1
logical volume Ownership:
crw-rw---- 1 oracle dba 64 0x010001 Apr 21 14:09 rlv_x_kw_01
crw-rw---- 1 oracle dba 64 0x010002 Apr 21 14:09 rlv_x_kw_02
When i change the volume group owner to oracle, it works fine. I want to know why it should be oracle??
Please let me know if you have any references on this as i am a beginer and i want to learn in depth
Thanks,

Just as a sidenode:
for 11.2 you should set the ownerwship to be "installation user" of grid infrastructure and usergroup "ASM administrator", which you specify during GI installation.
For this reason documentation states
grid:asmadmin
However if in your case you are using oracle as the installation owner and dba as the asm administrator group, than this is o.k.
Sebastian

Similar Messages

ASM: cannot create asm disks - permission denied

We cannot create ASM disks using the command:
# /etc/init.d/oracleasm creatdisk ASMDISK1 /dev/mapper/mpathdp1
Marking disk "ASMDISK1" as an ASM disk: [FAILED]
The log (/var/log/oracleasm) has the following:
Clearing disk header: done
Disk "ASMDISK1" does not exist or is not instantiated
Writing disk header: done
Instantiating disk: oracleasm-instantiate-disk: Unable to create ASM disk "ASMDISK1": Permission denied
failed
Clearing disk header: done
The command is being executed by the root user. Our environment is OEL6:
[oracle@uxdbidbd1 mapper]$ uname -rm
2.6.32-100.28.11.el6.x86_64 x86_64
To install ASMLib we did the following:
Installed the three packages:
1.oracleasm-support-2.1.4-1.el5.x86_64.rpm
2.oracleasmlib-2.0.4-1.el5.x86_64.rpm
3.oracleasm-2.6.18-238.9.1.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
[root@uxdbidbd1 ~]# modprobe oracleasm
[root@uxdbidbd1 ~]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: oracle
Default group to own the driver interface []: oinstall
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
[root@uxdbidbd1 ~]#
[root@uxdbidbd1 ~]# /etc/init.d/oracleasm status
Checking if ASM is loaded: yes
Checking if /dev/oracleasm is mounted: yes
Our SA partitioned the disk using fdisk:
[root@uxdbidbd1 ~]# fdisk -l /dev/mapper/mpathd
Disk /dev/mapper/mpathd: 52.4 GB, 52428800000 bytes
255 heads, 63 sectors/track, 6374 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4849251a
Device Boot Start End Blocks Id System
/dev/mapper/mpathdp1 1 6374 51199123+ 83 Linux
Here are the owner/permissions:
[oracle@uxdbidbd1 mapper]$ ls -al /dev/mapper/
lrwxrwxrwx. 1 root root 7 Apr 22 14:58 mpathd -> ../dm-5
brw-rw-r--. 1 oracle oinstall 253, 6 Apr 25 10:56 mpathdp1
[oracle@uxdbidbd1 dev]$ ls -al /dev
brw-rw----. 1 root disk 253, 5 Apr 22 15:45 dm-5
drwxr-xr-x. 4 root root 0 Apr 22 14:58 oracleasm
[oracle@uxdbidbd1 oracleasm]$ ls -al /dev/oracleasm
total 0
drwxr-xr-x. 4 root root 0 Apr 22 14:58 .
drwxr-xr-x. 23 root root 7200 Apr 24 03:41 ..
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .check_iid
drwxr-xr-x. 1 root root 0 Apr 22 14:58 disks
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .get_iid
drwxrwx---. 1 oracle oinstall 0 Apr 22 14:58 iid
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_disk
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_version
We ran an strace on the createdisk command that is failing and I noticed this in the output file:
28830 mknod("/dev/oracleasm/disks/ASMDISK1", S_IFBLK|0600, makedev(253, 6)) = -1 EACCES (Permission denied)
28830 write(2, "oracleasm-instantiate-disk: ", 28) = 28
28830 write(2, "Unable to create ASM disk \"ASMDI"..., 56) = 56
We changed /dev/oracleasm/disks to 777 in order to test but we got the same result. Do we need to adjust the permissions to all of the parent directories in the path (/dev/oracleasm/disks)? I've been looking around for anything related to permissions on /dev/oracleasm but the docs don't mention anything. Any help would be greatly appreciated.

From what I understand, you should not set device permissions of /dev/oracleasm since oracleasm takes care of it according to /etc/init.d/oracleasm configure.
The problem in your case seems to be that ASM refuses to initialize and write metadata to your device. Was the device previously used by ASM? ASM will fail to initialize a device that contains previous ASM metadata. To erase the device you will need to use the dd command, e.g. dd if=/dev/zero of=/dev/sdb. Both ASMLib and raw devices require the candidate disks to be partitioned before they can be accessed. To create a partition on /dev/sdb, for instance, type fdisk /dev/sdb and create a standard partition using the defaults. This will create /dev/sdb1 and you can try oracleasm createdisk again.
You may try the above, but anyway, I was not sure how much you can trust your installation. The problem could also be that you installed the oracleasm kernel driver and asmlib software for OEL 5. Oracle Linux 6 includes an oracleasm kernel driver and as far as I remember you must not install another oracleasm kernel driver. Using modprob oracleasm and installing oracleasm support package using yum should do the trick. You may also need to download and install the asmlib package for the Oracle ASM grid install to see the ASM disks.

Oracleasm cannot find asm disks on boot

Hello!
RAC 11.2.0.2 on SLES10.
I have configured asmlib on a RAC system (multipath configured) and everything worked as a charm before booting node 2 in the cluster. Problem is that after reboot of node 2 i cannot see my asm disks anymore on that node. This only happens on node 2. I dont have this issue after rebooting node 1. However, if i do a manually "scandisks" on node 2 it sees the disks again and the cluster starts successfully..
I cannot see any difference between the two nodes.. the asmlib rpm's matches the kernel version.
oracle@prod2:~> uname -a
Linux prod2 2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux
oracle@prod2:~> rpm -qa |grep oracleasm
oracleasm-support-2.1.4-1.SLE10
oracleasm-2.6.16.60-0.54.5-smp-2.0.5-1.SLE10
oracleasmlib-2.0.4-1.SLE10/etc/sysconfig/oracleasm looks like this:
# This is a configuration file for automatic loading of the Oracle
# Automatic Storage Management library kernel driver. It is generated
# By running /etc/init.d/oracleasm configure. Please use that method
# to modify this file
# ORACLEASM_ENABELED: 'true' means to load the driver on boot.
ORACLEASM_ENABLED=true
# ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
ORACLEASM_UID=oracle
# ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
ORACLEASM_GID=dba
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dm"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sd"I would be grateful if anyone out there can shed some light on this issue..
Thanks a bunch!

Hi,
I think you need to upgrade your powerpath version. If you are using clariion for your storage.

Cannot create ASM disk groups in DBCA - Oracle 11gR1, Windows 32bit

Good afternoon,
Using 11gR1 on Windows XP, I need help installing a database (single instance) using ASM, I am not able to select disks to be stamped for use by ASM. I have done the following steps:
1. Installed the Oracle 11gR1 software (no database created - just the software)
2. Connected nine (9) SCSI hard drives to the system
3. Created a primary partition on each hard drive, formatted the partition but did *not* assign a drive letter
4. Created a listener service (working properly - checked with lsnrctl status)
5. Started DBCA to create a single database instance using ASMIn DBCA I performed the following:
a. at the welcome screen, click Next
b. at "Step 1 of 16", click Next (accepting the default "Create a Database")
c. at "Step 2 of 16", click Next (accepting the default "General Purpose or Transaction Processing)
d. at "Step 3 of 16", "Global Database Name" set to "dbca", "SID" set to "dbca", click Next
e. at "Step 4 of 16", click Next (accepting the defaults)
f. at "Step 5 of 16", click "Use same administrative passwords for all accounts" and entered password, click Next
g. at "Step 6 of 16", click "Automatic Storage Management (ASM)", click Next
Everything seems just fine until I reach the following step
h. at "Step 7 of 16", click "Create New"
    - The Create Disk Group window pops up (there is nothing shown in the "Select Member Disk Area")
    - set the "Disk Group Name" to "DATAGROUP"
    - click on "Show All" (no devices shown after clicking)
    - click on "Stamp Disks..." this causes the "asmtool operation" window to pop up
      - click on "Add or change label", click on Next
      - the "Select Disks" step appears.   There are 11 hard drives listed but NONE of them
        can be selected - all I can do here is click on Cancel*The question:* Why aren't the drives selectable and what do I need to do to make them selectable ?
Thank you very much for your help,
John.

>
The question: Why aren't the drives selectable and what do I need to do to make them selectable ?
>
To answer my own question (now that I've figured it out), the reason is because the partition should not be formatted.
When Windows displays the "New Partition Wizard", it is important to:
1. not assign a drive letter
2. and select "Do not format this partition"
This will cause Windows to mount the volume thus making it accessible to Oracle.
Hopefully this will help someone not fall in this trap as I did,
John.

ASM diskgroups unmounting, getting ORA-01157: cannot identify/lock data fil

All,
We've recently purchased a RAMSAN device for better throughput. I created the initial diskgroup with the following syntax:
CREATE DISKGROUP EMTPRD0X_SSD01 NORMAL REDUNDANCY
FAILGROUP RS1 DISK '/dev/rdsk_ramsan_primary' NAME ssd_prim
FAILGROUP RS2 DISK '/dev/rdsk_ramsan_backup' NAME ssd_bkup;
and then created a temporary tablespace on top of that diskgroup:
create temporary tablespace temp04 tempfile '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g;
Everything seemed fine at first and then end users started seeing the following errors in the alert log:
SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
Tue Oct 12 16:12:51 2010
Errors in file /opt/oracle/oradump/emtprd02/udump/emtprd02_ora_11578.trc:
ORA-01157: cannot identify/lock data file 3009 - see DBWR trace file
ORA-01110: data file 3009: '+EMTPRD0X_SSD01/emtprd0x/tempfile/temp04.256.732210281'
After talking with Oracle support I was told that the only workaround for diskgroups unmounting themselves is to put a control file/redo log/dummy tablespace inside of that diskgroup and continually write/read from it.
Does that make sense?
They pointed me to note 603204.1 - Why FRA Diskgroup Gets Mounted/Dismounted.
The system is a 3 node Oracle 10.2.0.4 rac running on ASM Solaris x86 64bit.
Any ideas?
Thanks,
Brian

Post Operating System (OS) name & version for DB server system.
Post results of
SELECT * from v$version
My db is not in archivelog mode poor choice
and no backup was taken. Worse choise
Is there any way I can recover this db? Recover as in no data loss?
Very doubtful.
Possible to open with data loss.
01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause: The background process was either unable to find one of the data
//         files or failed to lock it because the file was already in use.
//         The database will prohibit access to this file but other files will
//         be unaffected. However the first instance to open the database will
//         need to access all online data files. Accompanying error from the
//         operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
//         open the database or do ALTER SYSTEM CHECK DATAFILES.What exactly cause this mess?
Edited by: sb92075 on Jan 7, 2010 8:59 PM

How to identify ASM DiskGroup attached to which Disks ???

Hi Guys,
In 11gR2 RAC, How to identify which ASM Diskgroup is attached to which Disks...( OS is RHEL 5.4).
We could list ASM Diskgroups by,
*#oracleasm listdisks* but this command doesn't show the disks assigned to ASM DiskGroup.
Even for checking location of OCR and Voting Disks only show Diskgroup name and not the actual disks.
$ocrcheck
$crsctl query css votedisk
( like in 10gR2 RAC, We do entry in /etc/rules.d/udev/60-raw-rules file for raw mapping of OCR, Voting Disk and Other ASM Diskgroup)
Plz help me, As one of the client place, I could see so many LUNs assigned to the Server and not getting exact idea which Disks have been used for OCR, Voting Disk and DATA Diskgroup.
Thanks,
Manish

Well for this you can use oracleasm querydisk.Using this you can identify which device as marked for asm or not. for example you can see this below example.
[oracle@localhost init.d]$ sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jun 3 11:52:12 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select path from v$asm_disk;
PATH
/dev/oracleasm/disks/VOL2
/dev/oracleasm/disks/VOL1
SQL> exit;
[oracle@localhost init.d]$ su
Password:
[root@localhost init.d]# /sbin/fdisk -l
Disk /dev/sda: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1        1305    10482381   83 Linux
/dev/sda2            1306        9401    65031120   83 Linux
/dev/sda3            9402        9662     2096482+ 82 Linux swap / Solaris
/dev/sda4            9663        9726      514080    5 Extended
/dev/sda5            9663        9726      514048+ 83 Linux
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id System
/dev/sdb1               1        4859    39029886   83 Linux
/dev/sdb2            4860        9729    39118275   83 Linux
[root@localhost init.d]# ./oracleasm querydisk /dev/sdb1
Device "/dev/sdb1" is marked an ASM disk with the label "VOL1"
[root@localhost init.d]# ./oracleasm querydisk /dev/sdb2
Device "/dev/sdb2" is marked an ASM disk with the label "VOL2"
[root@localhost init.d]# ./oracleasm querydisk /dev/sda1
Device "/dev/sda1" is not marked as an ASM disk
[root@localhost init.d]#Also in windows :
C:\Documents and Settings\comp>asmtool -list
NTFS                             \Device\Harddisk0\Partition1           140655M
ORCLDISKDATA1                    \Device\Harddisk0\Partition2             4102M
ORCLDISKDATA2                    \Device\Harddisk0\Partition3             4102M
NTFS                             \Device\Harddisk0\Partition4           152617M
C:\Documents and Settings\comp>answered by chinar.
refer:-how to identify which rawdevice Disk Is named as VOL1 IN ASM from os level
Happy New Year.
regards,

Create ASM Disk Groups cannot see Disk Path to select during installation

Hello Guys,
I am setting up 2 node RAC on 11gR2 and Linux.
I have configured all the pre-installation steps that are required to run Grid Setup as per my understanding.
I have configure SAN partitions using multipath.
I can see my SAN volume when i query multipath -l
Then i configured the raw partitions by oracleasm. Configured and then created mount points:
/dev/oracleasm/disks/
CRSVOL1 DATAVOL1 FRAVOL1
Later on I created the disks using oracle asm command:
/usr/sbin/oracleasm createdisk CRSVOL1 /dev/mapper/racdbp1 and so on...
I have run /usr/sbin/oracleasm scandisks
Cleaning any stale ASM disks...
Scanning system for ASM disks...
And when i list disk with command /usr/sbin/oracleasm listdisks
it shows the disk like this on both nodes:
CRSVOL1
DATAVOL1
FRAVOL1
BUT during the installation screen when it comes to create ASM Disk Groups It shows nothing in the add disk frame, I cant select the volumes I can list, like i did above.
Any hint please?
Thanks, Imran

Thanks but my problem is very specific. I feel that i have performed all the necessary steps to get complete the step i discussed above. As per different commands all is set. But i am unable to see Disks and Disks Paths during the installation screen. This is another output to verify if the installe user have rights on the asm devices:
[grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
DATAVOL1 ETSCRS1 ETSVOT1 ETSVOT3 FRAVOL1
ETSASM1 ETSCRS2 ETSVOT2 EXTRADM
[grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
[grid@racnode1 disks]$ ls -ltr
total 0
brw-rw---- 1 grid asmadmin 8, 1 Oct 2 16:47 ETSASM1
brw-rw---- 1 grid asmadmin 8, 5 Oct 2 16:47 DATAVOL1
brw-rw---- 1 grid asmadmin 8, 6 Oct 2 16:47 FRAVOL1
brw-rw---- 1 grid asmadmin 8, 7 Oct 2 16:47 ETSVOT1
brw-rw---- 1 grid asmadmin 8, 8 Oct 2 16:47 ETSVOT2
brw-rw---- 1 grid asmadmin 8, 9 Oct 2 16:47 ETSVOT3
brw-rw---- 1 grid asmadmin 8, 10 Oct 2 16:47 ETSCRS1
brw-rw---- 1 grid asmadmin 8, 11 Oct 2 16:47 ETSCRS2
brw-rw---- 1 grid asmadmin 8, 13 Oct 2 16:47 EXTRADM
I will appreciate if you can help me to get through this step... Is there anything else needs to be verified?
Regards, Imran

ORA-01157: cannot identify/lock data file 13 - see DBWR trace file

Hi all,
I've a Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
I'm using ASM.
Yesterday I added new disks and then I changed the +/etc/udev/rules.d/98-oracle.rules+ file.
Now it looks like this (the bolded are the new ones):
# Oracle Configuration Registry
KERNEL=="emcpowerd1", OWNER="root", GROUP="oinstall", MODE="640", NAME="ocr"
# Voting Disks
KERNEL=="emcpowerr1", OWNER="oracle", GROUP="oinstall", MODE="640", NAME="voting"
# Spfile ASM+
KERNEL=="emcpowers1", OWNER="oracle", GROUP="dba", MODE="660", NAME="spfileASM"
# ASM Devices
KERNEL=="emcpowerj1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm0" #onlineredo asm disk
KERNEL=="emcpowern1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm1" #data asm disk
KERNEL=="emcpowerh1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm2" #data asm disk
KERNEL=="emcpowerq1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm3" #data asm disk
KERNEL=="emcpowere1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm4" #data asm disk
KERNEL=="emcpowerg1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm5" #data asm disk
KERNEL=="emcpowerl1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm6" #data asm disk
KERNEL=="emcpowero1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm7" #data asm disk
KERNEL=="emcpowerf1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm8" #data asm disk
KERNEL=="emcpowerm1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm9" #data asm disk
KERNEL=="emcpoweri1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm10" #data asm disk
KERNEL=="emcpowerp1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm11" #data asm disk
KERNEL=="emcpowerk1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm12" #data asm disk
KERNEL=="emcpowert", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm210" #data asm disk SATA
KERNEL=="emcpowerc", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm211" #data asm disk SATA
KERNEL=="emcpowerb", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm212" #data asm disk SATA
KERNEL=="emcpowera", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm213" #data asm disk SATA
It's the same on both RAC nodes.
The operating system, a RedHat 5.4, see the new devices (both nodes):
ls -ltr /dev/asm*
brw-rw---- 1 oracle dba 120, 16 May 18 10:03 /dev/asm212
brw-rw---- 1 oracle dba 120, 304 May 18 10:03 /dev/asm210
brw-rw---- 1 oracle dba 120, 32 May 18 10:03 /dev/asm211
brw-rw---- 1 oracle dba 120, 0 May 18 10:03 /dev/asm213
brw-rw---- 1 oracle dba 120, 209 May 18 10:05 /dev/asm1
brw-rw---- 1 oracle dba 120, 81 May 18 13:40 /dev/asm8
brw-rw---- 1 oracle dba 120, 97 May 18 13:40 /dev/asm5
brw-rw---- 1 oracle dba 120, 193 May 18 13:40 /dev/asm9
brw-rw---- 1 oracle dba 120, 161 May 18 13:40 /dev/asm12
brw-rw---- 1 oracle dba 120, 241 May 18 13:40 /dev/asm11
brw-rw---- 1 oracle dba 120, 177 May 18 13:40 /dev/asm6
brw-rw---- 1 oracle dba 120, 225 May 18 13:40 /dev/asm7
brw-rw---- 1 oracle dba 120, 65 May 18 13:40 /dev/asm4
brw-rw---- 1 oracle dba 120, 129 May 18 13:40 /dev/asm10
brw-rw---- 1 oracle dba 120, 257 May 18 13:40 /dev/asm3
brw-rw---- 1 oracle dba 120, 113 May 18 13:40 /dev/asm2
brw-rw---- 1 oracle dba 120, 145 May 18 13:40 /dev/asm0
Both ASM instance see new devices:
From ASM1
SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:43:10 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM1
SQL> select path from v$asm_disk;
PATH
/dev/asm212
/dev/asm211
/dev/asm213
/dev/asm210
/dev/asm1
/dev/asm4
/dev/asm5
/dev/asm0
/dev/asm12
/dev/asm9
/dev/asm2
/dev/asm10
/dev/asm7
/dev/asm11
/dev/asm3
/dev/asm8
/dev/asm6
17 rows selected.
SQL>
From ASM2
SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:42:39 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM2
SQL> select path from v$asm_disk;
PATH
/dev/asm213
/dev/asm211
/dev/asm210
/dev/asm212
/dev/asm8
/dev/asm7
/dev/asm6
/dev/asm11
/dev/asm4
/dev/asm12
/dev/asm5
/dev/asm9
/dev/asm1
/dev/asm3
/dev/asm10
/dev/asm2
/dev/asm0
17 rows selected.
SQL>
Then I created a disk group:
CREATE DISKGROUP STORE EXTERNAL REDUNDANCY DISK '/dev/asm210';
Then I created a new tablespace:
CREATE TABLESPACE store DATAFILE '+STORE';
I did all this operations from NODE1.
What is happening now is that everytime I try to read something from new diskgroup FROM NODE2 I get the ORA-01157:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707
No problem to read from NODE1.
The simple query on dba_data_file work from NODE1 and fails from NODE2 with the ORA-01157.
I found this on the alert log:
<msg time='2010-05-18T10:06:41.084+00:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
module='' pid='11014'>
<txt>Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
</txt>
</msg>
And this from the trace:
Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
System name: Linux
Node name: node02
Release: 2.6.18-128.7.1.el5
Version: #1 SMP Wed Aug 19 04:00:49 EDT 2009
Machine: x86_64
Instance name: EVODB2
Redo thread mounted by this instance: 2
Oracle process number: 19
Unix process pid: 11014, image: oracle@node02 (SMON)
*** 2010-05-18 10:06:41.084
*** SESSION ID:(151.1) 2010-05-18 10:06:41.084
*** CLIENT ID:() 2010-05-18 10:06:41.084
*** SERVICE NAME:(SYS$BACKGROUND) 2010-05-18 10:06:41.084
*** MODULE NAME:() 2010-05-18 10:06:41.084
*** ACTION NAME:() 2010-05-18 10:06:41.084
DDE rules only execution for: ORA 1110
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
----- DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- (Action duration in csec: 0) -----
----- END DDE Actions Dump -----
*** 2010-05-18 10:06:41.084
SMON: following errors trapped and ignored:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
Any suggestion about how to solve the problem?
Thanks in advance!
Samuel

I didn't understand what do you mean with thread...
But I think you found the problem
Initialization files of both ASM instance are: SPFILE='/dev/spfileASM'
that SPFILE is (common for both):
+ASM2.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
+ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
+ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'#Manual Mount
*.asm_diskstring='/dev/asm*'
*.cluster_database=true
*.diagnostic_dest='/u01/app/oracle'
+ASM1.instance_number=1
+ASM2.instance_number=2
*.instance_type='asm'
*.large_pool_size=12M
+ASM1.local_listener='LISTENER_ASM'
+AC
Then I executed another query:
From ASM1
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM1
SQL> select name, state from v$asm_diskgroup;
NAME STATE
ARCHIVELOG MOUNTED
DATA MOUNTED
ONLINELOG MOUNTED
STORE MOUNTED
SQL>
From ASM2
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM2
SQL> select name, state from v$asm_diskgroup;
NAME STATE
ARCHIVELOG MOUNTED
DATA MOUNTED
ONLINELOG MOUNTED
STORE DISMOUNTED
SQL>
Than the question is:
how can I mount the disk group STORE also on ASM2?
I think the problems is into the spfile lines:
+ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
+ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'
How can I change the +ASM2.asm_diskgroups value?
Thanks

Questions on asm disk discovery:

Questions on asm disk discovery:
1）What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) Which one of the above two finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
Thanks.

From my understanding all disk you see in /dev/oracleasm/disks are the disks in your system that been discovered by asmlib at discovery stage.
Currently, due to bug 13465545, ASM instance will discover disks from both locations, ASM_DISKSTRING and gpnp profile, which can cause some mess in disk representation for asm. You can check the settings using asmcmd command: dsget, and set to be the same using dsset.
I think its more secure to set ASM_DISKSTRING to only the disks used by asm instance.
ASMCMD> dsget
Regards
Ed

Questions on asm disk discover:

Questions on asm disk discover:
1）What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) which one finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we do not rely on the path the discover the asmlib
disks. asm_diskstring='ORCL:*' will identify the right disks. I am not sure if setting 'ORCL:*' is the most economic way as I am not sure if Oracle will have to scan all the disks
on the OS and probe the disks that it has rigths to determine which disks belong to ASM. If Oracle has to screen all the disks in this way, then I think setting
asm_diskstring='<path_to_asmlib_disk>' will be much faster. However, this will be open to the persistent problem. Is my understanding correct?
Thanks.

Questions on asm disk discovery:
1）What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) Which one of the above two finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
Thanks.

Error while creating asm disk group

i am trying to convert my database SRAVAN as an ASM instance.
so do i need to set ORACLE_SID=+ASM???? r else it wil be SRAVAN??
I WAS ENDED UP WITH FOLLOWING ERRORS WHILE CREATING DISK GROUP.
guyz please do help me
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/u04/app/oracle/product/asmdisks/disk1'
5 FAILGROUP ctlr2
6 DISK '/u04/app/oracle/product/asmdisks/disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk2' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk2'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk1' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk1'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
[oracle@sierra200 dbs]$ cd /u04/app/oracle/product/asmdisks
[oracle@sierra200 asmdisks]$ ls -ltr
total 205008
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:42 disk1
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:47 disk2
Thanks & Regards
Sravan Dalavai

Looks like you are asking ASM to use plain files. Have you used the Device Loopback (losetup) a d made the emulate raw devices?
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml

Oracle Grid Installer cannot list available disks

Hi all,
I'm trying to install Oracle Database 11g R2 64-bit with ASM on an Oracle Enterprise Linux 5.5 64-bit.
The problem I'm facing is that the Grid Infrastructure Installer cannot list available disks. In the setp of creating Diskgroups, I only see blank disk.
Following the main actions I took:
[root@srv07 ~]# fdisk /dev/sdb
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1638, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1638, default 1638):
Using default value 1638
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
[root@srv07 ~]# rpm -qa | grep oracleasm
oracleasm-support-2.1.3-1.el5
oracleasm-2.6.18-194.el5-2.0.5-1.el5
[root@srv07 ~]# oracleasm configure -i
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface [grid]:
Default group to own the driver interface [asmdba]:
Start Oracle ASM library driver on boot (y/n) [y]:
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
[root@srv07 ~]# /usr/sbin/oracleasm createdisk DISK1 /dev/sdb1
Writing disk header: done
Instantiating disk: done
[root@srv07 ~]# /usr/sbin/oracleasm listdisks
DISK1
[root@srv07 ~]# /usr/sbin/oracleasm scandisks
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...The log generated by the Installer can be viwed from: http://www.ahmedbaraka.com/temp/infralog.txt
Any guideline is appreciated.

Hi Srini,
I have tried as you mentioned like installing Java in C:\Java... and I have tried the by setting the JRE_LOCATION of local path. No use of it.
tried with -jreloc and setting the java path in environment variables too.
As I understand, the problem i have seen at files copied path is not expected as required. Please see the path below...
C:\DOCUME~1\v859971\LOCALS~1\Temp\OraInstall2013-09-06_03-36-31PM\jre\bin\javaw.exe.
After running the Setup.exe -deinstall... temporary folder is creating with timestamp and all the required files are coping here...
"jre" folder also created and copied required java files directly into jre folder, but not in jre\bin folder.
folder path is like this
C:\DOCUME~1\v859971\LOCALS~1\Temp\OraInstall2013-09-06_03-36-31PM\jre\javaw.exe.
Setup application is expecting jre\bin\javaw.exe, but folder structure is created as jre\javaw.exe. There it is coming the issue.
I have even tried with copying all the files into bin folder and executed the setup.exe, it again creating a new temporary file
not able to resolve it...

Java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DB

I am deploying my application components on Oracle RAC database, when i install my app component i will run a script which creates a user and tablespace on bot rac-nodes(node1 and node2)
as database is clustered, the user are created on 2 nodes and tablespace is stored in a shared location for two rac nodes
i am able to successfully run my script on rac-node1 and and installed my component and when i started installing the app component on node2 getting error
java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: '/db/db/db/ora10g/10.2.0/admin/dbadmin_01.dbf'
ORA-06512: at "ADMIN.XL_SP_DBCHECK", line 48
ORA-06512: at line 1
"dbadmin_01.dbf is the custom tablespace which created by me"
i a mgetting error while installing the app component on rac-node2

You should not create database files outside of the ASM.
I'm not sure you can move the datafile, I would export the data from the tablespace (if there is data you need there), delete the tablespace and recreate it in the ASM, then import the data back.
If you want to move the datafile, you can try using RMAN (from node1).
First connect to the database with sqlplus and execute:
alter tablespace <tbs_name> offline;Then start RMAN: rman target /
BACKUP AS COPY DATAFILE '<file>' FORMAT '+<ASM_DG>';Then in sqlplus, execute:
alter tablespace <tbs_name> online;I'm not sure it will work, and I hope I got the commands right because I can't check it right now.
Good luck
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Java.sql.SQLException: ORA-01157: cannot identify/lock data file : PLz Help

My datafiles are in ASM file system, however the only one file ACIPEN_DATA is the one, which is not in ASM file system, and this the file which is in concern.
We are getting the following exception in the lxkratgas1.lex1.lexmark.com when connecting to ACIPEN_DATA.
This exception is coming up sometimes and the sometimes the file is getting processed successfully
Caused by: java.sql.SQLException: ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: '/oracle/SE/product/10.2.0/db_1/dbs/ACIPEN_DATA'
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1169)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:278)
at atg.adapter.gsa.SQLStatement.executeUpdate(SQLStatement.java:725)
at atg.adapter.gsa.Table.insert(Table.java:1378)
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6272)
... 61 more
====================================================================
We have checked the datafile, it is absolutely online.
Can some expert jump in and resolve this issue Please.

01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause: The background process was either unable to find one of the data
//         files or failed to lock it because the file was already in use.
//         The database will prohibit access to this file but other files will
//         be unaffected. However the first instance to open the database will
//         need to access all online data files. Accompanying error from the
//         operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
//         open the database or do ALTER SYSTEM CHECK DATAFILES.is this a RAC database?

ORA-01157: cannot identify/lock data file error in standby database.

Hi,
i have a primary database and standby database (11.2.0.1.0) running in ASM with different diskgroup names. I applied an incremental backup on standby database to resolve archive log gap and generated a controlfile for standby in primary database and restored the controlfile in standby database.But when i started the MRP process its not starting and thows error in alert log ORA-01157: cannot identify/lock data file. When i queried the standby database file it shows the location on primary database datafiles names not the standby database.
PRIMARY DATABASE
SQL> select name from v$datafile;
NAME
+DATA/oradb/datafile/system.256.788911005
+DATA/oradb/datafile/sysaux.257.788911005
+DATA/oradb/datafile/undotbs1.258.788911005
+DATA/oradb/datafile/users.259.788911005
STANDBY DATABASE
SQL> select name from v$datafile;
NAME
+STDBY/oradb/datafile/system.256.788911005
+STDBY/oradb/datafile/sysaux.257.788911005
+STDBY/oradb/datafile/undotbs1.258.788911005
+STDBY/oradb/datafile/users.259.788911005
The Actual physical location of standby database files in ASM in standby server is shown below
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
ASMCMD>
ASMCMD> ls
SYSAUX.259.805921967
SYSTEM.258.805921881
UNDOTBS1.260.805922023
USERS.261.805922029
ASMCMD>
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
i even tried to rename the datafiles in standby database but it throws error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Regards,
007

Hi saurabh,
I tried to rename the datafiles in standby database after restoring it throws the below error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Also in my pfile i have mentioned the below parameters
*.db_create_file_dest='+STDBY'
*.db_domain=''
*.db_file_name_convert='+DATA','+STDBY'
*.db_name='ORADB'
*.db_unique_name='11GDB'
Regards,
007

Cannot identify ASM disks

Similar Messages

Maybe you are looking for