DB Using ASM Storage (Spfile)

Hello,
I have setup a db to use asm storage. i need to view the contents of the spfile for that db.
when i go to the $ORACLE_HOME/dbs i get to see the init file which in turn points to an spfile like what is seen below
SPFILE='+DATA/asmdb/spfileasmdb.ora'
How can i view the contents of this from a diskgroup. i checked the asmcmd prompt but i dont think they have an option to "cat" or "vi" the file.
Can anyone show me how can i view this. Thx.

Hello,
I used the first approach but it doesnt wk, i get an error
SQL> create pfile='/u01/asmdb.ora' from spfile;
create pfile='/u01/asmdb.ora' from spfile
ERROR at line 1:
ORA-02236: invalid file name
i dont use EM, so is there another way out of this. Thx.

Similar Messages

Oracle 10g RAC using ASM - Storage Issue

I’ve an issue related to Oracle 10g RAC.
I’ve 2 node cluster each being Dell 2850 Server with RHEL 4.0
I’ve EMC CX300 SAN storage with following partitions
/orasoft     10 Gb          OCFS2 File system
/oracrs          2 Gb          OCFS2 File system
/orabackup      100 Gb          OCFS2 File system
The datafiles are on ASM which is not directly visible in OS.
I’ve common Oracle Home installed in /orasoft/db_1 which is shared by both nodes in cluster.
I’ve faced an issue recently related to EMC storage.
The /orasoft partition displays 1.4 Gb space available using df command.
With both nodes sharing the common Oracle Home (/orasoft/db_1), when ever I try to touch a file I get an error as No Space left on device. I’m unable to start any service with the same reason.
Is this setup correct ??
Can anyone help me with this storage issue ??

Need a clarification here...what do you mean by "Storage System"...do you mean a server/node or the SAN storage system. If you are referring to a server/node's local storage, then it would NOT be possible for use by RAC, since the disk space has to be shared among the nodes.
Here is what you can do:
- Create two partitions/devices (for example Disk_1 and Disk_2) in the SAN storage
- Create a ASM disk group which would mirror Disk_1 to Disk_2.
Again, please note that the partitions have to be visible and be accessible read/write from both the nodes/servers.
HTH
Thanks
Chandra Pabba

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

10.2.0.4 - 11.2 - dbua - fatal - db using asm as storage,... but it isn't

I'm upgrading my 10.2.0.4 to 11.2.0.1 on RHEL5.4.
I start up the 11.2 dbua, and select the database to upgrade, then dbua pops up a box that says:
"The database is using ASM as storage. Before you upgrade the database, you need to upgrade ASM using Automatic Storage Configuration Assistant (ASMCA) from grid infrastructure home. Starting 11gR2, ASM should be running from grid infrastructure home"
The problem is.... I am not running ASM.
Any reasons why dbua is complaining about this, and how I can get past it?
Thanks in advance.
Stuart.

