Create logfile using ASM

Hello All,
I am getting following errors in RAC standby Node 1 database.
ORA-00313: open failed for members of log group 23 of thread 1
RFS[2]: No standby redo logfiles of size 102400 blocks available
RFS[2]: Opened log for thread 1 sequence 146 dbid 1483762860 branch 732196712
Wed Oct 13 15:35:21 2010
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc1_8609.trc:
ORA-00313: open failed for members of log group 21 of thread 1
Wed Oct 13 15:35:21 2010
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc0_8607.trc:
ORA-00313: open failed for members of log group 21 of thread 1
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc0_8607.trc:
ORA-00313: open failed for members of log group 21 of thread 1
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc0_8607.trc:
ORA-00313: open failed for members of log group 21 of thread 1
ARC0: Archiving not possible: error count exceeded
Trace file says
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 21 thread 1: '+MDMDG1/mdm1/onlinelog/group_21.314.732284813'
ORA-00312: online log 21 thread 1: '+MDMDG2/mdm1/onlinelog/group_21.390.732284813'
*** 2010-10-13 15:04:24.216 4529 kcrr.c
ORA-16014: log 21 sequence# 131 not archived, no available destinations
ORA-00312: online log 21 thread 1: '+MDMDG1/mdm1/onlinelog/group_21.314.732284813'
ORA-00312: online log 21 thread 1: '+MDMDG2/mdm1/onlinelog/group_21.390.732284813'
and when I try to open the database
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01157: cannot identify/lock data file 16 - see DBWR trace file
ORA-01111: name for data file 16 is unknown - rename to correct file
ORA-01110: data file 16:
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00016'
I am not sure what is the problem and what to fix.
Thanks.

[oracle@rs1pre91dvdbaa01 ~]$ cat /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc1_8609.trc
Trace file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc1_8609.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
System name: Linux
Node name: rs1pre91dvdbaa01.pre.ccosvc.com
Release: 2.6.18-194.11.3.el5
Version: #1 SMP Mon Aug 23 15:51:38 EDT 2010
Machine: x86_64
Instance name: MDM11
Redo thread mounted by this instance: 1
Oracle process number: 35
Unix process pid: 8609, image: [email protected] (ARC1)
*** 2010-10-13 15:10:20.313
*** SESSION ID:(406.2) 2010-10-13 15:10:20.313
*** CLIENT ID:() 2010-10-13 15:10:20.313
*** SERVICE NAME:() 2010-10-13 15:10:20.313
*** MODULE NAME:() 2010-10-13 15:10:20.313
*** ACTION NAME:() 2010-10-13 15:10:20.313
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:15:20.506
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
*** 2010-10-13 15:20:20.756
ORA-00313: open failed for members of log group 21 of thread 1
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:25:21.228
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:30:21.550
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
DDE: Problem Key 'ORA 313' was flood controlled (0x5) (no incident)
*** 2010-10-13 15:35:21.835
ORA-00313: open failed for members of log group 21 of thread 1
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:40:22.121
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:45:22.422
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
DDE: Problem Key 'ORA 313' was flood controlled (0x5) (no incident)
*** 2010-10-13 15:50:22.674
ORA-00313: open failed for members of log group 21 of thread 1
ORA-00313: open failed for members of log group 21 of thread 1

Similar Messages

Can't create database using ASM (SOLVED)

