Error Unable To Remove The Asm Instances
Contents |
ASM GRID - ORACLE 11G REMOVED DISKGROUP NAME - ASM_DISK1 OS LEVEL DISK NAME ASSIGNED - DATA1 OPERATING prcr-1001 : resource ora.asm does not exist SYSTEM - OEL 6.0 WORKINGS SQL> select name from v$asm_diskgroup; NAME ---------------------- srvctl add asm DATA_GRP1 ASM_DISK1 SQL> select name from v$asm_disk; NAME ---------------------- DATA_GRP1_0000 ASM_DISK1_0000 While dropping the diskgroup, i got the
Prca-1032 : Asm Listener Listener Does Not Exist
following error and I was not able to drop it., SQL> alter diskgroup ASM_DISK1 drop disk ASM_DISK1_0000; alter diskgroup ASM_DISK1 drop disk ASM_DISK1_0000 * ERROR at line 1: ORA-15032: not
Connect To Asm Instance
all alterations performed ORA-15250: insufficient diskgroup space for rebalance completion SQL> alter diskgroup ASM_DISK1 drop disk ASM_DISK1_0000 rebalance power 8; alter diskgroup ASM_DISK1 drop disk ASM_DISK1_0000 rebalance power 8 * ERROR at line 1: ORA-15032: not all alterations performed ORA-15250: insufficient diskgroup space for rebalance completion Checked the Total space and Free space of the ASM Diskgroup. Since the disk srvctl add asm 12c was a newly added one, there was enough free space. SQL> set lines 200 pages 1000 SQL> col name format a30 SQL> select name,total_mb,free_mb from v$asm_disk; NAME TOTAL_MB FREE_MB -------------------- ------- ------- DATA_GRP1_0000 21050 20998 ASM_DISK1_0000 5567 5508 I tried to drop it again, SQL> drop diskgroup ASM_DISK1 including contents; drop diskgroup ASM_DISK1 including contents * ERROR at line 1: ORA-15039: diskgroup not dropped ORA-15027: active use of diskgroup "ASM_DISK1" precludes its dismount I dismounted the diskgroup and tried to drop it. SQL> alter diskgroup ASM_DISK1 dismount force; Diskgroup altered. SQL> drop diskgroup ASM_DISK1 including contents; drop diskgroup ASM_DISK1 including contents * ERROR at line 1: ORA-15039: diskgroup not dropped ORA-15001: diskgroup "ASM_DISK1" does not exist or is not mounted The below was the solution which I followed to remove the ASM diskgroup from the ASM Instance. Created a pfile from the spfile in a different location and restarted the database using that pfile. SQL> show parameter spfile NAME TYPE VALUE ---------------- ----
The chapter also describes ASM instance administration as well as upgrading, patching, and authentication for ASM instance access. You
Ora-29701: Unable To Connect To Cluster Synchronization Service
can also use procedures in this chapter to migrate a database asm listener was not found to use ASM. Administering an ASM instance is similar to administering an Oracle Database instance, but the srvctl modify asm process requires fewer procedures. You can use Oracle Enterprise Manager and SQL*Plus to perform ASM instance administration tasks. This chapter contains the following topics: Operating With Different http://www.oracle-scn.com/unable-to-remove-asm-diskgroup-from-the-asm-instance/ Releases of ASM and Database Instances Simultaneously Configuring Initialization Parameters for an ASM Instance Administering ASM Instances Using ASM Rolling Upgrades Patching ASM Instances Authentication for Accessing ASM Instances Migrating a Database to Use ASM See Also: "About ASM Instances" for a description of an ASM instance and Chapter 6, "Administering ASM with Oracle http://docs.oracle.com/cd/B28359_01/server.111/b31107/asminst.htm Enterprise Manager" for information about using Enterprise Manager to administer ASM Operating With Different Releases of ASM and Database Instances Simultaneously Automatic Storage Management (ASM) in Oracle Database 11g supports both older and newer software versions of Oracle database instances, including Oracle Database 10g. Both forward and backward compatibility is maintained between Oracle Database 10g and 11g, enabling combinations of 10.1, 10.2 and 11.1 releases for ASM and database instances to successfully interoperate. For compatibility between Oracle Clusterware and ASM, the Oracle Clusterware release must be greater than or equal to the ASM release. There are additional compatibility considerations when using disk groups with different releases of ASM and database instances. For information about disk group compatibility attributes settings, see "Disk Group Compatibility". When using different software versions, the database instance supports ASM functionality of the earliest release in use. For example: A 10.1 database instance operating with an 11.1 ASM instance supports only ASM 10.1 features. An 11.1 database instance
parameters for use with Oracle ASM. The chapter also describes Oracle ASM upgrading, patching, and authentication for Oracle ASM instance access. You can also use https://docs.oracle.com/cd/E11882_01/server.112/e18951/asminst.htm procedures in this chapter to migrate a database to use Oracle ASM. https://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_8013.htm Administering an Oracle ASM instance is similar to administering an Oracle Database instance, but the process requires fewer procedures. You can use Oracle Enterprise Manager and SQL*Plus to perform Oracle ASM instance administration tasks. Oracle ASM is installed in the Oracle Grid Infrastructure home separate from the Oracle Database unable to home. Only one Oracle ASM instance is supported on a server. When managing an Oracle ASM instance, the administration activity must be performed in the Oracle Grid Infrastructure home. This chapter contains the following topics: Operating with Different Releases of Oracle ASM and Database Instances Simultaneously Configuring Initialization Parameters for Oracle ASM Instances Managing Oracle ASM Instances Using Oracle ASM Rolling Upgrade does not exist Patching Oracle ASM Instances in Oracle RAC Environments Authentication for Accessing Oracle ASM Instances Migrating a Database to Use Oracle ASM For a description of an Oracle ASM instance, see "About Oracle ASM Instances". For information about using Oracle Enterprise Manager to administer Oracle ASM, see Chapter 9, "Administering Oracle ASM with Oracle Enterprise Manager". Operating with Different Releases of Oracle ASM and Database Instances Simultaneously Oracle Automatic Storage Management (Oracle ASM) in Oracle Database 11g Release 2 (11.2) supports 11g Release 2 (11.2) or older software versions of Oracle database instances, including Oracle Database 10g. For compatibility between Oracle Clusterware and Oracle ASM, the Oracle Clusterware release must be greater than or equal to the Oracle ASM release. Notes: An Oracle ASM instance must be at 11g Release 2 (11.2) to support an 11g Release 2 (11.2) Oracle Database. See Oracle Exadata documentation for information about the Oracle Database versions that Oracle ASM 11g Release 2 (11.2) supports when Oracle Exadata storage is present. There are additional compatibility considerations when using disk groups with different releases of Oracle ASM and da
instance, not from a normal database instance. For information on starting an Automatic Storage Management instance, refer to Oracle Database Storage Administrator's Guide. Purpose The DROP DISKGROUP statement lets you drop an Automatic Storage Management disk group along with all the files in the disk group. Automatic Storage Management first ensures that no files in the disk group are open. It then drops the disk group and all its member disks and clears the disk header. See Also: CREATE DISKGROUP and ALTER DISKGROUP for information on creating and modifying disk groups Oracle Database Storage Administrator's Guide for information on Automatic Storage Management and using disks groups to simplify database administration Prerequisites You must have the SYSDBA system privilege and you must have an Automatic Storage Management instance started, from which you issue this statement. The disk group to be dropped must be mounted. Syntax drop_diskgroup::= Description of the illustration drop_diskgroup.gif Semantics diskgroup_name Specify the name of the disk group you want to drop. INCLUDING CONTENTS Specify INCLUDING CONTENTS to confirm that Automatic Storage Management should drop all the files in the disk group. You must specify this clause if the disk group contains any files. EXCLUDING CONTENTS Specify EXCLUDING CONTENTS to ensure that Automatic Storage Management drops the disk group only when the disk group is empty. This is the default. If the disk group is not empty, then an error will be returned. FORCE This clause clears the headers on the disk belonging to a disk group that cannot be mounted by the ASM instance. The disk group cannot be mounted by any instance of the database. The Automatic Storage Management instance first determines whether the disk group is being u