DBCA not showing ASM diskgroup

where as the ora.asm the resource is executed too and asmcmd & sql (like sysasm) sees him starts: DATA & FRA, but when you try to create a database using dbca... nothing is visible.

FYI, there is a single database... not CARS.

Please help/advise, what needs to be done here.

Thanks in advance.

Thanks for the speed... but I solved it myself...

Basically, here, I played with acfs & portfolio and old sqlnet has the location of portfolio, which I removed already and it's only reason for diskgroup does not appear using dbca.

but this seems quite interesting, even for a whole new db, sqlnet info is critical.

And how do I get to this solution: looking at the logs step by step dbca.

my position: / ora/cfgtools/dbca /... must be a log file created, I started dbca, tail f just for her and you will see.

As I renamed the sqlnet.ora old sqlnet.ora.old... everything seems good.

but thanks again for your quick response...

Tags: Database

Similar Questions

  • ASM diskgroup space do not free themselves after RMAN archivelog delete

    Version Infra grid: 11.2.0.4

    DB version: 11.2.0.4

    OS: Oracle Linux 6.4

    Storage: Enterprise-class storage (EMC VMAX)

    We are in the Bank we have a database of CARS of Production 2 nodes very critical.

    Newspaper archives are stored in ARCH_DG diskgroup. Because of the unexpectedly heavy workload, our diskgroup ARCH_DG became full and we got the usual error

    ORA-00257: archiver error. Connect internal only, until this just released.

    To wear the DB back to business quickly, I tried to delete the old archive logs more than 1 day of the diskgroup first using the following command

    RMAN > delete noprompt archivelog until ' SYSDATE-1';

    So, I started to see the following message


    RECID = STAMP 19807 = 849396325 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10066.331.849396309 archived log file

    Delete archived log

    RECID = STAMP 19809 = 849396940 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10067.274.849396925 archived log file

    Delete archived log

    name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10068.341.849397529 RECID archived log file = 19810 STAMP = 849397543

    Delete archived log

    name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10069.298.849398167 RECID archived log file = 19812 STAMP = 849398182

    Delete archived log

    RECID = STAMP 19813 = 849398806 name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10070.317.849398783 archived log file

    Delete archived log

    name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10071.342.849399327 RECID archived log file = 19814 STAMP = 849399337

    Although I could see messages "deleted archived newspaper" as stated above there are 2 inconsistencies (odd behavior)

    1 inconsistency. Not a single byte released upwards of archive diskgroup. Each log archiving is 4 GB in size. I got "journal archived deleted" message at least 25 archived log files. For example, 100 GB should have been released.

    The diskgroup to archive has remained at 99.9% as shown below and the DB was inaccessible.

    SQL > select name,.

    Round(total_mb/1024,2) Total_GB.

    Round(free_mb/1024,2) Free_GB.

    free_mb/total_mb * 100 "% free"

    ABS ((free_mb/total_mb*100)-100) '% complete '.

    v $ asm_diskgroup;  2 3 4 5 6

    NAME TOTAL_GB FREE_GB % free full
    ------------------------------ ---------- ---------- ---------- ------------
    ARCH_DG 1000.78 99.9223633.077636719
    DATA_DG 10000.02 1188.19 11.8818616 88.1181384
    OCR_VOTE_DG 12 11.09 92.4623525 7.53764754
    < snipped >


    Inconsistency2. The number of available archived newspapers remained unchanged. He was always showing 301

    SQL > select count (*) from v$ archived_log where status = 'A ';

    COUNT (*)

    ----------

    301

    RMAN later > remove obsolete; command removed 17 archived newspapers.

    This means that 17 x 4 = 68 GB should have been released.

    But Diskgroup of free space and the County of v$ archived_log.status = 'A' is unchanged, as mentioned above.

    , Of ASMCMD, I deleted manually a full archive directory connects using rm-rf command.

    Even after running rm - rf on a whole directory full of archived newspaper space was not released and we always receive ""ORA-00257: archiver error '. "

    So, we had to shoot down the cluster using "stop crsctl crs. After the cluster has been raised using 'crsctl start crs' on both nodes,

    space has been freed up, and the DB became accessible.

    I wonder why the ASM diskgroup space was not release despite the removal of the archive logs. Are the 1 & 2 above mentioned inconsistencies caused by something handle to open the file ?

    Hello

    Please run command you at the level of the ASM, below

    SQL > alter diskgroup check all the repair;

    -At the end of the same thing, run below command and enable it to perform

    SQL > alter diskgroup rebalance power 4.

    -To validate the space

    $ asmcmd Pei lsdg

    Kind regards
    Loriette

  • RunInstall does not show the ASM disks

    Hello

    I googled arleady for so long but I can't find the solution for my problem.

    I'm under runInstall of the Oracle Grid Infrastructure installation program. When it comes to "Create the ASM disk groups", the window does not show one of my starts created previously, even if I change the discovery trail to ' / oracleasm/dev/discs / * "Please help!

    [dev root@grid1] # / usr/sbin/oracleasm listdisks

    DATA01

    DATA02

    FRA01

    FRA02

    OCRVOTE01

    OCRVOTE02

    OCRVOTE03

    [dev root@grid1] # / usr/sbin/oracleasm-discover

    ASMLib /opt/oracle/extapi/64/asm/orcl/1/libasm.so using

    [Library ASM - Generic Linux, version 2.0.4 (KABI_V2)]

    Disk discovery: ORCL:DATA01 [31455232 blocks (16105078784 bytes), maxio 512]

    Disk discovery: ORCL:DATA02 [31455232 blocks (16105078784 bytes), maxio 512]

    Disk discovery: ORCL:FRA01 [20969472 blocks (10736369664 bytes), maxio 512]

    Disk discovery: ORCL:FRA02 [20969472 blocks (10736369664 bytes), maxio 512]

    Disk discovery: ORCL:OCRVOTE01 [10477194 blocks (5364323328 bytes), maxio 512]

    Disk discovery: ORCL:OCRVOTE02 [10483712 blocks (5367660544 bytes), maxio 512]

    Disk discovery: ORCL:OCRVOTE03 [10483712 blocks (5367660544 bytes), maxio 512]

    [dev root@grid1] # / usr/sbin/oracleasm querydisk DATA01

    Disk 'DATA01' is a valid ASM disk

    [records root@grid1] # pwd

    / dev/oracleasm/Disks

    [records root@grid1] # he's

    Total 0

    BRW - rw - 1 grid asmadmin 8, 65 4 Mar 11:18 DATA01

    BRW - rw - 1 grid asmadmin 8, 81-4 Mar 11:18 DATA02

    BRW - rw - 1 grid asmadmin 8, 97-4 Mar 11:18 FRA01

    BRW - rw - 1 grid asmadmin 8, 113 4 Mar 11:18 FRA02

    BRW - rw - 1 grid asmadmin 8, 17 4 Mar 11:16 OCRVOTE01

    BRW - rw - 1 grid asmadmin 8, 33-4 Mar 11:17 OCRVOTE02

    BRW - rw - 1 grid asmadmin 8, 49-4 Mar 11:17 OCRVOTE03

    [records root@grid1] # rpm - qa | grep oracle

    oracleasm-support - 2.1.8 - 1.el6.x86_64

    oracleasmlib - 2.0.4 - 1.el6.x86_64

    oraclelinux-release-6Server - 6.0.2.x86_64

    oraclelinux-release-notes-6Server - 14.x86_64

    kmod-oracleasm - 2.0.8 - 4.el6_6.x86_64

    Oracle-logos - 60.0.14 - 1.0.2.el6.noarch

    to clarify this, please login as user "grid" and run the command
         id

    This will show you if id is a member of the Group asmadmin.

    Martin

  • Cannot create the ASM Diskgroup ORA 15020 and ORA-15018

    Hello team,

    Could not create the ASM diskgroup with the following error:

    SQL > create diskgroup redundancy data_asm1 external disk ' / dev/sdf *;

    create diskgroup redundancy data_asm1 external disk ' / dev/sdf. "

    *

    ERROR on line 1:

    ORA-15018: diskgroup cannot be created.

    ORA-15020: discovered in double disc ASM 'DATA_ASM1_0000 '.

    ASM Diskstring

    SQL > show parameter asm_diskstring

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    asm_diskstring string/dev/oracleasm/disks/DISK *, /dev / sd *

    Please let me know how to solve this problem

    Kind regards

    Hello

    check your disc diskgroup status grid +. display result

    1 res ora of $ crsctl State. GRID.dg or $ crsctl status res ora.grid.dg

    Note the distinction uppercase / lowercase of the crs resource

    2. run below as a user of the grid. (necessary to set SID = + ASM? If not already preset)

    ASMCMD > lsdg

    Tobi

  • ASM Diskgroup

    Hello

    SQL > select NAME from v$ asm_diskgroup;

    NAME

    ------------------------------

    DATA

    FRA

    SQL > show disk parameter;

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    asm_diskgroups string FRA

    asm_diskstring string/dev/oracleasm/disks

    I wonder why these two commands produce two different values for asm_diskgroups?  Could someone please give me a hint?

    Hello

    The ASM Diskgroup can be started in multiple ways.

    11.2 docs

    On attachment to the boot disk groups

    At startup, the Oracle ASM instance try to mount the following disk groups:

    • Drive of the specified groups in the ASM_DISKGROUPS initialization parameter
    • Group of disks used by the Cluster Synchronization Services (CSS) for the vote of the files
    • Groups of disks used by Oracle Clusterware for Oracle Cluster Registry (OCR)
    • Group of disks used by the Oracle ASM instance to store the settings of the server ASM (SPFILE) file

    If no disk group are in the previous list, then the instance Oracle ASM do not mount at startup disk groups.

    What I see is happening... .i, please post below

    When you start the ASM, oracle will try read header of all the disk/LUN using asm_diskstring parameter in OCR/RSC (srvctl config asm) or spfile. If find ASM no matter what set of ASM DISKS it will try to mount automatically, because only when the DSO starting, he will deliver ALTER DISKGROUP MOUNT ALL.

    ASM find / know what are diskgroup can be mounted due head ASM DISK that contains this info on diskgroup.

    Other cases

    ASM is set on not (AUTO_START = never) automatically starts and is not not running, but the database is configured to start automatically (AUTO_START = always) and database dependency with diskgroup resource (for example, ora. DATA.dg), so during the startup of the crsd resource lance database dependency CSSD > ASM > DISGROUP > DATABASE

    11 GR 1 material and beyond... A lot of things (asm diskgroup, databases, etc.) became the resource managed by CRSD. Thus, by default, these resources are managed by CRSD not only by itself. I mean crsd knows and manage what resource needs to be started or a stop in the correct order.

    On your case a database resource can be begin your ASM diskgroup

    START_DEPENDENCIES = hard (ora. DATA.dg, ora. FRA.dg)

    This means that this resource will start only if these diskgroup and all its dependencies set first.

    Post edited by: Levi-Pereira

  • The ASM diskgroup in exadata space question

    All,

    I have an environment exadata 1 CCR node with 3 knots of strorage.

    My RECO ASM diskgroup is constantly showing the problems of space... Always higher than 80%.

    I just want to get a Board if I can remove mirroring and recover the space... Even though I know that the result of the deletion of the mirroring...

    Can I reduce the diskgroup RECO and create an another diskgroup?

    I want just a few ideas to do this without great risk involved...

    You may want to consider these MOS notes for more information on resizing the griddisks:
    Resize diskgroup without downtime to Exadata (Doc ID 1272569.1)
    How to resize the disk drive/grid ASM in environment Exadata (Doc ID 1245494.1)

    As others have mentioned, there is no way to change the level of redundancy in ASM, so you need to delete and re-create the diskgroup if you want to change to redundancy. We strongly discourage the use of EXTERNAL with Exadata redundancy.

  • How to identify the ASM DiskGroup attached to which disks?

    Hi guys,.

    In RAC 11 GR 2, how to identify which ASM Diskgroup is attached to which disks... (OS is RHEL 5.4).

    We could list ASM starts by,
    *#oracleasm listdisks * but this command does not display the disks assigned to ASM DiskGroup.

    Even for check location of OCR and voting disks only show Diskgroup name and not the actual discs.
    $ocrcheck
    $crsctl query css votedisk


    (as in gr 10, 2 RAC, we entered /etc/rules.d/udev/60-raw-rules raw file mapping of the OCR, voting disk and other ASM Diskgroup)


    Please help me, as long as the customer place, I could see LUN as assigned to the server and get is not an exact idea whose records have been used for OCR and voting disk DATA Diskgroup.


    Thank you
    Manish

    And for this, you can use oracleasm querydisk. Using that you can identify which device marked for asm or not. for example you can see below the example.

    [oracle@localhost init.d]$ sqlplus "/as sysdba"
    
    SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jun 3 11:52:12 2010
    
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    
    SQL> select path from v$asm_disk;
    
    PATH
    --------------------------------------------------------------------------------
    /dev/oracleasm/disks/VOL2
    /dev/oracleasm/disks/VOL1
    
    SQL> exit;
    
    [oracle@localhost init.d]$ su
    Password:
    [root@localhost init.d]# /sbin/fdisk -l
    
    Disk /dev/sda: 80.0 GB, 80000000000 bytes
    255 heads, 63 sectors/track, 9726 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        1305    10482381   83  Linux
    /dev/sda2            1306        9401    65031120   83  Linux
    /dev/sda3            9402        9662     2096482+  82  Linux swap / Solaris
    /dev/sda4            9663        9726      514080    5  Extended
    /dev/sda5            9663        9726      514048+  83  Linux
    
    Disk /dev/sdb: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1               1        4859    39029886   83  Linux
    /dev/sdb2            4860        9729    39118275   83  Linux
    [root@localhost init.d]# ./oracleasm querydisk /dev/sdb1
    Device "/dev/sdb1" is marked an ASM disk with the label "VOL1"
    [root@localhost init.d]# ./oracleasm querydisk /dev/sdb2
    Device "/dev/sdb2" is marked an ASM disk with the label "VOL2"
    [root@localhost init.d]# ./oracleasm querydisk /dev/sda1
    Device "/dev/sda1" is not marked as an ASM disk
    [root@localhost init.d]#
    

    Also in windows:

    C:\Documents and Settings\comp>asmtool -list
    NTFS                             \Device\Harddisk0\Partition1           140655M
    ORCLDISKDATA1                    \Device\Harddisk0\Partition2             4102M
    ORCLDISKDATA2                    \Device\Harddisk0\Partition3             4102M
    NTFS                             \Device\Harddisk0\Partition4           152617M
    
    C:\Documents and Settings\comp>
    

    answered by Alex.
    Reference:-How to identify what disc rawdevice is named as VOL1 in ASM OS level

    Happy new year.
    Kind regards

  • WITH REDUNDANCY ASM DISKGROUP

    Hi all


    REDUNDANCY NORMAL == NEED 2 GROUPS of FAILURE (I'm clear)


    I am trying to create diskgroup with REDUNDANCY NORMAL (only with 2 raw devices).

    Command line == > I can't create disk with REDUNDANCY NORMAL group

    Through DBCA == > I can.


    select GROUP_NUMBER, name, ALLOCATION_UNIT_SIZE AU_SZ, STATE, TYPE, TOTAL_MB, FREE_MB, OFFLINE_DISKS from v$asm_diskgroup;
    
    GROUP_NUMBER NAME                                AU_SZ STATE       TYPE     TOTAL_MB    FREE_MB OFFLINE_DISKS
    ------------ ------------------------------ ---------- ----------- ------ ---------- ---------- -------------
               1 ASM_DG_DATA                       1048576 MOUNTED     NORMAL      20472      14142             0
               2 ASM_DG_FRA                        1048576 MOUNTED     EXTERN      10236       7143             0
    
    

    
    SQL> create diskgroup DATA NORMAL REDUNDANCY
      2  failgroup disk1 Disk
      3  '/dev/raw/raw5' name data1,
      4  '/dev/raw/raw6' name data2;
    create diskgroup DATA NORMAL REDUNDANCY
    *
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15072: command requires at least 2 failure groups, discovered only 1
    
    

    But through dbca, I can create diskgroup only with 2 drives

    02.png

    SQL> select GROUP_NUMBER, name, ALLOCATION_UNIT_SIZE AU_SZ, STATE,  TYPE, TOTAL_MB, FREE_MB, OFFLINE_DISKS from v$asm_diskgroup;
    
    
    GROUP_NUMBER NAME                                AU_SZ STATE       TYPE     TOTAL_MB    FREE_MB OFFLINE_DISKS
    ------------ ------------------------------ ---------- ----------- ------ ---------- ---------- -------------
               1 ASM_DG_DATA                       1048576 MOUNTED     NORMAL      20472      14142             0
               2 ASM_DG_FRA                        1048576 MOUNTED     EXTERN      10236       7143             0
               3 ASM_DATA                          1048576 MOUNTED     NORMAL      40946      40844             0
    
    

    SQL> select a.disk_number, b.group_number, a.path, b.name, b.type from v$asm_disk a, v$asm_diskgroup b 
    where a.group_number=b.group_number;
    
    DISK_NUMBER GROUP_NUMBER PATH                   NAME                           TYPE
    ----------- ------------ ---------------------- ------------------------------ ------
              0            3 /dev/raw/raw6          ASM_DATA                       NORMAL
              1            3 /dev/raw/raw5          ASM_DATA                       NORMAL
              0            2 /dev/raw/raw3          ASM_DG_FRA                     EXTERN
              1            1 /dev/raw/raw2          ASM_DG_DATA                    NORMAL
              0            1 /dev/raw/raw1          ASM_DG_DATA                    NORMAL
    

    ...

    ..

    My question/confusion is only 2 discs,

    I can create a diskgroup (redundancy = normal) using DBCA, but similar operation cannot perform through command line.

    DB version: 10.2.0.5 on RHEL

    Shows your screenshot of the ASMCA you assign disk/dev/raw/raw5 in FailGroup FG1 and disk/dev/raw/raw6 in FailGroup FG2 - two * different * FailGroups. Each disc is in a separate FailGroup.

    Your Interactive SQL command specifies only 1 FailGroup when there is to specify two FailGroups.

    Hemant K Collette

  • DBFS ASM diskgroup

    Re: our new X 3 machines (in the data center, not yet installed).

    I know that some of these was kind of covered in the previous thread on DBFS. However, I have a little different issues...

    I understand that the DBFS ASM diskgroup is mandatory and that, due to the nature of how calculated its size, the ACS consultants set to its minimum size. However, is it possible (preferably at configuration time) increase the ASM diskgroup? Or is it meant to be a size defined, anything?

    Oracle, told me that I could put newspapers Flashback in DBFS ASM diskgroup (as long as I don't configure DBFS to use, of course). I don't know that I've read that Flashback Logs MUST be put in the db_recovery_file_dest (fast recovery or RECO diskgroup area). Anyone used DBFS (ASM diskgroup) for such storage? I know that this is not IDEAL given the fact, that it won't spread across all storage cells, but I'm trying to find a way to separate newspapers archive logs Flashback as we monitor the location of the log archiving for the use of space (we get an alert if it becomes too full and automatically kick off an archivelog backup/purge at a certain level of use).

    Mark

    Spinning two first records on each cell contains a partition of 29 GB in size with the operating system. The other 10 contain rather a GridDisk 29 GB size where the diskgroup DBFS_DG is built. In other words: DBFS_DG The diskgroup is spreading through all the cells, but only on 10 discs (not 12 as DATA and RECO) on each cell.

    In this way, the GridDisks that make up DATA and RECO can be the same size on all readers of spinning. And the diskgroup DBFS_DG consume about 300 GB on each cell for this reason, which can not be changed reasonably, I guess.

    You can set DB_RECOVERY_FILE_DEST = '+ DBFS_DG' and turn on Flashback Database, so that Flashback Logs are generated, even if you set LOG_ARCHIVE_DEST_1 in the diskgroup RECO, so that Archivelogs get stored there. And with RMAN backups, you specify the FORMAT '+ RECCE' to get the backups in the recovery area (DBFS_DG in this example).

    Kind regards

    Uwe Hesse

  • Not correct ASM disk size

    Hi all

    I'm dealing with an interesting event in ASM. Summary of the problem;

    + FRA size 400 GB and free 175GB, the lsdg like this command output space on below;

    ASCMD > lsdg
    Name Type State Rebal Unbal sector block to Total_MB Free_MB Usable_file_MB Offline_disks Req_mir_free_MB
    EXTERN MOUNTED N N 512 4096 1048576 409600 175717 0 175717 0 FRA.
    EXTERN MOUNTED N N 512 4096 1048576 2252800 440059 0 440059 0 DATA.

    According to 'the' result of command FRA 265 GB size
    ASMCMD > cd + fra
    ASMCMD > of
    Used_MB Mirror_used_MB
    26515 26515

    So two value is different. I thit it is because we are questioned same area. Do you know why the two news are different?

    Perhalps it may be help response from your answer that, depending on the result to the "' select * v $ flash_recovery_area_usage;" " All the FRA in SQL * more.

    SQL > select * from v$ flash_recovery_area_usage;

    FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    ------------ ------------------ ------------------------- ---------------
    CONTROLFILE 0 0 0
    ONLINELOG 0 0 0
    0 8 ARCHIVELOG.92
    BACKUPPIECE 0 0 0
    IMAGECOPY 0 0 0
    FLASHBACKLOG 5.84 0 118

    Thank you...

    Hello

    Unbalanced disc can cause the missing disk free space does not allow to make any allocation to a disk group because each file should be evenly distributed across all disks by ASM political stripping.

    Configuration asymmetric discs and some operations on ASM disks can create this type of problem. Frequently, the problem must be resolved after a succesfull rebalance as much as all the drives have the same storage capacity, and there is no underlying hardware problem.
    The most common reasons may be the following:

    1 - the capacity of the disks within the ASM diskgroup are different
    2 - ASM instance is shutdowned normal/immediate before rebalancing is complete.
    3-disc is a FALL / HUNG State
    4. after an order to add disk rebalancing is still in place

    You can also try:

    ALTER DISKGROUP FRA CHECK ALL REPAIR;
    

    PS: Make sure you have these files on FRA was backed up somewhere safe.

    Kind regards
    Levi Pereira

  • How to find the drive assigned to ASM diskgroup

    Hi all
    I created some ASM disks and do not know if I attributed to a diskgroup. Please may I know how to find the disc by ASM diskgroup or free on the disk that can be used.


    Thank you.

    Hello

    You must make reference to:
    http://download.Oracle.com/docs/CD/B28359_01/server.111/b31107/asmdiskgrps.htm#CHDIBGGH
    If you scroll down a bit you'll find: "groups example 4-3 look at a disk with associated disks.

    You can also check more specifically:
    http://www.Stanford.edu/dept/ITSS/docs/Oracle/10G/server.101/b10755/dynviews_1019.htm

    HTH,
    Thierry

  • How to OCR and the drive to vote of raw devices for ASM diskgroup

    Hello

    I plan to upgrade my environment clusterware/ASM 11.1.0.6 to the grid
    infrastructure 11.2.0.1 on Solaris sparc 64-bit.
    I also plan on spending the OCR and discs of raw devices to ASM voting
    starts. But how to do? When should I do: upgrade
    process or after the upgrade? When should I start?

    Thank you

    create a disk group or use an existing disk group that matches your redundancy needs

    To ocr asm
    ===============
    1 ensure that the clusterware version 11.2.0
    # crsctl query crs activeversion
    Oracle Clusterware version active on the cluster is [11.2.0.1.0]

    2. replace the OCR file by the asm disk group
    #ocrconfig - replaced - replacement<+ASM diskgroup="">

    3 remove the old file ocr
    #ocrconfig - remove

    4. check the integrity of the ocr
    $cluvfy comp ocr n - verbose

    SE asm votedisk
    ======================
    1. Add the voting disk to the asm disk group
    #crsctl replace votedisk<+asm disk="" groupname="">

    Note: According to the disk group redundancy the required number of ocr and voting disk files will be created
    Normal: 2ocr, 3voting disc
    For the great: 3 ocr, voting 5 disc

    do not backup the ocr/votedisk dd in 11.2.0

  • Display spfile ASM diskgroup while the database cannot be started?

    Hi all

    We are 10.2.0.3 and window 2003 server. And the init.ora file has a line in ' SPFILE='+DG_DATA/MITCH/spfileMITCH.ora'.

    Once I cannot start the database and got the below error. I googled and he said if I can reduce large_pool_size or sga_target, I should be able to start. But I need to know what in the spfile to create the new file init. So my question is how to view the contents of a SPFILE recorded in the ASM diskgroup. I have leans on the log of alerts to found the parameter values. But I don't know if there is a way better and safer to enter the SPFILE. Thanks in advance for your help,

    Shirley

    ORA-27102: out of memory
    OSD-00026: additional error information
    S/O-error: (OS 1455) the pagefile is too small for this operation ends

    Shirley,

    Not even in normal file system you "cannot read spfile. Its always better to create pfile from spfile

     sqlplus '/as sysdba'
     sqlplus >create pfile='/location/init.ora' from spfile;
    
     or you can start an instance with pfile
     sqlplus> startup nomount pfile='/location..../init.ora';
     If successfully processed all the parameters
     sqlplus>alter database mount;
     sqlplus>alter database open;
    
     If successful shutdown it down and create spfile from pfile='/location/init.ora';
    
     sqlplus>create spfile from pfile='/location/init.ora';
     sqlplus>startup;
    

    Concerning

  • Can Notes show the number of records with each folder?

    Can Notes show the number of records with each folder?

    No it can't. It would be nice tho.

  • iPad Mini will not show iOS10 update?

    Hi all.

    My iPad mini 1st generation will not show the update option to iOS10 via iTunes or wireless.

    Any suggestions how?

    Your iPad CPU is not powerful enough to run iOS 10.

    (144743)

Maybe you are looking for

  • Satellite P100-160 where can I get a new battery quickly?

    I got a Toshiba Satellite P100-160 (17 "screen version) for about three and a half years now and the battery is toast. The battery I States the following: Toshiba Li-ion batteryModel PA3479U-1BRSPABAS078DC 10.8V Please could someone tell me where I c

  • Banking online with Acer Chromebooks

    I did online banking on my Windows desktop PC for a few years. Does anyone have a trained or experienced, notice to know if banking services online (cloud) with Chromebooks is less safe than on a hard drive? I would prefer banking with my Chromebooks

  • Inspiron 15 (3521) Wireless 'limited'... but only in some places!

    I spent days trying to solve this problem on this laptop. I bought it as a Christmas gift for my son, to see that he had a problem with wifi connectivity. What is crazy is that he connects perfectly to my home router and will link perfectly with two

  • Moving my documents, pictures, music, etc. Records

    My laptop has two 30 GB hard drives, and I've heard that move all data files to a drive that is separated from the unit containing windows will improve performance.  In addition, the 'C' drive is completed.How can I move the location of these folders

  • BlackBerry Storm Smartphones Calander

    I just got my new storm and when I went to enter the appointments in the calendar, I noticed that he was separated from 09:00 to 17:00, how to extend or modify the schedule to cover my early morning and late evening appointments?