Link to " Database Storage Consolidation with ASM White Paper " now fixed

I cannot access document "Database Storage Consolidation with ASM White Paper " on http://www.oracle.com/technetwork/database/index-100339.html.
The new link seems also to be broken http://www.oracle.com/technology/products/database/asm/pdf/db_storage_consolidation_wp%2012-05.pdf
Link is now working.
Edited by: P. Forstmann on 21 sept. 2010 08:51
Edited by: P. Forstmann on 21 sept. 2010 08:51

This link has been repaired.
Regards, OTN

Similar Messages

Odbc connection test success but can't link the database to oracle with 1013 call failed error.

i am using my MS Access 2013 to connect with my oracle database. I created the odbc link and successfully have connection test pass. However i can;t link the database with my MS access. When i am using different software (mapinfo), i am able to connect to oracle database. The error is"1013: user requested cancel of current operation"

In MS access, i open the external data and select odbc. Select my odbc link created previously, enter the password and after a while the error message pop up.
But if i am using another tools, such as SQL Developer or Mapinfo, i will able to connect to oracle database using the same odbc link.

Database upgrade - Oracle 10g r2 ,RAC(2 Nodes with ASM) upgrade from HP-UX to RHEL 5.9

Hi All
I am planning to upgrade our RAC database 2 nodes with ASM from HP-UX to RHEL 5.9.
Following is our setup
Current setup:
Oracle Database 10g r2 (10.2.0.5.0) RAC database.
Nodes: 2
Storage: ASM
OS: HP-UX ia64
Database Size: 1.2 TB
New Setup:
Oracle Database 10g r2(10.2.0.5.0) RAC database
Nodes: 2
Storage: ASM
OS: RHEL 5.9 x86 64
Since we are moving from a big endian format to a small endian format(HP-UX to RHEL 5.9) the same ASM cannot be used.
Kindly help me with process and other important documents to be followed.
Thanks.

Hi...
If it was a standlone database concepts like transportable tablespaces, rman would have been convenient.
Since we are using a RAC database with ASM as storage how do we use these techniques specified in NOTE:733205.1
Due to endianness issue we cannot use the same ASM instance.
Along with the new RAC node install a new ASM instance would have to be created.
Kindly help me with migration for RAC with existing ASM to new Hardware
Thanks and Regards

Closet - core routed link. What to do with VLAN1.

I am connecting closets to core over routed links, what do I do with VLAN1? Right now it is enabled with no IP address. Do I do a shut? Leave it up and give it an addres with a 255.255.255.255 mask? Everything seems to be working except for NTP which may not be related.

For security reasons I would disable vlan1, this is Cisco's default vlan. I still would suggest setting up a vlan for management purposes (vlan10 or similar) and give it an IP address so you can remotley manage this device.
Adam

Where can i find the utility source of "Dynamic LOVs" White Paper ?

I downloaded this white paper :-
http://www.oracle.com/technology/products/forms/pdf/10g/community_paper_generic_lov.pdf
and its title is :
Oracle Forms 10g – Dynamic LOVs
The problem here is that I can't find the The utility source :-
• COLORS.PLL
• LOV.PLL
• GEN_LOV.FMB
• INIT_LOV.FMB
• TEST_LOV.FMB
does anyone have any idea where can i find the Source ?!
please i want specific link , not like that exist in the white paper :-
{The utility sources can be downloaded from the Oracle Technology Network (OTN1).}

Francois Degrelle wrote:
On the same page .........Despite fact that I don't know what page you are talking about - because the pdf file that I was talking about I downloaded it directly from Google - but I'm really grateful very much for you Francois.

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

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

How to create database with ASM

HI
How to create database with ASM?
I install vmware workstation on window XP .On virtual machine install Linux 5 enterprise (Oracle) install.
I install oracle DB software only. Also make 3 disk for ASM .
1 -- When I want to install oracle DB with ASM . In this process candidate disks not show . Why?
How I can see disks ..
so I simple install oracle DB software only.
2 -- Now I want to create database with ASM by DBCA .
What process I will follow ?
Please guide me
Thanks

