Standby Database ASM Disk Groups

Hi Guys
I wonder if anyone can tell me - does a standby database have to have an identical configuration for its ASM Disk Groups?
My production database has two disk groups, one for data and the other for temp. Can I get away with a single diskgroup in my standby database or would I need two of the same name as the production database?
Cheers
Simon

Hi Saml
I have been busy googling at the same time as discussing this and it would appear that it will use the db_file_name_convert:
http://asanga-pradeep.blogspot.com.au/2012/07/11gr2-standalone-data-guard-with-asm.html
The link above shows the output of someones RMAN session where the OMF names are changed automatically. Problem is that some people are recommending that the parameter not be used, so now I am really confused!
I think I will try the parameter, if it doesnt work or the duplicate fails I will drop the temp table space in production and then do the duplicate, then recreate the temp tablespace. I can do that because there will be no one on the system on Sunday when I do it.
Thanks again for your help - I will let you know how it goes.
Ragards
Simon

Similar Messages

ASM disk group and multiple databases

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

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

RE: Creation of two oracle database in Single ASM Disk group

IS it possible to create two oracle database in Single ASM Disk group. if it is possible how?.
Giri

All you have to do is to create a tablespace at the most minimumlevel and your db would become a client of the disk group. Other than that, you can migrate your db tothe disk group and it would be then start using the same disk group shared by another database for its use also.
HTH
Aman....

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

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

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

DBCA did not see the ASM disk group in NODE 2 but see in NODE 1

Are there anyone who encountered creating a database using DBCA with ASM as file system?
Our issue before is in both nodes the DBCA did not see the ASM disk group.
But after setting the TNS_ADMIN in both nodes and running the DBCA as administrator in Node 1, the DBCA able to see now the ASM disk group. Unfortunately, in Node 2 it didn't work out?
So we didn't know why is it from Node 2, the DBCA still didn't see the ASM disk group?Since it is both the same.
Any ideas? Please advise.
For you information, we are using Windows 64-bit, Oracle 11g R2
Thank you in advance for those who will respond.
Edited by: 822505 on Dec 20, 2010 7:47 PM

822505 wrote:
Are there anyone who encountered creating a database using DBCA with ASM as file system?
Our issue before is in both nodes the DBCA did not see the ASM disk group.
But after setting the TNS_ADMIN in both nodes and running the DBCA as administrator in Node 1, the DBCA able to see now the ASM disk group. Unfortunately, in Node 2 it didn't work out?
So we didn't know why is it from Node 2, the DBCA still didn't see the ASM disk group?Since it is both the same.
Any ideas? Please advise.
For you information, we are using Windows 64-bit, Oracle 11g R2
Thank you in advance for those who will respond.
Are the disks given to the ASM are visible from Node2?
Aman....

EM Alert: Warning:+ASM Disk Group requires rebalance

Environment:
O.S Version : HP-UX B.11.31 U ia64
Oracle DB Version : 11.2.0.3.0 , Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Database files are on : ASM Disk Group
It is about the ASM Diskgroup low disk space alert by Oracle Enterprise Manager.
Message=Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space.
Metric=Disk Minimum Free (%) without Rebalance
Metric value=18.961548
Disk Group Name=DG_FLASH_01
Severity=Warning
Target Name=+ASM_dbsrver.siva.com
Target type=Automatic Storage Management
There is only 1 LUN assigned to this diskgroup +DG_FLASH_01_.
We have a Oracle Enterprise Manager Grid Control Job MN_DBSRVR_DEL_ARCHIVELOGS runs every 12 hours by 1 AM and again at 1PM daily. It cleans-up the archivelogs older than 3 days old. The FLASH diskgroup is continuously being written with new files for both archivelogs and flashback logs.
If there was multiple disks and a vast difference between the files on the different LUNs then a rebalance would be good to run.
How to address such recurring alert of " *Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space*. " with _only one LUN on the +ASM Diskgroup_?

