ASM disk mount and dismount !

Hello ,
I found this listing continues in my alert.log.I found when oracle archives it mounts the disk and the unmounts it.Is it Usual?
Thread 1 cannot allocate new log, sequence 161
Checkpoint not complete
Current log# 1 seq# 160 mem# 0: +ORCL_ONLINE_OPS1/dwh/redo01.log
Thread 1 advanced to log sequence 161
Current log# 2 seq# 161 mem# 0: +ORCL_ONLINE_OPS1/dwh/redo02.log
Wed Jan 9 17:22:13 2008
SUCCESS: diskgroup ORCL_ARCH was mounted
SUCCESS: diskgroup ORCL_ARCH was dismounted
SUCCESS: diskgroup ORCL_ARCH was mounted
SUCCESS: diskgroup ORCL_ARCH was dismounted
SUCCESS: diskgroup ORCL_ARCH was mounted
SUCCESS: diskgroup ORCL_ARCH was dismounted
Wed Jan 9 17:27:50 2008
Shutting down archive processes
Wed Jan 9 17:27:55 2008
Thansk,
Pam

please check metalink note
Note.361173.1 Asm Diskgroup success Mount And Umount messages in alert.log during Rman Backup
Thanks,
Anil

Similar Messages

RAC ASM diskgroup mounted and dismounted so frequent

Hi,
We have installed a Oracle 10g RAC with ASM.
It was going well, but we found some messages in the alertlog as follows:
Mon Jan 22 08:43:45 2007
Thread 2 advanced to log sequence 1113
Current log# 9 seq# 1113 mem# 0: +DATA/dvpc/onlinelog/group_9.284.609078417
Current log# 9 seq# 1113 mem# 1: +FLASH/dvpc/onlinelog/group_9.265.609078421
Mon Jan 22 08:43:45 2007
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
Mon Jan 22 11:28:41 2007
Thread 2 advanced to log sequence 1114
Current log# 10 seq# 1114 mem# 0: +DATA/dvpc/onlinelog/group_10.285.609078423
Current log# 10 seq# 1114 mem# 1: +FLASH/dvpc/onlinelog/group_10.266.609078425
Mon Jan 22 11:28:41 2007
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
Mon Jan 22 14:12:02 2007
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
Mon Jan 22 14:12:02 2007
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
SUCCESS: diskgroup LOG was mounted
SUCCESS: diskgroup LOG was dismounted
Why these diskgroups mounted and dismounted so frequent?

Yes, diskgroup needs to be mounted before it can be written to;) And because there are only archive logs in the LOG diskgroup it's unmounted when archiving is done.
What's a bit odd is that the "normal" archival messages seem to be missing from alert.log.

ASM Disk Mount Error