Hi
Steps to create database with ASM.
1.Install oracle binary with active CRS(For single node installation CRS is activated when you run root.sh) .
2.Create disk without file ssytem.
3.Assign disk to raw .
4.Change owner and permission to raw devices.
5.Configure ASM manually or USing DBCA.
Manually ASM Configuration.
a.Create initialization parameter file and password file.
b.Mandatory parameter is "instance_type=asm" as per your need configure rest of parameter like db_cache_size,large_pool_size,processes,remote_login_passwordfile,shared_pool_size etc..
c.To discover disk configure "asm_diskstring=/dev/raw/raw*"
Using DBCA to configure ASM.
1.In storage type section choose ASM.It will ask for password of sysdba in 10g.
2.ASM configuration window will open -> here it create disk group -> it shows all available ASM candidate disk automatical -> choose normal redundancy,external redundancy or high redundancy.
ASM disk also can be conbfigured with ASMLIB .
If ASM disk is configured you can start asm instance in nomount state and query to v$asm_disk to see all candidate disk.V$asm_disk only shows disk which is configured in asm_diskstrings.
Hope this will help U,
Tinku

Create 10g Database with ASM on Windows Server 2003 x64

I am running Windows 2003 Server Enterprise x64 on a Dell server and wish to install Oracle 10g 10.2 with ASM.
First, I performed a software only install. Then, I created several raw partitions on each of two SATA2 disks, and created a disk group - DGROUP1 - using two partitions from each disk. So far so good.
Next, I tried to use DBCA to create a general purpose database using ASM, and that is where the problem arose. I can use sqlplus to stop and start the ASM instance, but when I use DBCA to select ASM for storage I am asked for the SYS password for ASM. I enter it and get a message "Passwords cannot be verified because: Io exception: The network adapter could not establish the connection". If I ignore this I can go on to select my DGROUP1, but the installation ultimately fails due to "insufficient privileges".
Can anyone please help?

Hi Martin
Thanks for the reply. I used ASMTOOLG to stamp the disks and then used DBCA and followed the description hereo create the disk group DGROUP1:
http://www.databasejournal.com/features/oracle/article.php/3571371
At one point, DBCA prompted me to run "localconfig add", which I did.
If it is a missing password file that is the problem, is it possible to create one to put things right?
Charles

DR type restore of 10gR1 RAC with ASM database to another cluster

Hi,
We have a requirement to restore the image copy of our production database to another location. The production database is a 10-node 10gR1 RAC deployment with ASM. The image copy is in the FRA.
We want to restore this image copy onto a 2-node 10gR1 RAC cluster, which is also running a development environment. We have so far used the 'backup copy copy of database' command to pipe the image copy from the FRA to an NFS mounted filesystem. We plan to restore (and convert the names) the files from here. I have a list of steps we need to undertake - like adding the production database metadata on the development cluster into CRS, restore the spfile and controlfile, restore and convert the datafiles from the production ASM diskgroup to the development ASM diskgroup.
has anyone out there done this? Are there any nasty 'gotchas' or pitfalls?
Please, tell me your pain so I can spare it myself :o)
regards
Dilbert

user562223 wrote:
We are planning to take cold backup through RMAN. But now the issue is that if something going wrong with the storage then both the diskgroup on the same storage will not be mounted.
What should be the backup & recovery strategy for this scenario? How to bring the server back online?The strategy depends entirely on the risk analysis and assessment. Do you need to be able to recover the database to the moment just before it crashed? Do you need point-in-time recovery? What are the availability requirements? Etc.
Databases can be quite diverse in nature. It can be fairly static with very few changes, to very dynamic to totally dynamic. In some cases, the database only needs to be restored as a "container" (structures with no data) as that is all the processes need and as these will supply the data. In other cases, the entire database with all committed transactions to the second before the crash is needed. In a few cases, you may want to use Data Guard and standby/clone databases instead.
There is no single set of rman instructions that you can copy-and-paste to implement any of these diverse backup and recovery strategies. You need to determine and define your backup, restore and availability requirement first - before looking at which rman commands to use and in what sequence, where and when.

Benefits of Partitioning a Database running with ASM

Hi All,
I am trying to understand the additional benefits of performing partitioning of table space on a database which is running with ASM.
Further I wish to understand the approach followed by other teams for partitioning tables and the benfits they reaped out of using ILM.
Regards,
Vinod Dudeja