trace.log shows dbua thinking ASM is installed. I'll update this when Oracle Support come back to me...
Thread-14] 2010-01-28 13:51:34.608 NZDT ] CompManager.doPreMigrationChecks:2596] Logging Dir at this point :=/u04/app/oracle/cfgtoollogs/dbua/TRAIN/upgrade3
Thread-14] 2010-01-28 13:51:34.612 NZDT ] CompManager.doPreMigrationChecks:2605] ++++++++++ASM Checks Start++++++++++
Thread-14] 2010-01-28 13:51:34.612 NZDT ] CompManager.isModeSet:9243] DB Upgrade Mode Setting := 1
Thread-14] 2010-01-28 13:51:34.613 NZDT ] CompManager.isModeSet:9244] Mode := 1 is set
Thread-14] 2010-01-28 13:51:34.613 NZDT ] SQLEngine.reInitialize:730] Reinitializing SQLEngine...
Thread-14] 2010-01-28 13:51:34.613 NZDT ] OracleHome.getVersion:877] OracleHome.getVersion called. Current Version: 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.614 NZDT ] OracleHome.getVersion:943] Current Version From Inventory: 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.614 NZDT ] OracleHome.getVersion:948] using sqlplus: /u04/app/oracle/product/10.2.0/db_1/bin/sqlplus
Thread-14] 2010-01-28 13:51:34.614 NZDT ] OracleHome.getVersion:877] OracleHome.getVersion called. Current Version: 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.615 NZDT ] OracleHome.getVersion:943] Current Version From Inventory: 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.615 NZDT ] OracleHome.getVersion:948] using sqlplus: /u04/app/oracle/product/10.2.0/db_1/bin/sqlplus
Thread-14] 2010-01-28 13:51:34.615 NZDT ] OracleHome.getVersion:877] OracleHome.getVersion called. Current Version: 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.616 NZDT ] OracleHome.getVersion:943] Current Version From Inventory: 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.616 NZDT ] OracleHome.getVersion:948] using sqlplus: /u04/app/oracle/product/10.2.0/db_1/bin/sqlplus
Thread-14] 2010-01-28 13:51:34.616 NZDT ] SQLPlusEngine.getCmmdParams:222] m_home 10.2.0.4.0
Thread-14] 2010-01-28 13:51:34.616 NZDT ] SQLPlusEngine.getCmmdParams:223] version > 112 false
Thread-14] 2010-01-28 13:51:34.617 NZDT ] SQLEngine.getEnvParams:547] Default NLS_LANG: AMERICAN_AMERICA.AL32UTF8
Thread-14] 2010-01-28 13:51:34.617 NZDT ] SQLEngine.getEnvParams:557] NLS_LANG: AMERICAN_AMERICA.AL32UTF8
Thread-14] 2010-01-28 13:51:34.618 NZDT ] SQLEngine.initialize:317] Execing SQLPLUS/SVRMGR process...
Thread-14] 2010-01-28 13:51:34.659 NZDT ] SQLEngine.initialize:354] m_bReaderStarted: false
Thread-14] 2010-01-28 13:51:34.660 NZDT ] SQLEngine.initialize:358] Starting Reader Thread...
Thread-14] 2010-01-28 13:51:34.666 NZDT ] SQLEngine.initialize:407] Waiting for m_bReaderStarted to be true
Thread-14] 2010-01-28 13:51:34.823 NZDT ] CompManager.asmUpgradeFeasible:9419] Databases uses ASM? :=true
Thread-14] 2010-01-28 13:51:34.835 NZDT ] HAUtils.getHASHome:583] Oracle home from system properties: /u04/app/oracle/product/11.2.0/dbhome_1
Thread-14] 2010-01-28 13:51:34.836 NZDT ] HAUtils.getCRSHome:540] Getting configured CRS/HAS home for Oracle home ( /u04/app/oracle/product/11.2.0/dbhome_1 ) ...
Thread-14] 2010-01-28 13:51:34.836 NZDT ] GETCRSHOMEUtil.<init>:76] Toolname: getcrshome --- Tool location: /u04/app/oracle/product/11.2.0/dbhome_1/srvm/adminTool dependencies: Ljava.lang.String;@1d6f122
Thread-14] 2010-01-28 13:51:34.837 NZDT ] NativeSystem.isCmdScv:471] isCmdScv: cmd=]
Thread-26] 2010-01-28 13:51:34.883 NZDT ] StreamReader.run:61] In StreamReader.run
Thread-25] 2010-01-28 13:51:34.885 NZDT ] StreamReader.run:61] In StreamReader.run
Thread-14] 2010-01-28 13:51:34.889 NZDT ] CmdToolUtil.doexecute:372] nativeSystem.runRemoteExecCmd failed. Command = /u04/app/oracle/product/11.2.0/dbhome_1/srvm/admin/getcrshome arguments = ] env = null
Thread-14] 2010-01-28 13:51:34.890 NZDT ] ASMUtils.initialize:184] Error initializing ASMUtils: PRCT-1011 : Failed to run "getcrshome"
PRCT-1011 : Failed to run "getcrshome"
at oracle.cluster.deployment.ClusterwareInfo.getConfiguredCRSHome(ClusterwareInfo.java:423)
at oracle.sysman.assistants.util.hasi.HAUtils.getCRSHome(HAUtils.java:544)
at oracle.sysman.assistants.util.hasi.HAUtils.getHASHome(HAUtils.java:604)
at oracle.sysman.assistants.util.asm.ASMUtils.initialize(ASMUtils.java:157)
at oracle.sysman.assistants.util.asm.ASMUtils.getASMUtils(ASMUtils.java:137)
at oracle.sysman.assistants.dbma.backend.CompManager.asmUpgradeFeasible(CompManager.java:9424)
at oracle.sysman.assistants.dbma.backend.CompManager.doPreMigrationChecks(CompManager.java:2606)
at oracle.sysman.assistants.dbma.backend.CompManager.obtainDatabaseInformation(CompManager.java:3749)
at oracle.sysman.assistants.dbma.ui.DatabasesPage.doProcessing(DatabasesPage.java:792)
at oracle.sysman.assistants.util.WaitDialog.run(WaitDialog.java:187)
at java.lang.Thread.run(Thread.java:595)
Caused by: PRCT-1011 : Failed to run "getcrshome"
at oracle.cluster.cmdtools.CmdToolUtil.doexecute(CmdToolUtil.java:376)
at oracle.cluster.cmdtools.CmdToolUtil.execute(CmdToolUtil.java:324)
at oracle.cluster.cmdtools.GETCRSHOMEUtil.getCRS_HOME(GETCRSHOMEUtil.java:122)
at oracle.cluster.cmdtools.GETCRSHOMEUtil.getCRS_HOME(GETCRSHOMEUtil.java:100)
at oracle.cluster.deployment.ClusterwareInfo.getConfiguredCRSHome(ClusterwareInfo.java:420)
... 10 more
Thread-14] 2010-01-28 13:51:34.892 NZDT ] ASMUtils.validateASMInstance:237] clusterware/siha home not found
Thread-14] 2010-01-28 13:51:34.893 NZDT ] CompManager.asmUpgradeFeasible:9431] validateASM exception Grid Infrastructure or Clusterware home not found. ASM should be running under this home.
AWT-EventQueue-0] 2010-01-28 13:51:59.113 NZDT ] SQLEngine.done:2148] Done called
Edited by: stuartu on Jan 29, 2010 9:37 AM
Edited by: stuartu on Jan 29, 2010 9:45 AM