Hi,
I am consistently getting the following error since yesterday while mounting the ASM disk.
1. I created the ASM disks successfully and created the appropriate ASM DiskGroups using asmca utility.
2. I was able to see the diskgroups as mounted from asmcmd tool.
3. All of a sudden, all the diskgroups were dismounted yesterday and I see the following error in the alert logs for all the
diskgroups.
4. This is using ASM11g
As I exhausted all my avenues to fix, I have turned to you for further assistance. Please do the needful.
SQL> /* ASMCMD */ALTER DISKGROUP DataVSPSI MOUNT
NOTE: cache registered group DATAVSPSI number=3 incarn=0x7934bf5d
NOTE: cache began mount (first) of group DATAVSPSI number=3 incarn=0x7934bf5d
NOTE: Assigning number (3,0) to disk (ORCL:D01_VSP_SI)
Thu Dec 27 17:38:29 2012
NOTE: start heartbeating (grp 3)
kfdp_query(DATAVSPSI): 11
kfdp_queryBg(): 11
NOTE: cache opening disk 0 of grp 3: D01_VSP_SI label:D01_VSP_SI
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache mounting (first) external redundancy group 3/0x7934BF5D (DATAVSPSI)
NOTE: starting recovery of thread=1 ckpt=2.1 group=3 (DATAVSPSI)
WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
AU:4 disk_offset(bytes):4333568 io_size:122880 operation:Read type:asynchronous
result:I/O error process_id:32162
WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
AU:4 disk_offset(bytes):4202496 io_size:131072 operation:Read type:asynchronous
result:I/O error process_id:32162
ORA-15080: synchronous I/O operation to a disk failed
ERROR: ASM recovery failed to read ACD
NOTE: cache initiating offline of disk 0 group DATAVSPSI
NOTE: process 32162 initiating offline of disk 0.3940831150 (D01_VSP_SI) with mask 0x7e in group 3
WARNING: Disk D01_VSP_SI in mode 0x7f is now being taken offline
NOTE: initiating PST update: grp = 3, dsk = 0/0xeae44fae, mode = 0x15
kfdp_updateDsk(): 12
kfdp_updateDskBg(): 12
ERROR: too many offline disks in PST (grp 3)
WARNING: Disk D01_VSP_SI in mode 0x7f offline aborted
Thu Dec 27 17:38:29 2012
NOTE: halting all I/Os to diskgroup DATAVSPSI
NOTE: crash recovery signalled OER-15130
ERROR: ORA-15130 signalled during mount of diskgroup DATAVSPSI
NOTE: cache dismounting (clean) group 3/0x7934BF5D (DATAVSPSI)
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 3/0x7934BF5D (DATAVSPSI)
Also, I think the lower level disk is fine as I am able to write to the disk as follows :
[oracle@rmanqa01 trace]$ dd of=/dev/sdp1
Test Test
0+1 records in
0+1 records out
10 bytes (10 B) copied, 4.97435 seconds, 0.0 kB/s
[oracle@rmanqa01 trace]$ id
uid=500(oracle) gid=500(oinstall) groups=6(disk),500(oinstall),501(dba),502(oper),503(asmadmin),504(asmdba),505(asmoper),506(horcm)
[oracle@rmanqa01 trace]$ ls -l /dev/sdp1
brw-rw---- 1 root disk 8, 241 Dec 28 11:59 /dev/sdp1
[oracle@rmanqa01 trace]$
The oracleasm also lists the disk D01_VSP_SI as follows :
[root@rmanqa01 log]# /etc/init.d/oracleasm listdisks
A01_VSP_SI
ADSK01
ARCH_AMS_SI
D01_VSP_SI
DATA_AMS_SI
DDSK01
DEMO_ARCH
DEMO_DATA
L01_VSP_SI
RDSK01
REDO_AMS_SI
You have new mail in /var/spool/mail/root
[root@rmanqa01 log]# /etc/init.d/oracleasm querydisk D01_VSP_SI
Disk "D01_VSP_SI" is a valid ASM disk
[root@rmanqa01 log]#
kfed tool was giving proper data till yesterday.
Today, I am getting the following :
./kfed read /dev/oracleasm/disks/D01_VSP_SI
kfbh.endian: 84 ; 0x000: 0x54
kfbh.hard: 101 ; 0x001: 0x65
kfbh.type: 115 ; 0x002: *** Unknown Enum ***
kfbh.datfmt: 116 ; 0x003: 0x74
kfbh.block.blk: 1936020512 ; 0x004: T=0 NUMB=0x73655420
kfbh.block.obj: 2147486324 ; 0x008: TYPE=0x8 NUMB=0xa74
kfbh.check: 2886846267 ; 0x00c: 0xac11c73b
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
ERROR!!!, failed to get the oracore error message
[oracle@rmanqa01 bin]$
Please help.
Thanks
V V
Edited by: user13479556 on Dec 28, 2012 12:00 PM

