ORA-15061: ASM operation not supported [string]

Cause : A nAMS poeartoinw a sattepmtde hta ti sivnaildo rn o tspuprotde yb hti svresoino ft h eAMS nisatnec.

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

Tihsi sa ni netranle rorrc oed hta ti suesdf o rmianatiinn gcmoptaiibltiyb ewtene osfwtaer evrisosn nads huol dnvee rb evsiilbet ot h euesr ;cnotcatO rcal espuprotS evriecs.

update : 26-09-2017
ORA-15061

ORA-15061 - ASM operation not supported [string]
ORA-15061 - ASM operation not supported [string]

  • ora-14304 : List partitioning method expects a single partitioning column
  • ora-02271 : table does not have such constraint
  • ora-38457 : The attribute "string" is not a valid XMLType attribute.
  • ora-27166 : tried to join current thread
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-24330 : internal OCI error
  • ora-31499 : null value specified for required parameter string
  • ora-08100 : index is not valid - see trace file for diagnostics
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-01518 : CREATE DATABASE must specify more than one log file
  • ora-36274 : (XSCGMDLAGG05) The operator used in this equation needs a weight variable.
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-26679 : operation not allowed on LOB or LONG columns in LCR
  • ora-38312 : original name is used by an existing object
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-22328 : object "string"."string" has errors. string
  • ora-24338 : statement handle not executed
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-13481 : the destination type is not supported
  • ora-01249 : archiving not allowed in a clone database
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-32341 : The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string"
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-32590 : log group specification not allowed here
  • ora-28051 : the account is locked
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-01792 : maximum number of columns in a table or view is 1000
  • 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.