Changes to spfile in +ASM

I'm having to do some changes to an 11.2 database on Linux 5.9 and have a simple question:
The database is a primary database for two physical standby databases.
The database is configured with Grid and ASM.
I need to make some parameter changes and save them to the spfile and restart the databases.
Normally, I would "alter system set something=value scope=spfile".
But with ASM, our spfile is in the ASM, and there is no spfile at the OS level, only an init<sid>.ora file which of course points to the spfile in the ASM.
My question is if I can simply run the command as I normally would and it would save the changes to the spfile in the ASM.
Or, do I have to create a backup copy of my pfile, then make the changes to the spfile, then create a pfile from spfile, and start the database up using the pfile (with system changes), then delete the old spfile in the ASM and then create a new spfile in the ASM from the pfile?  Then when I'm done, copy back over my saved backup pfile as the new init<sid>.ora file, and bounce the database again.
It seems I've had to do this in the past when dealing with ASM and DG.
As for the standby databases, can I simply just make the changes and save them to the spfile and restart the standby database up to mount mode again?
Also (one last question), these databases are configured with DGMGRL.  Do I need to deal with it too (or instead)?
The changes I need to make are Oracle hidden parameter changes that are needed to avoid hitting a bug (as directed by OSS).
Thanks in advance.

Okay, thank you.  I wonder in what situation I am thinking of when I had to do it the way I described.
Thanks again.

