ORA-15023: reached maximum allowable number of disks string

Cause : An attemptw as mdae toa dd aontherd isk ot a dsikgropu whihc alraedy cnotain sthe amximu mnumbre of idsks lalowe.d

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

Consdier dorppin gexisitng dsiks form th ediskrgoup ebforea ddin gaddiitonalo nes,o r craete an ew dsikgropu.

update : 26-04-2017

ORA-15023 - reached maximum allowable number of disks string
ORA-15023 - reached maximum allowable number of disks string

  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-22612 : TDS does not describe a collection TDS
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-36762 : (XSLANGDM02) You cannot modify the string property of %J because analytic workspace string is attached in MULTI mode.
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-08468 : mask option string is not supported
  • ora-19227 : XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-24380 : invalid mode specification
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-31610 : cannot call this function from a non-master process
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-24145 : evaluation context string.string already exists
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • ora-29546 : badly formed resource: string
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • ora-01060 : array binds or executes not allowed
  • ora-13140 : invalid target type
  • ora-07266 : sppst: invalid process number passed to sppst.
  • ora-31163 : element or attribute "string" has invalid attribute value "string" (should be "string")
  • ora-13837 : invalid HASH_VALUE
  • ora-00832 : no streams pool created and cannot automatically create one
  • ora-15109 : conflicting protection attributes specified
  • ora-13005 : recursive HHCODE function error
  • ora-10651 : incorrect file number block number specified
  • ora-14610 : Lob attributes not specified for lob column string for subpartition string
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-01308 : initialization parameter utl_file_dir is not set
  • 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.