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 : 24-07-2017
ORA-15061

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

  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-01563 : rollback segment is PUBLIC, need to use the keyword PUBLIC
  • ora-24186 : wrong object type, could not transform message
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-24102 : invalid prefix for generate_job_name
  • ora-16953 : Type of SQL statement not supported.
  • ora-01158 : database string already mounted
  • ora-16411 : ONDEMAND archival requires active managed recovery operation
  • ora-12626 : TNS:bad event type
  • ora-01480 : trailing null missing from STR bind value
  • ora-28509 : unable to establish a connection to non-Oracle system
  • ora-01970 : You must specify a database name for CREATE CONTROLFILE
  • ora-12416 : policy string not found
  • ora-24416 : Invalid session Poolname was specified.
  • ora-32124 : Illegal attribute passed
  • ora-39111 : Dependent object type string skipped, base object type string already exists
  • ora-07634 : smsdbp: $CRETVA failure
  • ora-09886 : osnTXtt: translation error while expanding txipc@.trc.
  • ora-12685 : Native service required remotely but disabled locally
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-12075 : invalid object or field
  • ora-00328 : archived log ends at change string, need later change string
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-34363 : (MXDSS13) number other user writing
  • ora-12510 : TNS:database temporarily lacks resources to handle the request
  • ora-09877 : sstascre: shmget error, unable to get a shared memory segment.
  • ora-38758 : cannot flashback data file string; restored since last recovery
  • ora-32763 : Turn off N-Pass Temp LOB cleanup
  • 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.