Similar Messages

  • Do I need to restart database in change of spfile?

    Hi
    All,
    Do I need to restart database in change of spfile? my database is in 10.2.0.3 on AIX.
    and one more thing when I do more on spfile it displaying the contents that is readable i am thinking that spfile is binary file so how it can be possible.
    Thanks,
    Vishal

    You may be interested in reading this page
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#sthref438
    SPFILE is a dynamic file so it does not need any sort of server restart.Also though it can be readable by any utility which can read any binary,its not advisable to read spfile like this.The best (recommended ) way is to create a pfile from it and then alter it if you need it.
    Aman....

  • Change Node association of ASM instance

    Hi,
    I have a 4-node cluster running RHEL 5 and GI - 11.2.0.2. After a successful installation we discovered that the asm instance association got switched between Node 2 & Node 3.
    e.g., - Node 2 is running ASM3 instance
    Node 3 is running ASM2 instance.
    Is it possible to correct this, or do I need to rebuild the whole cluster again!?
    Thanks,
    AbbY

    Hi AbbY,
    this is the result, that the root.sh on node 3 was faster than the one on node 2 during install.
    If you would like to have the ASM instance in a specific order after installation, you have to run them sequentially (and nor in parallel).
    But one thing you should also be aware of, is that the ASM number in 11.2 is not fix anymore:
    => The ASM instance number is dependant on the node number (olsnodes -n -i -t -s).
    => Each nodes gets a lease for the node number for approx. 1 week. It's like a DHCP lease, which can expire if not started.
    So if you would shut down node 2 and 3 for one week and then restart the nodes in a different order, lease would change (and therefor the ASM instance number).
    Which leads to the further question (because this is really flexible): Why do you want the +ASM instances to have fixed names?
    If your nodes would be "Mars" and "Pluto", would it matter where ASM1 and ASM2 runs on?
    If you say: We need to know for sqlplus to connect to ASM instance. Why not simply connect this way to ASM:
    sqlplus sys/pwd@hostname:port/+ASM
    You will always end up on the ASM instance on the node (no matter what instance number the ASM instance has on that node).
    O.k. I have to admit there are still a few tools who need the instance number (like asmcmd), but I know this necessity will change, since cluster gets more flexible in the future.
    Sebastian

  • Unable to startup 12c RAC database, can't open spfile in ASM

    hello,
    I'm testing 12cRAC database on RHEL5 and need your help to troubleshoot and fix the following issue  -
    DBCA fails at the end of the configuration to create and startup new RAC database with the following errors
    ORA-01078: failure in processing system parameters
    ORA-01565: error in identifying file '+DATA/TDB1/spfileTDB1.ora'
    ORA-17503: ksfdopn:2 Failed to open file +DATA/TDB1/spfileTDB1.ora
    ORA-15056: additional error message
    ORA-17503: ksfdopn:2 Failed to open file +DATA/TDB1/spfiletdb1.ora
    ORA-01017: invalid username/password; logon denied
    I also tried executing script (which was created by DBCA) to create the new DB  manually and got the same results - it happens during first attempt to start it up using SPFILE after new DB was successfully created (it was started up using pfile)
    Clusterware with ASM install was successful, binaries were also installed without issues,
    cluster seems healthy, I see correct files within ASM using asmcmd etc ..
    got stuck here and need some directions ... very confused by ORA-01017 password error
    wonder if anyone had same or similar issues ?
    Thank you !

    Fixed.
    Thank you everyone for suggestions and recommendations -
    ASM is accessible using asmcmd and I can see all the DB files incuding spfile, they were created by DBCA, alert log showed same information I posted
    After extensive troubleshooting and testing the issue was idedntified and fixed - 'dba' group needs to be the primary group for 'oracle' user, not the secondary one. I suspected that something was not right with 'oracle' user access to asm based on that strange password error. There is more I need to check as the issue and fix with swapping groups seems strange. Secondary group is not enough ti have proper rights ??? my first reaction was - seriously ? wtf ?
    Anyway - I need to move one now ...
    Thank you again !

  • RMAN Active Cloning: how to include SPFILE on ASM

    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
    Storage : ASM Diskgroups
    On RMAN active cloning of databases, how to include the SPFILE to be cloned on the ASM Storage?

    Hello;
    Check out the example here :
    http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmdupad.htm
    Under "Example 25-4 Duplicating from a File System to ASM (Active)"
    or
    Example 25-5 Duplicating from ASM to ASM (Active)
    Best Regards
    mseberg
    Edited by: mseberg on May 15, 2013 10:34 AM

  • Changing spfile parameters

    Hello,
    I am working on a RAC database with ASM and getting error - ORA-04031: unable to allocate 1072 bytes of shared memory.
    I need to increase the SGA_MAX_SIZE but the spfile is present as part of ASM file system.
    please let me know the steps for changing SGA_MAX_SIZE in spfile under ASM system.
    Thanks!

    SPfile is on ASM, that is not the problem.
    You can use "ALTER SYSTEM SET.... SCOPE=SPFILE", when you use spfile
    SQL> show parameter spfile
    SQL> alter system set SGA_MAX_SIZE=xxxx scope=spfile;After that shutdown/startup database...
    Oh don't forget to change SGA_TARGET as well
    SQL> alter system set sga_target=xxxxx

  • Moving spfile from non-asm to asm file system

    Hi All
    We are migrating non-asm file system to asm file system, we are held up in moving the spfile from non-asm file system to asm file system ...
    we tried the below method
    Recreate SPFILE on ASM diskgroup
    SQL> create pfile='c:\initTEST.ora' from spfile;
    File created.
    SQL> create spfile='+DGRP2/spfileTEST.ora' from pfile='c:\initTEST.ora';
    File created.
    after this we started both the running instance and asm instance
    but after starting the instance TEST we saw the instance still using spfile of non-asm file system
    what is the correct way of moving the spfile from non-asm to asm file system..
    Regards
    Hariharan.T

    You need to perform this first:
    First rename the $ORACLE_HOME/dbs/spfileTEST.ora to spfileTEST.ora_old
    create initTEST.ora in dbs location with below contents:
    Also i recommend you to recreate the spfile in ASM as it might not be in good shape.
    When ever you start the oracle instance there is a specific order to find the oracle pfile/spfile
    1. O_H/dbs/spfile<SID>.ora
    2. O_H/dbs/init<SID>.ora
    3. O_H/dbs/spfile.ora
    4. O_H/dbs/init.ora
    in your case instance always finds spfileTEST.ora in dbs location (non -ASM) and will stop looking further. If you remove it our of the way it will find initTEST.ora which will redirect to spfile present in ASM.
    NOTE: As per your earlier update you created spfile in ASM after puttin spfile='+DG...' in the initTEST.ora..
    If you start the instance with this SPFILE you will be getting "maxmimum cursors limit exceeded" error.
    -Ravi.M

  • Having trouble move Spfile from filesystem to asm

    I find out the db started with :
    Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileTST1.ora
    Tried to create a pfile, then create a spfile ='+DAT' won';t work with ora-03113 error.
    I did srvctl config database, the spfile is point to +dat
    Database unique name: TST
    Database name: TST
    Oracle home: /u01/app/oracle/product/11.2.0/dbhome_1
    Oracle user: oracle
    Spfile: DAT/TST/spfileTST.ora
    Domain:
    Start options: open
    Stop options: immediate
    Database role: PRIMARY
    Management policy: AUTOMATIC
    Server pools: TST
    Database instances: TST1,TST2
    Disk Groups: DAT,FRA
    Mount point paths:
    Services:
    Type: RAC
    Database is administrator managed
    How do I get around this issue and put spfile on ASM so I can bring the RAC instances?
    Thanks in advance.

    SQL> show parameter db_create
    NAME TYPE VALUE
    db_create_file_dest string +HR_DAT
    db_create_online_log_dest_1 string +HR_DAT
    db_create_online_log_dest_2 string +HR_FRA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Could not find ASM spfile

    Hello,
    I was unable to locate the spfile of my ASM instance.
    Re:
    I just did a complete reinstall and my suspicion that it might had something to do with removing the first datagroup was correct:
    SQL> show parameter pfile
    NAME                         TYPE      VALUE
    spfile                         string      +DATA/asm/asmparameterfile/registry.253.729008643Now I wonder if this is new to release 2, and if this is actually a good idea, having the spfile in a ASM group rather than in the dbs directory.
    Thanks.

    Hi Markus,
    yes this is new to 11gR2.
    And yes it does make sense. Because up to 11.2 if you only used ASM (no shared filesystem) you could not have spfile for ASM just pfiles.
    This leads to the problem that your ASM instances can diverge (if you only update 1 file).
    Hence Oracle wanted to have the spfile for ASM in a central place.
    Since there is no other shared filesystem than ASM, they put it into ASM.
    However in the GPnP file, the OLR (Oracle Local Registry) and the OCR (Oracle Cluster Registry) they have the entries to identify the DISCOVERY String and the spfile location.
    So ASM can startup but will then access the SPFILE on the ASM diskgroup.
    If you need to move the spfile, you can use spcopy command from asmcmd.
    In an Oracle Restart environment, someone can argue if this makes sense, if it would not have been easier to put it simply into the filesystem.
    However since Oracle Restart is just the clusterware in single instance, they probably did not fix the standard functionality....
    Sebastian

  • OCR and voting disks on ASM, problems in case of fail-over instances

    Hi everybody
    in case at your site you :
    - have an 11.2 fail-over cluster using Grid Infrastructure (CRS, OCR, voting disks),
    where you have yourself created additional CRS resources to handle single-node db instances,
    their listener, their disks and so on (which are started only on one node at a time,
    can fail from that node and restart to another);
    - have put OCR and voting disks into an ASM diskgroup (as strongly suggested by Oracle);
    then you might have problems (as we had) because you might:
    - reach max number of diskgroups handled by an ASM instance (63 only, above which you get ORA-15068);
    - experiment delays (especially in case of multipath), find fake CRS resources, etc.
    whenever you dismount disks from one node and mount to another;
    So (if both conditions are true) you might be interested in this story,
    then please keep reading on for the boring details.
    One step backward (I'll try to keep it simple).
    Oracle Grid Infrastructure is mainly used by RAC db instances,
    which means that any db you create usually has one instance started on each node,
    and all instances access read / write the same disks from each node.
    So, ASM instance on each node will mount diskgroups in Shared Mode,
    because the same diskgroups are mounted also by other ASM instances on the other nodes.
    ASM instances have a spfile parameter CLUSTER_DATABASE=true (and this parameter implies
    that every diskgroup is mounted in Shared Mode, among other things).
    In this context, it is quite obvious that Oracle strongly recommends to put OCR and voting disks
    inside ASM: this (usually called CRS_DATA) will become diskgroup number 1
    and ASM instances will mount it before CRS starts.
    Then, additional diskgroup will be added by users, for DATA, REDO, FRA etc of each RAC db,
    and will be mounted later when a RAC db instance starts on the specific node.
    In case of fail-over cluster, where instances are not RAC type and there is
    only one instance running (on one of the nodes) at any time for each db, it is different.
    All diskgroups of db instances don't need to be mounted in Shared Mode,
    because they are used by one instance only at a time
    (on the contrary, they should be mounted in Exclusive Mode).
    Yet, if you follow Oracle advice and put OCR and voting inside ASM, then:
    - at installation OUI will start ASM instance on each node with CLUSTER_DATABASE=true;
    - the first diskgroup, which contains OCR and votings, will be mounted Shared Mode;
    - all other diskgroups, used by each db instance, will be mounted Shared Mode, too,
    even if you'll take care that they'll be mounted by one ASM instance at a time.
    At our site, for our three-nodes cluster, this fact has two consequences.
    One conseguence is that we hit ORA-15068 limit (max 63 diskgroups) earlier than expected:
    - none ot the instances on this cluster are Production (only Test, Dev, etc);
    - we planned to have usually 10 instances on each node, each of them with 3 diskgroups (DATA, REDO, FRA),
    so 30 diskgroups each node, for a total of 90 diskgroups (30 instances) on the cluster;
    - in case one node failed, surviving two should get resources of the failing node,
    in the worst case: one node with 60 diskgroups (20 instances), the other one with 30 diskgroups (10 instances)
    - in case two nodes failed, the only node survived should not be able to mount additional diskgroups
    (because of limit of max 63 diskgroup mounted by an ASM instance), so all other would remain unmounted
    and their db instances stopped (they are not Production instances);
    But it didn't worked, since ASM has parameter CLUSTER_DATABASE=true, so you cannot mount 90 diskgroups,
    you can mount 62 globally (once a diskgroup is mounted on one node, it is given a number between 2 and 63,
    and other diskgroups mounted on other nodes cannot reuse that number).
    So as a matter of fact we can mount only 21 diskgroups (about 7 instances) on each node.
    The second conseguence is that, every time our CRS handmade scripts dismount diskgroups
    from one node and mount it to another, there are delays in the range of seconds (especially with multipath).
    Also we found inside CRS log that, whenever we mounted diskgroups (on one node only), then
    behind the scenes were created on the fly additional fake resources
    of type ora*.dg, maybe to accomodate the fact that on other nodes those diskgroups were left unmounted
    (once again, instances are single-node here, and not RAC type).
    That's all.
    Did anyone go into similar problems?
    We opened a SR to Oracle asking about what options do we have here, and we are disappointed by their answer.
    Regards
    Oscar

    Hi Klaas-Jan
    - best practises require that also online redolog files are in a separate diskgroup, in case of ASM logical corruption (we are a little bit paranoid): in case DATA dg gets corrupted, you can restore Full backup plus Archived RedoLog plus Online Redolog (otherwise you will stop at the latest Archived).
    So we have 3 diskgroups for each db instance: DATA, REDO, FRA.
    - in case of fail-over cluster (active-passive), Oracle provide some templates of CRS scripts (in $CRS_HOME/crs/crs/public) that you edit and change at your will, also you might create additionale scripts in case of additional resources you might need (Oracle Agents, backups agent, file systems, monitoring tools, etc)
    About our problem, the only solution is to move OCR and voting disks from ASM and change pfile af all ASM instance (parameter CLUSTER_DATABASE from true to false ).
    Oracle aswers were a litlle bit odd:
    - first they told us to use Grid Standalone (without CRS, OCR, voting at all), but we told them that we needed a Fail-over solution
    - then they told us to use RAC Single Node, which actually has some better features, in csae of planned fail-over it might be able to migreate
    client sessions without causing a reconnect (for SELECTs only, not in case of a running transaction), but we already have a few fail-over cluster, we cannot change them all
    So we plan to move OCR and voting disks into block devices (we think that the other solution, which needs a Shared File System, will take longer).
    Thanks Marko for pointing us to OCFS2 pros / cons.
    We asked Oracle a confirmation that it supported, they said yes but it is discouraged (and also, doesn't work with OUI nor ASMCA).
    Anyway that's the simplest approach, this is a non-Prod cluster, we'll start here and if everthing is fine, after a while we'll do it also on Prod ones.
    - Note 605828.1, paragraph 5, Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0, 11.2.0) on RHEL5/OL5
    - Note 428681.1: OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)
    -"Grid Infrastructure Install on Linux", paragraph 3.1.6, Table 3-2
    Oscar

  • Creating Oracle 11g Database Manually on ASM on 11g R2 Grid

    Hi:
    Earlier added this issue alongwith Grid installation. Only Jorg replied to me but could not find a complete solution. So thought of starting a new thread.
    Wanted to know if any one of you have successfully created Oracle Database Manually on ASM on Oracle 11g R2 Grid.
    I have installed Oracle 11g R2 grid (grid user) and Oracle 11g R2 DB software succesfully (oracle user).
    Now trying to create a database manually on ASM as Oracle user.
    First I create an pfile in $ORACLE_HOME/dbs
    then I started by db on nomount stage. when I create a spfile on to my ASM diskgroup I get
    I have created 2 diskgroups '+DGASMSPFILE' (ASM Spfile) and '+DGDBDATA' (for database)
    Grid is up and running.
    From Oracle user:
    Have created a sample initDBRAC.ora
    Now I want to create Oracle Database Global Spfile into '+DGASMSPFILE'
    export ORACLE_SID=DBRAC
    $ sqlplus / as sysdba
    SQL> create spfile='+DGASMSPFILE/spfileDBRAC.ora' from pfile;
    ORA-17502:ksfdcre:4 failed to create file +DGASMSPFILE/spfileDBRAC.ora
    ORA-12547: TNS lost contact
    "Oracle user" should have privileges to access ASM diskgroup right? What is the permission set for /dev/sdc* (earlier it was root:oinstall I changed it to grid:oinstall even then no difference.
    Trace output:
    ASM_DISKSTRING= /dev/sdc*
    ***********************************************************************1st trace file
    Fatal NI connect error 12547, connecting to:
    (DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/crs/11.2.0/grid/bin/oracle)(ARGV0=oracle+ASM1_o000_dbrac)(ENVS='ORACLE_HOME=/crs/11.2.0/grid,ORACLE_SID=+ASM1')(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(enable=setuser)(CONNECT_DATA=(CID=(PROGRAM=oracle@skyit6)(HOST=skyit6)(USER=oracle))))
    VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.1.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
    Time: 01-JUN-2011 01:27:07
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12547
    TNS for Linux: Version 11.2.0.1.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
    Time: 01-JUN-2011 01:27:07
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12547
    TNS-12547: TNS:lost contact
    ns secondary err code: 12560
    nt main err code: 517
    TNS-00517: Lost contact
    nt secondary err code: 32
    nt OS err code: 0
    ERROR: Failed to connect with connect string: (DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/crs/11.2.0/grid/bin/oracle)(ARGV0=oracle+ASM1_o000_dbrac)(ENVS='ORACLE_HOME=/crs/11.2.0/grid,ORACLE_SID=+ASM1')(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(enable=setuser))
    Wed Jun 01 01:27:07 2011
    ERROR: slave communication error with ASM; terminating process 16772
    Errors in file /oraeng/app/oracle/product/diag/rdbms/dbrac/DBRAC/trace/DBRAC_ora_16772.trc:
    Regards
    Dinesh

    Hi Sebastian:
    When I installed grid software, oracle db software and created oracle db manually things worked fine.
    When I restart the RAC environment I found the following issues:
    1) all the resources does not come up automatically, once i issue crs_start -all all the services comes up. (most of the resources related to node1 comes up but cluster resources related to node2 does not come up) crsctl check crs shows that things are online.
    2) wanted to recreate a database manually after restarting the RAC enviroment. To start of as usual tried to create a spfile in ASM disk "Create spfile='+DGDBSPFILE' from pfile'
    I get ORA-17502:ksfdcre:4 failed to create file +DGDBSPFILE'
    12547: TNS: lost contact
    looks like permission problem.
    The same command worked before restarting the RAC environment. Pls let me know if I am missing out anything.
    Is it because i am unable to access ASM instance.
    3) As you had mentioned tried to set the sbit by executing the following statement:
    $ /opt/grid/bin/setasmgidwrap o=/opt/oracle/product/11.2.0/db/bin/oracle
    should this be put into "rc" folder in linux so that it gets set everytime linux starts up. because once i restart the permission get changed.
    I should execute it from grid user to change the permission of 'oracle' binary in 'oracle user' right?
    Can you explain me why is this required (sbit).
    Thanks.
    Regards
    Dinesh

  • RAC Instances using different spfile

    I have ASM instance is running on both the RAC servers and I am using SPFILE. I made some changes in SPFILE of the
    database instances and tried to modify few parameters with scope=both and also with scope =spfile and then bounced both
    the database instances.
    All the changes can be seen in both the instances but when I fired:
    SQL>show parameter spfile;
    on one database instance the output is:
    SQL> show parameter pfile
    NAME TYPE VALUE
    spfile string /u01/app/oracle/product/10.2/d
    b_1/dbs/spfileRACDB1.ora
    and on other database it is:
    SQL> show parameter pfile
    NAME TYPE VALUE
    spfile string +DATA/racdb/spfileracdb.ora
    but the changes I made in the spfile can be seen in both the instances.
    I want that both the instances should use the same spfile.......
    Can someone please tell me the steps to use same spfile on both the instances (i.e. +DATA/racdb/spfileracdb.ora )                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Create a PFILE on both nodes and that PFILE should have only 1 enty
    spfile=+DATA/racdb/spfileracdb.ora
    Start the instances with this pfile and drop "/u01/app/oracle/product/10.2/d
    b_1/dbs/spfileRACDB1.ora", then both of the instances should be using the same spfile.
    Daljit Singh

  • File to be put on ASM

    Dear All,
    db version:10.2.0.3
    o/s:redhat linux4
    In my production instance all configuration files(datafiles,parameterfiles,logfile,controlfiles) are on SAN filesystem .I want to migrate them to ASM hoping that i will get performance gains.i have some doubts.
    1)i want to keep 2 copies of logfiles,controlfiles and archive files if i use failure groups it doesnt makes any sense coz in last underline storage is comming from san.i would like to put 1 copy in asm and 1 copy in local hardrive is it possible and no performance issues will happen?
    Regards

    hungry_dba wrote:
    Dear All,
    db version:10.2.0.3
    o/s:redhat linux4
    In my production instance all configuration files(datafiles,parameterfiles,logfile,controlfiles) are on SAN filesystem .I want to migrate them to ASM hoping that i will get performance gains.i have some doubts.
    1)i want to keep 2 copies of logfiles,controlfiles and archive files if i use failure groups it doesnt makes any sense coz in last underline storage is comming from san.i would like to put 1 copy in asm and 1 copy in local hardrive is it possible and no performance issues will happen?
    Hi,
    You can put DATAFILE, CONTROLFILE,REDO and SPFILE in ASM DISKGROUP. If you setup Flash Recovery Area (FRA) to Filesystem during database creation, REDO,CONTROLFILE are automatically multiplexed in FRA and ARCHIVELOG is generate in FRA. (i.e Filesystem).
    Also you can manually multiplex REDO and Controlfile and setup Archivelog Location to Filesystem and Disksgroup as you wish.
    P.S REDO is always multiplexed in Main Location and FRA during creation of REDO.
    The performance will depend on your hardware, if you are using the same array for both (diskgroup and filesystem) I believe it will not have performance problems.
    But you must analyze performance issues and bottlenecks during the operation of your environment.
    Hope this helps,
    Levi Pereira

  • ASM DG creation fails on sles11_x86_64 with 11gR1

    Hi,
    I have sles11x86_64 installed and using Veritas Volume manager raw disks for ASM but ASM dg creation fails with error mentioned below;
    ls /dev/vx/rdsk/asmdg/asmvol
    /dev/vx/rdsk/asmdg/asmvol
    test:~ # ls -l /dev/vx/rdsk/asmdg/asmvol
    crw-rw---- 1 oracle oinstall 199, 65533 Feb 26 12:08 /dev/vx/rdsk/asmdg/asmvol
    test:~ # su - oracle
    oracle@test:~> bash
    oracle@test:~> export ORACLE_SID=+ASM
    oracle@test:~> export ORACLE_HOME=/oracle/orabin/product/11.1.0/db_1
    oracle@test:~> cd /oracle/orabin/product/11.1.0/db_1/bin
    cat /etc/oratab
    # This file is used by ORACLE utilities. It is created by root.sh
    # and updated by the Database Configuration Assistant when creating
    # a database.
    # A colon, ':', is used as the field terminator. A new line terminates
    # the entry. Lines beginning with a pound sign, '#', are comments.
    # Entries are of the form:
    # $ORACLE_SID:$ORACLE_HOME:<N|Y>:
    # The first and second fields are the system identifier and home
    # directory of the database respectively. The third filed indicates
    # to the dbstart utility that the database should , "Y", or should not,
    # "N", be brought up at system boot time.
    # Multiple entries with the same $ORACLE_SID are not allowed.
    +ASM:/oracle/orabin/product/11.1.0/db_1:N
    test./sqlplus /nolog
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Feb 26 12:25:32 2010
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    SQL> connect /as sysdba
    Connected.
    SQL> select name from v$asm_diskgroup;
    no rows selected
    SQL> select path from v$asm_disk;
    PATH
    /dev/vx/rdsk/asmdg/asmvol
    SQL> create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol';
    create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol'
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15201: disk /dev/vx/rdsk/asmdg/asmvol contains a valid RDBMS file
    SQL> select name from v$asm_diskgroup;
    no rows selected
    SQL> create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol' -f;
    create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol' -f
    ERROR at line 1:
    ORA-00933: SQL command not properly ended
    SQL> create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol' force;
    create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol' force
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15080: synchronous I/O operation to a disk failed
    ORA-15080: synchronous I/O operation to a disk failed
    ORA-15080: synchronous I/O operation to a disk failed
    ORA-15080: synchronous I/O operation to a disk failed
    SQL> create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol';
    create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol'
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15201: disk /dev/vx/rdsk/asmdg/asmvol contains a valid RDBMS file
    SQL> create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol' force;
    create diskgroup asm_dg external redundancy disk '/dev/vx/rdsk/asmdg/asmvol' force
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15080: synchronous I/O operation to a disk failed
    ORA-15080: synchronous I/O operation to a disk failed
    ORA-15080: synchronous I/O operation to a disk failed
    ORA-15080: synchronous I/O operation to a disk failed
    SQL>
    can some body help on this.
    Also wanted to know the background process during ASM creation.
    ~Dhananjay
    Edited by: user9075978 on Feb 26, 2010 4:18 AM

    Force the partition table on the second node to be reread
    # partprobe
    Initialize all shared disks on one node (execute as user root)
    dd if=/dev/zero of=/dev/sdc1 bs=1M count=10
    dd if=/dev/zero of=/dev/sdc2 bs=1M count=10
    dd if=/dev/zero of=/dev/sdc3 bs=1M count=10
    dd if=/dev/zero of=/dev/sdc4 bs=1M count=10
    dd if=/dev/zero of=/dev/sdd1 bs=1M count=10
    dd if=/dev/zero of=/dev/sdd2 bs=1M count=10
    dd if=/dev/zero of=/dev/sdd3 bs=1M count=10
    dd if=/dev/zero of=/dev/sdd4 bs=1M count=10
    dd if=/dev/zero of=/dev/sde1 bs=1M count=10
    dd if=/dev/zero of=/dev/sde2 bs=1M count=10
    dd if=/dev/zero of=/dev/sde3 bs=1M count=10
    dd if=/dev/zero of=/dev/sde4 bs=1M count=10
    dd if=/dev/zero of=/dev/sdf3 bs=1M count=10
    dd if=/dev/zero of=/dev/sdf4 bs=1M count=10
    Install ASM lib (execute as user root) on all cluster nodes
         rpm -i /ptc/oms/asmlib/*
    Configure ASM lib (set driver owner to oracle and group to dba) on all cluster nodes
    /etc/init.d/oracleasm configure
    Label ASM lib disks on one node (execute as user root)
    /etc/init.d/oracleasm createdisk data01 /dev/sdc3
    /etc/init.d/oracleasm createdisk data02 /dev/sdc4
    /etc/init.d/oracleasm createdisk flash01 /dev/sdd3
    /etc/init.d/oracleasm createdisk flash02 /dev/sdd4
    /etc/init.d/oracleasm createdisk flash03 /dev/sde3
    /etc/init.d/oracleasm createdisk flash04 /dev/sde4
    /etc/init.d/oracleasm createdisk flash05 /dev/sdf3
    /etc/init.d/oracleasm createdisk flash06 /dev/sdf4
    Scan and list the disks on the other node (execute as user root)
    /etc/init.d/oracleasm scandisks
    /etc/init.d/oracleasm listdisks
    Set up udev to configure block device permissions (as user root)
    vi /etc/udev/permissions.d/49-oracle.permissions
    sdc1:root:oinstall:0640
    sdd1:root:oinstall:0640
    # Voting
    sdc2:crs:oinstall:0640
    sdd2:crs:oinstall:0640
    sde2:crs:oinstall:0640
    # ASM spfile
    sde1:asm:oinstall:0640
    # ASM devices
    sdc3:asm:oinstall:0640
    sdc4:asm:oinstall:0640
    sdd3:asm:oinstall:0640
    sdd4:asm:oinstall:0640
    sde3:asm:oinstall:0640
    sde4:asm:oinstall:0640
    sdf3:asm:oinstall:0640
    sdf4:asm:oinstall:0640
    Restart the udev service (execute as user root)
    /sbin/udevstart

  • Change in Oracle Parameters and Log file size

    Hello All,
    We have scheduled DB Check job and the log file showed few errors and warnings in the oracle parameter that needs to be corrected. We have also gone through the SAP Note #830576 – Oracle Parameter Configuration to change these parameters accordingly. However we need few clarifications on the same.
    1.Can we change these parameters directly in init<SID>.ora file or only in SP file. If yes can we edit the same and change it or do we need to change it using BR tools.
    2.We have tried to change few parameters using DB26 tcode. But it prompts for maintaining the connection variables in DBCO tcode. We try to make change only in default database but it prompts for connection variables.
    Also we get check point error. As per note 309526 can we create the new log file with 100MB size and drop the existing one. Or are there any other considerations that we need to follow for the size of log file and creating new log file. Kindly advise on this. Our Environment is as follows.
    OS: Windows 2003 Server
    DB: Oracle 10g
    regards,
    Madhu

    Hi,
    Madhu, We can change oracle parameters at both the levels that is init<SID> as well as SPFILE level.
    1. If you do the changes at init<SID> level then you have to generate the SPFILE  again and then database has to be restarted for the parameters to take effect.
        If you make the changes in SPFILE then the parameters will take effect depending on the parameter type whether it is dynamic or static. You also need to generate the PFILE i.e init<SID>.ora
    2. If possible do not change the oracle parameters using the tcode. I would say it would be better if you do it via the database and it would be much easier.
    3. Well its always good to have a larger redo log size. But only one thing to keep in mind is that once you change the size of the redolog the size of the archive log also changes although the number of files will decrease.
    Apart from that there wont be any issues.
    Regards,
    Suhas

Maybe you are looking for