Verify asm instance

Hi
What is the best way to verify that asm instance is mounted,up and ready ?
. oraenv
ORACLE_SID = [] ? +ASM
sqlplus "/ as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 11 14:30:38 2011
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-01507: database not mounted

Ricardinho wrote:
Hi
What is the best way to verify that asm instance is mounted,up and ready ?
. oraenv
ORACLE_SID = [] ? +ASM
sqlplus "/ as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 11 14:30:38 2011
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-01507: database not mounted
Ricardo,
ASM instance has nothing to get it mounted or up. All what it has a spfile which just starts the instance. So it would never be mounted or open and will be always in the started status.
HTH
Aman....

Similar Messages

  • Multiple ASM instances using single cluster install - Is it possible??

    Hi,
    I have 2 node RAC cluster installed on Linux. All the storage is on EMC. I need to setup another environment using HP storage on the same hosts. Is it possible to created second ASM instance using the same cluster install?? I wanted to have clear separation b/w EMC and HP environments and that's wondering if it's feasible to do that.
    Haven't tried it yet to see if it complains.
    Thx
    Anitha

    Anitha,
    The data migration won't happen (at least not aggressively) until you do step 2 in your list where you remove the EMC disks. That removal operation will take a long time as Oracle will have to move the data before it can complete the operation. If you want to be sure, I'd recommend creating a new disk group with one of your new disks, put a small tablespace in it, create some data in it, then add a disk to that new group and remove the original disk. Then you'll have some confidence in the procedure and verify that it works without risking your production data. After you test, you can drop the disk group and use the disks for their intended purposes.
    To answer your question, yes, that's the process exactly as I suggested it above. Should work fine--but will probably take a while to do the remove, so be prepared to leave that running for quite a while (i.e. don't expect to close the terminal and go home right after running the remove).
    Dan

  • How to create an asm instance manaually? oracle 11gr2.

    env: oracle 11gr2 os: hpux or aix single machine , not rac.
    question:how to create an asm instance manaually?? diskgroup,listener,db ,they can be resigistered to crs??
    can anyone give me document about it?

    Hi,
    This is a simple answer:
    Automatic Storage Management (ASM)
    ASM was a new storage option introduced with Oracle Database 10gR1 that provides the services of a filesystem, logical volume manager, and software RAID in a platform-independent manner. ASM can stripe and mirror your disks, allow disks to be added or removed while the database is under load, and automatically balance I/O to remove "hot spots." It also supports direct and asynchronous I/O and implements the Oracle Data Manager API (simplified I/O system call interface) introduced in Oracle9i.
    ASM is not a general-purpose filesystem and can be used only for Oracle data files, redo logs, and control files. Files in ASM can be created and named automatically by the database (by use of the Oracle Managed Files feature) or manually by the DBA. Because the files stored in ASM are not accessible to the operating system, the only way to perform backup and recovery operations on databases that use ASM files is through Recovery Manager (RMAN).
    ASM is implemented as a separate Oracle instance that must be up if other databases are to be able to access it. Memory requirements for ASM are light: only 64 MB for most systems.
    Installing ASM
    On Linux platforms, ASM can use raw devices or devices managed via the ASMLib interface. Oracle recommends ASMLib over raw devices for ease-of-use and performance reasons. ASMLib 2.0 is available for free download from OTN. This section walks through the process of configuring a simple ASM instance by using ASMLib 2.0 and building a database that uses ASM for disk storage.
    Determine Which Version of ASMLib You Need
    ASMLib 2.0 is delivered as a set of three Linux packages:
    * oracleasmlib-2.0 - the ASM libraries
    * oracleasm-support-2.0 - utilities needed to administer ASMLib
    * oracleasm - a kernel module for the ASM library
    Each Linux distribution has its own set of ASMLib 2.0 packages, and within each distribution, each kernel version has a corresponding oracleasm package. The following paragraphs describe how to determine which set of packages you need.
    First, determine which kernel you are using by logging in as root and running the following command:
    uname -rm
    Ex:
    # uname -rm
    2.6.9-22.ELsmp i686
    The example shows that this is a 2.6.9-22 kernel for an SMP (multiprocessor) box using Intel i686 CPUs.
    Use this information to find the correct ASMLib packages on OTN:
    1. Point your Web browser to http://www.oracle.com/technology/tech/linux/asmlib/index.html
    2. Select the link for your version of Linux.
    3. Download the oracleasmlib and oracleasm-support packages for your version of Linux
    4. Download the oracleasm package corresponding to your kernel. In the example above, the oracleasm-2.6.9-22.ELsmp-2.0.0-1.i686.rpm package was used.
    Next, install the packages by executing the following command as root:
    rpm -Uvh oracleasm-kernel_version-asmlib_version.cpu_type.rpm \
    oracleasmlib-asmlib_version.cpu_type.rpm \
    oracleasm-support-asmlib_version.cpu_type.rpm
    Ex:
    # rpm -Uvh \
    > oracleasm-2.6.9-22.ELsmp-2.0.0-1.i686.rpm \
    > oracleasmlib-2.0.1-1.i386.rpm \
    > oracleasm-support-2.0.1-1.i386.rpm
    Preparing... ########################################### [100%]
    1:oracleasm-support ########################################### [ 33%]
    2:oracleasm-2.6.9-22.ELsm########################################### [ 67%]
    3:oracleasmlib ########################################### [100%]
    Configuring ASMLib
    Before using ASMLib, you must run a configuration script to prepare the driver. Run the following command as root, and answer the prompts as shown in the example below.
    # /etc/init.d/oracleasm configure
    Configuring the Oracle ASM library driver.
    This will configure the on-boot properties of the Oracle ASM library
    driver. The following questions will determine whether the driver is
    loaded on boot and what permissions it will have. The current values
    will be shown in brackets ('[]'). Hitting <ENTER> without typing an
    answer will keep that current value. Ctrl-C will abort.
    Default user to own the driver interface []: oracle
    Default group to own the driver interface []: dba
    Start Oracle ASM library driver on boot (y/n) [n]: y
    Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
    Writing Oracle ASM library driver configuration: [  OK  ]
    Creating /dev/oracleasm mount point: [  OK  ]
    Loading module "oracleasm": [  OK  ]
    Mounting ASMlib driver filesystem: [  OK  ]
    Scanning system for ASM disks: [  OK  ]
    Next you tell the ASM driver which disks you want it to use. Oracle recommends that each disk contain a single partition for the entire disk. See Partitioning the Disks at the beginning of this section for an example of creating disk partitions.
    You mark disks for use by ASMLib by running the following command as root:
    /etc/init.d/oracleasm createdisk DISK_NAME device_name
    Tip: Enter the DISK_NAME in UPPERCASE letters.
    Ex:
    # /etc/init.d/oracleasm createdisk VOL1 /dev/sdb1
    Marking disk "/dev/sdb1" as an ASM disk: [  OK  ]
    # /etc/init.d/oracleasm createdisk VOL1 /dev/sdc1
    Marking disk "/dev/sdc1" as an ASM disk: [  OK  ]
    # /etc/init.d/oracleasm createdisk VOL1 /dev/sdd1
    Marking disk "/dev/sdd1" as an ASM disk: [  OK  ]
    Verify that ASMLib has marked the disks:
    # /etc/init.d/oracleasm listdisks
    VOL1
    VOL2
    VOL3
    Create the ASM Instance
    ASM runs as a separate Oracle instance which can be created and configured using the Oracle Universal Installer. Now that ASMLib is installed and the disks are marked for use, you can create an ASM instance.
    Log in as oracle and start runInstaller:
    $ ./runInstaller
    1. Select Installation Method
    * Select Advanced Installation
    * Click on Next
    2. Specify Inventory Directory and Credentials
    * Inventory Directory: /u01/app/oracle/oraInventory
    * Operating System group name: oinstall
    * Click on Next
    3. Select Installation Type
    * Select Enterprise Edition
    * Click on Next
    4. Specify Home Details
    * Name: OraDB10gASM
    * Path: /u01/app/oracle/product/10.2.0/asm
    Note:Oracle recommends using a different ORACLE_HOME for ASM than the ORACLE_HOME used for the database for ease of administration.
    * Click on Next
    5. Product-specific Prerequisite Checks
    * If you've been following the steps in this guide, all the checks should pass without difficulty. If one or more checks fail, correct the problem before proceeding.
    * Click on Next
    6. Select Configuration Option
    * Select Configure Automatic Storage Management (ASM)
    * Enter the ASM SYS password and confirm
    * Click on Next
    7. Configure Automatic Storage Management
    * Disk Group Name: DATA
    * Redundancy
    - High mirrors data twice.
    - Normal mirrors data once. This is the default.
    - External does not mirror data within ASM. This is typically used if an external RAID array is providing redundancy.
    * Add Disks
    The disks you configured for use with ASMLib are listed as Candidate Disks. Select each disk you wish to include in the disk group.
    * Click on Next
    8. Summary
    * A summary of the products being installed is presented.
    * Click on Install.
    9. Execute Configuration Scripts
    * At the end of the installation, a pop up window will appear indicating scripts that need to be run as root. Login as root and run the indicated scripts.
    * Click on OK when finished.
    10. Configuration Assistants
    * The Oracle Net, Oracle Database, and iSQL*Plus configuration assistants will run automatically
    11. End of Installation
    * Make note of the URLs presented in the summary, and click on Exit when ready.
    12. Congratulations! Your new Oracle ASM Instance is up and ready for use.
    Kind regards
    Mohamed

  • ASM instance startup problem..

    Hi,
    SQL> startup
    ASM instance started
    Total System Global Area 79691776 bytes
    Fixed Size 1289004 bytes
    Variable Size 53236948 bytes
    ASM Cache 25165824 bytes
    ORA-15032: not all alterations performed
    ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"
    DB Version=10.2.0.2.0
    Os = windows xp
    Thanks,

    ORA-15063:     ASM discovered an insufficient number of disks for diskgroup "string"
    Cause:     ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.
    Action:     Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.

  • One node is up but when we start the crs on node 2 then ASM instance killed.

    Hi Friends
    i am facing below strange problem
    one node is up but when we start the crs on node 2 then ASM instance killed. i found that one ip 169.254.98.19 is binding with private interconnect IP rathter than assigned IP.
    Please help me

    Hi Pradeep ,
    Oracle S/W verstion is 11.2.0.3. Actually , we start the CRS and DB on node 1 but when we try to start on node 2 , getting below error.
    [gpnpd(18284748)]CRS-2328:GPNPD started on node ggnetp04.
    2013-09-03 19:48:29.162
    [cssd(17694820)]CRS-1713:CSSD daemon is started in clustered mode
    2013-09-03 19:48:30.557
    [ohasd(13697160)]CRS-2767:Resource state recovery not attempted for 'ora.diskmon' as its target state is OFFLINE
    2013-09-03 19:48:41.013
    [cssd(17694820)]CRS-1707:Lease acquisition for node ggnetp04 number 2 completed
    2013-09-03 19:48:42.490
    [cssd(17694820)]CRS-1605:CSSD voting file is online: /dev/rhdiskpower0; details in /opt/app/11.2.0.3/grid/log/ggnetp04/cssd/ocssd.log.
    2013-09-03 19:48:45.483
    [cssd(17694820)]CRS-1601:CSSD Reconfiguration complete. Active nodes are ggnetp03 ggnetp04 .
    2013-09-03 19:48:47.257
    [ctssd(18022612)]CRS-2403:The Cluster Time Synchronization Service on host ggnetp04 is in observer mode.
    2013-09-03 19:48:47.632
    [ctssd(18022612)]CRS-2407:The new Cluster Time Synchronization Service reference node is host ggnetp03.
    2013-09-03 19:48:47.633
    [ctssd(18022612)]CRS-2401:The Cluster Time Synchronization Service started on host ggnetp04.
    [client(16056466)]CRS-10001:03-Sep-13 19:48 ACFS-9391: Checking for existing ADVM/ACFS installation.
    [client(16056468)]CRS-10001:03-Sep-13 19:48 ACFS-9392: Validating ADVM/ACFS installation files for operating system.
    [client(16056470)]CRS-10001:03-Sep-13 19:48 ACFS-9393: Verifying ASM Administrator setup.
    [client(16056472)]CRS-10001:03-Sep-13 19:48 ACFS-9308: Loading installed ADVM/ACFS drivers.
    [client(16056478)]CRS-10001:03-Sep-13 19:48 ACFS-9154: Loading 'oracleadvm.ext' driver.
    [client(16056486)]CRS-10001:03-Sep-13 19:48 ACFS-9154: Loading 'oracleacfs.ext' driver.
    [client(16056494)]CRS-10001:03-Sep-13 19:48 ACFS-9327: Verifying ADVM/ACFS devices.
    [client(16056498)]CRS-10001:03-Sep-13 19:48 ACFS-9156: Detecting control device '/dev/asm/.asm_ctl_spec'.
    [client(16056504)]CRS-10001:03-Sep-13 19:48 ACFS-9156: Detecting control device '/dev/ofsctl'.
    [client(16056508)]CRS-10001:03-Sep-13 19:48 ACFS-9322: completed
    2013-09-03 19:48:59.667
    [ctssd(18022612)]CRS-2409:The clock on host ggnetp04 is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.
    2013-09-03 19:50:53.936
    [cssd(17694820)]CRS-1662:Member kill requested by node ggnetp03 for member number 1, group DB+ASM
    2013-09-03 19:50:57.493
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:50:57.494
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2013-09-03 19:50:58.828
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:50:58.943
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:50:59.235
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:53:00.252
    [cssd(17694820)]CRS-1662:Member kill requested by node ggnetp03 for member number 1, group DB+ASM
    2013-09-03 19:53:03.101
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:53:03.102
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2013-09-03 19:53:05.430
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:53:05.539
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:53:05.815
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:55:07.436
    [cssd(17694820)]CRS-1662:Member kill requested by node ggnetp03 for member number 1, group DB+ASM
    2013-09-03 19:55:09.673
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:55:09.674
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log"
    2013-09-03 19:55:12.007
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:55:12.115
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:55:12.389
    [/opt/app/11.2.0.3/grid/bin/oraagent.bin(16777322)]CRS-5019:All OCR locations are on ASM disk groups [DATA], and none of these disk groups are mounted. Details are at "(:CLSN00100:)" in "/opt/app/11.2.0.3/grid/log/ggnetp04/agent/ohasd/oraagent_grid/oraagent_grid.log".
    2013-09-03 19:55:12.405
    [ohasd(13697160)]CRS-2807:Resource 'ora.asm' failed to start automatically.
    2013-09-03 19:55:12.405
    [ohasd(13697160)]CRS-2807:Resource 'ora.crsd' failed to start automatically.
    2013-09-03 20:23:32.040
    [ctssd(18022612)]CRS-2409:The clock on host ggnetp04 is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.

  • Can there be multiple ASM instances on single node?

    Hi,
    Can there be multiple ASM instances on single node?
    This one says No : http://www.freelists.org/archives/oracle-l/02-2008/msg00317.html
    And This one says Yes : http://www.databasejournal.com/features/oracle/article.php/3571371
    Thanks in advance.
    Thanks,
    Harsha
    Edited by: user498756 on Sep 11, 2008 2:23 AM

    ...that document doesnt say you cannot have multiple ASM instances on a node. It says "...ASM, +you only need one ASM+ instance for that computer, to manage the two database instances that use ASM."
    The fact that you only need one - and I cannot think of a good reason to have more than one - does not preclude the fact that you do seem to be able to have multiple ASM instances on a single node, each looking after its own set of disks and diskgroups.
    Again - I cannot think of a good reason to do so though!
    -Bob

  • Upgrade ASM instance database 10g to 11g

    Hi,
    In my environment, I have ASM instance database 10.2.0.3 running on solaris 10 (64-bit), I need to upgrade to ASM instance 11.1.0.6 database. please guide me an overview of steps...
    thanks in advance

    Thanks for the response,
    Sorry, In my environment I know database (10.2.0.3) is mounted in ASM diskgroups, now i have a concern
    1) If database is mounted in ASM diskgroups, could it be a database instance or it has to be only ASM instance connected to the database?
    2) As in my upgrade from ASM instance (10.2.0.3) to ASM instance (11.1.0.6), do we need to upgrade asm instance as well as database? i mean to invoke DBUA twice for upgrading ASM instance then for upgrading database as well?
    Sorry for some silly questions...please make me clear...
    Regards

  • How to configure Oracle Enterprise manager 11.2.0.1 for ASM instance

    Hi All,
    Please let us know How to configure Oracle Enterprise manager 11.2.0.1 for ASM instance.
    Reagrds,
    Vikas

    Assuming an agent is running on the servers you want to monitor,
    navigate to the Agent home page (Via setup --> Agent)
    When in the agent home page select 'Add Database'and press [Go]
    Assuming yopur database now gets recognized, select the Configure icon and enter the password for dbsnmp.
    When done, press [Ok] to return to the agent home page.
    Regards
    Rob
    http://oemgc.wordpress.com

  • ASM instance on one node can not startup

    use dbca create database failure
    [oracle@rac1 ~]$ dbca -silent -responseFile /home/oracle/dbca.rsp
    Look at the log file "/opt/ora/product/10.2.0/db_1/cfgtoollogs/dbca/mydb.log" for further details.
    [oracle@rac1 ~]$ cat "/opt/ora/product/10.2.0/db_1/cfgtoollogs/dbca/mydb.log"
    PRKS-1009 : Failed to start ASM instance "+ASM2" on node "rac2", [CRS-0215: Could not start resource 'ora.rac2.ASM2.asm'.]
    ORA-03135: connection lost contact
    [oracle@rac2 bin]$ ./crs_stat -t
    Name           Type           Target    State     Host
    ora....SM1.asm application    ONLINE    ONLINE    rac1
    ora....C1.lsnr application    ONLINE    ONLINE    rac1
    ora.rac1.gsd   application    ONLINE    ONLINE    rac1
    ora.rac1.ons   application    ONLINE    ONLINE    rac1
    ora.rac1.vip   application    ONLINE    ONLINE    rac1
    ora....SM2.asm application    ONLINE    OFFLINE
    ora....C2.lsnr application    ONLINE    ONLINE    rac2
    ora.rac2.gsd   application    ONLINE    ONLINE    rac2
    ora.rac2.ons   application    ONLINE    ONLINE    rac2
    ora.rac2.vip   application    ONLINE    ONLINE    rac2so i try to start asm instance on rac2
    [oracle@rac2 bin]$ ./srvctl start asm -n rac2
    PRKS-1009 : Failed to start ASM instance "+ASM2" on node "rac2", [PRKS-1009 : Failed to start ASM instance "+ASM2" on node "rac2", [rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 25 17:58:21 2011
    rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:Enter user-name: Connected to an idle instance.
    rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:SQL> ORA-03113: end-of-file on communication channel
    rac2:ora.rac2.ASM2.asm:SQL> Disconnected
    rac2:ora.rac2.ASM2.asm:
    CRS-0215: Could not start resource 'ora.rac2.ASM2.asm'.]]
      [PRKS-1009 : Failed to start ASM instance "+ASM2" on node "rac2", [rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 25 17:58:21 2011
    rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:Enter user-name: Connected to an idle instance.
    rac2:ora.rac2.ASM2.asm:
    rac2:ora.rac2.ASM2.asm:SQL> ORA-03113: end-of-file on communication channel
    rac2:ora.rac2.ASM2.asm:SQL> Disconnected
    rac2:ora.rac2.ASM2.asm:check the alert log find
    Mon Jul 25 17:58:23 2011
    Maximum Tranmission Unit (mtu) of the ether adapter is different
    on the node running instance 1, and this node.
    Ether adapters connecting the cluster nodes must be configured
    with identical mtu on all the nodes, for Oracle.
    Please ensure the mtu attribute of the ether adapter on all
    nodes are identical, before running Oracle.
    Mon Jul 25 17:58:23 2011
    Errors in file /opt/ora/admin/+ASM/bdump/+asm2_lmon_29711.trc:
    ORA-27550: Target ID protocol check failed. tid vers=%d, type=%d, remote instance number=%d, local instance number=%d
    LMON: terminating instance due to error 27550
    Mon Jul 25 17:58:25 2011
    Shutting down instance (abort)
    License high water mark = 0
    Mon Jul 25 17:58:28 2011
    Instance terminated by LMON, pid = 29711
    Mon Jul 25 17:58:30 2011
    Instance terminated by USER, pid = 29831and i checked my eth
    [root@rac1 oracle]# ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:0C:29:3C:42:0C
              inet addr:192.168.40.102  Bcast:192.168.40.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:9762 errors:0 dropped:0 overruns:0 frame:0
              TX packets:6028 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:1193646 (1.1 MiB)  TX bytes:1037252 (1012.9 KiB)
              Interrupt:67 Base address:0x2400
    eth0:1    Link encap:Ethernet  HWaddr 00:0C:29:3C:42:0C
              inet addr:192.168.40.201  Bcast:192.168.40.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              Interrupt:67 Base address:0x2400
    eth1      Link encap:Ethernet  HWaddr 00:0C:29:3C:42:16
              inet addr:10.10.17.221  Bcast:10.10.17.225  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:30185 errors:0 dropped:0 overruns:0 frame:0
              TX packets:37936 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:19988844 (19.0 MiB)  TX bytes:35126056 (33.4 MiB)
              Interrupt:51 Base address:0x2480
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:52537 errors:0 dropped:0 overruns:0 frame:0
              TX packets:52537 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:4380651 (4.1 MiB)  TX bytes:4380651 (4.1 MiB)
    [root@rac2 ~]# ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:0C:29:9C:CC:90
              inet addr:192.168.40.103  Bcast:192.168.40.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:3665 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1489 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:563952 (550.7 KiB)  TX bytes:243127 (237.4 KiB)
              Interrupt:67 Base address:0x2400
    eth0:1    Link encap:Ethernet  HWaddr 00:0C:29:9C:CC:90
              inet addr:192.168.40.202  Bcast:192.168.40.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              Interrupt:67 Base address:0x2400
    eth1      Link encap:Ethernet  HWaddr 00:0C:29:9C:CC:9A
              inet addr:10.10.17.222  Bcast:10.10.17.225  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:38281 errors:0 dropped:0 overruns:0 frame:0
              TX packets:29683 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:35182270 (33.5 MiB)  TX bytes:19905266 (18.9 MiB)
              Interrupt:51 Base address:0x2480
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:44387 errors:0 dropped:0 overruns:0 frame:0
              TX packets:44387 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:2299383 (2.1 MiB)  TX bytes:2299383 (2.1 MiB)any idea ?
    i try to run dbca on rac2 ,it seems OK
    ============
    ASM instance still have problem,no ASM instance create in rac1
    [oracle@rac2 bin]$ ./crs_stat -t
    Name           Type           Target    State     Host
    ora.mydb.db    application    ONLINE    ONLINE    rac1
    ora....b1.inst application    ONLINE    OFFLINE
    ora....b2.inst application    ONLINE    ONLINE    rac2
    ora....SM1.asm application    ONLINE    OFFLINE
    ora....C1.lsnr application    ONLINE    ONLINE    rac1
    ora....C2.lsnr application    ONLINE    OFFLINE              =>  ora.rac1.LISTENER_RAC2.lsnr   (i do not know where this resource come from ??)
    ora.rac1.gsd   application    ONLINE    ONLINE    rac1
    ora.rac1.ons   application    ONLINE    ONLINE    rac1
    ora.rac1.vip   application    ONLINE    ONLINE    rac1
    ora....SM2.asm application    ONLINE    ONLINE    rac2
    ora....C2.lsnr application    ONLINE    ONLINE    rac2
    ora.rac2.gsd   application    ONLINE    ONLINE    rac2
    ora.rac2.ons   application    ONLINE    ONLINE    rac2
    ora.rac2.vip   application    ONLINE    ONLINE    rac2and here is my dbca.rsp file content
    [GENERAL]
    RESPONSEFILE_VERSION = "10.0.0"
    OPERATION_TYPE = "createDatabase"
    [CREATEDATABASE]
    GDBNAME = "mydb.us.oracle.com"
    SID = "mydb"
    NODELIST=rac1,rac2
    TEMPLATENAME = "/home/oracle/mydb.dbc"
    SYSPASSWORD = "Myss123456"
    SYSTEMPASSWORD = "Myss123456"
    EMCONFIGURATION = "NONE"
    DBSNMPPASSWORD = "Myss123456"
    STORAGETYPE=ASM
    DISKLIST=/dev/oracleasm/disks/VOL1,/dev/oracleasm/disks/VOL2
    DISKGROUPNAME=ORADG
    REDUNDANCY=EXTRENAL
    DISKSTRING="/dev/oracleasm/disks/*"
    ASM_SYS_PASSWORD="Myss123456"
    LISTENERS = "listener1 listener2"Edited by: 859340 on 2011-7-24 下午7:23
    Edited by: 859340 on 2011-7-24 下午7:32
    Edited by: 859340 on 2011-7-24 下午7:35
    Edited by: 859340 on 2011-7-24 下午7:51

    Hi,
    Use this tech note on MOS.
    *Instance Crash on startup with ORA-27550: Target ID protocol check failed [ID 730516.1]*
    Regards,
    Levi Pereira

  • ASM instances on 2 node Oracle RAC 10g r2  on Red Hat 4 u1

    Hi all
    I'm experiencing a problem in configuring diskgroups under +ASM instances on a two node Oracle RAC.
    I followed the official guide and also official documents from metalink site, but i'm stuck with the visibility of asm disks.
    I created fake disks on nfs with Netapp certified storage binding them to block device with the usual trick "losetup /dev/loopX /nfs/disk1 " ,
    run "oracleasm createdisk DISKX /dev/loopX" on one node and
    "oracleasm scandisks" on the other one.
    With "oracleasm listdisks" i can see the disks at OS level in both nodes , but , when i try to create and mount diskgroup in the ASM instances , on the instance on which i create the diskgroup all is well, but the other one doesn't see the disks at all, and diskgroup mount fails with :
    ERROR: no PST quorum in group 1: required 2, found 0
    Tue Sep 20 16:22:32 2005
    NOTE: cache dismounting group 1/0x6F88595E (DG1)
    NOTE: dbwr not being msg'd to dismount
    ERROR: diskgroup DG1 was not mounted
    any help would be appreciated
    thanks a lot.
    Antonello

    I'm having this same problem. Did you ever find a solution?

  • Asm instances on single system

    Hi ,
    How many ASM instance can reside on one single machine.....

    Hi,
    Only one ASM instance can run on a server.
    Mahir

  • Multiple ASM instances on a single node

    Can i have multiple ASM instances on a single node? This is to have each instance supporting different environment dev,stage etc
    Thanks
    Sannidhi

    I had been discussing the same issue with someone from Oracle. I asked for multiple ASMs on a server so that we could have seperate ASMs running for, say, 10g and 11g.
    He explained that we should think of ASM as being the same as Veritas FileSystem. We don't run multiple instances of Veritas on our servers. On single Veritas "instance" (set of drivers) provides all the Veritas Fx mountpoints on the server. Similarly, there should be only 1 ASM instance on a server.
    (substitute UFS or ZFS or CFS for Veritas in the above example and you still have only 1 filesystem manager on a server providing one type of filesystem, although you could have, say , UFS and Veritas co-exist ; just as you could have Veritas, ASM and Raw co-exist on a server).
    Hemant K Chitale
    Edited by: Hemant K Chitale on Sep 29, 2009 11:50 AM

  • Multiple ASM Instances on single node

    Hi All,
    After going through some threads it seems to me that multiple ASM instances on a node is not supported and recommended by ORACLE but i coudn't find any ORACLE document or support matrix mentioning this. Can any one give me a pointer to this. Please correct me if i am wrong and Multiple ASM instances are fully supported by ORACLE.
    Thanks,

    Multiple ASM instances on a single node are supported but not recommended due to several issues you could encounter during that kind of configuration.
    Possible interraction between those instances for identification of each disk area usage,each disk area permissions , database instance to asm instance mapping and so on, could result in unwanted behaviour, as ASM is in some way just oracle's representation of LVM.
    Intention is that any kind of distinction/separation of oracle related data under the ASM should be done through the disk groups.
    So it seems it would be better to apply this kind of logic rather than doing suspiciously magical and rare configurations that could bring you similiary strange and unexpected problems.

  • ASM instance crash due  to error ORA-27506: IPC error connecting to a port

    Hi All,
    Today the ASM instance goes down.
    When i checked the alert log I found the below error.
    ORA-27506: IPC error connecting to a port
    ORA-27300: OS system dependent operation:sendmsg failed with status: 22
    ORA-27301: OS failure message: Invalid argument
    ORA-27302: failure occurred at: sskgxpsnd1
    Please find the environment details.
    OS : RHEL-5
    DB: 11.1.0.7 2-node RAC
    I want to know the root cause of this issue.
    Please suggest.
    Thanks and Regards,

    Hi,
    Could you please upload cluster alert log and cssd.log?
    regards,
    Kishore

  • Create a new user for oracle 10G ASM instance with sysdba system privilege

    Hi,
    In our Golden Gate Project, we require the SYS user credential to connect to the Oracle 10g  ASM instance to read the database transaction logs.But our client is not providing the SYS user credential to  connnect to ASM instance.
    I'm getting the error message "ORA-01109:  database not open",When I tried to create a new user using the  below the steps in oracle 10g ASM instance
    1. Login using "sqlplus / as sysdba"
    2. Create user <username> identified by <password>;
    But in oracle 11g ASM instance, I'm able to create new  user  by connecting the ASM instance with SYSASM role without issues.
    Is there is any workaround to create a new user with sysdba system privilege in oracle 10g ASM instance?.
    Thanks in advance .

    Hi,
    Recreate the password file for the ASM instance as follows:
    Unix:
    orapwd file=<ORACLE_HOME>/dbs/PWD<SID> password=<sys_password>
    Windows:
    orapwd file=<ORACLE_HOME>/database/PWD<SID>.ora password=<sys_password>
    Now sys password is reset, we are ready to use sys for ASM management. I decided to create another user ASMDBA as I tried above.
    SQL> create user ASMDBA identified by test01;
    User created.
    SQL> grant SYSASM, SYSOPER to ASMDBA;
    Grant succeeded.
    SQL> select * from v$pwfile_users;
    USERNAME SYSDBA SYSOPE SYSASM
    SYS TRUE TRUE TRUE
    ASMDBA FALSE TRUE TRUE
    Please see this link : http://orachat.com/how-to-change-asm-sys-password-creating-sysasm-user-11g/
    Thank you

Maybe you are looking for