Hi all
I'm trying to use ASM for the first time, on Oracle 10.2.0.1 on Solaris x64.
I have installed the ASM instance into /opt/oracle/asm/10.2.0 and created disk groups. I have cssd running OK. I am able to start and stop the ASM instance without problems, and I can select from v$asm_diskgroup to confirm that disks are mounted OK.
I have then installed Oracle EE separately into /opt/oracle/server/10.2.0. I first did a software only install, and now I am trying to create a DB.
The problems come when I try to use this ASM instance to host a new database. I first tried to use DBCA to create a new database, but on database creation I got the following errors:
ORA-00200: control file could not be created
ORA-00202: control file: '+DBLIVE1'
ORA-17502: ksfdcre:4 Failed to create file +DBLIVE1
ORA-15001: diskgroup "DBLIVE1" does not exist or is not mounted
ORA-15055: Message 15055 not found; No message file for product=RDBMS, facility=ORA
ORA-01031: insufficient privileges
I then told DBCA just to create the DB creation scripts, and I tried manually running these with SQL*Plus.
When doing it with SQL*PLus, I initially got the same error as shown above. But then something changed (sorry, not sure what), and now the error I get is:
CREATE DATABASE "NEONREL1"
ERROR at line 1:
ORA-01501: CREATE DATABASE failed
ORA-00349: failure obtaining block size for '+DBLIVE1'
ORA-01031: insufficient privileges
I've put some debug info below, showing me succesfully connecting to the ASM instance and then attempting to create the DB using the db creation scripts, showing the error at the end. You can see that the oracle OS user is able to connect fine to ASM, then I swithc ORACLE_SID and ORACLE_HOME to the EE install and try to create the DB, at which point it apparently can't connect to ASM any more.
I've tried the DB creation many times, and in between attempts I completely empty $ORACLE_HOME/admin/<dbname> and delete the files related to the attempted install from $ORACLE_HOME/dbs/ . I've also stopping/starting ASM, rebooting, and I've done the install of ASM and EE a couple of times over in case I made any mistakes in my earlier attempts.
Any help would be much appreciated!
Tom
##### CHECKING ASM
oracle@neonrcom-db1:~$ uname -a
SunOS neonrcom-db1 5.10 Generic_127128-11 i86pc i386 i86pc
# css is running
oracle@neonrcom-db1:~$ ps -ef | grep css
oracle 498 1 0 21:46:40 ? 0:01 /opt/oracle/asm/10.2.0/bin/ocssd.bin
# listener is running in the ASM instance
oracle@neonrcom-db1:~$ ps -ef | grep tnsl
oracle 1332 1 0 21:49:59 ? 0:00 /opt/oracle/asm/10.2.0/bin/tnslsnr LISTENER -inherit
# ASM is only entry in /var/opt/oracle/oratab
oracle@neonrcom-db1:~$ grep -v "^#" /var/opt/oracle/oratab
+ASM:/opt/oracle/asm/10.2.0:N
# I can connect to ASM fine, and it has diskgroups mounted.
oracle@neonrcom-db1:~$ export ORACLE_HOME=/opt/oracle/asm/10.2.0
oracle@neonrcom-db1:~$ export ORACLE_SID='+ASM'
oracle@neonrcom-db1:~$ sqlplus "sys as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 21 20:53:10 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> set line 150
SQL> select name, block_size, state, type, total_mb, free_mb from v$asm_diskgroup;
NAME BLOCK_SIZE STATE TYPE TOTAL_MB FREE_MB
DBARCH1 4096 MOUNTED EXTERN 2096856 2096784
DBLIVE1 4096 MOUNTED EXTERN 4193904 4193812
#### Contents of init.ora for new DB
db_create_file_dest=+DBLIVE1
db_recovery_file_dest=+DBARCH1
db_recovery_file_dest_size=2147483648
##### DB INSTALLATION ATTEMPT
oracle@neonrcom-db1:~$ export ORACLE_HOME=/opt/oracle/server/10.2.0
oracle@neonrcom-db1:~$ export ORACLE_SID='NEONREL1'
oracle@neonrcom-db1:~$ export PATH=$ORACLE_HOME/bin:$PATH
oracle@neonrcom-db1:~$ /opt/oracle/server/10.2.0/admin/NEONREL1/scripts/NEONREL1.sh
You should Add this entry in the /var/opt/oracle/oratab: NEONREL1:/opt/oracle/server/10.2.0:Y
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 21 22:10:54 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
specify a password for sys as parameter 1
Enter value for 1: xxx
specify a password for system as parameter 2
Enter value for 2: xxx
specify a password for sysman as parameter 3
Enter value for 3: xxx
specify a password for dbsnmp as parameter 4
Enter value for 4: xxx
specify ASM SYS user password as parameter 6
Enter value for 6: xxx
Connected to an idle instance.
SQL> spool /opt/oracle/server/10.2.0/admin/NEONREL1/scripts/CreateDB.log
SQL> startup nomount pfile="/opt/oracle/server/10.2.0/admin/NEONREL1/scripts/init.ora";
ORACLE instance started.
Total System Global Area 1.9294E+10 bytes
Fixed Size 2054976 bytes
Variable Size 2264925376 bytes
Database Buffers 1.7012E+10 bytes
Redo Buffers 14721024 bytes
SQL> CREATE DATABASE "NEONREL1"
2 MAXINSTANCES 8
3 MAXLOGHISTORY 1
4 MAXLOGFILES 16
5 MAXLOGMEMBERS 3
6 MAXDATAFILES 100
7 DATAFILE SIZE 300M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
8 EXTENT MANAGEMENT LOCAL
9 SYSAUX DATAFILE SIZE 120M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
10 SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE SIZE 20M AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
11 SMALLFILE UNDO TABLESPACE "UNDOTBS1" DATAFILE SIZE 200M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
12 CHARACTER SET AL32UTF8
13 NATIONAL CHARACTER SET UTF8
14 LOGFILE GROUP 1 SIZE 51200K,
15 GROUP 2 SIZE 51200K,
16 GROUP 3 SIZE 51200K
17 USER SYS IDENTIFIED BY "&&sysPassword" USER SYSTEM IDENTIFIED BY "&&systemPassword";
CREATE DATABASE "NEONREL1"
ERROR at line 1:
ORA-01501: CREATE DATABASE failed
ORA-00349: failure obtaining block size for '+DBLIVE1'
ORA-01031: insufficient privileges
Message was edited by:
tjobbins

