ASM Storage

Hi,
I have ASM on linux. I take backup of the database. I have a another database installed on Windows system, using ASM.
Can I use the backup taken on linux, in the windows machine?
Thanks

804656 wrote:
Hi,
I have ASM on linux. I take backup of the database. I have a another database installed on Windows system, using ASM.
Can I use the backup taken on linux, in the windows machine?
No! Just the ASM being installed doens't mean that you can share the files on one o/s over the other as the files are going to be created based on the Endian format which would be specific to the o/s - either it would be Big or Small endian. So you just can't take files from Linux and use them as it is on Windows(as an example) if both share different formats of Endian. Look at the MOS notes mentioned and read about the Convert Database command to do a cross platform migration.
Aman....

Similar Messages

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

Migrated the database to ASM storage .

Hi friends,
I have migrated the database from 10g(non-asm) to 11g ASM storage on solaris machine. I am facing database slowness after the database upgrade.I don't find any problem in the ADDM/AWR report.
Could you please suggest me whether anything needs to check?
Regards
Rocky

Can you run ADDM from the dbconsole?
Also you can run sql tuning advisor.
However, its worth checking your diskgroups.
Can you post Mountpoints defined in /etc/vfstab ?

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.

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
"

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

Oracle 10g RAC+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 ??

Hi,
If you create a new diskgroup you may be to add the same diskgroup to parameter file or spfile and which will be needing down time.
sugestion: Instead of creating new diskgroup you should to add disk to existing group.if you add asm disk to existing group your all problem will be solved and Oracle itself will be managing all.And than i am sure no need to add entry in the parameter or spfile like +db_create_file_dest=.....
regards,
Sher khan

Asm storage doubts

hi all,
In our test env we have two database in a node with only one disk group which stores around 1.5 TB of data files.
* Is that a good practice to store two DB data files in the same disk group.
* If it is in same disk group what happens when we restore a db for cloning.
a. Is that asm scans all the disks to find a free space to store the data during restore.( I do see it takes 15 hours for restoring a 800GB of a single DB data files with 6 channels specified in restore command)
*During mount stage it takes long time to open the database. Is that asm scans the entire diskgroup to match the physical structure of the files with control file.
*During restore or opening up the database there is absolutely no load on the server.
SQL> select GROUP_NUMBER,DISK_NUMBER,TOTAL_MB,FREE_MB,READS,WRITES,READ_TIME,WRITE_TIME from V$ASM_DISK;
GROUP_NUMBER DISK_NUMBER   TOTAL_MB    FREE_MB      READS     WRITES READ_TIME WRITE_TIME
           2           5     153593       6238   61237253    3255630 1606217.37 317411.015
           2           6     153593       6248   62021450    3113196 1615818.5 300858.424
           2           7     153593       6234   60130864    3145717 1602473.04 309295.707
           2           8     153593       6253   63976632    3504263 1612983.03 325407.467
           2           0     153597       6254   61040136    3484440 1618972.86 287943.441
           2           1     153597       6268   64525211    3182327 1644359.02 295506.291
           2           2     153597       6238   64116126    4290514 1604709.78 372315.757
           2           3     153597       6277   65550559    3145245 1633260.86 289411.098
           2           4     153593       6246   62872224    3744320 1639207.33 313410.323
           2           9     153593       6248   62781328    3077681 1636946.1 295827.542Please advice on the above.
thanks,
baskar.l

*Is that a good practice to store two DB data files in the same disk group.Yes it is. In fact this is recommended by oracle. Oracles recommendation goes towards TWO disk groups: one for ALL database and one used as flash (or fast) recovery area.
* If it is in same disk group what happens when we restore a db for cloning.Your database will be restored there. Space is managed as a bitmap. Of course ASM has to look for free space to store the data.
. Is that asm scans all the disks to find a free space to store the data during restore.( I do see it takes 15 hours for restoring a 800GB of a single DB data files with 6 channels specified in restore command)As mentioned above: Space is managed in a bitmap structure, thus highly compact and fast.
Your restore time will be entirely dominated by getting the data from tape and save it to the disks. "Finding" free space will be less than 1% of that time.
*During mount stage it takes long time to open the database. Is that asm scans the entire diskgroup to match the physical structure of the files with control file.Either you are starting a database which was not shut down in a clean way (e.g. "shutdown abort" used to shutdown the database) or you have a lot of files. Or the storage system is slow or overloaded and so on. But asm does not scan the entire diskgroup in any way.
*During restore or opening up the database there is absolutely no load on the server.What about your storage subsystem? Did you check load there? Are the disks shared between LUNs?
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de
Edited by: Ronny Egner on Mar 31, 2010 12:12 PM