Thanks Berx for pointing that out.
I deleted the ASM disks and the diskgroups and re-created a fresh and was able to start the ASM instance and mount the DGs.
Now the mount is persistent, but the dbca fails with the following error in the alert log. Under what situations can this error be seen ?
NOTE: Loaded library: System
SUCCESS: diskgroup DATAAMSSI was mounted
SUCCESS: diskgroup ARCHAMSSI was mounted
ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.DATAAMSSI.dg*ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.ARCHAMSSI.dg*Mon Dec 31 20:25:25 2012
SUCCESS: diskgroup LOGAMSSI was mounted
Mon Dec 31 20:25:25 2012
ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.LOGAMSSI.dg
Mon Dec 31 20:25:25 2012
Successful mount of redo thread 1, with mount id 784925673
Completed: Create controlfile reuse set database "R3AMSSI"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'+DATAAMSSI/R3AMSSI/system01.dbf',
'+DATAAMSSI/R3AMSSI/sysaux01.dbf',
'+DATAAMSSI/R3AMSSI/undotbs01.dbf',
'+DATAAMSSI/R3AMSSI/users01.dbf'
LOGFILE GROUP 1 ('+LOGAMSSI/R3AMSSI/redo01.log') SIZE 51200K,
GROUP 2 ('+LOGAMSSI/R3AMSSI/redo02.log') SIZE 51200K,
GROUP 3 ('+LOGAMSSI/R3AMSSI/redo03.log') SIZE 51200K RESETLOGS
Stopping background process MMNL
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
Mon Dec 31 20:25:28 2012
MMON started with pid=17, OS id=10452
ALTER SYSTEM enable restricted session;
Mon Dec 31 20:25:28 2012
MMNL started with pid=18, OS id=10454
alter database "R3AMSSI" open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 945183
Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
Mon Dec 31 20:25:29 2012
Checker run found 5 new persistent data failures
Mon Dec 31 20:27:07 2012
I can verify from asmcmd that the redologs mentioned above as missing is very much present in '+LOGAMSSI/R3AMSSI'
Thanks
V V

ASM disk mount in alter log

Hello
I am running Oracle 10g with ASM and I am seeing 1 of my 3 disk groups being mounted and unmounted in the alter log of on database instance.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
On this disk group I have only my archive logs. Is this normal ?

Danny,
Are you on RAC? Check this mealink note 361173.1 which talks about the same thing.
Update:
Ignore the messages. They are just informal ones and will be removed from future(!)versions. Basically ASM close (or dismount) those groups when it closes the file descriptors on that DG and mounts when it opens first file on that DG.
Look at this thread over Orafaq where Gopal mentioned for this message this note,
http://www.orafaq.com/maillist/oracle-l/2007/02/18/1244.htm
Aman....
Edited by: Aman.... on Sep 19, 2008 8:52 AM

Can The ASM Disk Header and Disk Group Be Renamed?

I have a requirement to mount multiple SAN clones (EMC Symclone) of a production ASM instance on the same development server. RMAN is too slow to be an option, unless I find a white paper explaining any way to make RMAN perform a clone faster than the SAN.
The default response is normally, "Do your clone to dedicated hardware." However, that answer is not an option for obvious financial reasons, especially since I am working with a RAC environment with ~10 development and test environments.
The only way to do this (that I can think of) is to rename the disk header and probably the disk group prior to making it available to the ASM instance.
I have heard that Oracle has come up with an undocumented solution for one or more businesses. I believe it has something to do with the kfed library located in $ORACLE_HOME/rdbms/lib.
Has anyone out there managed to do this? If so, can you share your solution or point me in the right direction?
I know I am not the only one out there looking for a solution to this issue...
Thanks in advance.

This is absolutely possible. Can be done via kfed. I never found the answer searching the net and had to figure it out. Here it is in hopes that it helps someone else. DISCLAIMER.... If you screw up your disks don't blame me. If you have any questions about this you can email me: [email protected]
The procedure is basically this:
- compile kfed
- dump the disk header with kfed
- Modify the dump file
- write the dump back to the disk header.
** Changing ANYTHING other than the diskgroup name will render your disks useless.
Here is a script to do the work for you:
for file in `ls /dev/vx/rdsk/as1_pccdw/asmdata*`
do
echo "Processing DATA disk $file ..."
search=ASCDW_DATA
replace=AS1CDW_DATA
newlength=`echo $replace | wc -m`
let newlength=$newlength-1
shortname=`echo $file | cut -f 6 -d /`
kfed op=read dev=$file | sed -e '24,24s/ '$search' / '$replace' /' -e '24,24s/length=.*/length='$newlength'/' > /tmp/$shortname.kfed
kfed op=write dev=$file text=/tmp/$shortname.kfed CHKSUM=YES
done
for file in `ls /dev/vx/rdsk/as1_pccdw/asmredo*`
do
echo "Processing REDO disk $file ..."
search=ASCDW_REDO
replace=AS1CDW_REDO
newlength=`echo $replace | wc -m`
let newlength=$newlength-1
shortname=`echo $file | cut -f 6 -d /`
kfed op=read dev=$file | sed -e '24,24s/ '$search' / '$replace' /' -e '24,24s/length=.*/length='$newlength'/' > /tmp/$shortname.kfed
kfed op=write dev=$file text=/tmp/$shortname.kfed CHKSUM=YES
done
Edited by: user4630111 on Nov 10, 2008 6:03 PM