Update: I've worked out the difference between the two sets of errors I get.
The basic error is this:
ORA-00200: control file could not be created
ORA-00202: control file: '+DBLIVE1'
ORA-17502: ksfdcre:4 Failed to create file +DBLIVE1
ORA-15001: diskgroup "DBLIVE1" does not exist or is not mounted
ORA-15055: Message 15055 not found; No message file for product=RDBMS, facility=ORA
ORA-01031: insufficient privileges
However if my init.ora contains the line:
control_files=/opt/oracle/server/10.2.0/dbs/cntrlNEONREL1.dbf
then I instead get the second error:
CREATE DATABASE "NEONREL1"
ERROR at line 1:
ORA-01501: CREATE DATABASE failed
ORA-00349: failure obtaining block size for '+DBLIVE1'
ORA-01031: insufficient privileges
So basically these must be the same error, just in the second case I'm not trying to put the control file on the ASM so it fails at a different point.
But both errors must be because of the same cause, I suppose.

Install and Create Database Using ASM Restart

I'm performing a clean install of Oracle grid + database (11gR2) on Oracle Linux R5U6. Both installs seem to go just fine. The ASM processes start and run just fine. But, when I try to create a database, I get the following errors:
PRCR-1079: Failed to start resource ora.test.db
ORA-01031: insufficient privileges
ORA-01031: insufficient privileges
CRS-2674: Start of 'ora.test.db' on 'asm' failed
ORA-01034: ORACLE not available
ORA-01034: ORACLE not available
0
Any ideas?
Thanks
Jim
-----------Create Groups and Users--------------------------------------------------------------------
groupadd oinstall
groupadd dba
groupadd oper
groupadd asmdba
groupadd asmoper
groupadd asmadmin
useradd -g oinstall -G asmdba,asmoper,asmadmin grid
useradd -g oinstall -G dba,oper,asmdba,asmoper,asmadmin oracle
passwd grid
passwd oracle
[root@asm asm]# id oracle
uid=502(oracle) gid=502(oinstall) groups=502(oinstall),503(dba),504(oper),505(asmdba),506(asmoper),507(asmadmin)
[root@asm asm]# id grid
uid=501(grid) gid=502(oinstall) groups=502(oinstall),505(asmdba),506(asmoper),507(asmadmin)
[root@asm asm]# uname -rm
2.6.18-238.el5 i686
[root@asm asm]# uname -a
Linux asm.protoeffect.cxm 2.6.18-238.el5 #1 SMP Tue Jan 4 15:24:05 EST 2011 i686 i686 i386 GNU/Linux
----------------------ASM RPM Installs---------------------------------------------------------
[root@asm asm]# rpm -Uvh oracleasm-support-2.1.7-1.el5.i386.rpm \
oracleasm-2.6.18-238.el5-2.0.5-1.el5.i686.rpm \
oracleasmlib-2.0.4-1.el5.i386.rpm
warning: oracleasm-support-2.1.7-1.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing... ########################################### [100%]
1:oracleasm-support ########################################### [ 33%]
2:oracleasm-2.6.18-238.el########################################### [ 67%]
3:oracleasmlib ########################################### [100%]
-------------------ASM Configure------------------------------------------------------------
[root@asm asm]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: grid
Default group to own the driver interface []: asmadmin
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
-------------------Allocating Disks------------------------------------------------------------
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK1 /dev/sdb1
Marking disk "DISK1" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK2 /dev/sdc1
Marking disk "DISK2" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK3 /dev/sdd1
Marking disk "DISK3" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK4 /dev/sde1
Marking disk "DISK4" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK5 /dev/sdf1
Marking disk "DISK5" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK6 /dev/sdg1
Marking disk "DISK6" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK7 /dev/sdh1
Marking disk "DISK7" as an ASM disk: [ OK ]
[root@asm asm]# /etc/init.d/oracleasm createdisk DISK8 /dev/sdi1
Marking disk "DISK8" as an ASM disk: [ OK ]
[root@asm asm]#
[root@asm asm]#
[root@asm asm]# /etc/init.d/oracleasm listdisks
DISK1
DISK2
DISK3
DISK4
DISK5
DISK6
DISK7
DISK8
---------------------GRID Response File----------------------------------------------------------
oracle.install.responseFileVersion=/oracle/install/rspfmt_crsinstall_response_schema_v11_2_0
ORACLE_HOSTNAME=asm.protoeffect.cxm
INVENTORY_LOCATION=/u01/app/oraInventory
SELECTED_LANGUAGES=en
oracle.install.option=HA_CONFIG
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/11.2.0/grid
oracle.install.asm.OSDBA=asmdba
oracle.install.asm.OSOPER=asmoper
oracle.install.asm.OSASM=asmadmin
oracle.install.crs.config.gpnp.scanName=
oracle.install.crs.config.gpnp.scanPort=0
oracle.install.crs.config.clusterName=
oracle.install.crs.config.gpnp.configureGNS=true
oracle.install.crs.config.gpnp.gnsSubDomain=
oracle.install.crs.config.gpnp.gnsVIPAddress=
oracle.install.crs.config.autoConfigureClusterNodeVIP=false
oracle.install.crs.config.clusterNodes=
oracle.install.crs.config.privateInterconnects=
oracle.install.crs.config.storageOption=
oracle.install.crs.config.sharedFileSystemStorage.diskDriveMapping=
oracle.install.crs.config.sharedFileSystemStorage.votingDiskLocations=
oracle.install.crs.config.sharedFileSystemStorage.votingDiskRedundancy=NORMAL
oracle.install.crs.config.sharedFileSystemStorage.ocrLocations=
oracle.install.crs.config.sharedFileSystemStorage.ocrRedundancy=NORMAL
oracle.install.crs.config.useIPMI=false
oracle.install.crs.config.ipmi.bmcUsername=
oracle.install.crs.config.ipmi.bmcPassword=
oracle.install.asm.SYSASMPassword=
oracle.install.asm.diskGroup.name=DATA
oracle.install.asm.diskGroup.redundancy=NORMAL
oracle.install.asm.diskGroup.disks=ORCL:DISK1,ORCL:DISK2,ORCL:DISK3,ORCL:DISK4
oracle.install.asm.diskGroup.diskDiscoveryString=
oracle.install.asm.monitorPassword=
oracle.install.crs.upgrade.clusterNodes=
oracle.install.asm.upgradeASM=false
[grid@asm ~]$ ps -ef | grep pmon
grid 9950 1 0 09:25 ? 00:00:00 asm_pmon_+ASM
grid 10053 4345 0 09:26 pts/2 00:00:00 grep pmon
------------------------Database Software Install Response File-------------------------------------------------------
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v11_2_0
oracle.install.option=INSTALL_DB_SWONLY
ORACLE_HOSTNAME=asm.protoeffect.cxm
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/u01/app/oraInventory
SELECTED_LANGUAGES=en
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
ORACLE_BASE=/u01/app/oracle
oracle.install.db.InstallEdition=EE
oracle.install.db.isCustomInstall=false
oracle.install.db.customComponents=
oracle.install.db.DBA_GROUP=dba
oracle.install.db.OPER_GROUP=oper
oracle.install.db.CLUSTER_NODES=
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
oracle.install.db.config.starterdb.globalDBName=
oracle.install.db.config.starterdb.SID=
oracle.install.db.config.starterdb.characterSet=
oracle.install.db.config.starterdb.memoryLimit=
oracle.install.db.config.starterdb.memoryOption=false
oracle.install.db.config.starterdb.installExampleSchemas=false
oracle.install.db.config.starterdb.enableSecuritySettings=true
oracle.install.db.config.starterdb.password.ALL=
oracle.install.db.config.starterdb.password.SYS=
oracle.install.db.config.starterdb.password.SYSTEM=
oracle.install.db.config.starterdb.password.SYSMAN=
oracle.install.db.config.starterdb.password.DBSNMP=
oracle.install.db.config.starterdb.control=DB_CONTROL
oracle.install.db.config.starterdb.gridcontrol.gridControlServiceURL=
oracle.install.db.config.starterdb.dbcontrol.enableEmailNotification=false
oracle.install.db.config.starterdb.dbcontrol.emailAddress=
oracle.install.db.config.starterdb.dbcontrol.SMTPServer=
oracle.install.db.config.starterdb.automatedBackup.enable=false
oracle.install.db.config.starterdb.automatedBackup.osuid=
oracle.install.db.config.starterdb.automatedBackup.ospwd=
oracle.install.db.config.starterdb.storageType=
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=
oracle.install.db.config.asm.diskGroup=
oracle.install.db.config.asm.ASMSNMPPassword=
MYORACLESUPPORT_USERNAME=J
MYORACLESUPPORT_PASSWORD=
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=false
PROXY_HOST=
PROXY_PORT=
-------------Database Creation Info------------------------------------------------------------------
Name Value
audit_file_dest {ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/adump
audit_trail db
compatible 11.2.0.0.0
db_block_size 8KB
db_create_file_dest +DATA
db_domain
db_name test
diagnostic_dest {ORACLE_BASE}
dispatchers (PROTOCOL=TCP) (SERVICE={SID}XDB)
memory_target 1225MB
open_cursors 300
processes 150
remote_login_passwordfile EXCLUSIVE
undo_tablespace UNDOTBS1

This is the problem with you
Now time to solve this problem, to make “user grid in secondary group dba”
http://justinnovation.wordpress.com/category/database/ora/
# usermod -G asmadmin,asmdba,asmoper,dba grid
Now you will notice the Privileges are changed
# id grid
uid=501(grid) gid=1000(oinstall) groups=1000(oinstall),1100(dba),1300(asmadmin),1400(asmdba),1500(asmoper)
now try to runInstaller again!
Good Luck!
帖子经 Haseeb Alam编辑过

Can Grid Control 10gR2 create a standby database when primary db uses ASM?

Does anyone know if Grid Control 10gR2 will be able to create a standby database when the primary database uses ASM for data files, redo log files, and archive log files but the standby database will use mounted disks? If it can, would it matter that the primary db will be a RAC cluster and the standby will be a single instance db?

I appreciate your reply and hope you are correct. Have you had a look at the 10gR2 Grid Control to confirm this or are you only going on published statements? The reason I ask is because previous versions of Grid Control claimed to support ASM but they would only allow you to work with them AFTER you had created a standby database manually but you couldn't actually use Grid Control to create a standby database from a primary database that had its log files on ASM disks.

Can use ASM only when creating database using dbca

I have a problem. When i create a database using DBCA, i can only use ASM as the file sytem. why ?
i just installed the 10gR2 with cluster and donno why i cannot use ocfs.
Thanks.

What were your reasons with going with OCFS rather than ASM?
Thanks.

DBCA can not use ASM for database storage due to following reason: Could no

Hi
I've a recently installed RAC11gR2(11.2.0.3) on HP-UX
I installed Grid Infrastructure with grid user:
Node1: # id grid
uid=1100(grid) gid=1000(oinstall) groups=1031(dba),1021(asmdba)
Node2: # id grid
uid=1100(grid) gid=1000(oinstall) groups=1031(dba),1021(asmdba)
I installed the Oracle Server with oracle user:
Node1: # id oracle
uid=1101(oracle) gid=1000(oinstall) groups=1031(dba),1021(asmdba),1033(oper)
Node2: # id oracle
uid=1101(oracle) gid=1000(oinstall) groups=1031(dba),1021(asmdba),1033(oper)
All related Grid Infrastructure is functioning well in both nodes:
$ crs_stat -t
Name Type Target State Host
ora.DATA.dg ora....up.type ONLINE ONLINE node03
ora.FRA.dg ora....up.type ONLINE ONLINE node03
ora....ER.lsnr ora....er.type ONLINE ONLINE node03
ora....N1.lsnr ora....er.type ONLINE ONLINE node04
ora.asm ora.asm.type ONLINE ONLINE node03
ora.cvu ora.cvu.type ONLINE ONLINE node04
ora.gsd ora.gsd.type OFFLINE OFFLINE
ora....network ora....rk.type ONLINE ONLINE node03
ora.oc4j ora.oc4j.type OFFLINE OFFLINE
ora.ons ora.ons.type ONLINE ONLINE node03
ora.scan1.vip ora....ip.type ONLINE ONLINE node04
ora....SM1.asm application ONLINE ONLINE node03
ora....03.lsnr application ONLINE ONLINE node03
ora....d03.gsd application OFFLINE OFFLINE
ora....d03.ons application ONLINE ONLINE node03
ora....d03.vip ora....t1.type ONLINE ONLINE node03
ora....SM2.asm application ONLINE ONLINE node04
ora....04.lsnr application ONLINE ONLINE node04
ora....d04.gsd application OFFLINE OFFLINE
ora....d04.ons application ONLINE ONLINE node04
ora....d04.vip ora....t1.type ONLINE ONLINE node04
$
The ASM instance are running well in both nodes
Connected with oracle user, the listener has registered perfectly the ASM instance in each node:
$
$ lsnrctl status
LSNRCTL for HPUX: Version 11.2.0.3.0 - Production on 16-MAY-2012 15:41:06
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for HPUX: Version 11.2.0.3.0 - Production
Start Date 16-MAY-2012 15:24:19
Uptime 0 days 0 hr. 16 min. 47 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora
Listener Log File /u01/app/grid/diag/tnslsnr/node03/listener/alert/log .xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=16.0.0.133)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=16.0.0.136)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
The command completed successfully
$
$
DATA & FRA disk group are created:
$
$ echo $ORACLE_SID
+ASM1
$
$ asmcmd
ASMCMD>
ASMCMD> ls -lt
State Type Rebal Name
MOUNTED EXTERN N DATA/
MOUNTED EXTERN N FRA/
ASMCMD>
ASMCMD>
The big issue is... that the DBCA can not see the diskgroups. When I choose ASM Storage it can not see them. It shows the chart in blank and if i try to write the disk group, so the following message appears: can not use ASM for database storage due to following reason: Could not connect to ASM due to following error: ORA-01034 ORACLE not available
What can be passing in this case... ?
Thanks in advance