Database creation fail in ASM Storage

Hi,
In Suse Linux, we installed the Grid Infra Standalone Server & Database. After ASM Instance started, in ASM instance v$asm_diskgroup shows the DATA diskgroup was mounted. But from Database Instance when we query the v$asm_diskgroup show "no row selected".
When i try to create database using DBCA or manualy creation i'm getting following error.
ORA-01501: Create Database Failed
ORA-00200: Control file could not be created
ORA-00202: Control file : '+DATA'
ora--17502: ksfdcre:4 Failed to create file '+DATA'
ora--15055: unable to connect to ASM instance
ora-27140: attach to post/wait facility failed
ora-27300: OS system dependent operation: invalid_egid failed with status: 1
ora-27301: OS failure message: Operation not permitted
with Regards,
Baalaji V

Did you install Grid infra as Oracle user or different user?
In case of different user, does oracle user and grid infra should share same admin group.
This is what I did on OLE 5.0
# groupadd -g 1000 oinstall
# groupadd -g 1100 asmadmin
# groupadd -g 1200 dba
# groupadd -g 1201 oper
# groupadd -g 1300 asmdba
# groupadd -g 1301 asmoper
# mkdir –p /u01/apps/grid
# mkdir -p /u01/apps/oracle
# useradd -u 1100 -g oinstall -G dba,asmdba,asmoper -d /home/grid grid
# useradd -u 1001 -g oinstall -G dba,asmadmin,asmdba,asmoper -d /home/oracle oracle
# chown -R grid:oinstall /u01/apps/grid
# chmod -R 775 /u01
# chown oracle:oinstall /u01/apps/oracle
as GRID user I had installed Grid Infra and created ASM instance and as ORACLE user I had created a database. One more thing listener is running under Grid Infra not under Oracle RDBMS.
Even after this I did get some permission issue not able to access orainventory etc., but then what was fixed then and there.
Hope this helps.
rdgs,
Kamalesh JK
jkkstar inc

Error with dbca -silent ASM storage type

dbca -silent -createDatabase -templateName General_Purpose.dbc \
-gdbName $LOWER_SID -sid $LOWER_SID \
-sysPassword P1casso -systemPassword P1casso \
-sysmanPassword P1casso -dbsnmpPassword P1casso -asmsnmpPassword P1casso \
-emConfiguration LOCAL \
-storageType ASM -diskGroupName DATA_DM01 \
-totalMemory 1024 -automaticMemoryManagement true \
-nodeinfo dm01db01,dm01db02 -characterset AL32UTF8 -nationalCharacterSet AL16UTF16 \
-obfuscatedPasswords false -sampleSchema true \
-oratabLocation /etc/oratab
I get the following error
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '+DATA_DM01/test2/system01.dbf'
ORA-17503: ksfdopn:2 Failed to open file +DATA_DM01/test2/system01.dbf
ORA-15001: diskgroup "DATA_DM01" does not exist or is not mounted
ORA-15204: database version 11.2.0.0.0 is incompatible with diskgroup DATA_DM01
Please can I know what the problem or what parameter setting are missed