ASM disk group and multiple databases

Hi,
I want to create a second database on my RAC cluster. Can the ASM diskgroups I have defined for use with the first database , service the second database or do I have to create another set of ASM diskgroups for the second dataabase?
Thanks,
Anne

ASM does not have any data files. ASM will store data files required for the RDBMS instance only.
After you have installed the Oracle binaries, (best practice is to have two Oracle homes one for ASM and another for RDBMS), you can create the ASM instances using DBCA and during this process or later can create ASM diskgroups.
( e,g disk1G, disk2G,disk3G,disk4G) using the above four you can create ASM DISK GROUPS..

App-v 5.0: howto mount and dismount via powershell (just for testing purposes)

Hi,
Please advise howto easily mount an App-v package and full remove it afterwards (when ok).
This only to test the package is ok on a machine without the need to put it into sccm or a management server.
J.
Jan Hoedt

Hi,
this article is a must have to read abour PoSh cmdlets and App-V5.
If you want to test you can:
Get-AppvClientPackage | Mount-AppvClientPackage
This command, gets all your published App-V packages and mount them to 100%.
If you want to remove a package which is published to you, you can use:
Get-AppvClientPackage -name *yourpackage* | Stop-AppvClientPackage | Repair-AppvClientPackage | Unpublish-AppvClientPackage | Remove-AppvClientPackage
to remove it. I alsways stop, and repair it first, so I'm sure all user changes are removed also.
Keep in mind, the remove-cmdlet need elevated rights.

Difference between ASM Disk Group, ADVM Volume and ACFS File system

Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
An 11gR2 ASM Disk Group can contain :
ASM Disks
ADVM volumes
ACFS file systems
Q2. ADVM volumes appear to be dynamic volumes.
However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
Can you create / modify ACFS file systems using ASM.
The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
through ASM ?
through native OS file system creation ?
through OEM ?
through acfsutil ?
my head is exploding
Any help and clarification greatly appreciated
Jim

Q1 - ADVM volume is a type of special file created in the ASM DG. Once created, it creates a block device on the OS itself that can be used just like any other block device. http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
Q2 - the asm disk group is a disk group, not really a logical volume. It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol. However, you won't find any general purpose applications that can do so. In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do. In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics. This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications. It understands the database performance characteristics and is tuned to work well in that situation. Because it is developed in house, it takes advantage of the ASM design model. Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
Q4 - You can create and modify ACFS file systems using command line tools and ASMCA. Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA. EM can also be used for both items. ACFS sits on top of ADVM, which is a file in an ASM disk group. ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics.
Q5 - several ways:
1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out. This creates an ADVM volume. Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
2) Use ASMCA - A gui to create a volume and format a file system. Probably the easiest if your head is exploding.
3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
Here is information on ASMCA, with examples:
http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
Information on command line tools, with examples:
Basic Steps to Manage Oracle ACFS Systems

TrueCrypt - Mounting and writing to a hidden volume in Leopard

I realize the answer to this question may be pretty obvious to some, but I've read the TrueCrypt user manual, and I've searched these forums, TrueCrypt's forums, and google for the answer to my question but I still can't figure this out...
I've created an encrypted file container with a hidden volume using the setup wizard. After completing the wizard, I can't figure out how to properly write data to the hidden volume. The TrueCrypt manual says,
"When hidden volume protection is enabled, TrueCrypt does not actually mount the hidden volume. It only decrypts its header (in RAM) and retrieves information about the size of the hidden volume (from the decrypted header). Then, the outer volume is mounted and any attempt to save data to the area of the hidden volume will be rejected (until the outer volume is dismounted)."
If TrueCrypt doesn't actually mount the hidden volume, and if and any attempt to save data to the area of the hidden volume will be rejected, then can someone please explain to me in layman's terms how the heck I am supposed to go about saving my sensitive files to the hidden volume?
Thanks!
http://www.truecrypt.org/