Thanks both
Really the problem initially was because of this:
[INS-06006] Passwordless SSH connectivity not set up between the following node(s): [node1, node2]. CVU may reports "PRVF-4007 : User equivalence check failed for user "user"" for same error
and I had to install node1 first and after node2 manually and perhaps for this the product was not well linked.
I resolved the problem establishing the keys with the wizard and after copying the following files from node1 to node2
/home/grid/.ssh -------> /home/grid/.ssh
authorized_keys
known_hosts
This is the procedure if you run the wizard at the node1.
The problem is that the wizard creates the keys incompletely...
Thanks

Advantages of using ASM

Can someone tell me some reason for using
ASM when using hardware stripe & mirror
besides that files are created and managed automatically?

Hi,
In large-scale environments, ASM eases the task of managing thousands of database files by using DISK GROUPS instead. Disk Groups are disk devices managed as a logical unit. When creating a new tablespace, control file, or redo log file you can specify a disk group as the storage area for the database structure rather than an operating system file.
ASM uses OMF and mirroring and striping features to provide a file system and logical manager that supports multiple databases, nodes, and RAC. ASM eliminates the need to purchase a 3rd party logical volume manager... ASM strips files, not logical volumes.
In addition to spreading db objects over multiple devices, ASM allows new disk devices to be added to the database while the database is running, as well as automatically rebalancing the distribution of files w/ minimum intervention.
The DBA assumes the traditional role of "System-admin space manager" this brings hardware provisioning for db objects more closely into the world of the DBA.
Can someone tell me some reason for using
ASM when using hardware stripe & mirror
besides that files are created and managed
automatically?