ORA-39070 Error when using datapump and writing to ASM storage

I am able to export data using datapump when i write to a file system. However, when i try to write to an ASM storage, i get the following errors.
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
below are the steps i tooks.
create or replace directory jp_dir2 as '+DATA/DEV01/exp_dir';
grant read,write on directory jp_dir2 to jpark;
expdp username/password schemas=testdirectory=jp_dir2 dumpfile=test.dmp log=test.log
Edited by: user564785 on Aug 25, 2011 6:49 AM

google: expdp ASM
first hit:
http://asanga-pradeep.blogspot.com/2010/08/expdp-and-impdp-with-asm.html
"Log files created during expdp cannot be stored inside ASM, for log files a directory object that uses OS file system location must be given. If not following error will be thrown
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
"

What are the caveats of using ASM as storage for RMAN backupsets?

Hello all,
We are currently evaluating RAC as our standard database platform. Until now we have been using 10g single instance with ASM for datafiles and local filesystems for RMAN backupsets and archivelogs. We chose to use local fileystems for backup components so that we can utilize a Tivoli filesystem backup in order to secure the backup pieces to tape.
With RAC, we are looking into a shared location for backupsets and archivelogs. OCFS2 is out of the picture due to it not functioning on top of linux LVM. It appears that our only "shared" option is to use ASM for backupsets and archivelogs.
My concern is that while the data diskgroups and rman diskgroups will be separate, they are both running on ASM and therefore if ASM fails or is corrupted, we have nothing. My current plan is to utilize the Tivoli RMAN MML (TDPO) to backup the backupsets to tape after the ASM backupset has completed.
What experiences have been had with using ASM for RMAN backups?
Any advice on additional protection we can employ to ensure that the database remains recoverable?
Thanks in advance,
David

