Alter diagnostic_dest to ASM

Hi
I have the following ASM-Volumgroups on REDHAT 5.4/Oracle 11.2.0.2/X86.64:
/home/grid>asmcmd
ASMCMD> ls
CRS/
DATA/
FLASH/
The database STRM has its Data on +DATA
ASMCMD> ls -l +DATA/STRM
Type Redund Striped Time Sys Name
Y CONTROLFILE/
Y DATAFILE/
Y ONLINELOG/
Y PARAMETERFILE/
Y TEMPFILE/
N spfileSTRM.ora => +DATA/STRM/PARAMETERFILE/spfile.259.743361239
ASMCMD>
and tried to change the Parameter diagnostic_dest in init.ora.
But I got always the following error:
SQL> startup;
ORA-48108: invalid value given for the diagnostic_dest init.ora parameter
ORA-48140: the specified ADR Base directory does not exist [+DATA]
ORA-48187: specified directory does not exist
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
SQL>
Can any expert helps?
Thanks
hqt200475

Hi Werner,
You are right!
Here is a Note in http://download.oracle.com/docs/cd/E11882_01/server.112/e16102/asmfiles.htm#i1023250
*"Oracle ASM cannot directly support some administrative file types on disk groups. These include trace files, audit files, alert logs, export files, tar files, and core files."*
Thanks & regards
hqt200475
Edited by: hqt200475 on 22.02.2011 02:09

Similar Messages

Enabling ASM fast resync - backout considerations.

Hi,
I've just completed some testing in a sandpit environment of the ASM fast resync functionality. This was done by ensuring all databases using by the ASM instance had their 'compatible' setting at 11.1 and then altering the compatible.asm and compatible.rdbms parameters for each of the ASM groups. eg
ALTER DISKGROUP TESTDATA SET ATTRIBUTE 'compatible.asm' = '11.1';
ALTER DISKGROUP TESTFRA SET ATTRIBUTE 'compatible.rdbms' = '11.1';
All seemed to work ok, and during a test, in which I chmodded a candidate disk, asm took it offline, and then the countdown timers started , after which I fixed the problem, brought it online, and ASM performed the fast resync.
I'm about to roll this change out to our dev cluster, and wondered if anybody had any ideas for a backout plan, or if there were any potential problems that I might come across that would necessitate a back out. It seems that when you make this change, it cannot be undone, so I want to make sure I don't get any nasty surprises.
Thanks

Hi,
unfortunately this parameter can only be increased (not decreased), so the only fallback method is a restore. So make sure you have actual RMAN backups.
Because you need to recreate the diskgroups and to the restore the databases...
Before activating it, make sure you don't run any 10g databases on these diskgroups!
However I don't know of any issues (expect still having 10g databases) which would require a "downgrade" ....
Regards
Sebastian

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

Please Help - When I try to add ASM Disk to ASM Diskgroup it crashes Server

