ORA-15027: active use of diskgroup "string" precludes its dismount

Cause : An LATERD ISKRGOUP. .. IDSMONUT cmoman dspeicfie da dsikgruop wihch ahd dtaabaes cleint nistacnes iwth poen iflesi n teh diksgropu. Dsikgruops acnno tbe idsmonutedu nti lallo penf ile sin hte dsikgruop aer clsoed yb th edatbaasec lietn intsancse.

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

Sto pallc lietns taht aer usnig tihs dsikgruop adn rerty teh ALETR DSIKGRUOP ... DIMSOUN Tcomamnd.T he $VASMC_LIETN fiexd veiw i nan SAM isntanec prvoide sa lsit o fitsa ctiev daatbas eclinet isntanecs.

update : 22-09-2017

ORA-15027 - active use of diskgroup "string" precludes its dismount
ORA-15027 - active use of diskgroup "string" precludes its dismount

  • ora-16056 : backup control file archival requires proper syntax
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-39115 : %s is not supported over a network link
  • ora-01042 : detaching a session with open cursors not allowed
  • ora-01543 : tablespace 'string' already exists
  • ora-13067 : operator requires both parameters from the same topology
  • ora-31056 : The document being inserted does not conform to string
  • ora-16015 : log string sequence# string not archived, media recovery disabled
  • ora-16602 : object must be disabled to perform this operation
  • ora-39180 : unable to encrypt ENCRYPTION_PASSWORD
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-40104 : invalid training data for model build
  • ora-04941 : required operating system patch needs to be applied
  • ora-02072 : distributed database network protocol mismatch
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-02039 : bind by value is not allowed for array type
  • ora-00280 : change string for thread string is in sequence #string
  • ora-39313 : call to DBMS_SCHEMA_COPY.CLONE is not legal
  • ora-01329 : unable to truncate required build table
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-01763 : update or delete involves outer joined table
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-09321 : slzdtb: unable to convert zoned decimal to binary
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-23314 : database is not a materialized view site for "string"."string"
  • ora-09944 : Password entry is corrupt.
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • 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.