ORA-15000: command disallowed by current instance type

Cause : The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance.

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

Connect to the correct instance type and re-issue the command.

update : 17-08-2017
ORA-15000

ORA-15000 - command disallowed by current instance type
ORA-15000 - command disallowed by current instance type

  • ora-19704 : file name exceeds maximum length of string
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-06951 : Operating system call error
  • ora-01116 : error in opening database file string
  • ora-25531 : MTTR specified is too small: string
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-16728 : consistency check for property string found string error
  • ora-00367 : checksum error in log file header
  • ora-10638 : Index status is invalid
  • ora-13141 : invalid RANGE window definition
  • ora-25285 : Invalid value string for array_mode
  • ora-22881 : dangling REF
  • ora-22316 : input type is not a collection type
  • ora-36316 : (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.
  • ora-13266 : error inserting data into table string
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-30432 : summary 'string.string' is in INVALID state
  • ora-32121 : Source FILE is null
  • ora-07494 : scgcm: unexpected error.
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-13340 : a point geometry has more than one coordinate
  • ora-12919 : Can not drop the default permanent tablespace
  • ora-06567 : invalid number of values specified
  • ora-02216 : tablespace name expected
  • ora-01782 : UNRECOVERABLE cannot be specified for a cluster or clustered table
  • ora-30177 : invalid flag used in a format specification
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-27143 : OS system call failure
  • 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.