I would make sure you set all the Kernel parameters correctly in the install guide.
So ASM is already running and you are creating the DB or you are trying to create an ASM instance?
Also found this on Metalink:
Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.4
SUSE \ UnitedLinux x86-64
Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opetron Architecture)
Linux x86-64
Symptoms
When trying to increase the SGA to approach half available RAM with an Oracle 64bit version on a Linux 64bit operating system, even though shmmax is set to match half the amount of RAM, you get the following error when trying to start the instance:
SQL> startup nomount
ORA-27102: out of memory
Linux-x86_64 Error: 28: No space left on device
Changes
shmall is set to default at 2097152
Cause
shmall is number of pages of shared memory to be made available system-wide.
Solution
Set shmall equal to shmmax divided by the page size.
FYI: The page size can be seen using the following command:
$ getconf PAGE_SIZE
Errors
ORA-27102 out of memory

COLD BACKUP DATABASE CLONING with +ASM

Hi,
I need some help to clone the database using Cold backup with +ASM. Can somebody help me on this
Here is the steps we did on Source Database.
1. Copied all the $ORACLE_HOME from Source to TARGET.
2. Created pfile from spfile.
3. Created backup control file on the Source.
Questions:
=======
1. Source has 3 diskgroups, do we need to create new 3 disk groups on the TARGET ?
2. If we needed 3 new disk groups on TARGET, how can we move all the data from SOURCE diskgroup to TARGET disk group, Do we need to use RMAN?
Please let me know what else need to do to bring up the TARGET database.
Thanks
Dheeru.

Hi,
1. Source has 3 diskgroups, do we need to create new 3 disk groups on the TARGET ?Not necessarily.
2. If we needed 3 new disk groups on TARGET, how can we move all the data from SOURCE diskgroup to TARGET disk group, Do we need to use RMAN? Yes, use RMAN to clone/duplicate the database.
Rapid Clone Documentation Resources, Release 11i and 12 [ID 799735.1]
Cloning ASM database using RMAN Duplicate
http://oracleandme.blogspot.com/2007/08/cloning-e-biz-using-rman-duplicate.html
Thanks,
Hussein

Standby database with ASM disks?

Has anyone successfully created a standby database when the primary database and the standby database are using ASM disks? If the answer is yes, how did you copy the files(database backup, control files, etc.) from the asm on primary to asm on standby?
Note: I am using 10gR2 on HP-UX but the copy part should be platform independent so however you did it should help me.

Hi d_carmichael2001,
I had done database migration from Non-asm to ASM for single instance by RMAN.
and i think mostly steps are same for create standby database on ASM.
Have a Look.......
1.create a ASM instance manually on new server.
2.Take a backup of Prod database and controlfile.
**backup of controlfile for Standby should be taken as
BACKUP CURRENT CONTROLFILE FOR STANDBY;
Backup database cmd will be same as Backup database plus archivelog;
3. create standby database by using following cmd and set necessary parameter before execute it
Diskgroup for standby should be define in standby spfile's.
**Standby database should be in nomount stange
**connect as % rman TARGET / AUXILIARY SYS/sys_pwd@sbdb1
Use
DUPLICATE TARGET DATABASE FOR STANDBY ;
This command will copy the datafiles, archived redo log files and standby control file in the backup set to the standby database's storage area.
Thanks
Kuljeet Pal Singh

What are the differences of creating a physical standby database with ASM?

I want to create a physical standby database for my 10g(10.2.0.1) database. But it is using ASM. Is it possible to create a standby database for a database using ASM?
What are the differences of creating a physical standby database with ASM?

tell us what your research shows and we'll try to
validate it. I am simulating Oracle ASM on a PC and I want to try
DataGuard on it now. So I am trying to create DataGuard
on an ASM system. The purpose is only learning and test.That's telling us how you are researching, not what you have observed.
Your research could have included looking at the documetation, and you might have found http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#sthref1642
which discusses exactly what you are looking for.
Message was edited by:
Hans Forbrich

Installing Oracle Database with ASM on Oracle VM for SPARC

We're installing Solaris 11 and Oracle VM for SPARC so we can install Oracle Database with ASM. There is a requirement when creating the database that the raw disk have an owner that is the same as the database. Everytime we try to change the owner it will always show that the owner is root.
Any ideas?

Hi
Please let me know from where you are allocating ASM raw disks for the guest domain.
i hope you are changing the disk permissions using chown -R
Also confirm the permission using command # ls -IL /dev/rdsk
Regards
AB

Link to " Database Storage Consolidation with ASM White Paper " now fixed

Similar Messages

Maybe you are looking for