No offense, but I could never get it to work reliably for me. I admit I have not used it for almost a
year (since 10.5.x). It would work acceptably at times, but other times it would be slow as molasses
(copying files) or Finder would be lock up. Sometimes when copying from NTFS volumes OS X would
lock up tight and the only way out was to cut the power. I noticed the problems would surface
mostly when some other Mac Fuse dependent programs were being run at the same time (such
as Parallels Desktop).
To be fair though, I suspect the Apple 10.5.x Hard disk driver (for my machine) as being partly to
blame as most of the external disk mounting and lockup problems disappeared when I upgraded
to Snow Leopard.
I suspect Mac Fuse also. I have had various versions of Mac Fuse that didn't work well on my
machine either. When I first put Snow Leopard on my machine I had to use Tomas Carnecky's
compiled version of MacFuse 2.1.7. to get True Crypt working. Now they updated True Crypt and
I have had to use the new Public 2.1.5 Beta version of Mac Fuse to get the updated True Crypt
working.
Being a software developer I am sure you are aware of the endless problems various hardware
combinations and configurations can dish out. No offense, but I had to switch to Paragon NTFS
to be able to get a solution that worked reliably on my machine.
Some folks use your NTFS-3G product without any problems whatsoever, but like I said,
different hardware combos yield different results.
I have not tried Tuxera, actually I had not even heard of it until a couple of days ago.
The name is cute, how (if you don't mind telling) or who, came up with the label?
Linus Torvolds and that familiar Penguin comes to mind when I here the name.
It's not because NTFS-3G is free, that I don't use it.
I am a die hard "free" fan, I love "free", as in free lunch, free software, free money and of course
free BEER!
Kj ♘

Add ASM disk in RAC

Hello everyone,
We are on 10gR2 ASM.
The system admin has provided one disk as follows:
On node-1 (tphsmsd1)
/dev/rdisk/disk83 CANDIDATE
On node-2 (tphsmsd2)
/dev/rdisk/disk77 CANDIDATE
I've read that paths of ASM disks in RAC may be different.
When I give "ls -l /dev/rdisk/disk83" gives no such files and vice-versa for disk on node2.
I don't understand how ASM handles this ? If I add disk (disk83) on node 1 how it's going to get to that disk on node 2 ?
thanks
Jitu Keshwani

Jitu Keshwani wrote:
I've read that paths of ASM disks in RAC may be different.
When I give "ls -l /dev/rdisk/disk83" gives no such files and vice-versa for disk on node2.
I don't understand how ASM handles this ? If I add disk (disk83) on node 1 how it's going to get to that disk on node 2 ?The header label of the disk, identifies the ASM disk name and diskgroup it belongs to. You can hexdump or octaldump the 1st 128 bytes of the device as ascii chars to view the label. The string "+ORCLDISK+" in the header identifies it as an ASM disk. This is then followed by the ASM diskname and then the AM diskgroup it belongs to.
But there's no reason for not having a consistent and static device name layer across all cluster nodes. Each scsi device has a WWID (World Wide ID)- a unique identifier. This means that the kernel (and kernel drivers) can uniquely identify a device.
On Linux, Multipath is used to map a logical device name to a WWID - and using the same +/etc/multipath.conf+ configuration file on all cluster nodes, ensures that the same device names are used across the cluster.
But from the the device file entry you listed, you're likely not running Linux? In that case, depending on the Unix flavour used and the type of cluster storage, there can be similar options to Linux's Multipath. One such option is EMC's PowerPath - but that of course is specific to EMC SANs and requires additional licensing fees.

ASM disk shows different Readings

Our env is 3 node rac with ASM and 6 Standby Databases on it.
I am Missing around 1.5 TB for FRA disk on ASM
ASM disk FRA shows :
ASMCMD> du FRA/
Used_MB      Mirror_used_MB
240646              240646
Standby database shows the usage of ASM Disk Group and it says 3 % is left on FRA
SQL> SELECT name, free_mb, total_mb, free_mb/total_mb*100 as percentage FROM v$asm_diskgroup;
NAME                              FREE_MB   TOTAL_MB PERCENTAGE
DATA                              1741308    2047972 85.0259672
FRA                                 76433    2047972 3.7321311
FUNDATA                           1023841    1023986 99.9858397
FUNFRA                             958964    1023986 93.6501085
OCR                                  1631       2038 80.0294406
VOTE                                 2550       3057 83.4151129
Can anyone Guide me on this please.

Hi,
Check the redundancy of your disk groups Doc: ORACLE-BASE - Automatic Storage Management (ASM) in Oracle Database 10g
NORMAL REDUNDANCY - Two-way mirroring, requiring two failure groups.
HIGH REDUNDANCY - Three-way mirroring, requiring three failure groups.
EXTERNAL REDUNDANCY - No mirroring for disks that are already protected using hardware mirroring or RAID. If you have hardware RAID it should be used in preference to ASM redundancy, so this will be the standard option for most installations
HTH

Oracleasm listdisks is not listing all disk groups and returning "strange special characters" and disks groups are dismounting unexpected

Hi everybody,
I have a 3 node Oracle Cluster with verstion 11.2.0.3.0 installed using ASM/ACFS/ADVM.
Red Hat 5.7 - Kernel 2.6.18-371.12.1.el5 64bits
OracleASM version:
     oracleasm-support-2.1.8-1.el5
     oracleasm-2.6.18-371.12.1.el5-2.0.5-1.el5
     oracleasmlib-2.0.4-1.el5
On may, 2014 we had a physical failure in our storage system and all our disk partitions were completely lost.
The Oracle Grid Infrastructure and Oracle RDBMS haven't needed to be reinstalled because they were healthy.
The Oracle Cluster Registry (OCR) was lost (it was composed by three ASM disk groups in a redundant structure) and after recreation of the OCR disk groups I recover the Oracle Registry information from backup.
All cluster information were recovered (listener, SCAN, VIP, databases and services)
Databases could not be started because all ASM disk groups have been lost and oracle ASM instance (asmcmd -p) was showing all disk groups, but they were all "empty" - the physical partition related with them were recreated.
All the "old" disk groups were dropped, and the "new" disk groups were recreated and all the backups from the databases were restored.
After all services were up, and the environment seems to be OK, I check the healthiness of it, by executing the oracle cluster post-installation tool and others verify tools (crsctl and srvctl), well all returning messages saying that the environment was completely OK and no errors were found or generated (including in many log files I have inspected)
After 2 weeks from the completely recover of the environment, without any error/failure message been received from it, the disk groups started to dismount unexpectedly, from whatever node and not only one specific disk group stops, but any one of them, any time.
I opened a SR in Metalink (Oracle Support) and they conduct me to upgrade RedHat kernel version and OracleASM version.
Simultaneously I opened a Case Solution in RedHat to help me identify the better way to do the upgrade in advantage of the Oracle specifications.
From:
rpm -qa | grep kernel
kernel-devel-2.6.18-274.el5
kernel-headers-2.6.18-274.el5
kernel-2.6.18-274.el5
rpm -qa | grep oracleasm
oracleasm-support-2.1.8-1.el5
oracleasmlib-2.0.4-1.el5
oracleasm-2.6.18-274.el5-2.0.5-1.el5
To:
rpm -qa | grep kernel
kernel-devel-2.6.18-371.12.1.el5
kernel-2.6.18-371.12.1.el5
kernel-headers-2.6.18-371.12.1.el5
rpm -qa | grep oracleasm
oracleasm-support-2.1.8-1.el5
oracleasm-2.6.18-371.12.1.el5-2.0.5-1.el5
oracleasmlib-2.0.4-1.el5
Well, after this upgrade less times the disk groups dismounted, but they continue dismounting from whatever node, any disk group, any time.
So, I opened another SR in Metalink (3-10143566371 still open) and they are conducting me again to upgrade the RedHat kernel version and OracleASM version.
Information about OracleASM:
# oracleasm listdisks
ACFS
FRA
OCR01
OCR02
OCR03
$ asmcmd -p
ASMCMD [+] > ls -l
State    Type    Rebal Name
MOUNTED EXTERN N      ACFS/
MOUNTED EXTERN N      ARCH/
MOUNTED EXTERN N      DEV/
MOUNTED EXTERN N      DIR_LOG/
MOUNTED EXTERN N      JAVA_ARCHIVE/
MOUNTED EXTERN N      MSAF/
MOUNTED NORMAL N      OCR/
MOUNTED EXTERN N      PRD_DATA/
MOUNTED EXTERN N      PRD_REDO1/
MOUNTED EXTERN N      PRD_REDO2/
MOUNTED EXTERN N      PRD_REDO3/
MOUNTED EXTERN N      PRD_REDO4/
MOUNTED EXTERN N      RASTR/
MOUNTED EXTERN N      STAGE/
This is what happens when execute "oracleasm scandisks":
# oracleasm scandisks
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...
Instantiating disk "ùìÿÿÿÿÿÿÿÿÿÿÿìóæþÿ¥Ï¨®Ð¢"
Unable to instantiate disk "ùìÿÿÿÿÿÿÿÿÿÿÿìóæþÿ¥Ï¨®Ð¢"
Instantiating disk "ü´ñõ
                        ñõúìsö"
Unable to instantiate disk "ü´ñõ
                                ñõúìsö"
~±Ã1~u·}cÿ-Ûg disk "
¾s
~±Ã1~u·}cÿ-Ûinstantiate disk "
¾s
Instantiating disk "à·Öªß³Ö½Þ®hìëÖßßÞÖÛÜØÖÕ"
Unable to instantiate disk "à·Öªß³Ö½Þ®hìëÖßßÞÖÛÜØÖÕ"
Instantiating disk "êËbkî,c
~,XZ±´b¹u²´biÅr"
Unable to instantiate disk "êËbkî,c
~,XZ±´b¹u²´biÅr"
Instantiating disk "
PuTTYPuTTYUnable to instantiate disk "
kÍ3|úùõ/øÊInstantiating disk "u
i)ïìL"
kÍ3|úùõ/øÊe to instantiate disk "u
My question is: "This will really solve the problem?"
Another: "Oracle really understood what is happening and they can help me to solve this problem?"
Final: "Can anyone please help me this problem?"