Create space in ASM Instance

Dear All,
Here is the configuration we have:
Primary Database: Oracle RAC (2 Nodes). 11g R1 RAC, 10g R2 Database using ASM (OS: Windows Server 2003)
Data Guard: 10g R2 Database using ASM (OS: Windows Server 2003)
We are getting the following errors in the alert log file of ASM Instance (Data Guard) - Data Gaurd mode is 'Max Performance':
ORA-00270: error creating archive log +DG_DATAFILES_AND_FB/accelastdby/primary_arch_logs/arc32471_0721252017.002
ORA-19504: failed to create file "+DG_DATAFILES_AND_FB/accelastdby/primary_arch_logs/arc32471_0721252017.002"
ORA-17502: ksfdcre:4 Failed to create file +DG_DATAFILES_AND_FB/accelastdby/primary_arch_logs/arc32471_0721252017.002
ORA-15041: diskgroup space exhausted
Uopn checking the disk group DG_DATAFILES_AND_FB, free space is 0.
What are the possible options to create more space on this disk group? Can we delete some files safely without any impact (for example: Archive logs which have been applied to database)?
Thanks for your advice.
Regards,
Muhammad Riaz

Hi,
First you can add more disks to the diskgroup so you can get more space, ASM will do rebalance once new disks added.
Second, It seems that your archivelog in dataguard were not deleted after being applied. You can delete the applied archivelog in dataguard, use RMAN is the best option
Hope this helps
Cheers
FZheng

