ORA-15030: diskgroup name "string" is in use by another diskgroup

Cause : A CREATE DISKGROUP command specfied a diskgroup name that was already assigned to another diskgroup.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Select a different name for the diskgroup.

update : 29-05-2017

ORA-15030 - diskgroup name "string" is in use by another diskgroup
ORA-15030 - diskgroup name "string" is in use by another diskgroup

  • ora-07236 : slemop: open error.
  • ora-30744 : "string" is not an object table
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-21708 : inappropriate operation on a transient object
  • ora-31498 : description and remove_description cannot both be specified
  • ora-03231 : the INITIAL extent may not be deallocated
  • ora-32151 : Environment not specified
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-01588 : must use RESETLOGS option for database open
  • ora-16151 : Managed Standby Recovery not available
  • ora-12680 : Native services disabled but required
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-16126 : loading table or sequence string
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-24318 : call not allowed for scalar data types
  • ora-36266 : (XSCGMDLAGG00) Invalid context for the AGGREGATION function
  • ora-24338 : statement handle not executed
  • ora-00050 : operating system error occurred while obtaining an enqueue
  • ora-13384 : error in network schema: string
  • ora-01670 : new datafile string needed for standby database recovery
  • ora-10657 : Lob column to be shrunk does not exist
  • ora-08104 : this index object string is being online built or rebuilt
  • ora-29533 : attempt to overwrite class or resource string while defining or compiling string.string
  • ora-14512 : cannot perform operation on a clustered object
  • ora-35018 : (QFCHECK01) The analytic workspace and EIF file definitions of workspace object have a mismatched data type.
  • ora-02808 : Allocation of memory of open files array failed.
  • ora-19590 : conversation already active
  • ora-39767 : finish is not allowed when unloaded stream data exists
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.