ASM starts

Hi all

10.2.0.4.0 RAC on Win server 2008.

for the first time, I looked in the newspaper of asm file. I found something strange. why he keeps assemble and disassemble? What is acceptable behavior?

My Sep 03 12:16:59 2014

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

My Sep 03 13:06:26 2014

Thread 1 Advanced to record the sequence 95946 (switch LGWR)

Currently journal # 5 seq # 95946 mem # 0: +ASM_CF_DG/unigidc/onlinelog/group_5.261.745547573

Currently journal # 5 seq # 95946 mem # 1: +ASM_RF_DG/unigidc/onlinelog/group_5.261.745547573

My Sep 03 13:06:26 2014

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

My Oct 03 14:12:01, 2014

Thread 1 Advanced to record the sequence 95947 (switch LGWR)

Currently journal # 1, seq # 95947 mem # 0: +ASM_CF_DG/unigidc/onlinelog/group_1.257.745541821

Currently journal # 1, seq # 95947 mem # 1: +ASM_RF_DG/unigidc/onlinelog/group_1.257.745541821

My Oct 03 14:12:01, 2014

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

My Oct 03 14:40:09 2014

Thread 1 Advanced to record the sequence 95948 (switch LGWR)

Currently Journal # 2 seq # 95948 mem # 0: +ASM_CF_DG/unigidc/onlinelog/group_2.258.745541823

Currently Journal # 2 seq # 95948 mem # 1: +ASM_RF_DG/unigidc/onlinelog/group_2.258.745541823

My Oct 03 14:40:09 2014

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

SUCCESS: diskgroup ASM_FRA_DG rose

SUCCESS: diskgroup ASM_FRA_DG has been removed

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

This kind of newspapers were there in the log file of almost every day.

Thanks in advance.

It is true, in version 10 and 11, but mount/diskmount disk may not have access to the databases.

HTH - Antonio NAVARRO

Tags: Database

Similar Questions

  • Is have RAID (1 + 0) so that Failgroups for all ASM ASM starts is a well-known best practice?

    Dear Experts,

    Is have RAID (1 + 0) so that Failgroups for all ASM ASM starts is a well-known best practice?

    Having both is the best practice

    • RAID (1 + 0)
    • ASM Failgroups for all ASM starts

    Thank you

    IVW

    You can create groups of ASM disks with normal or high redundancy or specify external redundancy. It depends on your reliability requirements and storage performance. Remember that ASM is not RAID and redundancy is the base file. ASM uses alternating devices. Oracle is generally recommended to have redundancy of storage. If you have RAID redundancy at the level of hardware controller or storage, Oracle recommends to configure ASM disks with external redundancy groups. Redundancy of the DSO is only between groups of disk failure and by default, each device's own failure group. Of course, you always want to make sure that you do not rely on redundancy of data between logical devices or partitions residing on a single physical unit. Compared to external RAID redundancy redundancy ASM using will give the DBA more control and transparency on the setting of the underlying.

  • Disaster recovery with different ASM starts

    Hi@all,

    in fact, I'm testing a scenario of recovery after a disaster. To an Oracle Linux 6 Server with installed grid below 12 c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 instance of database) I'm doing a recovery after a disaster. But I'm unleashed by the restoration and recovery of the database. The problem here is that ASM diskgroup name has changed. As you read I also changed the physical server, but I think that should not be a problem.

    To the old server, I have two ASM starts '+ DATA' and '+ FRA_1', to the new, they are called '+ DATA_SRVNAME' and '+ FRA_SRVNAME '. I already changed the startup in spfile parameter, but now after restoring the controlfile RMAN has directions to the old diksgroup:

    RMAN> report schema;


using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name SID


List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1    0        SYSTEM               ***     +DATA/SID/datafile/system.438.816606399

    So I tried three ways. First was rename data file name:

    ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';

    Then had to set the newname in RMAN:

    set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';

    And the second was to recreate the controlfile with

    CREATE CONTROLFILE REUSE DATABASE "SID" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 1
    MAXLOGHISTORY 1815
LOGFILE
  GROUP 1 ('+DATA__SRVNAME', '+FRA_SRVNAME')  SIZE 1024M,
DATAFILE
  '+DATASRVNAME/SID/datafile/system.438.816606399',