As I stated earlier there is only one disk on this diskgroup
DISK_NUMBER      OS_MB   TOTAL_MB    FREE_MB NAME                           PATH
          0      65536      65536      12995 DG_FLASH_01_0000        /devasm/gc/ora_asm_gc_b03_a14_d10_08_36
          0      65536      65536      43064 DG_DATA_01_0000         /devasm/gc/ora_asm_gc_b03_a13_d12_08_35So disk REBALANCE not required
Edited by: Sivaprasad S on Feb 14, 2013 11:46 PM

Oracle ASM disk group

Hi,
Having a multiple Oracle ASM disk group is more beneficial for Oracle database? if no why? if yes why?
Any metalink note if have.
thanks

Any metalink note do you refer?What is your database version?
Please see these docs.
11g ASM New Feature [ID 429098.1]
ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
Thanks,
Hussein

Share an ASM disk group among multiple nodes

According to Oracle documentation:
*“To share an ASM disk group among multiple nodes, you must install Oracle Cluster ware on all of the nodes, regardless of whether you install Oracle RAC on the nodes”.*
And if I understand it right to share the same ASM storage group from multiple nodes from separate RACs or multiple non-RAC nodes ASM instances in those nodes need to communicate to synchronize ASM related metadata using same technique like cache fusions.
My question is how this ASM communication take place among different ASM instances located in different RACs and standalone servers. Do we have to have some kind of Interconnect settings among the nodes?

Hi,
ASM and database instances require shared access to the disks in a disk group. ASM instances manage the metadata of the disk group and provide file layout information to the database instances.
ASM instances can be clustered using Oracle Clusterware; there is one ASM instance for each cluster node. If there are several database instances for different databases on the same node, then the database instances share the same single ASM instance on that node.
If the ASM instance on a node fails, then all of the database instances on that node also fail. Unlike a file system failure, an ASM instance failure does not require restarting the operating system. In an Oracle RAC environment, the ASM and database instances on the surviving nodes automatically recover from an ASM instance failure on a node.
see this link
http://download.oracle.com/docs/cd/B28359_01/server.111/b31107/asmcon.htm :)

How to move or migrate whole directories between ASM disk groups?

Hello everyone!
I'm playing around with Oracle ASM and Oracle Database (11g R1), I'm a student. This is just for testing purposes.
Computer specifications are:
Processor: Intel Pentium 4 HT 3.00 Ghz.
RAM Memory: 2 GB.
Hard Disk: 250 GB
O.S.: Windows XP Professional Edition SP 2.
I installed Oracle ASM, I created an ASM disk group (+FRA), I installed Oracle Database and I created a testing database. The database is working properly over the ASM disk group. Days ago, I got help about the initialization parameters DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_1, DB_CREATE_ONLINE_LOG_DEST_2 and DB_RECOVERY_FILE_DEST, based on their function, I created another 3 ASM disk groups (+FILES, LOG1, LOG2). Currently, the four initialization parameters are pointing to its corresponding ASM disk group. As you can deduce, at the installation moment of the Oracle Database I used the ASM disk group "+FRA" and inside it were created the directories: CONTROLFILE, DATAFILE, ONLINELOG, PARAMETERFILE, TEMPFILE and the SPFile.
My point is I wanna move or migrate the directories DATAFILE, PARAMETERFILE, TEMPFILE and the SPFile to "+FILES", ONLINELOG and CONTROLFILE to "+LOG1" and "+LOG2", this way, the ASM disk group "+FRA" will contain the Flash Recovery Area only. What is the procedure to do this?
Thanks in advance!

user1987306 wrote:
Hello everyone!
My point is I wanna move or migrate the directories DATAFILE, PARAMETERFILE, TEMPFILE and the SPFile to "+FILES", ONLINELOG and CONTROLFILE to "+LOG1" and "+LOG2", this way, the ASM disk group "+FRA" will contain the Flash Recovery Area only. What is the procedure to do this?
Thanks in advance!
Hi,
There are couple of approaches you can use, here is some of them
- To move datafile, start the database in mount state
RMAN > copy datafile '+FRA/xxx' to '+FILES1';
SQL > alter database rename file '+FRA/xxx' to '+FILES1/xxx';
- To move tempfile
SQL > alter tablespace TEMP add tempfile '+FILES1' SIZE 10M;
SQL > alter database tempfile '+FRA/xxx' drop;
- To move onlinelog
SQL > alter database add logfile member '+LOG1' to group 1;
SQL > alter database add logfile member '+LOG2' to group 1;
SQL > alter database drop logfile member '+FRA/xxx';
- To move controlfile
SQL > restore controlfile to '+FILES1' from '+FRA/xxx';
update the spfile to reflect new location of controlfile
Cheers