We are using a Pillar SAN and have LUNS Created and are using the following multipath device: (I'm a DBA more then anything else... but I am rather familiar with linux .... SAN Hardware not so much)
Device Size Mount Point
/dev/dpda1 11G /u01
The Above device is working fine... Below are the ASM Disks being Created
Device Size Oracle ASM Disk Name
/dev/dpdb1 198G ORCL1
/dev/dpdc1 21G SIRE1
/dev/dpdd1 21G CART1
/dev/dpde1 21G SRTS1
/dev/dpdf1 21G CRTT1
I try to create to the first ASM Disk
/etc/init.d/oracleasm createdisk ORCL1 /dev/dpdb1
Marking disk "ORCL1" as an ASM disk: [FAILED]
So I check the oracleasm log:
#cat /var/log/oracleasm
Device "/dev/dpdb1" is not a partition
I did some research and found that this is a common problem with multipath devices and to work around it you have to use asmtool
# /usr/sbin/asmtool -C -l /dev/oracleasm -n ORCL1 -s /dev/dpdb1 -a force=yes
asmtool: Device "/dev/dpdb1" is not a partition
asmtool: Continuing anyway
now I scan and list the disks
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
# /etc/init.d/oracleasm listdisks
ORCL1
Here is whats going on in /var/log/messages when I run the oracleasm scandisks command
# date
Fri Aug 14 13:51:58 MST 2009
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
cat /var/log/messages | grep "Aug 14 13:5"
Aug 14 13:52:06 seer kernel: dpdb: dpdb1
Aug 14 13:52:06 seer kernel: dpdc: dpdc1
Aug 14 13:52:06 seer kernel: dpdd: dpdd1
Aug 14 13:52:06 seer kernel: dpde: dpde1
Aug 14 13:52:06 seer kernel: dpdf: dpdf1
Aug 14 13:52:06 seer kernel: dpdg: dpdg1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: printk: 30 messages suppressed.
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: sda : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sda : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: Dev sda: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdb: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdb: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdb: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdb: sdb1
Aug 14 13:52:06 seer kernel: SCSI device sdc: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdc: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdc: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdc: sdc1
Aug 14 13:52:06 seer kernel: SCSI device sdd: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdd: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdd: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdd: sdd1
Aug 14 13:52:06 seer kernel: SCSI device sde: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sde: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sde: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sde: sde1
Aug 14 13:52:06 seer kernel: SCSI device sdf: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdf: sdf1
Aug 14 13:52:06 seer kernel: SCSI device sdg: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdg: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdg: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdg: sdg1
Aug 14 13:52:06 seer kernel: SCSI device sdh: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdh: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdh: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdh: sdh1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sdi, logical block 0
Aug 14 13:52:06 seer kernel: sdi : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdi : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdi: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdi: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdi: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdi:end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer last message repeated 4 times
Aug 14 13:52:06 seer kernel: Dev sdi: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdj: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdj: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdj: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdj: sdj1
Aug 14 13:52:06 seer kernel: SCSI device sdk: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdk: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdk: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdk: sdk1
Aug 14 13:52:06 seer kernel: SCSI device sdl: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdl: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdl: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdl: sdl1
Aug 14 13:52:06 seer kernel: SCSI device sdm: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdm: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdm: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdm: sdm1
Aug 14 13:52:06 seer kernel: SCSI device sdn: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdn: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdn: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdn: sdn1
Aug 14 13:52:06 seer kernel: SCSI device sdo: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdo: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdo: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdo: sdo1
Aug 14 13:52:06 seer kernel: SCSI device sdp: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdp: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdp: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdp: sdp1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: sdq : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdq : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdq: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdq: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdq: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdq:end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdq: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdr: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdr: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdr: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdr: sdr1
Aug 14 13:52:06 seer kernel: SCSI device sds: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sds: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sds: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sds: sds1
Aug 14 13:52:06 seer kernel: SCSI device sdt: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdt: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdt: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdt: sdt1
Aug 14 13:52:06 seer kernel: SCSI device sdu: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdu: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdu: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdu: sdu1
Aug 14 13:52:06 seer kernel: SCSI device sdv: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdv: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdv: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdv: sdv1
Aug 14 13:52:06 seer kernel: SCSI device sdw: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdw: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdw: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdw: sdw1
Aug 14 13:52:06 seer kernel: SCSI device sdx: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdx: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdx: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdx: sdx1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: sdy : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdy : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdy: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdy: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdy: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdy:end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdy: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdz: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdz: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdz: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdz: sdz1
Aug 14 13:52:06 seer kernel: SCSI device sdaa: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdaa: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaa: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaa: sdaa1
Aug 14 13:52:06 seer kernel: SCSI device sdab: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdab: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdab: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdab: sdab1
Aug 14 13:52:06 seer kernel: SCSI device sdac: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdac: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdac: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdac: sdac1
Aug 14 13:52:06 seer kernel: SCSI device sdad: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdad: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdad: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdad: sdad1
Aug 14 13:52:06 seer kernel: SCSI device sdae: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdae: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdae: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdae: sdae1
Aug 14 13:52:06 seer kernel: SCSI device sdaf: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdaf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaf: sdaf1
Aug 14 13:52:06 seer kernel: scsi_wr_disk: unknown partition table
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdy, sector 0
Here's some extra info:
# /sbin/blkid | grep asm
/dev/sdc1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdk1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sds1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdaa1: LABEL="ORCL1" TYPE="oracleasm"
/dev/dpdb1: LABEL="ORCL1" TYPE="oracleasm"
I have learned that by excluding devices in the oracleasm configuration file I eliminate those I/O errors in /var/log/messages
# cat /etc/sysconfig/oracleasm
# 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=oinstall
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dp sd"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sdc sdk sds sdaa sda"
# ls -la /dev/oracleasm/disks/
total 0
drwxr-xr-x 1 root root 0 Aug 14 10:47 .
drwxr-xr-x 4 root root 0 Aug 13 15:32 ..
brw-rw---- 1 oracle oinstall 251, 33 Aug 14 13:46 ORCL1
Now I can go into dbca to create the ASM instance, which starts up fine... create a new diskgroup, I see ORCL1 as a provision ASM disk I select it ... Click OK
CRASH!!! Box hangs have to reboot it....
I have gotten myself to exactly the same point right before clicking OK and here is what is in the ASM alertlog so far
Fri Aug 14 14:42:02 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.1.0/db_1/dbs/spfile+ASM.ora
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
diagnostic_dest = "/u01/app/oracle"
Fri Aug 14 14:42:04 2009
PMON started with pid=2, OS id=3300
Fri Aug 14 14:42:04 2009
VKTM started with pid=3, OS id=3302 at elevated priority
VKTM running at (20)ms precision
Fri Aug 14 14:42:04 2009
DIAG started with pid=4, OS id=3306
Fri Aug 14 14:42:04 2009
PSP0 started with pid=5, OS id=3308
Fri Aug 14 14:42:04 2009
DSKM started with pid=6, OS id=3310
Fri Aug 14 14:42:04 2009
DIA0 started with pid=7, OS id=3312
Fri Aug 14 14:42:04 2009
MMAN started with pid=8, OS id=3314
Fri Aug 14 14:42:04 2009
DBW0 started with pid=9, OS id=3316
Fri Aug 14 14:42:04 2009
LGWR started with pid=6, OS id=3318
Fri Aug 14 14:42:04 2009
CKPT started with pid=10, OS id=3320
Fri Aug 14 14:42:04 2009
SMON started with pid=11, OS id=3322
Fri Aug 14 14:42:04 2009
RBAL started with pid=12, OS id=3324
Fri Aug 14 14:42:04 2009
GMON started with pid=13, OS id=3326
ORACLE_BASE from environment = /u01/app/oracle
Fri Aug 14 14:42:04 2009
SQL> ALTER DISKGROUP ALL MOUNT
Fri Aug 14 14:42:41 2009
At this point I don't want to click the OK until I am sure someone is in the office to reboot the machine manually if I do hang it again.... I hung it twice yesterday, however I did not have the devices excluded in the oracleasm configuration file as i do now
Edited by: user10193377 on Aug 14, 2009 3:23 PM
Well Clicking OK hun it again and I am waiting to get back into it, to see what new information might be gleened
Does anyone have any ideas on what to check or where to look????? Will update more once I can log back in

Hi Mark,
It looks like something is not correct with your raw device partition based on the error messages:
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
It could be a number of things. I would check with your vendor and Oracle support to see if the multipath software drive is supported and if there is a potential workaround for ASM. Sorry this is not quite the solution, but its what jumps to mind based on issues with multipath software and storage vendors for ASM with Linux and Oracle. Have you checked the validation matrix available on Metalink?
Cheers,
Ben

Standby database errors - Alter database open read only

alter database open read only
AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
Signalling error 1152 for datafile 1!
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 216
Mon Dec 20 11:58:18 2010
Standby crash recovery need archive log for thread 1 sequence 216 to continue.
Please verify that primary database is transporting redo logs to the standby database.
Wait timeout: thread 1 sequence 216
Standby crash recovery aborted due to error 16016.
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!
Completed standby crash recovery.
Signalling error 1152 for datafile 1!
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
ORA-10458 signalled during: alter database open read only...
Mon Dec 20 12:13:46 2010
ALTER DATABASE RECOVER managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (MDM2)
Mon Dec 20 12:13:46 2010
MRP0 started with pid=23, OS id=18974
MRP0: Background Managed Standby Recovery process started (MDM2)
started logmerger process
Mon Dec 20 12:13:51 2010
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 216
Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
The above lines are from alert log of standby database.
Standby standbase
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
Parameters set on primary are
log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
log_archive_dest_state_1 ENABLE
log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
log_archive_dest_state_2 ENABLE
dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
fal_server MDM2
standby_file_management AUTO
log_archive_config dg_config=(MDM1,MDM2)
db_file_name_convert MDM2, MDM1
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
Standby pfile
*.archive_lag_target=900
*.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
*.db_block_size=8192
*.db_create_file_dest='+MDMDG1'
*.db_domain=''
*.db_file_name_convert='MDM1','MDM2'
*.db_name='MDM'
*.db_recovery_file_dest='+MDMDG2'
*.db_recovery_file_dest_size=10485760000
*.db_unique_name='MDM2'
*.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
*.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
*.fal_server='MDM11','MDM12'
*.instance_name='MDM2'
*.log_archive_config='dg_config=(MDM1,MDM2)'
*.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
*.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='MDM_%t_%s_%r.arc'
*.log_file_name_convert='MDM1','MDM2'
*.memory_target=838860800
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.processes=500
*.remote_login_passwordfile='exclusive'
*.sessions=555
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
On standby ASM
ASMCMD [+] > find * *
+MDMDG1/ASM/
+MDMDG1/ASM/ASMPARAMETERFILE/
+MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
+MDMDG1/MDM/
+MDMDG1/MDM2/
+MDMDG1/MDM2/CONTROLFILE/
+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
+MDMDG1/MDM2/CONTROLFILE/current.265.738243333
+MDMDG1/MDM2/DATAFILE/
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
+MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
+MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
+MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
+MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
+MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
+MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
+MDMDG1/MDM2/DATAFILE/USERS.278.738243347
+MDMDG1/MDM2/ONLINELOG/
+MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
+MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
+MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
+MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
+MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
+MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
+MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
+MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
+MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
+MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
+MDMDG2/MDM/
+MDMDG2/MDM/DG_CONFIG/
+MDMDG2/MDM2/
+MDMDG2/MDM2/AUTOBACKUP/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
+MDMDG2/MDM2/CONTROLFILE/
+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
+MDMDG2/MDM2/CONTROLFILE/current.271.738243335
+MDMDG2/MDM2/ONLINELOG/
+MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
+MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
+MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
+MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
+MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
+MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
+MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
+MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
+MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
+MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
+MDMDG3/MDM/
+MDMDG3/MDM/ARCH/
+MDMDG3/MDM2/
+MDMDG3/MDM2/ARCH/
-- Please can I know how to open read only standby database.

user5846399 wrote:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!archived log for thread 1 sequence# 216
This file is needed for recovery, Find it and move it to the standby database side.

RAC and ASM issue

Hi All,
i am getting an error message in asm_alert log file saying "NOTE: ASMB process exiting due to lack of ASM file activity".
This leads to frequent crashing of NODE 1. Please check below detail error and suggest solution.
Thu Mar 24 07:05:11 2011
LMD0 (ospid: 32493) has not called a wait for 94 secs.
GES: System Load is HIGH.
GES: Current load is 55.87 and high load threshold is 20.00
Thu Mar 24 07:06:32 2011
LMD0 (ospid: 32493) has not called a wait for 174 secs.
GES: System Load is HIGH.
GES: Current load is 71.23 and high load threshold is 20.00
Thu Mar 24 07:06:36 2011
+Trace dumping is performing id=[cdmp_20110324070635]+
Thu Mar 24 07:07:49 2011
+Trace dumping is performing id=[cdmp_20110324070635]+
Thu Mar 24 07:08:16 2011
Waiting for clusterware split-brain resolution
Thu Mar 24 07:18:17 2011
Errors in file /u01/app/oracle/diag/asm/asm/+ASM1/trace/+ASM1_lmon_32484.trc (incident=60073):+
ORA-29740: evicted by member 1, group incarnation 120
Incident details in: /u01/app/oracle/diag/asm/asm/+ASM1/incident/incdir_60073/+ASM1_lmon_32484_i60073.trc+
Thu Mar 24 07:18:19 2011
+Trace dumping is performing id=[cdmp_20110324071819]+
Errors in file /u01/app/oracle/diag/asm/asm/+ASM1/trace/+ASM1_lmon_32484.trc:+
ORA-29740: evicted by member 1, group incarnation 120
LMON (ospid: 32484): terminating the instance due to error 29740
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/diag/asm/asm/+ASM1/trace/+ASM1_diag_32459.trc+
+Trace dumping is performing id=[cdmp_20110324071820]+
Instance terminated by LMON, pid = 32484
Thu Mar 24 07:18:31 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 172.20.223.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 172.20.222.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/asm_1/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side pfile /u01/app/oracle/product/11.1.0/asm_1/dbs/initASM1.ora+
System parameters with non-default values:
large_pool_size          = 12M
instance_type            = "asm"
cluster_database         = TRUE
instance_number          = 1
asm_diskstring           = "ORCL:*"
asm_diskgroups           = "REDO01"
asm_diskgroups           = "REDO02"
asm_diskgroups           = "DATA"
asm_diskgroups           = "RECOVERY"
diagnostic_dest          = "/u01/app/oracle"
Cluster communication is configured to use the following interface(s) for this instance
+172.20.223.25+
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Thu Mar 24 07:18:36 2011
PMON started with pid=2, OS id=23120
Thu Mar 24 07:18:36 2011
VKTM started with pid=3, OS id=23123 at elevated priority
VKTM running at (20)ms precision
Thu Mar 24 07:18:36 2011
DIAG started with pid=4, OS id=23127
Thu Mar 24 07:18:37 2011
PING started with pid=5, OS id=23129
Thu Mar 24 07:18:37 2011
PSP0 started with pid=6, OS id=23131
Thu Mar 24 07:18:37 2011
DIA0 started with pid=7, OS id=23133
Thu Mar 24 07:18:37 2011
LMON started with pid=8, OS id=23135
Thu Mar 24 07:18:37 2011
LMD0 started with pid=9, OS id=23137
Thu Mar 24 07:18:37 2011
LMS0 started with pid=10, OS id=23148 at elevated priority
Thu Mar 24 07:18:37 2011
MMAN started with pid=11, OS id=23152
Thu Mar 24 07:18:38 2011
DBW0 started with pid=12, OS id=23170
Thu Mar 24 07:18:38 2011
LGWR started with pid=13, OS id=23176
Thu Mar 24 07:18:38 2011
CKPT started with pid=14, OS id=23218
Thu Mar 24 07:18:38 2011
SMON started with pid=15, OS id=23224
Thu Mar 24 07:18:38 2011
RBAL started with pid=16, OS id=23237
Thu Mar 24 07:18:38 2011
GMON started with pid=17, OS id=23239
lmon registered with NM - instance id 1 (internal mem no 0)
Reconfiguration started (old inc 0, new inc 124)
ASM instance
List of nodes:
+0 1 2+
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
* allocate domain 1, invalid = TRUE
* allocate domain 2, invalid = TRUE
* allocate domain 3, invalid = TRUE
* allocate domain 4, invalid = TRUE
* domain 0 valid = 1 according to instance 1
* domain 1 valid = 1 according to instance 1
* domain 2 valid = 1 according to instance 1
* domain 3 valid = 1 according to instance 1
* domain 4 valid = 1 according to instance 1
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
LMS 0: 0 GCS shadows traversed, 0 replayed
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Fix write in gcs resources
Reconfiguration complete
Thu Mar 24 07:18:40 2011
LCK0 started with pid=18, OS id=23277
ORACLE_BASE from environment = /u01/app/oracle
Thu Mar 24 07:18:41 2011
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: cache registered group DATA number=1 incarn=0xf7063e39
NOTE: cache began mount (not first) of group DATA number=1 incarn=0xf7063e39
NOTE: cache registered group RECOVERY number=2 incarn=0xf7063e3a
NOTE: cache began mount (not first) of group RECOVERY number=2 incarn=0xf7063e3a
NOTE: cache registered group REDO01 number=3 incarn=0xf7163e3b
NOTE: cache began mount (not first) of group REDO01 number=3 incarn=0xf7163e3b
NOTE: cache registered group REDO02 number=4 incarn=0xf7163e3c
NOTE: cache began mount (not first) of group REDO02 number=4 incarn=0xf7163e3c
NOTE:Loaded lib: /opt/oracle/extapi/32/asm/orcl/1/libasm.so
NOTE: Assigning number (1,0) to disk (ORCL:ASM_DATA1)
NOTE: Assigning number (1,1) to disk (ORCL:ASM_DATA2)
NOTE: Assigning number (2,0) to disk (ORCL:ASM_RECO1)
NOTE: Assigning number (3,0) to disk (ORCL:ASM_LOG1)
NOTE: Assigning number (4,0) to disk (ORCL:ASM_LOG2)
kfdp_query(): 5
kfdp_queryBg(): 5
NOTE: cache opening disk 0 of grp 1: DATA1 label:ASM_DATA1
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache opening disk 1 of grp 1: DATA2 label:ASM_DATA2
NOTE: cache mounting (not first) group 1/0xF7063E39 (DATA)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 1
NOTE: LGWR attempting to mount thread 1 for diskgroup 1
NOTE: LGWR mounted thread 1 for disk group 1
NOTE: opening chunk 1 at fcn 0.10794571 ABA
NOTE: seq=81 blk=1313
NOTE: cache mounting group 1/0xF7063E39 (DATA) succeeded
NOTE: cache ending mount (success) of group DATA number=1 incarn=0xf7063e39
kfdp_query(): 6
kfdp_queryBg(): 6
NOTE: cache opening disk 0 of grp 2: RECO1 label:ASM_RECO1
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 2/0xF7063E3A (RECOVERY)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 2
NOTE: LGWR attempting to mount thread 1 for diskgroup 2
NOTE: LGWR mounted thread 1 for disk group 2
NOTE: opening chunk 1 at fcn 0.10436377 ABA
NOTE: seq=48 blk=4298
NOTE: cache mounting group 2/0xF7063E3A (RECOVERY) succeeded
NOTE: cache ending mount (success) of group RECOVERY number=2 incarn=0xf7063e3a
kfdp_query(): 7
kfdp_queryBg(): 7
NOTE: cache opening disk 0 of grp 3: LOG1 label:ASM_LOG1
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 3/0xF7163E3B (REDO01)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 3
NOTE: LGWR attempting to mount thread 1 for diskgroup 3
NOTE: LGWR mounted thread 1 for disk group 3
NOTE: opening chunk 1 at fcn 0.229332 ABA
NOTE: seq=30 blk=10690
NOTE: cache mounting group 3/0xF7163E3B (REDO01) succeeded
NOTE: cache ending mount (success) of group REDO01 number=3 incarn=0xf7163e3b
kfdp_query(): 8
kfdp_queryBg(): 8
NOTE: cache opening disk 0 of grp 4: LOG2 label:ASM_LOG2
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 4/0xF7163E3C (REDO02)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 4
NOTE: LGWR attempting to mount thread 1 for diskgroup 4
NOTE: LGWR mounted thread 1 for disk group 4
NOTE: opening chunk 1 at fcn 0.225880 ABA
NOTE: seq=30 blk=10556
NOTE: cache mounting group 4/0xF7163E3C (REDO02) succeeded
NOTE: cache ending mount (success) of group REDO02 number=4 incarn=0xf7163e3c
kfdp_query(): 9
kfdp_queryBg(): 9
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 1
SUCCESS: diskgroup DATA was mounted
kfdp_query(): 10
kfdp_queryBg(): 10
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 2
SUCCESS: diskgroup RECOVERY was mounted
kfdp_query(): 11
kfdp_queryBg(): 11
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 3
SUCCESS: diskgroup REDO01 was mounted
kfdp_query(): 12
kfdp_queryBg(): 12
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 4
SUCCESS: diskgroup REDO02 was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT
Thu Mar 24 08:26:28 2011
Starting background process ASMB
Thu Mar 24 08:26:28 2011
ASMB started with pid=20, OS id=9597
NOTE: ASMB process exiting due to lack of ASM file activity for 5 seconds
Thu Mar 24 08:27:39 2011
Starting background process ASMB
Thu Mar 24 08:27:39 2011
ASMB started with pid=25, OS id=10735
NOTE: ASMB process exiting due to lack of ASM file activity for 5 seconds
+[oracle@qa1crmrac1 trace]$ tail -1500 alert_ASM1.log
Thu Mar 24 07:05:11 2011
LMD0 (ospid: 32493) has not called a wait for 94 secs.
GES: System Load is HIGH.
GES: Current load is 55.87 and high load threshold is 20.00
Thu Mar 24 07:06:32 2011
LMD0 (ospid: 32493) has not called a wait for 174 secs.
GES: System Load is HIGH.
GES: Current load is 71.23 and high load threshold is 20.00
Thu Mar 24 07:06:36 2011
+Trace dumping is performing id=[cdmp_20110324070635]+
Thu Mar 24 07:07:49 2011
+Trace dumping is performing id=[cdmp_20110324070635]+
Thu Mar 24 07:08:16 2011
Waiting for clusterware split-brain resolution
Thu Mar 24 07:18:17 2011
Errors in file /u01/app/oracle/diag/asm/asm/+ASM1/trace/+ASM1_lmon_32484.trc (incident=60073):+
ORA-29740: evicted by member 1, group incarnation 120
Incident details in: /u01/app/oracle/diag/asm/asm/+ASM1/incident/incdir_60073/+ASM1_lmon_32484_i60073.trc+
Thu Mar 24 07:18:19 2011
+Trace dumping is performing id=[cdmp_20110324071819]+
Errors in file /u01/app/oracle/diag/asm/asm/+ASM1/trace/+ASM1_lmon_32484.trc:+
ORA-29740: evicted by member 1, group incarnation 120
LMON (ospid: 32484): terminating the instance due to error 29740
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/diag/asm/asm/+ASM1/trace/+ASM1_diag_32459.trc+
+Trace dumping is performing id=[cdmp_20110324071820]+
Instance terminated by LMON, pid = 32484
Thu Mar 24 07:18:31 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth1 172.20.223.0 configured from OCR for use as a cluster interconnect
Interface type 1 eth0 172.20.222.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/asm_1/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side pfile /u01/app/oracle/product/11.1.0/asm_1/dbs/initASM1.ora+
System parameters with non-default values:
large_pool_size          = 12M
instance_type            = "asm"
cluster_database         = TRUE
instance_number          = 1
asm_diskstring           = "ORCL:*"
asm_diskgroups           = "REDO01"
asm_diskgroups           = "REDO02"
asm_diskgroups           = "DATA"
asm_diskgroups           = "RECOVERY"
diagnostic_dest          = "/u01/app/oracle"
Cluster communication is configured to use the following interface(s) for this instance
+172.20.223.25+
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Thu Mar 24 07:18:36 2011
PMON started with pid=2, OS id=23120
Thu Mar 24 07:18:36 2011
VKTM started with pid=3, OS id=23123 at elevated priority
VKTM running at (20)ms precision
Thu Mar 24 07:18:36 2011
DIAG started with pid=4, OS id=23127
Thu Mar 24 07:18:37 2011
PING started with pid=5, OS id=23129
Thu Mar 24 07:18:37 2011
PSP0 started with pid=6, OS id=23131
Thu Mar 24 07:18:37 2011
DIA0 started with pid=7, OS id=23133
Thu Mar 24 07:18:37 2011
LMON started with pid=8, OS id=23135
Thu Mar 24 07:18:37 2011
LMD0 started with pid=9, OS id=23137
Thu Mar 24 07:18:37 2011
LMS0 started with pid=10, OS id=23148 at elevated priority
Thu Mar 24 07:18:37 2011
MMAN started with pid=11, OS id=23152
Thu Mar 24 07:18:38 2011
DBW0 started with pid=12, OS id=23170
Thu Mar 24 07:18:38 2011
LGWR started with pid=13, OS id=23176
Thu Mar 24 07:18:38 2011
CKPT started with pid=14, OS id=23218
Thu Mar 24 07:18:38 2011
SMON started with pid=15, OS id=23224
Thu Mar 24 07:18:38 2011
RBAL started with pid=16, OS id=23237
Thu Mar 24 07:18:38 2011
GMON started with pid=17, OS id=23239
lmon registered with NM - instance id 1 (internal mem no 0)
Reconfiguration started (old inc 0, new inc 124)
ASM instance
List of nodes:
+0 1 2+
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
* allocate domain 1, invalid = TRUE
* allocate domain 2, invalid = TRUE
* allocate domain 3, invalid = TRUE
* allocate domain 4, invalid = TRUE
* domain 0 valid = 1 according to instance 1
* domain 1 valid = 1 according to instance 1
* domain 2 valid = 1 according to instance 1
* domain 3 valid = 1 according to instance 1
* domain 4 valid = 1 according to instance 1
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
LMS 0: 0 GCS shadows traversed, 0 replayed
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Fix write in gcs resources
Reconfiguration complete
Thu Mar 24 07:18:40 2011
LCK0 started with pid=18, OS id=23277
ORACLE_BASE from environment = /u01/app/oracle
Thu Mar 24 07:18:41 2011
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: cache registered group DATA number=1 incarn=0xf7063e39
NOTE: cache began mount (not first) of group DATA number=1 incarn=0xf7063e39
NOTE: cache registered group RECOVERY number=2 incarn=0xf7063e3a
NOTE: cache began mount (not first) of group RECOVERY number=2 incarn=0xf7063e3a
NOTE: cache registered group REDO01 number=3 incarn=0xf7163e3b
NOTE: cache began mount (not first) of group REDO01 number=3 incarn=0xf7163e3b
NOTE: cache registered group REDO02 number=4 incarn=0xf7163e3c
NOTE: cache began mount (not first) of group REDO02 number=4 incarn=0xf7163e3c
NOTE:Loaded lib: /opt/oracle/extapi/32/asm/orcl/1/libasm.so
NOTE: Assigning number (1,0) to disk (ORCL:ASM_DATA1)
NOTE: Assigning number (1,1) to disk (ORCL:ASM_DATA2)
NOTE: Assigning number (2,0) to disk (ORCL:ASM_RECO1)
NOTE: Assigning number (3,0) to disk (ORCL:ASM_LOG1)
NOTE: Assigning number (4,0) to disk (ORCL:ASM_LOG2)
kfdp_query(): 5
kfdp_queryBg(): 5
NOTE: cache opening disk 0 of grp 1: DATA1 label:ASM_DATA1
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache opening disk 1 of grp 1: DATA2 label:ASM_DATA2
NOTE: cache mounting (not first) group 1/0xF7063E39 (DATA)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 1
NOTE: LGWR attempting to mount thread 1 for diskgroup 1
NOTE: LGWR mounted thread 1 for disk group 1
NOTE: opening chunk 1 at fcn 0.10794571 ABA
NOTE: seq=81 blk=1313
NOTE: cache mounting group 1/0xF7063E39 (DATA) succeeded
NOTE: cache ending mount (success) of group DATA number=1 incarn=0xf7063e39
kfdp_query(): 6
kfdp_queryBg(): 6
NOTE: cache opening disk 0 of grp 2: RECO1 label:ASM_RECO1
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 2/0xF7063E3A (RECOVERY)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 2
NOTE: LGWR attempting to mount thread 1 for diskgroup 2
NOTE: LGWR mounted thread 1 for disk group 2
NOTE: opening chunk 1 at fcn 0.10436377 ABA
NOTE: seq=48 blk=4298
NOTE: cache mounting group 2/0xF7063E3A (RECOVERY) succeeded
NOTE: cache ending mount (success) of group RECOVERY number=2 incarn=0xf7063e3a
kfdp_query(): 7
kfdp_queryBg(): 7
NOTE: cache opening disk 0 of grp 3: LOG1 label:ASM_LOG1
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 3/0xF7163E3B (REDO01)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 3
NOTE: LGWR attempting to mount thread 1 for diskgroup 3
NOTE: LGWR mounted thread 1 for disk group 3
NOTE: opening chunk 1 at fcn 0.229332 ABA
NOTE: seq=30 blk=10690
NOTE: cache mounting group 3/0xF7163E3B (REDO01) succeeded
NOTE: cache ending mount (success) of group REDO01 number=3 incarn=0xf7163e3b
kfdp_query(): 8
kfdp_queryBg(): 8
NOTE: cache opening disk 0 of grp 4: LOG2 label:ASM_LOG2
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 4/0xF7163E3C (REDO02)
kjbdomatt send to node 1
kjbdomatt send to node 2
NOTE: attached to recovery domain 4
NOTE: LGWR attempting to mount thread 1 for diskgroup 4
NOTE: LGWR mounted thread 1 for disk group 4
NOTE: opening chunk 1 at fcn 0.225880 ABA
NOTE: seq=30 blk=10556
NOTE: cache mounting group 4/0xF7163E3C (REDO02) succeeded
NOTE: cache ending mount (success) of group REDO02 number=4 incarn=0xf7163e3c
kfdp_query(): 9
kfdp_queryBg(): 9
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 1
SUCCESS: diskgroup DATA was mounted
kfdp_query(): 10
kfdp_queryBg(): 10
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 2
SUCCESS: diskgroup RECOVERY was mounted
kfdp_query(): 11
kfdp_queryBg(): 11
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 3
SUCCESS: diskgroup REDO01 was mounted
kfdp_query(): 12
kfdp_queryBg(): 12
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 4
SUCCESS: diskgroup REDO02 was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT
Thu Mar 24 08:26:28 2011
Starting background process ASMB
Thu Mar 24 08:26:28 2011
ASMB started with pid=20, OS id=9597
NOTE: ASMB process exiting due to lack of ASM file activity for 5 seconds
Thu Mar 24 08:27:39 2011
Starting background process ASMB
Thu Mar 24 08:27:39 2011
ASMB started with pid=25, OS id=10735
NOTE: ASMB process exiting due to lack of ASM file activity for 5 seconds
Do i need to set the compatible parameter?
Regards,
Vish

It looks to me like your server is absolutely buried, and ASM may just be an innocent bystander. What is going on in the database when this happens? Also, run sar samples at 30 second intervals up to when this happens to see what is happening. It's overhead, but you need to find what is causing the problem with the server(s).
Are you swapping?

ORA-15100: invalid or missing diskgroup name in 11g ASM

We have 11g R2 DB and 11g ASM installed on linux server, it was working till morning,due to some maintenance we rebooted server, then i am trying to bring up asm instance, its falling with below error.
[oracle@adg dbs]$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 16 16:15:57 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Automatic Storage Management option
SQL> startup force pfile='/u01/app/11.2.0/grid/dbs/init+ASM.ora';
ASM instance started
Total System Global Area 284565504 bytes
Fixed Size 1336036 bytes
Variable Size 258063644 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
SQL> show parameter string
NAME TYPE VALUE
asm_diskstring string DATA, DATA1
SQL> shut immediate
ORA-15100: invalid or missing diskgroup name
ASM instance shutdown
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Automatic Storage Management option
[oracle@adg dbs]$ vi init+ASM.ora
[oracle@adg dbs]$ /etc/init.d/oracleasm listdisks
DISK1
DISK2
[[root@adg ~]# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
ERROR: diskgroup RECOVERY_AREA was not mounted
NOTE: cache deleting context for group RECOVERY_AREA 2/625504078
ORA-15032: not all alterations performed
ORA-15017: diskgroup "RECOVERY_AREA" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "RECOVERY_AREA"
ERROR: ALTER DISKGROUP RECOVERY_AREA MOUNT /* asm agent */
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_rbal_6520.trc ; (incident=8105):
ORA-00600: internal error code, arguments: [kfrcGetNRB05], [1], [340], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM/incident/incdir_8105/+ASM_rbal_6520_i8105.trc
ERROR: ORA-600 in COD recovery for diskgroup 1/0xfe086f4c (DATA)
ERROR: ORA-600 thrown in RBAL for group number 1
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_rbal_6520.trc:
ORA-00600: internal error code, arguments: [kfrcGetNRB05], [1], [340], [], [], [], [], [], [], [], [], []
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_rbal_6520.trc:
ORA-00600: internal error code, arguments: [kfrcGetNRB05], [1], [340], [], [], [], [], [], [], [], [], []
RBAL (ospid: 6520): terminating the instance due to error 488
Tue Aug 16 15:47:03 2011
ORA-1092 : opitsk aborting process
Tue Aug 16 15:47:04 2011
Instance terminated by RBAL, pid = 6520
Tue Aug 16 15:51:08 2011
Starting ORACLE instance (normal)

I tried already.
SQL> select disk_number, name, label, path, mount_status,HEADER_STATUS, state from v$asm_disk
2 ;
DISK_NUMBER NAME LABEL
PATH
MOUNT_S HEADER_STATU STATE
1 DISK2
ORCL:DISK2
CLOSED MEMBER NORMAL
0 DISK1
ORCL:DISK1
CLOSED MEMBER NORMAL
DISK_NUMBER NAME LABEL
PATH
MOUNT_S HEADER_STATU STATE
SQL> alter diskgroup recovery_area mount;
alter diskgroup recovery_area mount
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15017: diskgroup "RECOVERY_AREA" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"RECOVERY_AREA"
SQL>
here is alert log information
==================
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/11.2.0/grid/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Automatic Storage Management option.
Using parameter settings in client-side pfile /u01/app/11.2.0/grid/dbs/init+ASM.ora on machine adg.xxxx.com
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
remote_login_passwordfile= "EXCLUSIVE"
asm_diskstring = ""
asm_power_limit = 1
diagnostic_dest = "/u01/app/oracle"
Tue Aug 16 16:32:26 2011
PMON started with pid=2, OS id=11558
Tue Aug 16 16:32:26 2011
VKTM started with pid=3, OS id=11560 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Aug 16 16:32:26 2011
GEN0 started with pid=4, OS id=11564
Tue Aug 16 16:32:26 2011
DIAG started with pid=5, OS id=11566
Tue Aug 16 16:32:26 2011
PSP0 started with pid=6, OS id=11568
Tue Aug 16 16:32:26 2011
DIA0 started with pid=7, OS id=11570
Tue Aug 16 16:32:27 2011
MMAN started with pid=8, OS id=11572
Tue Aug 16 16:32:27 2011
DBW0 started with pid=9, OS id=11574
Tue Aug 16 16:32:27 2011
LGWR started with pid=10, OS id=11576
Tue Aug 16 16:32:27 2011
CKPT started with pid=11, OS id=11578
Tue Aug 16 16:32:27 2011
SMON started with pid=12, OS id=11580
Tue Aug 16 16:32:27 2011
RBAL started with pid=13, OS id=11582
Tue Aug 16 16:32:27 2011
GMON started with pid=14, OS id=11584
Tue Aug 16 16:32:27 2011
MMON started with pid=15, OS id=11586
Tue Aug 16 16:32:27 2011
MMNL started with pid=16, OS id=11588
ORACLE_BASE from environment = /u01/app/oracle
Tue Aug 16 16:32:27 2011
SQL> ALTER DISKGROUP ALL MOUNT
Tue Aug 16 16:34:23 2011
SQL> alter diskgroup recovery_area mount
NOTE: cache registered group RECOVERY_AREA number=1 incarn=0x100b432b
NOTE: cache began mount (first) of group RECOVERY_AREA number=1 incarn=0x100b432b
Tue Aug 16 16:34:24 2011
NOTE: Loaded library: /opt/oracle/extapi/32/asm/orcl/1/libasm.so
Tue Aug 16 16:34:24 2011
ERROR: no PST quorum in group: required 2, found 0
NOTE: cache dismounting (clean) group 1/0x100B432B (RECOVERY_AREA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 1/0x100B432B (RECOVERY_AREA)
NOTE: cache ending mount (fail) of group RECOVERY_AREA number=1 incarn=0x100b432b
kfdp_dismount(): 2
kfdp_dismountBg(): 2
ERROR: diskgroup RECOVERY_AREA was not mounted
NOTE: cache deleting context for group RECOVERY_AREA 1/269173547
ORA-15032: not all alterations performed
ORA-15017: diskgroup "RECOVERY_AREA" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "RECOVERY_AREA"
ERROR: alter diskgroup recovery_area mount
Tue Aug 16 16:34:53 2011
SQL> alter diskgroup recovery_area mount
NOTE: cache registered group RECOVERY_AREA number=1 incarn=0xc86b4331
NOTE: cache began mount (first) of group RECOVERY_AREA number=1 incarn=0xc86b4331
Tue Aug 16 16:34:53 2011
ERROR: no PST quorum in group: required 2, found 0
NOTE: cache dismounting (clean) group 1/0xC86B4331 (RECOVERY_AREA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 1/0xC86B4331 (RECOVERY_AREA)
NOTE: cache ending mount (fail) of group RECOVERY_AREA number=1 incarn=0xc86b4331
kfdp_dismount(): 4
kfdp_dismountBg(): 4
ERROR: diskgroup RECOVERY_AREA was not mounted
NOTE: cache deleting context for group RECOVERY_AREA 1/-932494543
ORA-15032: not all alterations performed
ORA-15017: diskgroup "RECOVERY_AREA" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "RECOVERY_AREA"
ERROR: alter diskgroup recovery_area mount

Alert_+asm.log

Hi gurus,
Oracle RAC 11.2.03 at redhat 5.4
we had a RAC database on 11.1.0.1 and we migrated to 11.2.0.3 in a few months.
All works fine but there is a abnormal issue. (i think it is abnormal).
we have asm log at:
/u01/app/oracle/diag/asm/+asm/+ASM1/trace/alert_+asm1.log
/u01/app/oracle/diag/asm/+asm/+ASM2/trace/alert_+asm2.log
but all the rest of log/traces are under /u02
SQL> sho parameter diag
NAME                                 TYPE        VALUE
diagnostic_dest                      string      /u02/app/oracle
SQL> sho parameter background_dump_dest
NAME                                 TYPE        VALUE
background_dump_dest                 string      /u02/app/oracle/diag/rdbms/db_cos                                      /db_1/traceif i check adr base at sql:
SQL> select value from v$diag_info where name='ADR Base';
VALUE
/u02/app/oracle
but if I check adrci it show ADR base as /u01/app/oracle. I think here i have the problem, i should change it, right?
but if i try:
adrci> set base =/u02/app/oracle
exit and enter again base is reset to /u01/app/oracle. How i set it permanent?
Edited by: Me_101 on 29-ene-2013 4:08

Both was right, i had asm parameters incorrect
SQL> sho parameter diag
NAME                                 TYPE        VALUE
diagnostic_dest                      string      /u01/app/oracle
SQL> sho parameter background_dump_dest
NAME                                 TYPE        VALUE
background_dump_dest                 string      /u01/app/oracle/diag/asm/+asm/
                                                 +ASM1/traceSQL> alter system set diagnostic_dest='/u02/app/oracle' scope=both sid='*';
System altered.
and:
SQL> sho parameter background_dump
NAME                                 TYPE        VALUE
background_dump_dest                 string      /u02/app/oracle/diag/asm/+asm/
                                                 +ASM2/trace
SQL> sho parameter diag
NAME                                 TYPE        VALUE
diagnostic_dest                      string      /u02/app/oracle*JUST A POINT --> CRS_HOME is for previus Oracle, for 11g is ORA_CRS_HOME

RAC 11g Rel2 - clusterware wont come up after ASM parameter changes Help!

I was tring to make the below parameter change in ASM, but got the below error message
SQL> alter system set db_cache_size=200M scope=spfile sid='*';
alter system set db_cache_size=200M scope=spfile sid='*'
ERROR at line 1:
ORA-32017: failure in updating SPFILE
ORA-00384: Insufficient memory to grow cache
Per note 737458.1
You need to unset SGA_TARGET, restart your database and modify DB_CACHE_SIZE, and then reset SGA_TARGET as before.
So I issued the following in ASM.
ASM> alter system set memory_max_target=0 scope=spfile sid='*';
System altered.
ASM> alter system set memory_target=0 scope=spfile sid='*';
System altered.
hutdown the clusterware and asm using crsctl stop cluster -all
Attempted to start the clusterware using crsctl start cluster -all , received the below error messages
CRS-2672: Attempting to start 'ora.cssd' on 'server100'
CRS-2672: Attempting to start 'ora.diskmon' on server100'
CRS-2676: Start of 'ora.diskmon' on 'server100' succeeded
CRS-2676: Start of 'ora.cssd' on server100' succeeded
CRS-2672: Attempting to start 'ora.ctssd' on server100'
CRS-2676: Start of 'ora.ctssd' on server100'
succeeded
CRS-2672: Attempting to start 'ora.asm' on server100'
ORA-00843: Parameter not taking MEMORY_MAX_TARGET into account
CRS-2674: Start of 'ora.asm' on 'server100' failed
CRS-2679: Attempting to clean 'ora.asm' on server100'
CRS-2681: Clean of 'ora.asm' on 'server100' succeeded
CRS-2673: Attempting to stop 'ora.ctssd' on server100'
CRS-2677: Stop of 'ora.ctssd' on 'server100' succeeded
CRS-2673: Attempting to stop 'ora.diskmon' on server100'
CRS-2677: Stop of 'ora.diskmon' on 'server100' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on server100'
CRS-2677: Stop of 'ora.cssd' on server100' succeeded
CRS-4000: Command Start failed, or completed with errors.
The OCR and voting disk is stored in an ASM disk group. ASM did not like the parameter changes and threw the above errors. I have a backups available.
Can anyone tell me how to revert these parameters ?
I am unable to issue any comamnds becuse the cluster is down
SQL> create pfile ='/home/p.ora' from spfile;
create pfile ='/home/p.ora' from spfile
ERROR at line 1:
ORA-29701: unable to connect to Cluster Synchronization Service
ORA-29701: unable to connect to Cluster Synchronization Service
SQL>
Thanks
DNJ
Edited by: user11177991 on Aug 5, 2011 9:45 AM

user11177991 wrote:
Can anyone tell me how to revert these parameters ?
I am unable to issue any comamnds becuse the cluster is down
SQL> create pfile ='/home/p.ora' from spfile;
create pfile ='/home/p.ora' from spfile
ERROR at line 1:
ORA-29701: unable to connect to Cluster Synchronization Service
ORA-29701: unable to connect to Cluster Synchronization Service
Thanks
DNJ
Hi DNJ,
What you need to do is create temporary pfile with parameters like below
*.asm_diskgroups='DATA','FRA'
*.asm_diskstring='ORCL:*'
*.asm_power_limit=1
*.diagnostic_dest='/u01/app/oracle'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE' modify the above diskgroups to reflect your diskgroup configuration
then start the asm using that temporary pfile
SQL > startup pfile='/tmp/asmpfile.ora'once the asm instance started you can recreate the spfile
create spfile='+DATA' from pfile='/tmp/asmpfile.ora'shutdown the asm and start it back again
Hope this helps
Cheers

How can I add a new controlfile in ASM?

In the ASM,I can't copy any file.How Can I create a new online controlfile? Thanks!

You can use "alter database backup controlfile to trace" command to get the control file contents.
Now you can use create controlfile:
1) If you use resetlogs, use file creation context form for specification of log files.
2) If you use resetlogs, use file reference context.
Why do you want to create a new control file. Is it for multiplexing purpose?
Reference: Chapter-12 of Oracle database administrator guide 10gR2
search for title "Creating a Control File in ASM" ...
Hope this will help you.
Regards,
Neeraj

How can I move back the rman convert file from file system to ASM?

I have no idea on pluging-in the data files which were unloaded as follows:
SQL> alter tablespace P_CDDH_DSPGD_V1_2011 read only;
SQL> alter tablespace P_IDX_CDDH_DSPGD_V1_2011 read only;
SQL> exec dbms_tts.transport_set_check('P_CDDH_DSPGD_V1_2011,P_IDX_CDDH_DSPGD_V1_2011',true);
SQL> select * from transport_set_violations;
UNIX> expdp tossadm@pmscdhf1 dumpfile=ttsfy1.dmp directory=trans_dir transport_tablespaces = P_CDDH_DSPGD_V1_2011,P_IDX_CDDH_DSPGD_V1_2011
RMAN> convert tablespace P_CDDH_DSPGD_V1_2011, P_IDX_CDDH_DSPGD_V1_2011 format = '/appl/oem/backup/temp/%I_%s_%t_extbspace.dbf';
Starting conversion at source at 03-OCT-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=116 instance=pmscdhf11 device type=DISK
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00079 name=+PMSCDHF1/p_cddh_dspgd_v1_2011_01.dbf
converted datafile=/appl/oem/backup/temp/3536350174_2820_827849001_extbspace.dbf
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:02:15
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00080 name=+PMSCDHF1/p_idx_cddh_dspgd_v1_2011_02.dbf
converted datafile=/appl/oem/backup/temp/3536350174_2821_827849136_extbspace.dbf
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:01:45
Finished conversion at source at 03-OCT-13
Starting Control File Autobackup at 03-OCT-13
piece handle=/dbms/oracle/r1110/db_01/dbs/c-3536350174-20131003-02 comment=NONE
Finished Control File Autobackup at 03-OCT-13
SQL> drop tablespace P_CDDH_DSPGD_V1_2011 including contents;
SQL> drop tablespace P_IDX_CDDH_DSPGD_V1_2011 including contents;
Afterward, how can I relocate the backup files "/appl/oem/backup/temp/3536350174_2820_827849001_extbspace.dbf", "/appl/oem/backup/temp/3536350174_2821_827849136_extbspace.dbf" back to the ASM group +PMSCDHF1 ???

The 11.1 documentation only says "Enables you to copy files between ASM disk groups on local instances to and from remote instances" and "You can also use this command to copy files from ASM disk groups to the operating system."
http://docs.oracle.com/cd/B28359_01/server.111/b31107/asm_util.htm#CHDJEIEA
The 11.2 documentation says "Copy files from a disk group to the operating system Copy files from a disk group to a disk group Copy files from the operating system to a disk group"
http://docs.oracle.com/cd/E11882_01/server.112/e18951/asm_util003.htm#CHDJEIEA
I've never tried 11.1
Hemant K Chitale

How to restore (not duplicate) DB from RAC ASM to non ASM

Hello everybody,
i am trying to recover db from RAC+ASM to non ASM no RAC node. I am running Oracle 10g (10.2.0.4) on Win2003 Server. I have functional backup from my prod system.
Here are my steps:
*1. On prod server i make backup running this script in RMAN*
configure channel device type 'SBT_TAPE' parms'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=e:\backup)';
RUN {
backup device type SBT_TAPE database tag zal20081129;
SQL 'alter system archive log current';
backup device type SBT_TAPE archivelog ALL tag zal20081129;
*2. I prepared clon instance on another server (The same Oracle version) and start it to nomount mode.*
*3. I copied the backup from prod server to clon server to exactly the same path. (e:\backup)*
*4. I connect to RMAN on my new node and I use the DBID parameter and I restore controlfile.*
rman
connect target /
set DBID 3079749916
startup nomount
run {
allocate CHANNEL CTAPE DEVICE TYPE 'SBT_TAPE' PARMS'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=f:\backup)';
allocate channel CDISK DEVICE TYPE DISK;
restore controlfile from 'f:\backup\78k91lrn_1_1';
alter database mount;
*5.Then I check the backup, crosscheck etc.*
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
169 Full 42.78G SBT_TAPE 01:12:54 04-MAR-09
BP Key: 169 Status: AVAILABLE Compressed: NO Tag: DATAFILES
Handle: 75k91hcj_1_1 Media:
List of Datafiles in backup set 169
File LV Type Ckp SCN Ckp Time Name
1 Full 928460863 04-MAR-09 +DATA/agost/datafile/system.272.668509367
2 Full 928460863 04-MAR-09 +DATA/agost/datafile/undotbs1.273.668509387
3 Full 928460863 04-MAR-09 +DATA/agost/datafile/sysaux.263.668509393
4 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_archive_data.298.668509401
5 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_archive_index.258.668509401
6 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_blob.259.668509401
7 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_data.274.668509405
8 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_index.275.668509533
9 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_report_data.260.668509661
10 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_report_index.261.668509661
12 Full 928460863 04-MAR-09 +DATA/agost/datafile/undotbs2.264.668509661
13 Full 928460863 04-MAR-09 +DATA/agost/datafile/users.265.668509667
14 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_index.270.668510837
15 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_index.299.668510843
16 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_data.300.668510859
17 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_data.301.668510865
BS Key Size Device Type Elapsed Time Completion Time
171 1.98G SBT_TAPE 00:02:54 04-MAR-09
BP Key: 171 Status: AVAILABLE Compressed: NO Tag: ARCHIVE_LOGS
Handle: 77k91lm2_1_1 Media:
List of Archived Logs in backup set 171
Thrd Seq Low SCN Low Time Next SCN Next Time
1 790 927018133 03-MAR-09 927379509 03-MAR-09
1 791 927379509 03-MAR-09 927635333 03-MAR-09
1 792 927635333 03-MAR-09 927804715 03-MAR-09
1 793 927804715 03-MAR-09 928438198 04-MAR-09
1 794 928438198 04-MAR-09 928496353 04-MAR-09
1 795 928496353 04-MAR-09 928496667 04-MAR-09
2 941 927018173 03-MAR-09 927414357 03-MAR-09
2 942 927414357 03-MAR-09 927725821 03-MAR-09
2 943 927725821 03-MAR-09 927747874 03-MAR-09
2 944 927747874 03-MAR-09 927804436 03-MAR-09
2 945 927804436 03-MAR-09 928375778 03-MAR-09
2 946 928375778 03-MAR-09 928460503 04-MAR-09
2 947 928460503 04-MAR-09 928496341 04-MAR-09
2 948 928496341 04-MAR-09 928496660 04-MAR-09
*6. Then I run this script to restore and recover db.*
run {
SET UNTIL SEQUENCE 795 THREAD 1;
SET UNTIL SEQUENCE 948 THREAD 2;
restore database;
switch datafile all;
recover database;
*7. Everything goes well see under.*
RMAN> 2> 3> 4> 5> 6> 7>
executing command: SET until clause
executing command: SET until clause
Starting restore at 04-MAR-09
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting datafile backupset restore
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DATA/agost/datafile/system.272.668509367
restoring datafile 00002 to +DATA/agost/datafile/undotbs1.273.668509387
restoring datafile 00003 to +DATA/agost/datafile/sysaux.263.668509393
restoring datafile 00004 to +DATA/agost/datafile/ifsapp_archive_data.298.668509401
restoring datafile 00005 to +DATA/agost/datafile/ifsapp_archive_index.258.668509401
restoring datafile 00006 to +DATA/agost/datafile/ifsapp_blob.259.668509401
restoring datafile 00007 to +DATA/agost/datafile/ifsapp_data.274.668509405
restoring datafile 00008 to +DATA/agost/datafile/ifsapp_index.275.668509533
restoring datafile 00009 to +DATA/agost/datafile/ifsapp_report_data.260.668509661
restoring datafile 00010 to +DATA/agost/datafile/ifsapp_report_index.261.668509661
restoring datafile 00012 to +DATA/agost/datafile/undotbs2.264.668509661
restoring datafile 00013 to +DATA/agost/datafile/users.265.668509667
restoring datafile 00014 to +DATA/agost/datafile/ifsapp_index.270.668510837
restoring datafile 00015 to +DATA/agost/datafile/ifsapp_index.299.668510843
restoring datafile 00016 to +DATA/agost/datafile/ifsapp_data.300.668510859
restoring datafile 00017 to +DATA/agost/datafile/ifsapp_data.301.668510865
channel ORA_SBT_TAPE_1: reading from backup piece 75k91hcj_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=75k91hcj_1_1 tag=DATAFILES
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 01:25:12
Finished restore at 04-MAR-09
Starting recover at 04-MAR-09
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
starting media recovery
channel ORA_SBT_TAPE_1: starting archive log restore to default destination
channel ORA_SBT_TAPE_1: restoring archive log
archive log thread=1 sequence=794
channel ORA_SBT_TAPE_1: restoring archive log
archive log thread=2 sequence=947
channel ORA_SBT_TAPE_1: reading from backup piece 77k91lm2_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=77k91lm2_1_1 tag=ARCHIVE_LOGS
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:02:26
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_1_794_4TX5D7RD_.ARC thread=1 sequence=794
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_2_947_4TX5D7OY_.ARC thread=2 sequence=947
channel default: deleting archive log(s)
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_2_947_4TX5D7OY_.ARC recid=1563 stamp=680629925
channel default: deleting archive log(s)
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_1_794_4TX5D7RD_.ARC recid=1562 stamp=680629925
media recovery complete, elapsed time: 00:00:13
Finished recover at 04-MAR-09
*8. Then when i want to open database*
using command 'Alter system open resetlogs;' I got this error:
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 03/05/2009 07:26:03
RMAN-06003: ORACLE error from target database:
ORA-00600: internal error code, arguments: [kgeade_is_0], [|http://forums.oracle.com/forums/], [], [|http://forums.oracle.com/forums/], [], [|http://forums.oracle.com/forums/], [], [|http://forums.oracle.com/forums/]
In the alert log I have got this error: (for every log group)
ORA-00313: open failed for members of log group 4 of thread 2
ORA-00312: online log 4 thread 2: '+FLASHBACK/agost/onlinelog/group_4.260.668510637'
ORA-17503: ksfdopn:2 Failed to open file +FLASHBACK/agost/onlinelog/group_4.260.668510637
ORA-15001: diskgroup "FLASHBACK" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
ORA-00312: online log 4 thread 2: '+DATA/agost/onlinelog/group_4.268.668510633'
ORA-17503: ksfdopn:2 Failed to open file +DATA/agost/onlinelog/group_4.268.668510633
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
So obviouslly database wants to open online logs in the path like ASM. Which is wrong. What should I do to tell database to open it according to init.ora parameters
*.db_create_file_dest='e:\oradata\agost'
*.db_create_online_log_dest_1='e:\oradata\agost'
Any suggestions???
Thanks

Hi,
thanks for you quick answer. But I do restore to the local file system, even if the log says:
restoring datafile 00001 to +DATA/agost/datafile/system.272.668509367
restoring datafile 00002 to +DATA/agost/datafile/undotbs1.273.668509387 .....
all the datafiles are correctly restored. I think oracle uses the parameter db_create_file_dest and creates the files there.
I tried also the script with SET NEW NAME:
run {
Set newname for datafile 1 to 'e:\oradata\AGOST\system.272.668509367';
Set newname for datafile 2 to 'e:\oradata\AGOST\undotbs1.273.668509387';
Set newname for datafile 3 to 'e:\oradata\AGOST\sysaux.263.668509393';
Set newname for datafile 4 to 'e:\oradata\AGOST\ifsapp_archive_data.298.668509401';
Set newname for datafile 5 to 'e:\oradata\AGOST\ifsapp_archive_index.258.668509401';
Set newname for datafile 6 to 'e:\oradata\AGOST\ifsapp_blob.259.668509401';
Set newname for datafile 7 to 'e:\oradata\AGOST\ifsapp_data.274.668509405';
Set newname for datafile 8 to 'e:\oradata\AGOST\ifsapp_index.275.668509533';
Set newname for datafile 9 to 'e:\oradata\AGOST\ifsapp_report_data.260.668509661';
Set newname for datafile 10 to 'e:\oradata\AGOST\ifsapp_report_index.261.668509661';
Set newname for datafile 12 to 'e:\oradata\AGOST\undotbs2.264.668509661';
Set newname for datafile 13 to 'e:\oradata\AGOST\users.265.668509667';
Set newname for datafile 14 to 'e:\oradata\AGOST\ifsapp_index.270.668510837';
Set newname for datafile 15 to 'e:\oradata\AGOST\ifsapp_index.299.668510843';
Set newname for datafile 16 to 'e:\oradata\AGOST\ifsapp_data.300.668510859';
Set newname for datafile 17 to 'e:\oradata\AGOST\ifsapp_data.301.668510865';
Set newname for tempfile 1 to 'e:\oradata\AGOST\temp.276.668509397';
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_1.256.668509345'' TO ''e:\oradata\AGOST\REDO01.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_1.257.668509351'' TO ''e:\oradata\AGOST\REDO02.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_2.257.668509357'' TO ''e:\oradata\AGOST\REDO03.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_2.258.668509361'' TO ''e:\oradata\AGOST\REDO04.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_3.266.668510623'' TO ''e:\oradata\AGOST\REDO05.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_3.259.668510627'' TO ''e:\oradata\AGOST\REDO06.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_4.268.668510633'' TO ''e:\oradata\AGOST\REDO07.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_4.260.668510637'' TO ''e:\oradata\AGOST\REDO08.LOG'' ";
SET UNTIL SEQUENCE 795 THREAD 1;
SET UNTIL SEQUENCE 948 THREAD 2;
restore database;
switch datafile all;
recover database;
But it gives me this error in RMAN:
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
sql statement: ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_1.256.668509345'' TO ''e:\oradata\AGOST\REDO01.LOG''
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 03/06/2009 10:48:55
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: ALTER DATABASE RENAME FILE '+DATA/agost/onlinelog/group_1.256.668509345' TO 'e:\oradata\AGOST\REDO01.LOG'
RMAN-11001: Oracle Error:
ORA-00600: internal error code, arguments: [kgeade_is_0], [], [], [], [], [], [], []
and in alert log i have got this:
Errors in file c:\oracle\product\10.2.0\admin\agost\udump\agost_ora_3200.trc:
ORA-00600: internal error code, arguments: [kgeade_is_0], [], [], [], [], [], [], []
Fri Mar 06 10:48:55 2009
ORA-600 signalled during: ALTER DATABASE RENAME FILE '+DATA/agost/onlinelog/group_1.256.668509345' TO 'e:\oradata\AGOST\REDO01.LOG' ...
dont know what to do.
There must be way how to recover it. I think my first try (without SET NEWNAME) is closer to the end, there is only need to "repair" the online logs.
Any other suggestions?
thanks

GI installtion gives error while executing root.sh for ASM diskgroup

Dear Gurus,
We are implementing a 2 node RAC configuration with ASM on vmware and openfiler on LINUX RHEL 6.2. We started our installation with grid infrastructure. While executing root.sh on node 1 it gives error diskgroup cannot be mounted and no alterntions perfomed as below.
+[main] [ 2012-10-04 05:38:33.150 PDT ] [UsmcaLogger.logException:173] SEVERE:method oracle.sysman.assistants.usmca.backend.USMDiskGroupManager:mountDiskGroups+
+[main] [ 2012-10-04 05:38:33.151 PDT ] [UsmcaLogger.logException:174] ORA-15032: not all alterations performed+
ORA-15017: diskgroup "CRS" cannot be mounted
ORA-15088: diskgroup creation incomplete
+[main] [ 2012-10-04 05:38:33.338 PDT ] [UsmcaLogger.logException:175] oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-15032: not all alterations pe+
rformed
ORA-15017: diskgroup "CRS" cannot be mounted
Note:- we are not using ASMLib. We presented the LUN's to oracle binaries with Multipathing.

Put here relevant info of alertlog of ASM and CRS.
Please format your text by using tag at begin and end of output.

Error when trying to create a directory in ASM

Hello,
I've got Oracle RAC 11gR2. Two nodes with Windows Server 2008. Database in ASM instance.
I'm trying to create a directory "backupp" in ASM instance, but got error.
All Oracle Windows services are running under Local Ssystem Account.
I've logged in Windows Server 2008 with user AdminRAC, which is membor of Administrators and ORA_DBA Windows group.
Diskgroup: data
C:> SET ORACLE_HOME=C:\app\11.2.0\grid
C:\>SET ORACLE_SID=+ASM1
C:\asmcmd
Connected to an idle instance.
ASMCMD> mkdir +data/backupp
Can't open 'C:\app\11.2.0\grid/log/diag/asmcmd/user_AdminRAC/JNESRVRACA/alert/al
ert.log' for append
CLSU-00100: Operating System function: open failed failed with error data: 2
CLSU-00101: Operating System error message: The system cannot find the file spec
ified.
CLSU-00103: error location: SlfFopen1
ORA-15032: not all alterations performed
ORA-15005: name "+data/backupp" is already used by an existing alias (DBD ERROR:
OCIStmtExecute)
Can't open 'C:\app\11.2.0\grid/log/diag/asmcmd/user_AdminRAC/JNESRVRACA/alert/al
ert.log' for append
CLSU-00100: Operating System function: open failed failed with error data: 2
CLSU-00101: Operating System error message: The system cannot find the file spec
ified.
CLSU-00103: error location: SlfFopen1
ASMCMD>

user521219 wrote:
Hello,
I've got Oracle RAC 11gR2. Two nodes with Windows Server 2008. Database in ASM instance.
I'm trying to create a directory "backupp" in ASM instance, but got error.
All Oracle Windows services are running under Local Ssystem Account.
I've logged in Windows Server 2008 with user AdminRAC, which is membor of Administrators and ORA_DBA Windows group.
Diskgroup: data
C:> SET ORACLE_HOME=C:\app\11.2.0\grid
C:\>SET ORACLE_SID=+ASM1
C:\asmcmd
Connected to an idle instance.
ASMCMD> mkdir +data/backupp
Can't open 'C:\app\11.2.0\grid/log/diag/asmcmd/user_AdminRAC/JNESRVRACA/alert/al
ert.log' for append
CLSU-00100: Operating System function: open failed failed with error data: 2
CLSU-00101: Operating System error message: The system cannot find the file spec
ified.
CLSU-00103: error location: SlfFopen1
looks like two different problems exist
ORA-15032: not all alterations performed
ORA-15005: name "+data/backupp" is already used by an existing alias (DBD ERROR:
OCIStmtExecute)directory already exists
Can't open 'C:\app\11.2.0\grid/log/diag/asmcmd/user_AdminRAC/JNESRVRACA/alert/al
ert.log' for appenderror can't be logged

Best way to move redo log from one disk group to another in ASM?

Hi All,
Our db is 10.2.0.3 RAC db. And database servers are window 2003 server.
We need to move more than 50 redo logs (some are regular and some are standby) which are not redundant from one disk group to another. Say we need to move from disk group 1 to 2. Here are the options we are thinking about but not sure which one is the best from easiness and safety prospective.
Thank you very much for your help in advance.
Shirley
Option 1:
1)     shutdown immediate
2)     copy log files from disk group 1 to disk group2 using RMAN (need to research on this)
3)     startup mount
4)     alter database rename file ….
5)     Open database open
6)     delete the redo files from disk group 1 in ASM (how?)
Option 2:
1)     create a set of redo log groups in disk group 2
2)     drop the redo log groups in disk group 1 when they are inactive and have been archived
3)     delete the redo files associated with those dropped groups from disk group 1 (how?) (According to Oracle menu: when you drop the redo log group the operating system files are not deleted and you need to manually delete those files)
Option 3:
1)     create a set of redo members in disk group 2 for each redo log group in disk group 1
2)     drop the redo log memebers in disk group 1
3)     delete the redo files from disk group 1 associated with the dropped members

Absolutely not, they are not even remotely similar concepts.
OMF: Oracle Managed Files. It is an RDMBS feature, no matter what your storage technology is, Oracle will take care of file naming and location, you only have to define the size of a file, and in the case of a tablespace on an OMF DB Configuration you only need to issue a command similar to this:
CREATE TABLESPACE <TSName>; So the OMF environment creates an autoextensible datafile at the predefined location with 100M by default as its initial size.
On ASM it should only be required to specify '+DGroupName' as the datafile or redo log file argument so it can be fully managed by ASM.
EMC. http://www.emc.com No further commens on it.
~ Madrid
http://hrivera99.blogspot.com

Alter diagnostic_dest to ASM

Similar Messages

Maybe you are looking for