Hi,
my two cent.
Wait for the SR feedback.
But for the future I advice you to do an ASM Metadata backup to be able to restore this data if you lost
configurations or complete disks and so on.
asmcmd md_backup -b <Pfad>/Filename
and also an ocrconfig backup via crontab.
ocrconfig -local -manualbackup
regards

How reInstall Gride Infrastructure and Use old ASM disk groups

<pre>Hello to all
I installed Grig Infrastructure 11gR2 on a standalone server (OS is Linux)
and I configured ASM and my database created on ASM
Conceive that my OS disk corrupted and OS doesn't start and the Gride Home is on that disk,
and I have to install OS again
My ASM disks are safe , Now how can I install Grig Infrastructure again somehow that it can use previous ASM disks
and disk groups and I don't oblige to create my database again ?
In the step 2 of installing Gride Infrastructure it has four options
<pre>
1.Install and configure Oracle Grid Infrastructure for a Cluster
2.Configure Oracle Grid Infrastructure for a Standalone Server
3.Upgrade Oracle Gride Infrastructure or Oracle Automatice Storage Management
4.Install Oracle Gride Infrastructure Software Only
</pre>
If I select the option 2 it wants to create a disk group again
I guess that I need to select option 4 and then do some configuration but I don't know what I must configure
Do you know answer of my question , if yes please explain it's stages
Thank you so much
</pre>

