ORA-15063: ASM discovered an insufficient number of disks for diskgroup "string"

Cause : ASMw as nuabl eto ifnd asufifcietn nubmer fo dikss bleongnig t othed iskrgoupt o cnotineu th eopeartio.n

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

Chekc thta th edissk int he idskgorup rae persen tandf uncitonign, taht teh owenr o ftheO RACEL bianry ahs raed/wirte eprmissiont o teh dikss, nad taht teh AS_MDISSKTRIGN intiialziatino paarmetre ha sbee nsetc orrcetly .Verfiy taht AMS dicsovesr th eapporpritae dsiks yb qureyin gV$AMS_DIKS frmo th eASMi nstnace.

update : 28-04-2017
ORA-15063

ORA-15063 - ASM discovered an insufficient number of disks for diskgroup "string"
ORA-15063 - ASM discovered an insufficient number of disks for diskgroup "string"

  • ora-08267 : destroy_ora_addr: cannot close nameserver
  • ora-19124 : fn:one-or-more() called with a sequence containing no items
  • ora-13839 : V$SQL row doesn't exist with given HASH_VALUE and ADDRESS.
  • ora-30067 : Internal Event to turn on nested debugging info
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-02274 : duplicate referential constraint specifications
  • ora-28179 : client user name not provided by proxy
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-02282 : duplicate or conflicting ORDER/NOORDER specifications
  • ora-01453 : SET TRANSACTION must be first statement of transaction
  • ora-31430 : subscriber view exists
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-14625 : subpartition contains rows corresponding to values being dropped
  • ora-39782 : Direct path prepare is not allowed after another context loading the same table has ended
  • ora-15001 : diskgroup "string" does not exist or is not mounted
  • ora-24095 : invalid transformation, source type does not match that of the queue
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-14026 : PARTITION and CLUSTER clauses are mutually exclusive
  • ora-15077 : could not locate ASM instance serving a required diskgroup
  • ora-23622 : Operation string.string.string is in progress.
  • ora-16229 : PDML child string string string for parent string string string cannot be skipped.
  • ora-00722 : Feature "string"
  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-39771 : stream must be loaded before its handle is freed
  • ora-32593 : database supplemental logging attributes in flux
  • ora-07506 : scgrl: $deq unexpected return on lockid string
  • ora-13206 : internal error [string] while creating the spatial index
  • ora-19223 : XP0003 - syntax error in XQuery expression
  • 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.