How to create a new ASM Diskgroup in Oracle 10g RAC?

Hi,
Our env is Oracle 10g R2 RAC on HP-UX. I want to create a new ASM Diskgroup. Please let me know if the following steps are ok to create a new ASM Diskgroup.
1. Ensure the new Disk is visible in both ASM instances in RAC (v$asm_disk) and the header_status is 'CANDIDATE'
2. From Node 1 ASM Instance issue the create diskgroup command.
SQL> create diskgroup DATA2 external redundancy disk '/dev/rdsk/c4t0d5';
3. Query v$asm_diskgroup and make sure the Diskgroup is created.
4. Mount the DATA2 Diskgroup from Node 2 ASM Instance.
5. Query v$asm_diskgroup and make sure the Diskgroup is visible from Node2 ASM instance.
6. Ensure the header_status is 'MEMBER'.
Rgds,

correct.
instead of using device file '/dev/rdsk/c4t0d5' you can create an alternate device file using mknod, which is called "asm_disk_xg" for example.
check here: http://download.oracle.com/docs/cd/B19306_01/install.102/b14202/storage.htm#CDEECIHI
hth

11g r2 non rac using asm for sun cluster os (two node but non-rac)

I am going to install grid installation for non-rac using asm for two node sun cluster environment..
How to create candidate disk in solaris cluster (sparc os) to install grid home in asm.. please provide me the steps if anyone knows

