ORA-15014: location 'string' is not in the discovery set

Cause : The operating system path specified was outside the set of disks that are discovered by the instance.

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

Specify a operating system path within the set of disks that are discovered based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the ASM_DISKSTRING parameter.

update : 28-07-2017

ORA-15014 - location 'string' is not in the discovery set
ORA-15014 - location 'string' is not in the discovery set

  • ora-01010 : invalid OCI operation
  • ora-06109 : NETTCP: message receive failure
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-01181 : file string created before last known RESETLOGS, cannot recreate
  • ora-23417 : unknown materialized view type: string
  • ora-27158 : process control failure
  • ora-29315 : tablespace 'string' has been recreated
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-13829 : SQL profile named string already exists
  • ora-36676 : (XSDPART14) Missing dimension list for string.
  • ora-28336 : cannot encrypt SYS owned objects
  • ora-24367 : user handle has not been set in service handle
  • ora-08455 : syntax error in CURRENCY SIGN environment clause
  • ora-28521 : no heterogeneous capability information available
  • ora-32131 : bind data type cannot be changed
  • ora-22921 : length of input buffer is smaller than amount requested
  • ora-27061 : waiting for async I/Os failed
  • ora-09801 : Unable to get user ID from connection
  • ora-39765 : stream must be reset before used in a column array conversion
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-13140 : invalid target type
  • ora-14616 : table is not subpartitioned by List method
  • ora-14251 : Specified subpartition does not exist
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-15093 : buffer only contains string bytes, I/O requested is string bytes
  • ora-24149 : invalid rule name
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-38601 : FI Not enough memory for frequent itemset counting: string
  • ora-16518 : unable to allocate virtual instance id
  • 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.