user5846399 wrote:
dbca -silent -createDatabase -templateName General_Purpose.dbc \
-gdbName $LOWER_SID -sid $LOWER_SID \
-sysPassword P1casso -systemPassword P1casso \
-sysmanPassword P1casso -dbsnmpPassword P1casso -asmsnmpPassword P1casso \
-emConfiguration LOCAL \
-storageType ASM -diskGroupName DATA_DM01 \
-totalMemory 1024 -automaticMemoryManagement true \
-nodeinfo dm01db01,dm01db02 -characterset AL32UTF8 -nationalCharacterSet AL16UTF16 \
-obfuscatedPasswords false -sampleSchema true \
-oratabLocation /etc/oratab
I get the following error
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '+DATA_DM01/test2/system01.dbf'
ORA-17503: ksfdopn:2 Failed to open file +DATA_DM01/test2/system01.dbf
ORA-15001: diskgroup "DATA_DM01" does not exist or is not mounted
ORA-15204: database version 11.2.0.0.0 is incompatible with diskgroup DATA_DM01
Please can I know what the problem or what parameter setting are missedwhat about ur asm instance. Is it started??
$ export ORACLE_SID=+ASM1
$ sqlplus / as sysdba
SQL> select group_number, name, value from v$asm_attribute;
SQL> select name, COMPATIBILITY, DATABASE_COMPATIBILITY from v$asm_diskgroup;
if your compatible on diskgroups be "10.1" or "10.2", you can change to 11.2
SQL> alter diskgroup DATA set attribute 'compatible.asm'='11.2';
Hope this may help you
--neeraj

RMAN configuration (ASM Storage) 10g

hi
i am looking for a RMAN script which can
1. online backup the database to tape for ASM DISKGROUP
2. How can an incremental backup be taken for nologging objects (DWH)
3. can we configure 10g BCT for online tape backup (incremental)
4. how can we refresh the Production ASM database to staging (ASM) like cloning methods
thanks in advance