Please refer the thread Re: 11GR2 ASM in non-rac node not starting... failing with error ORA-29701
and this doc http://docs.oracle.com/cd/E11882_01/install.112/e24616/presolar.htm#CHDHAAHE

Oracle11g R2 Active Data guard using ASM Problem?

I have configured oracle11g r2 RAC on 2 notes using ASM Grid ( OS unix).
RAC is up and running.
Now I am configuring Active data Guard.
Under grid user instance +ASM and listener is running.
Under oracle user static listener is running.
All disk is mounted.
Oracle RAC and Data Guard directory and structure I have keeped same.
Now my problem is below:
$ ./rman target sys/HPinvent123nbl@dcpdb AUXILIARY sys/HPinvent123nbl@drpdb
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 16 16:28:32 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DCPDB (DBID=316773134)
connected to auxiliary database: DRPDB (not mounted)
RMAN> duplicate target database for standby from active database;
Starting Duplicate Db at 16-JAN-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=5644 device type=DISK
contents of Memory Script:
backup as copy reuse
targetfile '/u02/app/oracle/product/11.2.0/dbhome_1/dbs/orapwdcpdb1' auxiliary format
'/u02/app/oracle/product/11.2.0/dbhome_1/dbs/orapwdrpdb' ;
executing Memory Script
Starting backup at 16-JAN-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1897 instance=dcpdb1 device type=DISK
Finished backup at 16-JAN-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/16/2013 16:28:48
RMAN-06136: ORACLE error from auxiliary database: ORA-00200: control file could not be created
ORA-00202: control file: '+data'
ORA-17502: ksfdcre:4 Failed to create file +data
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
RMAN>
Please help.\
Thanks
Solaiman

root@drpdb1 []# id oracle
uid=108(oracle) gid=700(oinstall) groups=701(dba)
root@drpdb1 []# id grid
uid=109(grid) gid=700(oinstall) groups=701(dba),702(asmdba)
Edited by: 876149 on Jan 16, 2013 3:19 AM

Data Guard: db_file_name_convert/log_file_name_convert when using ASM/OMF

All,
I have a call currently open with Oracle regarding the setting of the parameters db_file_name_convert and log_file_name_convert in a data guard environment. We use ASM / OMF for storage and file naming and my question is basically do these parameters have to be set. The documentation says they do where the file structure is different between PRIMARY and STANDBY.
I have successfully tested failover and switchover without these parameters. I have also added a new tablespace on the PRIMARY and watched it create a new OMF datafile on standby when the logs are switched.
I just can't see a reason for setting them when using ASM / OMF.
I'm hoping someone can enlighten me here because I'm getting nowhere whith support. The following is our Data Guard setup:
PRIMARY
DB_NAME=IBSLIVE
DB_UNIQUE_NAME=IBSLIVE
ASM Disk Groups:
+PRODDATA (Data Files, Control Files, Redo Logs)
+PRODFLASH (Archive Logs, Flashback Logs, RMAN backups)
+PRODLOGS (Multiplexed Control & Redo Logs)
STANDBY
DB_NAME=IBSLIVE
DB_UNIQUE_NAME=IBSDR
ASM Disk Groups:
+DRDATA (Data Files, Control Files, Redo Logs)
+DRFLASH (Archive Logs, Flashback Logs, RMAN backups)
+DRREDO (Multiplexed Control & Redo Logs)
Many Thanks,
Ian.

Ian,
I'm having similar thoughts.
I have created a new instance with files in asm under +datadisk/obosact (this is the smae name as primary)
I then modify the db_unique_name from obosact to obosactdr as is required for standby to work
When I recover (duplicate target database for standby; ) I find that the files are in datadisk/obosactdr not in the datadisk/obosact area
I found this reference http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
4. Connect to the ASM instance on one standby host, and create a directory within the DATA disk group that has the same name as the DB_UNIQUE_NAME of the standby database. For example: SQL> ALTER DISKGROUP data ADD DIRECTORY '+DATA/BOSTON';
This step seems to indicate that the location of the files is determined by the db_unique_name not the db_file_name_convert paramenter
DId you ever resolve the issue?

Using ASM in a cluster, and new snapshot feature

Hi,
I'm currently studying ASM and trying to find some answers.
From what I understand and experienced so far, ASM can only be used as a local storage solution. In other words it cannot be used by network access. Is this correct?
How is the RDBMS database connecting to the ASM instance? Which process or what type of connection is it using? It's apparently not using listener, although the instance name is part of the database file path. How does this work please?
How does ASM work in a cluster environment? How does each node in a cluster connect to it?
As of 11g release 2, ASM provides a snapshot feature. I assume this can be used for the purpose of backup, but then each database should use it's own diskgroup, and I will still need to use alter database begin backup, correct?
Thanks!

