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 : 20-08-2017
ORA-15031

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

  • ora-27489 : unable to process job "string.string" from job class "string"
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-16031 : parameter string destination string exceeds string character limit
  • ora-27375 : valid agent name must be specified for secure queues
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-26744 : STREAMS capture process "string" does not support "string"."string" because of the following reason: string
  • ora-36681 : (XSDPART19) Partitions string and string are out of order.
  • ora-38622 : Decision Tree not enough memory, requires at least stringKB
  • ora-12528 : TNS:listener: all appropriate instances are blocking new connections
  • ora-01673 : data file string has not been identified
  • ora-23619 : non-Oracle system error: string
  • ora-29808 : specified primary operator binding does not exist
  • ora-12471 : Specified compartment or group is not authorized for user
  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-24089 : AQ Agent string already exists
  • ora-32121 : Source FILE is null
  • ora-33448 : (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
  • ora-04029 : error ORA-string occurred when querying stringstringstring
  • ora-06262 : NETNTT: nfconn() failed
  • ora-31653 : unable to determine job operation for privilege check
  • ora-04020 : deadlock detected while trying to lock object stringstringstringstringstring
  • ora-12093 : invalid interim table "string"."string"
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-09366 : Windows 3.1 Two-Task driver unable to allocate shared memory
  • ora-02039 : bind by value is not allowed for array type
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-24013 : invalid value string, RETRY_DELAY should be non-negative
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-24182 : attribute number specified does not exist
  • 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.