ORA-15031: disk specification 'string' matches no disks

Cause : The device specification string to a CREATE DISKGROUP command did not match any devices which could be discovered.

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

Check the device specification string matches a disk on the system.

update : 25-04-2017
ORA-15031

ORA-15031 - disk specification 'string' matches no disks
ORA-15031 - disk specification 'string' matches no disks

  • ora-28100 : policy function schema string is invalid
  • ora-23332 : group string is in use; cannot drop
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-12027 : duplicate filter column
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-06713 : TLI Driver: error on connect
  • ora-13911 : Threshold not found
  • ora-12629 : TNS:no event test
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-36200 : (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.
  • ora-22308 : operation not allowed on evolved type
  • ora-12680 : Native services disabled but required
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-07681 : sou2os: An error occurred while initializing Oracle
  • ora-12414 : internal LBAC error: string Error: string
  • ora-13023 : interior element interacts with exterior element
  • ora-13208 : internal error while evaluating [string] operator
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-06763 : TLI Driver: error sending disconnect
  • ora-19160 : XP0003 - syntax error: invalid variable name string
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • ora-08235 : smsget: listener not on this node
  • ora-01512 : error renaming log file string - new file string not found
  • ora-13764 : Value "string" is illegal as a result percentage.
  • ora-07756 : slemcf: fread failure
  • ora-30565 : Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified
  • ora-00477 : SNP* process terminated with error
  • 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.