Markus Waldorf wrote:
Hi,
I'm currently studying ASM and trying to find some answers.
From what I understand and experienced so far, ASM can only be used as a local storage solution. In other words it cannot be used by network access. Is this correct?Well, you are missing one point that it would entirely depend on the architecture that you are going to use. If you are going to use ASM for a single node, it would be available right there. If installed for a RAC system, ASM instance would be running on each node of the cluster and would be managing the storage which would be lying on the shared storage. The process ASMB would be responsible to exchange messages, take response and push the information back to the RDBMS instance.
How is the RDBMS database connecting to the ASM instance? Which process or what type of connection is it using? It's apparently not using listener, although the instance name is part of the database file path. How does this work please?Listener is not need Markus as its required to create the server processes which is NOT the job of the ASM instance. ASM instance would be connecting the client database with itself immediately when the first request would come from that database to do any operation over the disk group. As I mentioned above, ASMB would be working afterwards to carry forward the request/response tasks.
How does ASM work in a cluster environment? How does each node in a cluster connect to it? Each node would be having its own ASM instance running locally to it. In the case of RAC, ASM sid would be +ASMn where n would be 1, 2,... , going forward to the number of nodes being a part of teh cluster.
As of 11g release 2, ASM provides a snapshot feature. I assume this can be used for the purpose of backup, but then each database should use it's own diskgroup, and I will still need to use alter database begin backup, correct?You are probably talking about the ACFS Snapshot feature of 11.2 ASM. This is not to take the backup of the disk group but its like a o/s level backup of the mount point which is created over the ASM's ACFS mount point. Oracle has given this feature so that you can take the backup of your oracle home running on the ACFS mount point and in the case of any o/s level failure like someone has deleted certain folder from that mountpoint, you can get it back through the ACFS snapshot taken. For the disk group, the only backup available is metadata backup(and restore) but that also does NOT get the data of the database back for you. For the database level backup, you would stillneed to use RMAN only.
HTH
Aman....

Is it better to use ASM if my DB uses only one disk ?

Hello
I am planning to install a NEW database 11g R1 on a new windows server.
I am running a 9.2 DB and will export its data to the freshly installed 11gR1.
I ma wondering if i have to use the ASM feature ?
The dabatase files are small : 52 Gb, and it will keep on one disk.
I have understood that the main benefit of using ASM in automatic multi disk storage.
Does it worth to use it on my small DB ?
Thank you for your kind answers.
Christian

If you want to learn ASM then using it with a single disk system and just creating the diskgroups to not use Oracle redundancy is an option. Also one of the things ASM is designed to provide is async IO, that is, easy managment of raw partitions. Depending on your platform ASM may be desirable from this point of view.
Also does a one disk set-up today mean only a one disk set-up tomorrow? It is possible to migrate a database to a new disk server via ASM while the database is running. You create a mirror, allow it to populate, and then remove the original disk. The database data files are now on a new disk storage unit.
But ASM is by no means required or necessary. You just want to consider all the options it provides and the headaches it brings to determine which set of values: use or not, is right for your situation.
HTH -- Mark D Powell --

Dataguard using ASM in primary node and FILESYSTEM in standby node

Hi There!
I need to configure a Dataguard, and my primary DB is working on ASM, the standby node is going to be using filesystems, so I want to know if there is a guide that I can follow in order to get this task successfully completed.
My operating system is Solaris 10, and the DB Release is 10.2.0.4. I want to know the best practices.
Also I want to remember some RMAN Restore and Recover techniques to have this configuration ready, up and running.
Thanks in Advance.
Paola
@>--->----

setting this up isn't that different to setting up a single instance standby on ASM,
the MAA guide is here
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf
this details the configuration using ASM on both sides, if you want to use filesystem storage on the standby then the following parameters will need to be changed
*.db_file_name_convert='+DATA/CHICAGO/','+DATA/BOSTON/','+RECOVERY/CHICAGO','+RECOVERY/BOSTON'
*.log_file_name_convert='+DATA/CHICAGO/','+DATA/BOSTON/','+RECOVERY/CHICAGO','+RECOVERY/BOSTON'
to something like
*.db_file_name_convert='+DATA/CHICAGO/','/oradata/boston','+RECOVERY/CHICAGO','/recovery/boston'
*.log_file_name_convert='+DATA/CHICAGO/','/oradata/boston','+RECOVERY/CHICAGO','/recovery/boston'
alternativly you can set the DB_CREATE_FILE_DEST and DB_CREATE_ONLINE_LOG_DEST_n parameters and let oracle create OMF files for the dataguard instance.
Chris

Create logfile using ASM

Similar Messages

Maybe you are looking for