Hi,
no you are not obliged to recreate your database again. However there is a small flaw in the installation procedure, which does not make it 100% easy...
When you installed the Oracle Restart (Standalone GI), your ASM diskgroup will contain the SPFILE of the ASM instance. And this is exactly the small flaw you will be encountering. So you have 2 options for "recovery":
1.) Do a software only install (4), and run roothas.pl. This however will not create any ASM entries. You would have to add it manually (using srvctl) and you can specify the ASM Spfile with the srvctl command. Problem here is however to have to know where your ASM spfile has been. If you have a backup of your OLR and a backup of the GPNP profile, this might be easier to find out.
2.) Do a new installation (2) and configure a new diskgroup (with a "spare" disk or small lun and a new name), that Oracle restart creates ASM instance and the new ASMSpfile for you.
Then you can simply mount the diskgroup containing your database additionally. You then shoudl however move your new ASMSpfile to the new diskgroup (or simply exchange it with the existing one). In this case it is easier to find out where it was - however you will need a spare (though small) LUN for the new spfile (temporarily, until you exchange it).
In either case after you have your ASM instance back (and access to your old diskgroup), you have to reregister your database and services - if you do not have an OLR backup.
Again => It is doable and you can simply mount the ASM diskgroup containing your database. However I suggest you try this one time to know what really needs to be done in this case.
Regards
Sebastian