Hi Shakil,
hi
i am looking for a RMAN script which can
1. online backup the database to tape for ASM DISKGROUP
run {
allocate channel t1 type 'SBT_TAPE' parms="ENV=(BLKSIZE=1048576)";
send 'NB_ORA_POLICY=YOUR_POLICY, NB_ORA_SCHED=YOUR_SCHEDULE, NB_ORA_SERV=YOUR_SERVER';
backup
incremental level 0
skip inaccessible
tag online_backup_level0
filesperset 20
format 'full_online_%d_s%s_p%p_t%t' (database)
plus archivelog tag archived_logs
format 'arch_dia_%d_s%s_p%p_t%t'
include current controlfile tag control_file
format 'ct_file_%d_s%s_p%p_t%t';
release channel t1;
resync catalog;
EOF
2. How can an incremental backup be taken for nologging objects (DWH)
Incremental Backup Algorithm
Each data block in a datafile contains a system change number (SCN), which is the SCN at which the most recent change was made to the block. During an incremental backup, RMAN reads the SCN of each data block in the input file and compares it to the checkpoint SCN of the parent incremental backup. (If block change tracking is enabled, RMAN does not read the portions of the file known to have not changed since the parent incremental backup.) If the SCN in the input data block is greater than or equal to the checkpoint SCN of the parent, then RMAN copies the block.
One consequence of this mechanism is that RMAN applies all blocks containing changed data during recovery—even if the change is to an object created with the NOLOGGING option. Hence, making incremental backups is a safeguard against the loss of changes made by NOLOGGING operations.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1011469
3. can we configure 10g BCT for online tape backup (incremental)
Yes you can.
4. how can we refresh the Production ASM database to staging (ASM) like cloning methods
Yes you can.
thanks in advance
Regards,
Rodrigo Mufalani

Strange .nfs file in ASM storage

Hello
I'm using ASM in a RAC environment over NFS. I've noticed that where I've raw files for ASM I've also some .nfsXXXXXXXxx files:
[oracle@itsm-cldb1c oradata]$ ls -al
total 29417868
drwxrwxrwx 3 root root 4096 Aug 28 11:31 .
drwxr-xr-x 27 root root 4096 Aug 27 19:20 ..
drwxr-x--- 2 oracle oinstall 4096 Aug 28 08:58 dbs
-rw-r--r-- 1 oracle oinstall 10737418240 Aug 28 10:36 .nfs0011a52600000001
-rw-r--r-- 1 oracle oinstall 5368709120 Aug 28 11:21 .nfs0011a52700000002
-rw-r--r-- 1 oracle oinstall 4294967296 Aug 28 11:40 tdwdisk1
-rw-r--r-- 1 oracle oinstall 4294967296 Aug 28 11:40 tdwflash1
-rw-r--r-- 1 oracle oinstall 5368709120 Aug 28 11:39 tdwstorage1
[oracle@itsm-cldb1c oradata]$ rm -rf .nfs0011a52*
rm: cannot remove `.nfs0011a52600000001': Device or resource busy
rm: cannot remove `.nfs0011a52700000002': Device or resource busy
And these files are busy. Anyone knows what kind of files are them?
Thanks
Stefano

This usually happens if you are using NFS...and I think you are using NFS. If you remove a file that is currently/actively being used or open by running process , the file isn't really removed and it would manifest itself as a .nfsxxxx files.
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

Storage Grid - One Large Shared ASM Pool

Gurus,
We're looking into options/methods to take advantage of the "storage grid". We want to create a large diskgroup for data and fra and have these accessible to all our lower region servers (dev, qa, ...). These servers are all non-rac and non-clustered.
Is this concept possible without installing Oracle Clusterware?
If clusterware is required, it requires an additional NIC for the private network, since this is a non-production environment we are discussing the possibility to assign both public and private IPs to the same nic (save some hardware $$). Since we'd never failover b/c we are not running RAC, do you see any issues running this way? Or is there another way to share storage between many nodes?
TIA

I believe you are going to have to at least cluster the ASM. Each machine sharing the ASM storage will need an ASM instance that contains your large diskgroups.

How to Create Manual Standby for a Oracle 11g RAC with ASM to Single Instan

Hi All,
I have a task to configure a Single Instance Standby Database with ASM for 2-node Primary RAC+ASM database.
Version using : 11.1.0.6 Oracle 11g --- *" STANDARD EDITION "* Please note datagaurd will not be supported in standard edition.
Primary database - 2 -Node RAC using ASM storage (All datafiles, redologs, controfile and archive logs)
Need to setup a single instance standby database manually and than using scripts to transfer the archive logs from primary server to standby server to do recovery time to time.
Please let me know if there are any configuration document(s) which can help me to set the manual standby? or need your kind help to give your valuable ideas how to go in above situation.
Thanks in advance

Niall Litchfield wrote:
El DBA wrote:
Well if the archive logs are stored in ASM on the primary nodes, you almost definitely want to be using RMAN to access them. Then to transfer between primary and standby there are many options, this is essentially the step that Data Guard takes care of - so if you (and I) are running Standard Edition, this is the part to "worry" about.
I'm not really sure what you mean by this:
As in standard edition the archive destination will be on ASMI don't think the Edition of Oracle (Standard or Enterprise) dictates where and how you store your archive logs, but it's possible I've misunderstood what you mean...SE dictates that database storage for RAC will be ASM, including archive log files. Anything else is not officially supported. I haven't tested but it may be that you can use LOG_ARCHIVE_DUPLEX_DEST to specify a local filesystem for archive log files as well.
If that doesn't work you'll have to script rman "backup as copy" jobs regularly and then transport the results of that.
Niall Litchfield
http://www.orawin.info/
By the way, it seems Robert has been pretty helpful, it's polite to give him some points dude. And since this is your thread, not mine, give him a "helpful" from me too :p
El DBA
Incidentally if you are forced down the RMAN backup as copy route then this will likely throw your current backup retention strategy somewhat, you'll need to think carefully about when an archivelog can be deleted following backup, how many times it might be backed up and so on. I do understand, and have argued for, the use of SE RAC. I also understand and have argued for and implemented manually managed standby a number of times. However by the time your primary database is a RAC instance and you need a standby for DR etc then you really have to look very seriously at whether Standard Edition is still the right investment or not. You will be spending a lot of DBA time managing and troubleshooting this, and you will find that it is less reliable than the off the shelf solution. I suspect that you are very close to the point where an EE installation becomes a worthwhile investment here.
Niall Litchfield
http://www.orawin.info/

ASM Storage

Similar Messages

Maybe you are looking for