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 : 29-06-2017
ORA-15000

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

  • ora-20000 : %s
  • ora-13149 : failed to generate next sequence number for spatial table string
  • ora-06528 : Error executing PL/SQL profiler
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-38792 : encountered unknown flashback record from release string
  • ora-27161 : request for Oracle binary information failed
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-25471 : attribute name not specified for variable: string
  • ora-31654 : unable to convert file or volume size as specified to a number
  • ora-14284 : one or more of table's subpartitions reside in a read-only tablespace
  • ora-07222 : slspool: line printer spooler command exited with an error.
  • ora-26022 : index string.string was made unusable due to:
  • ora-06135 : NETTCP: connection rejected; server is stopping
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-30039 : Cannot drop the undo tablespace
  • ora-24145 : evaluation context string.string already exists
  • ora-31492 : could not set session parameters for LogMiner session
  • ora-21601 : attribute is not an object
  • ora-12641 : Authentication service failed to initialize
  • ora-00152 : current session does not match requested session
  • ora-35078 : (QFHEAD05) An EIF extension file header for string is not in the correct format.
  • ora-13951 : MMON sub-action time limit exceeded
  • ora-10930 : trace name context forever
  • ora-14038 : GLOBAL partitioned index must be prefixed
  • ora-01643 : system tablespace can not be made read only
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-25405 : transaction status unknown
  • ora-13266 : error inserting data into table string
  • ora-16770 : physical standby database not in read-only state
  • ora-02717 : osnpfs: incorrect number of bytes written
  • 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.