ASM Disk preparation for Datafiles and FRA in Oracle 10g RAC Inst

Dear Friends,
Please clarify wheteher the below method is correct to confiure ASM disks for Datafiles and FRA
Partitions provided by IT team for OCR and Voting Disk
/dev/sda1 - 150 GB (For +DATA)
/dev/sda2 - 100 GB (For +FRA)
OS : RHEL 5.6 (64 Bit)
kernel version = 2.6.18-238.el5
Steps:(Node1)
1) Install the RPM's for ASM
rpm -Uvh oracleasm-support-2.1.7-1.el5.x86_64.rpm
rpm -Uvh oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
rpm -Uvh oracleasmlib-2.0.4-1.el5.x86_64.rpm
2) Configure ASM
/etc/init.d/oracleasm configure
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
3) Cretae ASM Disk
/etc/init.d/oracleasm createdisk DISK1 /dev/sda1
/etc/init.d/oracleasm createdisk DISK2 /dev/sda2
4)/etc/init.d/oracleasm status
5)/etc/init.d/oracleasm scandisks
6)/etc/init.d/oracleasm listdisks
7) Nothing to perform on Node2
8) In dbca choose ASM and map the DISK1 for datafiles and DISK2 for FRA
Please confirm the above steps are right?if not please clarify
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?
Please refer any document / Metalink ID for the above complete process
Can i have ASM and oracle DB binary in the same home
Regards,
DB

user564706 wrote:
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?for asm disk created with oracleasm discovery path variable is ORCL:*
Please refer any document / Metalink ID for the above complete processhttp://docs.oracle.com/cd/B19306_01/install.102/b14203/storage.htm#BABIFHAB
Can i have ASM and oracle DB binary in the same homeyes. unless you want job role seperation or plan to run multiple versions of oracle homes
>
Regards,
DB

Disk Images will not mount and Disk Utility will not runru

I am having some major problems with Disk Utility, Disk Images, and software update. First, Disk utility will not open or run. When I double-click the application icon, nothing happens, no message, nothing. I am running OSX 10.4.11. I have deleted diskutility prefs. I am able to run Disk Utility from the Startup DVD of Tiger. On first run, it verified and repaired permissions. I run verify and repair permissions several more times from Startup DVD and everything is fine. But Disk Utility on my startup HD will not work. Similary, NONE of my disk images will mount. No matter what Disk Image i try to mount, nothing will. And I cannot use Disk utility to mount them! So, no matter what I download, no images will mount. And thirdly, when I try to run software update, it will not work. I do get a message: it says, "Could not load Software Update." Finally, i tried to download Onyx to delete log files, etc.. but again, the disk image will not mount. I was able to install a dashboard widget called "maintidget" and was successful in running the daily, weekly, and monthly maintenance tasks. Can anyone help? Everything else works fine!!! All apps! Safari, Mail, iTunes, MS Office, everything works fine. Thanks for ANY help!

Previously, I had run verify permissions, repair permissions multiple times(from startup DVD) - no probems found. Deleted disk utility prefs. Run the maintenance taskes (daily, weekly, monthly). Nothing worked. But, I forget to check the drive for problems. So I ran disk scan. It found "invalid node" and repair disk could not do it. So, do I erase and do a fresh install or get DiskWarrior? I am running Leopard so I do not have Time Machine but I have backed up my documents, iTunes Library, iPhoto Library, etc... Another thing I found out the hardway is to sync all your bookmarks, mail settings and messages, etc... with .mac if you have an account. Any more suggetions?

ASM disk mount and dismount !

Similar Messages

Maybe you are looking for