I've personally haven't implemented RMAN with ASM, but you may want to review Faster Backup, Faster Recovery which discusses RMAN utilizing ASM.
And although you may not get any of the negative aspects from these presentations, you may want to check out High Availability Customer Case Studies, Presentations, Profiles, Analyst Reports, and Press Releases.
Hope this helps!

How to check my Oracle dbms is using ASM for storage?

Thanks.

On unix first check whether you have any ASM instance or not by:
ps -ef | grep pmon
It will show you an entry similar to:
oracle 6953 1 0 Jun24 ? 00:00:07 asm_pmon_+ASM
which means you are having ASM instance on the box, next to find out whether a DB is using it or not login to that DB and issue (from sqlplus):
SQL>select name from v$datafile;
If any of the datafile path is starting from a "+" sign it means you are using ASM diskgroup for that file.
You can also issue:
show parameter db_recovery_file_dest
to check if the flashback area of your database is sitting on ASM or not.
Daljit Singh

Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
Here is the rman restore script:
run
set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
set until sequence 60298 thread 2;
restore database;
switch datafile all;
recover database;
Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
1. The restore output shows this:
creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /ora01/db/ehr/system01.dbf
restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
restoring datafile 00005 to /ora01/db/ehr/users01.dbf
restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
After the datafiles are restored the "switch datafile all" command fails:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch command at 10/18/2010 13:58:37
ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
So my question is how do I get this database restored to non-ASM (and non omf)?

So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
Here is the output of "list backup":
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
19724 41.12M DISK 00:00:10 14-OCT-10
BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
List of Archived Logs in backup set 19724
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
19725 Full 126.40G DISK 09:11:51 15-OCT-10
List of Datafiles in backup set 19725
File LV Type Ckp SCN Ckp Time Name
1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
Backup Set Copy #1 of backup set 19725
Device Type Elapsed Time Completion Time Compressed Tag
DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
List of Backup Pieces for backup set 19725 Copy #1
BP Key Pc# Status Piece Name
65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
BS Key Size Device Type Elapsed Time Completion Time
19726 228.10M DISK 00:00:49 15-OCT-10
BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
List of Archived Logs in backup set 19726
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

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?

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....

Using ASM in Oracle 10g

Hi all,
I'd like to learn using ASM (Automatic Storage Management) feature in Oracle 10g using a single PC. As far as I know, I need hardware of disk array.
Is it possible to use ASM feature in Oracle 10g in a normal PC? or by using the normal IDE harddisk? or by using external USB hardisk? or by using any software emulator?
I would highly appreciate any guideline.
Thanks in advance.
Ahmed B.

You can find the for windows also on the same site. Below is the link:
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_22.shtml

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

Trouble using asm instance for new database

I have an asm instance and am trying to create a new database that will use the asm storage. I'm using dbca to create the new database. This is a test system on windows so I'm using the asmtool -create flatfiles for disks with the asmallow_only_raw_disks parameter set to false.
If I have #SQLNET.AUTHENTICATION_SERVICES = (NTS) commented out in my sqlnet.ora, then I can't get into asmcmd:
ORA-01031: insufficient privileges (DBD ERROR: OCISessionBegin)
and dbca won't create the new database that uses asm because the dbca gets the same 01031 error when trying to create the control files for that database.
If I have SQLNET.AUTHENTICATION_SERVICES = (NTS) NOT commented out, the I can get into asmcmd, but I can't startup the databases using sys, even though I am sitting at the server,
AND, dbca won't create the new database that uses asm becuase the dbca can't start the instance
credential retrieval failure.
I'm in a catch 22. Something is not right with my system but I just can't seem to figure out what it is.
The asm instance does have a password file.

I let the dbca create scripts and am currently walking through the scripts. I think it's my asm database that is actually creating the problem. I did the orapwd and oradim manually and can startup nomount the instance just fine. The create database statement fails on creating the controlfile but it's saying it already exists. I suspected the dbca form wasn't giving me all the errors like it should.
Thanks for your suggestion on the password file.

DB Using ASM Storage (Spfile)

Similar Messages

Maybe you are looking for