CHARACTER SET AL32UTF8;

    But the three methods gave me the error that the file data to the new location is not available (for example):

    ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist

    So now my question: how am I able to say the controlfile or the database to use the another diskgroup in ASM?

    I know, the simplest way would be to create a diskgroup + DATA and do the restore / recovery, but on the new server, I have no more storage to assign to a new diskgroup, and because there are running other forums I would'nt change ASM starts.

    Do you have anny solution?

    A big thank you and best regards,

    Dave

    Please try this

    RMAN > run

    {

    the value of newname for datafile 1 to "+ DATA_SRVNAME";

    restore data file 1;

    switch datafile 1;

    recover datafile 1;

    }

    Did you create + diskgroup DATA_SRVNAME?

    and

  • How to install the db oracle11gr2 shared on two asm starts

    I have two ASMDGs (ASMDG & ASMDG2 say) with two separate databases (say, orcl & orcl2). Now, I want to install a shared database (say orcl1) on both of these ASMDGs. But I use dbca to create orcl1 when the selection starts, I can't select both two starts.

    Can anyone give help how do to install a database shared on two asm starts?

    Thank you

    Choose only one initially and, a little further in the DBCA, you can set the location of the data files separately.

    Here you can specify which of the two starts to use for each data file manually. You can create the ASM directories manually with asmcmd.

    I hope this information helps,

    Kind regards

    Enric Moya

  • warning message, critical on all ASM starts

    Hello
    Please can someone help me set up the Grid control for:
    -warning message when all ASM starts a database is with (for example 24 GB free)
    -critical message when all ASM starts a database is with (for example 4 GB free)

    I had implemented this feature previously in view using view oracle v$ asm_diskgroup, but now I need to put in place using the Grid control.

    Thank you
    Best regards
    Dragan

    Hello

    Please follow the oder to set the threshold.

    Click on "Targets" on Grid control--> databases--> select the db that uses ASM--> client on ASM instance (bottom of page)--> click metrics and parameters of strategy (bottom of page)

    You will get a page with the metric threshold, and you can configure all the critical and warning thresholds.

    I hope this helps.

    Concerning
    Ludmilla amine
    http://oracleracexpert.blogspot.com
    [Install and configure ASM in 10g | http://oracleracexpert.blogspot.com/2009/08/install-and-configure-asmlib-in-10g.html]

  • How to rename ASM starts after cloning disks of origin on the same server. ASMlib is used

    RHE Linux 6

    The single-instance grid installed Oracle (Oracle Restart) 11.2.0.4

    Oracle RDBMS 11.2.0.4 installed

    A 11.2.0.4 single-instance database running

    Our ASM GAVE, REDO, FRA mounted diskgroup

    We need to do a snapshot of storage for the creation of a copy of the current start ASM DATA, REDO, FRA on THE SAME server. Then we rename it cloned starts using the renamedg command.

    We did this several times if ASMlib is not used. For example, the command used when ASMlib is not used is:

    renamedg = newdgname = verbose = FRA2 FRA dgname true phase = the two asm_diskstring = "/ dev/oracle/fra *'"

    With ASMlib in use, I'm not sure the steps to follow

    First of all I'm not sure what should be provided to the asm_diskstring for the renamedg command parameter. I provide an asm_diskstring that identifies the path pointing to records belonging to the diskgroup cloned (I don't want to rename the original diskgroup). But ASM instance using ASMlib is the asm_diskstring parameter is in ' ORCL: *'.

    Second, I guess that after the rename diskgroup than asmlib returns an error because she would double discs.

    Could you please tell?

    Thanks in advance

    Massi

    Hello

    As you clone OS level, you have same ASMlib label.

    ASMlib mount always unique ASMLib label only.

    + You must identify these newly cloned device.

    + Rename these ASMLib force-renamedisk label after 1 Mb disk backup using dd read on a node.

    + Then run scandisks on other nodes.

    + Validate newly approved device is mounted or not on all nodes.

    $ ls - ltr/oracleasm/dev/discs / *.

    + Run command with asm_diskstring of/dev/discs/oracleasm renamedg / *.

    Kind regards

    Loriette

  • Oracle 10g 10.2.0.1.0 + ASM starts automatically on win2003

    Hello to everyone.

    I have an Oracle 10 g 10.2.0.1.0 database that uses ASM to store and I have the following problem.
    Whenever the server is restarted, and although all related oracle services are provisioned automatically, the database starts, and I have to manually start through sqlplus.
    After that, the database works very well.
    I checked to find errors in the alert.log but found none.
    I also checked the oradim.log where I found the following:

    Wed 22 Oct 11:01:48 2008
    E:\oracle\product\10.2.0\db_1\bin\oradim.exe-demarrage-SID ora10g - usrpwd * - log oradim.log - nocheck 0
    Wed 22 Oct 11:01:55 2008
    ORA-01078: failure in the treatment of system settings
    ORA-01565: error in the identification of file "+ DATA/ora10g/spfileora10g.ora".
    ORA-17503: ksfdopn:2 could not open the file +DATA/ora10g/spfileora10g.ora
    ORA-15077: could not locate instance ASM serving a required diskgroup

    Can someone explain please to me this behavior and how to act to solve the problem?

    Thanks in advance.
    Frank.

    Published by: user2052806 on Οκτ 22 2008 08:37 πμ

    I found this metalink note:

    THE ASM INSTANCE DOESN'T AUTOSTART ORA-01078, ORA-01565, ORA-17503 AND ORA-15077.
    DOC - ID: NOTE: 467125.1

    This is a bug in 10.2.0.1 and a patch is available as shown in this note. 4547817 is a group of complete patches (10.2.0.2), I think he understands the one-time fix. If you want to fix, you should go directly to 10.2.0.4.

    Werner

  • ASM starts on different types of storage?

    Hello

    We intend to keep + DATA storage quick flash, unfortunately our estimate of storage exceeds the maximum capacity of the fast flash drives. I was wondering if I can have faster drives for slower DATA disks for + and FRA that cause issues? We intend to have the recovery log DATA on + and + FRA for multiplexing, but if we probably go slower readers then we can multiplex oder in + the DATA itself. I would like to know your opinion.

    -RD

    > I was wondering if I can have faster drives for slower DATA disks for + and FRA that cause issues?

    N ° this combination would be used in several places.  It has been the case even in an era before pre - ASM and FRA. Backups would go slower discs if the organization chose to use slower disks for backups.

    > but if we probably go for slower readers, then we can multiplex oder in + the DATA itself.

    Yes, multiplexing between fast and slow drives is a bad idea.  I've implemented it with a group of separate drives on separate disks for recovery multiplexed logs.

    Hemant K Collette

  • Problem with different ASM disaster recovery start - new

    Hello together,

    I had an old net here about it but now will not solve the problem with the points in the old thread. Here's the old: https://community.oracle.com/thread/3608049?start=0 & tstart = 0

    I'm doing a disaster recovery with the 'apex11A' on a new server database, which has an another ASM starts. The old man starts is '+ DGA112_1' and '+ FRA112_1', newcomers are called '+ DATA_QUM169' and '+ FRA_QUM169 '. I changed the settings in the spfile restored by writing in a pfile file and creating the spfile from pfile.

    I tried in several ways. First lay the new ASM with RMAN to the course:

    run
{
SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

    Then I tried it in RMAN by defining the new ASM for each data file:

    run
{
SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

    Then I tried the bot in one:

    run
{
SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

    Whenever I get one

    Starting restore at 03-FEB-16
using channel ORA_DISK_1


creating datafile file number=1 name=+DATA_QUM169
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/03/2016 16:20:41
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'

    The backuppiece which I bring are correctly defined with

    RMAN> catalog backuppiece '/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1', '/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1';


cataloged backup piece
backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1 RECID=3779 STAMP=902851052
cataloged backup piece
backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1 RECID=3780 STAMP=902851052


RMAN> list backup;




List of Backup Sets
===================




BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3779    52.61M     DISK        00:00:00     03-FEB-16
        BP Key: 3779   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145340
        Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1


  List of Archived Logs in backup set 3779
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    24285   11073415926066 03-FEB-16 11073416327345 03-FEB-16
  1    24286   11073416327345 03-FEB-16 11073416678326 03-FEB-16


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3780    Full    813.86M    DISK        00:00:00     03-FEB-16
        BP Key: 3780   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145042
        Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1
  List of Datafiles in backup set 3780
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/system.1423.788355253
  2       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/sysaux.1422.788355259
  3       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/undotbs1.1359.788355263
  4       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/users.1362.788355273
  5       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4.1369.788356305
  6       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4_files.1366.788356317
  7       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms_archiv.1358.788357229
  8       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/planwerte.1357.788357243
  9       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_prod.1352.788456613
  10      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais.1353.788456763
  11      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms.1354.788456995
  12      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/externe_wirk.1355.788457525
  13      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2mt.1356.788458151
  14      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_read.1351.788458291
  15      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329
  16      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657
  17      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/macmon.1340.788458691
  18      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais_read.1339.788458725
  19      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2srm.266.788458799
  20      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859
  21      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/quickcheck.1338.788458887
  22      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/switch.1337.788459139
  23      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/veit_r.1333.788459167
  24      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/test-btdb.1298.795097725
  25      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11dev.986.874230931
  26      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11devbt.985.874230963
  27      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hrbew.1083.851007823
  28      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/optimadata.1032.865951029

    I also tried to put the new ASM SQL:

    SQL*Plus: Release 11.2.0.4.0 Production on Wed Feb 3 16:04:05 2016


Copyright (c) 1982, 2013, Oracle.  All rights reserved.




Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Automatic Storage Management and OLAP options


SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 1 - new file '+DATA_QUM169' not found
ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 2 - new file '+DATA_QUM169' not found
ORA-01110: data file 2: '+DGA112_1/apex11a/datafile/sysaux.1422.788355259'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 3 - new file '+DATA_QUM169' not found
ORA-01110: data file 3: '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 4 - new file '+DATA_QUM169' not found
ORA-01110: data file 4: '+DGA112_1/apex11a/datafile/users.1362.788355273'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 5 - new file '+DATA_QUM169' not found
ORA-01110: data file 5: '+DGA112_1/apex11a/datafile/apex4.1369.788356305'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 6 - new file '+DATA_QUM169' not found
ORA-01110: data file 6: '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 7 - new file '+DATA_QUM169' not found
ORA-01110: data file 7: '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 8 - new file '+DATA_QUM169' not found
ORA-01110: data file 8: '+DGA112_1/apex11a/datafile/planwerte.1357.788357243'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 9 - new file '+DATA_QUM169' not found
ORA-01110: data file 9: '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 10 - new file '+DATA_QUM169' not found
ORA-01110: data file 10: '+DGA112_1/apex11a/datafile/mais.1353.788456763'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 11 - new file '+DATA_QUM169' not found
ORA-01110: data file 11: '+DGA112_1/apex11a/datafile/mms.1354.788456995'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 12 - new file '+DATA_QUM169' not found
ORA-01110: data file 12:
'+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 13 - new file '+DATA_QUM169' not found
ORA-01110: data file 13: '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 14 - new file '+DATA_QUM169' not found
ORA-01110: data file 14: '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 15 - new file '+DATA_QUM169' not found
ORA-01110: data file 15: '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 16 - new file '+DATA_QUM169' not found
ORA-01110: data file 16: '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 17 - new file '+DATA_QUM169' not found
ORA-01110: data file 17: '+DGA112_1/apex11a/datafile/macmon.1340.788458691'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 18 - new file '+DATA_QUM169' not found
ORA-01110: data file 18: '+DGA112_1/apex11a/datafile/mais_read.1339.788458725'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 19 - new file '+DATA_QUM169' not found
ORA-01110: data file 19: '+DGA112_1/apex11a/datafile/mais2srm.266.788458799'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 20 - new file '+DATA_QUM169' not found
ORA-01110: data file 20:
'+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 21 - new file '+DATA_QUM169' not found
ORA-01110: data file 21: '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 22 - new file '+DATA_QUM169' not found
ORA-01110: data file 22: '+DGA112_1/apex11a/datafile/switch.1337.788459139'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 23 - new file '+DATA_QUM169' not found
ORA-01110: data file 23: '+DGA112_1/apex11a/datafile/veit_r.1333.788459167'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 24 - new file '+DATA_QUM169' not found
ORA-01110: data file 24: '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 25 - new file '+DATA_QUM169' not found
ORA-01110: data file 25: '+DGA112_1/apex11a/datafile/apex11dev.986.874230931'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 26 - new file '+DATA_QUM169' not found
ORA-01110: data file 26: '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 27 - new file '+DATA_QUM169' not found
ORA-01110: data file 27: '+DGA112_1/apex11a/datafile/hrbew.1083.851007823'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 28 - new file '+DATA_QUM169' not found
ORA-01110: data file 28: '+DGA112_1/apex11a/datafile/optimadata.1032.865951029'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form

    But my new database will not set the new ASM and I have no why.

    The db_create_file_dest parameter is set correctly, so I think that:

    NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_create_file_dest                  string      +DATA_QUM169

    I forgot something? Would be nice to get help ...

    A big thank you and best regards,

    David

    Your data checkpoint SCN file are in the LOW and HIGH range of the SNA for SEQUENCE 24286.

    Therefore, your UNTIL clause should be 24287 SEQUENCE up to THAT.

    Hemant K Collette

  • urgent asm does not start with ora 1031. !!!

    Hi guys,.
    Stuck with a problem who are unsure how to proceed... cluster services doesnot comeup... tried to watch using crsctl start - n node cluster gives me error... below I'm missing something here... Can someone help me please on this...

    [node + ASM1:root] crsctl start - n node of cluster
    CRS-2672: attempt to start 'ora.asm' on 'node '.
    ORA-01031: insufficient privileges
    CRS-5017: the action "ora.asm start" resource has met the following error:
    ORA-01031: insufficient privileges
    . For details, refer to "(:CLSN00107:))" "in ' / u01/app/11.2.0.3/grid/log/node/agent/ohasd/oraagent_grid/oraagent_grid.log '.
    CRS-2674: beginning of 'ora.asm', the 'node' failed
    CRS-2679: attempt to clean the 'ora.asm' on 'node '.
    ORA-01031: insufficient privileges
    CRS-2681: clean 'ora.asm' on 'node' successful
    CRS-4705: beginning of the Clusterware failed on the node.
    CRS-4000: Start command has failed, or completed with errors.


    crsctl check crs shows me the following...

    CRS-4638: Oracle high availability Services is online
    CRS-4535: cannot communicate with Cluster Ready Services
    CRS-4529: Cluster Synchronization Services is online
    CRS-4534: can not communicate with the event Manager

    tried from asm manually... but not sufficient privileges said...


    [node: + ASM1:grid] echo $ORACLE_HOME
    /U01/app/11.2.0.3/grid
    [node: + ASM1:grid] echo $ORACLE_SID
    + ASM1



    [node: + ASM1:grid] sqlplus "virtue sysdba".

    SQL * more: Production of liberation 11.2.0.3.0 sam 8 15:21:21 dec 2012

    Copyright (c) 1982, 2011, Oracle. All rights reserved.

    Connect to an instance is idle.

    SQL > startup
    ORA-01031: insufficient privileges

    Grid has the following privileges

    [node: + ASM1:grid] id
    UID = 501 (Grid) gid = 501 (oinstall) groups = 501 (oinstall), 502 (dba), 504 (asmadmin), 506 (asmdba), 507 (asmoper)

    ID [node: ipdexdev1:oracle]
    UID = 502 (Oracle) gid = 501 (oinstall) groups = 10 (wheel), 501 (oinstall), 502 (dba), 506 (asmdba)

    The other node works very well... against the privileges that they are the same on the other node too...

    sys / ACE sysasm

    then start

  • A single node of the cluster cannot start

    Hello all,.

    I hope you can help me. We have a 2 node rac. the first node cannot be started due to:

    [cssd (16558)] CRS-1714: impossible to discover all files with right to vote, a new attempt of discovery in 15 seconds; Details at (: CSSNM00070 :) in /pkg/app/11.2.0/grid/log/defr2elvhms01/cssd/ocssd.log)

    2015-09-28 14:45:19.038:

    [cssd (16558)] CRS-1714: impossible to discover all files with right to vote, a new attempt of discovery in 15 seconds; Details at (: CSSNM00070 :) in /pkg/app/11.2.0/grid/log/defr2elvhms01/cssd/ocssd.log)

    2015-09-28 14:45:34.059:

    [cssd (16558)] CRS-1714: impossible to discover all files with right to vote, a new attempt of discovery in 15 seconds; Details at (: CSSNM00070 :) in /pkg/app/11.2.0/grid/log/defr2elvhms01/cssd/ocssd.log)

    the crs is the OCR disk, it is visible it the log file:

    2015-09-28 14:46:49.120: Lib [SKGFD] [2107098880]: ASM:/opt/oracle/extapi/64/asm/orcl/1/libasm.so: handle 0x7fec68140800 for closing disk: ORCL:REDO:

    2015-09-28 14:46:49.120: [CSSD] [2107098880] clssnmvDiskVerify: discovery of a potential voting file

    2015-09-28 14:46:49.120: [SKGFD] [2107098880] handful 0x7fec68140dd0 to lib: ASM:/opt/oracle/extapi/64/asm/orcl/1/libasm.so: disc: ORCL:OCR1:

    2015-09-28 14:46:49.121: [CSSD] [2107098880] clssnmvDiskVerify: table of contents format offset expected (0x634c7373 0x546f636b), found(0x434c5366 0x0000)

    2015-09-28 14:46:49.121: Lib [SKGFD] [2107098880]: ASM:/opt/oracle/extapi/64/asm/orcl/1/libasm.so: handle 0x7fec68140dd0 for closing disk: ORCL:OCR1:

    2015-09-28 14:46:49.121: [CSSD] [2107098880] clssnmvDiskVerify: Discovery successful record 0

    2015-09-28 14:46:49.121: [CSSD] [2107098880] clssnmCompleteInitVFDiscovery: completing the first discovery of the file with the right to vote

    2015-09-28 14:46:49.121: [CSSD] [2107098880] clssnmvFindInitialConfigs: no vote files found

    2015-09-28 14:46:49.121: [CSSD] [2107098880](:CSSNM00070:) clssnmCompleteInitVFDiscovery: vote fichier non trouvé.) A new attempt of discovery in 15 seconds

    The failed node can be started in exclusive mode, and I'm able to connect to the asm, but of course without disks. When I am trying to mount starts, I get the following:

    SQL > alter the data carrier diskgroup.

    change data diskgroup mount

    *

    ERROR on line 1:

    ORA-15032: not all changes made

    ORA-15017: diskgroup 'DATA' cannot be mounted

    ORA-15063: ASM discovered an insufficient number of drives for diskgroup "DATA".

    ORA-15085: ASM disk "" the size of incompatible sector.


    We seem to be affected by the similar problem as written:

    After SAN Firmware Upgrade , ASM starts (using ASMLIB) not be mounted Due To ORA-15085: ASM disk "" the size of incompatible sector. (Doc ID 1500460.1()


    kernel cannot be updated thus affecting the ORACLEASM_USE_LOGICAL_BLOCK_SIZE is not possible.

    What we do not understand why the failed node has different physical block size / logic. Why the oracle on the failed node linux recognize different value? If it was the same thing, no doubt the cluster could start up:

    [root@defr2elvhms02 ~] # rpm - qa | grep-i asm

    oracleasmlib - 2.0.4 - 1.el6.x86_64

    oracleasm-support - 2.1.8 - 1.el6.x86_64

    [root@defr2elvhms02 ~] # uname - a

    Linux defr2elvhms02 2.6.32 - 400.37.1.el6uek.x86_64 #1 SMP Thu Feb 5 14:58:47 PST 2015 x86_64 x86_64 x86_64 GNU/Linux

    [root@defr2elvhms02 ~] #.

    [root@defr2elvhms02 ~] # oracleasm querydisk d OCR1

    Disc 'OCR1' is a valid ASM disk device [8.1]

    [root@defr2elvhms02 ~] # oracleasm querydisk d OCR2

    Disc 'OCR2' is a valid ASM disk device [8.17]

    [root@defr2elvhms02 ~] # oracleasm querydisk d OCR3

    Disc 'OCR3' is a valid ASM disk device [8.33]

    [root@defr2elvhms02 ~] # ls-l/dev/sda1

    BRW - rw-. Disc 1 root 8, 1 Sep 29 16:21 / dev/sda1

    [root@defr2elvhms02 ~] # ls-l/dev/sdb1

    BRW - rw-. Disc 1 root 8, 17 Sep 29 16:21 / dev/sdb1

    [root@defr2elvhms02 ~] # ls-l/dev/sdc1

    BRW - rw-. Disc 1 root 8: 33 Sep 29 16:21 / dev/sdc1

    [root@defr2elvhms02 ~] # fdisk-l/dev/sda

    Disk/dev/sda: 10.7 GB, 10737418240 bytes

    Heads of 64, 32 sectors/track, 10240 cylinders

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 512 bytes

    Size of the e/s (minimum/maximum): 512 bytes / 512 bytes

    Disk identifier: 0x20700d2b

    Device boot start end blocks Id system

    / dev/sda1 10 10240 10476544 83 Linux

    [root@defr2elvhms02 ~] # fdisk-l/dev/sda1

    Disk/dev/sda1: 10.7 GB, 10727981056 bytes

    Heads of 64, 32 sectors/track, 10231 bottles

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 512 bytes

    Size of the e/s (minimum/maximum): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

    [root@defr2elvhms02 ~] # fdisk-l/dev/sdb

    Disk/dev/sdb: 10.7 GB, 10737418240 bytes

    Heads of 64, 32 sectors/track, 10240 cylinders

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 512 bytes

    Size of the e/s (minimum/maximum): 512 bytes / 512 bytes

    Disk identifier: 0x62515b34

    Device boot start end blocks Id system

    / dev/sdb1 10 10240 10476544 83 Linux

    [root@defr2elvhms02 ~] # fdisk-l/dev/sdb1

    Disk/dev/sdb1: 10.7 GB, 10727981056 bytes

    Heads of 64, 32 sectors/track, 10231 bottles

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 512 bytes

    Size of the e/s (minimum/maximum): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

    [root@defr2elvhms02 ~] # fdisk-l/dev/sdc

    Disk/dev/sdc: 10.7 GB, 10737418240 bytes

    Heads of 64, 32 sectors/track, 10240 cylinders

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 512 bytes

    Size of the e/s (minimum/maximum): 512 bytes / 512 bytes

    Disk identifier: 0xc254acd9

    Device boot start end blocks Id system

    / dev/sdc1 10 10240 10476544 83 Linux

    [root@defr2elvhms02 ~] # fdisk-l/dev/sdc1

    Disk/dev/sdc1: 10.7 GB, 10727981056 bytes

    Heads of 64, 32 sectors/track, 10231 bottles

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 512 bytes

    Size of the e/s (minimum/maximum): 512 bytes / 512 bytes

    Disk identifier: 0x00000000

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

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

    [root@defr2elvhms01 ~] # uname - a

    Linux defr2elvhms01 2.6.32 - 400.37.1.el6uek.x86_64 #1 SMP Thu Feb 5 14:58:47 PST 2015 x86_64 x86_64 x86_64 GNU/Linux

    [root@defr2elvhms01 ~] # rpm - qa | grep-i asm

    oracleasmlib - 2.0.4 - 1.el6.x86_64

    oracleasm-support - 2.1.8 - 1.el6.x86_64

    [root@defr2elvhms01 ~] # oracleasm querydisk d OCR1

    Disc 'OCR1' is a valid ASM disk device [8.1]

    [root@defr2elvhms01 ~] # oracleasm querydisk d OCR2

    Disc 'OCR2' is a valid ASM disk device [8.17]

    [root@defr2elvhms01 ~] # oracleasm querydisk d OCR3

    Disc 'OCR3' is a valid ASM disk device [8.33]

    [root@defr2elvhms01 ~] # ls-l/dev/sdb1

    BRW - rw-. Disc 1 root 8, 17 Sep 29 15:32 / dev/sdb1

    [root@defr2elvhms01 ~] # ls-l/dev/sda1

    BRW - rw-. Disc 1 root 8, 1 Sep 29 15:32 / dev/sda1

    [root@defr2elvhms01 ~] # ls-l/dev/sdb1

    BRW - rw-. Disc 1 root 8, 17 Sep 29 15:32 / dev/sdb1

    [root@defr2elvhms01 ~] # ls-l/dev/sdc1

    BRW - rw-. Disc 1 root 8: 33 Sep 29 15:32 / dev/sdc1

    [root@defr2elvhms01 ~] # fdisk-l/dev/sda

    Disk/dev/sda: 10.7 GB, 10737418240 bytes

    Heads of 64, 32 sectors/track, 10240 cylinders

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 4096 bytes

    The e/s (minimum/maximum) size: 4096 bytes / 65536 bytes

    Disk identifier: 0x20700d2b

    Device boot start end blocks Id system

    / dev/sda1 10 10240 10476544 83 Linux

    [root@defr2elvhms01 ~] # fdisk-l/dev/sda1

    Disk/dev/sda1: 10.7 GB, 10727981056 bytes

    Heads of 64, 32 sectors/track, 10231 bottles

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 4096 bytes

    The e/s (minimum/maximum) size: 4096 bytes / 65536 bytes

    Disk identifier: 0x00000000

    [root@defr2elvhms01 ~] # fdisk-l/dev/sdb

    Disk/dev/sdb: 10.7 GB, 10737418240 bytes

    Heads of 64, 32 sectors/track, 10240 cylinders

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 4096 bytes

    The e/s (minimum/maximum) size: 4096 bytes / 65536 bytes

    Disk identifier: 0x62515b34

    Device boot start end blocks Id system

    / dev/sdb1 10 10240 10476544 83 Linux

    [root@defr2elvhms01 ~] # fdisk-l/dev/sdb1

    Disk/dev/sdb1: 10.7 GB, 10727981056 bytes

    Heads of 64, 32 sectors/track, 10231 bottles

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 4096 bytes

    The e/s (minimum/maximum) size: 4096 bytes / 65536 bytes

    Disk identifier: 0x00000000

    [root@defr2elvhms01 ~] # fdisk-l/dev/sdc

    Disk/dev/sdc: 10.7 GB, 10737418240 bytes

    Heads of 64, 32 sectors/track, 10240 cylinders

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 4096 bytes

    The e/s (minimum/maximum) size: 4096 bytes / 65536 bytes

    Disk identifier: 0xc254acd9

    Device boot start end blocks Id system

    / dev/sdc1 10 10240 10476544 83 Linux

    [root@defr2elvhms01 ~] # fdisk-l/dev/sdc1

    Disk/dev/sdc1: 10.7 GB, 10727981056 bytes

    Heads of 64, 32 sectors/track, 10231 bottles

    Units = cylinders of 2048 * 512 = 1048576 bytes

    Sector size (logical or physical): 512 bytes / 4096 bytes

    The e/s (minimum/maximum) size: 4096 bytes / 65536 bytes

    Disk identifier: 0x00000000

    Thank you for the help

    I have changed accounts.

    We managed to find the reason. First of all, it is a virtual machine. An expert colleague told me to check the hardware of vmware. We managed to find out that there is a difference of ILO to host vmware hardware. Even if the guest OS virtual material seem to be the same, but the difference between the results of operating system host different logical and physical size of block on 2 nodes. This is the reason.

    We had to update the kernel to apply the setting ORACLEASM_USE_LOGICAL_BLOCK_SIZE to repair the block size for clusterware difference. Everyone was puzzled about why, but the most important is the host VMware system in this issue.

    Thanks for the help

    Attila

  • file system support for ASM with NAS?

    Can someone tell me the management system of files for ASM with NAS?

    Thank you

    How To Create ASM starts using NFS/NAS files? (Doc ID 731775.1)

    http://docs.Oracle.com/CD/E11882_01/install.112/e17212/storage.htm#CWLIN291

  • Assignment of names manually in ASM files

    Version of grid infrastructure: 11.2.0.4

    RDBMS Version: 11.2.0.4

    When you have an ASM filesystem, you can add a file of data using Method1 or methode2 below.

    Name the files manually using the method 1 (non - OMF) is not recommended. But I don't remember why? Anyone know?


    -Method1 (non - OMF)

    ALTER TABLESPACE CSE_TBS add DATAFILE '+ UIM_DATA/eimprod/datafile/cse_tbs_03.dbf' size 10g autoextend on next 100 m MAXSIZE 32767 m;

    -Methode2 (OMF leaving decide the file naming)

    ALTER TABLESPACE CSE_TBS add DATAFILE '+ UIM_DATA' size 10g autoextend on next 100 m MAXSIZE 32767 m;

    ASM starts is only designed to manage Oracle data files. Whether or not, you use OMF ASM knows Oracle databases and put in the right place including the optimum settings for the distribution and duplication, without worrying. When you specify the name of the data file, ASM will always create a data using OMF file, but it will create an additional ALIAS according to the name you specified. I'm not sure if not using OMF is really recommended, but it can really be any advantage and quite confusing.

  • Settings memory ignored after reboot (ASM instance)

    Hi all

    ASM version: 11.2.0.4

    OS: SunOS fmsdb 5.10 Generic_150401-18 i86pc i386 i86pc

    I'm trying to reduce the setting memory_max_target on the ASM instance.


    Here are the current settings of the memory;

    SQL > target setting sho

    NAME                                 TYPE                              VALUE

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

    memory_max_target big integer 1 G

    memory_target large integer 1 G

    pga_aggregate_target large integer 0

    SGA_TARGET large integer 0

    I just changed the memory_max_target and the memory_target to 544 M in spfile. I can see the new values in spfile. Here's the new values;


    SQL > select NAME, display_value from v$ spparameter whose name IN ('memory_target', 'memory_max_target');

    NAME DISPLAY_VALUE

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

    memory_target 544 M

    memory_max_target 544 M


    After the reboot of the ASM instance, these new values ignored by Oracle.


    Here are the current settings of the memory after reboot;

    SQL * more: Production of the 11.2.0.4.0 version on Tue Mar 10 14:56:30 2015

    Copyright (c) 1982, 2013, Oracle.  All rights reserved.

    Connect to an instance is idle.

    SQL > startup

    ASM instance started

    Total System Global Area 1068937216 bytes

    Bytes of size 2257712 fixed

    1041513680 variable size bytes

    ASM Cache 25165824 bytes

    ASM starts up

    SQL > target setting sho

    NAME                                 TYPE                              VALUE

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

    memory_max_target big integer 1 G

    memory_target large integer 1 G

    pga_aggregate_target large integer 0

    SGA_TARGET large integer 0

    Why these settings changed?

    Thank you

    Erman

    Have a read of the default value and value MEMORY_TARGET & MEMORY_MAX_TARGET Minimum for ASM 11.2.0.4 and after (Doc ID 1982132.1)

    on Oracle support and you'll see why your memory_target is 1 GB. I did not use ASM recently and never paid no attention to the memory allocation when I did (because there was no reason to).

  • ASM: determine the total number of bytes read/written & Ops / s

    Hello

    My environment:

    • Oracle 11.2.0.3 EE
    • SuSE Enterprise Linux 11 SP1, 64-bit
    • ASM starts on RAW LUNS (2 per group) Hitachi disk storage
    • DB-server: HP DL380 G7

    I want to disc ASM ssd drive switch, direct attach to via HP DS2700 attachment:

    • DiskGroup + DATA
      5x400GB Enterprise SSD, RAID 5, 1.6 TB of raw capacity
      used to redo, data files
    • DiskGroup + ARCH
      4x400GB Enterprise SSD, RAID0 + 1, capacity of 800GBraw
      used to redo, Archives, Flash Recovery Area

    As I understand until this SSD technology, SSD have a livetime, indicating that there is a guaranteed amount of data that can be read/written on this subject. My goal is to design a system that has no point of two ssd failure in the same RAID group.

    1. How can I determine the total number of bytes read/written in ASM starts so far?
      My idea was to dermine ASM block size (select block_size from v$ asm_diskgroup) and then look at total reads and writes columns via iostat command in asmcmd. I guess that these values are since the last start of the DSO.
    2. Is it possible to determine the IOPS / sec per diskgroup?

    Thank you
    SCSI

    Casimir wrote:

    Do the calculation for 1. gives me an odd result:

    ASMCMD disk group management controls said that the default view is the amount of bytes and that the -io parameter must be used to display the number of e/s instead.

Maybe you are looking for

  • Delete all iTunes work

    I looked at all the forums and the only hope I had was the option > info to get the info from the 'old' get window. Apple has taken that away so now I'm back to square one. Any ideas on how to remove all of the work for each album/song in iTunes 12.3

  • What is the cellular part of the iPad? What he will do that the iPad without it going?

    I'm about to buy a new iPad. I have an iPad original 1. What is the WiFi part used for and what is the cell part used for?

  • Strange colors

    Hello A few days ago I pulled to the top of my Pavilion dv6 3240us and he did something weird. The colors are a little unhinged. Bright white area shows as Cyan and dark (black) are a kind of Burgundy or dark red.  I can adjust the contrast a bit dow

  • BlackBerry Smartphones Email icons.

    Hi all I recently received a replacement Storm. I got 2 emails, my Blackberry/Verizon one & my personal account. How can I get these icons for these accounts is displayed on my new storm? I went to e-mail settings and he said... ' Your account is cur

  • Vostro 420 with running DDR2-1066/PC2-8500 @ 1066?

    I know this will work very well with a faster memory running @ 800.  Site of crucial seems to imply that the machine will work @ 1066.  Anyone done this or tried?  What memory DDR3?  The G45 chipset that supports both.