ASM DISK groups set up at O/S level

Hi
I am having couple of questions regarding the ASM.
I was given LINUX Server and asked me to create the ASM DISK groups at O/S level.
Oracle version: Oracle 11g realease 2 with ASM and Stand alone server
O/S: Redhat Lilnux with 64 bit
1.Unix admin has already given the server and gave me the root access also.Now I need to map/set up the ASM DISK groups manually and create them at the O/S level and then INSTALL the ASM software.
a)We are using the asmlib for mapping at o/s level.Can any body give the command to know whether asmlib was installed on the Linux server.
b)How to see the free Partitions on the Linux server and allot them to ASM disks at O/S level and to create it.
2)Should I use two separate users ie . one for Grid infrastructure(Asm) and other for RDBMS Installation.
Say GRID user for Grid Infrastructure(Asm) and ORACLE user for RDBMS Installation.
If so what is the advantage in using different users for ASM and RDBMS installation respectively.
The grid user is a member of these OS groups :asmdba,asmoper, and asmadmin and not dba group
The oracle user is a member of these OS groups :dba and asmdba groups.
ofcourse grid user and oracle user is also a part of oinstall group.
Please find the url which I picked the above information.
http://levipereira.wordpress.com/2010/11/21/installing-the-grid-infrastructure-for-a-standalone-server/
Thanks in advance
Thanks
Veera

First of all you should be using installation guide from oracle which you can find at ..http://www.oracle.com/pls/db112/portal.portal_db?selected=11&frame=
If so what is the advantage in using different users for ASM and RDBMS installation respectively.There are two things, Grid & Database, Oracle wants to separate the administartion for both software, where users who are DBAs should not be allowed to change ASM stuff and vice-versa.
You can use fdisk command to partition the disks, and use # /usr/sbin/oracleasm createdisk command to create the disk.

Cleaning up ASM disk group after failed rman duplicate session?

I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
Thanks.

Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
SQL> desc v$asm_file
Name Null? Type
GROUP_NUMBER NUMBER
FILE_NUMBER NUMBER
COMPOUND_INDEX NUMBER
INCARNATION NUMBER
BLOCK_SIZE NUMBER
BLOCKS NUMBER
BYTES NUMBER
SPACE NUMBER
TYPE VARCHAR2(64)
REDUNDANCY VARCHAR2(6)
STRIPED VARCHAR2(6)
CREATION_DATE DATE
MODIFICATION_DATE
This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in...

Recover OCR and VOTE disk after complete corruption of ASM disk groups.

Hi Gurus,
I am simulating a recovery situation to perform recover of OCR and Vote files after complete corruption of ASM related disks and diskgroups. I have setup my environment as follows:\
Environment: RAC
OS: OEL 5.5 32-bit
GI Version: 11.2.0.2.0
ASM Disk groups: +OCR, +DATA
OCR, Vote Files location: +OCR
ASM Redundancy: External
ASM Disks: /dev/asm-disk1, /dev/asm-disk2
/dev/asm-disk1 - mapped on +OCR
/dev/asm-disk2 - mapped on +DATA
With the above configuration in place I have manually corrupted +OCR, +DATA diskgroups with dd command. I used this command to completely corrupt +OCR disk group.
dd if=/dev/zero of=/dev/asm-disk1. I have manual backups as well as automatic backups of OCR and Vote disk. I am not using ASMLib.
I followed this link:
http://docs.oracle.com/cd/E11882_01/rac.112/e17264/adminoc.htm#TDPRC237
When I tried to recover OCR file, I could not do so as there is no such diskgroup which ASM can restore the OCR, Voting disk to. I could not Re-create OCR and DATA diskgroups as I cannot connect to ASM instance. If you have a solution or workaround for my situation please describe it. That will be greatly appreciated.
Thanks and Regards,
Suresh.

