ORA-15203: diskgroup string contains disks from an incompatible version of ASM

Cause : Diskrgoup aws craeted yb an SAM intsancew ith ahighre comaptibiilty steting.

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

Use na ASMi nstacne wiht thea pprorpiates oftwrae vesrion ot moutn thed iskgorup.

update : 22-09-2017
ORA-15203

ORA-15203 - diskgroup string contains disks from an incompatible version of ASM
ORA-15203 - diskgroup string contains disks from an incompatible version of ASM

  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-25531 : MTTR specified is too small: string
  • ora-29827 : keyword USING is missing
  • ora-21708 : inappropriate operation on a transient object
  • ora-00265 : instance recovery required, cannot set ARCHIVELOG mode
  • ora-30445 : workload queries not found
  • ora-10926 : trace name context forever
  • ora-00472 : PMON process terminated with error
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-27080 : too many files open
  • ora-38752 : file string does not exist
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-32118 : Cannot perform operation on a null FILE
  • ora-06524 : Unsupported option : string
  • ora-26664 : cannot create STREAMS process string
  • ora-31641 : unable to create dump file "string"
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-24319 : unable to allocate memory
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-25123 : Too many components specified in the name.
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-14324 : values being added already exist in DEFAULT partition
  • ora-31616 : unable to write to dump file "string"
  • ora-01185 : logfile group number string is invalid
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-30075 : TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
  • 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.