Please go through the following document which have the detailed steps to restore the OCR
How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems [ID 1062983.1]

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

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

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

Can not find disks when creating ASM disk group (11.0.2.3 on OEL 6)

Hi
I`m trying to install 11.0.2.3 Grid on OEL6.
Every thing is fine until it prompt to ask where I want to put OCR and VOTING DISK. I choose to put them in ASM. So it prompt another window to ask create ASM DISK GROUP.
In this window there was an area called "add disk". There suppose to be some disks listed in this area to chose. But in my case, nothing here. I can not chose disks to add to ASM DISK GROUP.
Below are descriptions of my installation.
Oracle Grid 11.0.2.3
OEL 6 as the platform.
I use two nodes mounting the same NFS. I created some zero-padded files on the NFS directory as the ASM DISKS. (This disks should be showing the the area above)
I install everything using only one account oracle. The group is oinstall and dba
Edited by: Kramer on Jun 5, 2013 8:52 PM

Well as i see your asm_diskstring could be the problem. ASMlib would have been there isnt it , I would want you to stick to default value and then try also I would suggest you to once post the output of the following and lets see whats happening
[root@ora ~]# /etc/init.d/oracleasm scandisks
[root@ora ~]# /etc/init.d/oracleasm listdisks
[root@ora ~]# ls -ltr /dev/oracleasm/disks/*

ASM Disk Group Showing Full at 50%

Hi to all,
I have two sets of ASM disk groups, one I use for the main datafiles and the other I use for recovery.
The datafile ASM group is at 65% capacity. The Other "Recovery" Disk group became full at 50%, exactly half the size?!
Why does the group perform like this. It should be full when the disks are full? And why does the other group perform normally?
Has anyone else seen this problem before with ASM groups.
If anyone needs any more details please just ask me a question about it.
Thanks,
Jamie.

NAME PATH TOTAL_MB FREE_MB % Used DISK_NUMBER REDUNDA
STATE
DATA /dev/mapper/ASM1_V1p 35644 14389
60 9 NORMAL CONNECTED
1
DATA /dev/mapper/ASM14_V1 35644 14381
60 4 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM8_V1p 35644 14416
60 16 NORMAL CONNECTED
1
DATA /dev/mapper/ASM18_V1 35644 14389
60 8 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM16_V1 35644 14363
60 6 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM10_V1 35644 14335
60 0 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM4_V1p 35644 14415
60 12 NORMAL CONNECTED
1
DATA /dev/mapper/ASM15_V1 35644 14403
60 5 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM5_V1p 35644 14369
60 13 NORMAL CONNECTED
1
DATA /dev/mapper/ASM13_V1 35644 14331
60 3 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM2_V1p 35644 14393
60 10 NORMAL CONNECTED
1
DATA /dev/mapper/ASM11_V1 35644 14443
59 1 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM9_V1p 35644 14453
59 17 NORMAL CONNECTED
1
DATA /dev/mapper/ASM17_V1 35644 14401
60 7 NORMAL CONNECTED
p1
DATA /dev/mapper/ASM7_V1p 35644 14443
59 15 NORMAL CONNECTED
1
DATA /dev/mapper/ASM3_V1p 35644 14342
60 11 NORMAL CONNECTED
1
DATA /dev/mapper/ASM6_V1p 35644 14428
60 14 NORMAL CONNECTED
1
DATA /dev/mapper/ASM12_V1 35644 14370
60 2 NORMAL CONNECTED
p1
RECOVERY /dev/mapper/ASM19_V1 139996 139842
0 0 NORMAL MOUNTED
p1
RECOVERY /dev/mapper/ASM22_V1 139996 139842
0 2 NORMAL MOUNTED
p1

Standby Database ASM Disk Groups

Similar Messages

Maybe you are looking for