ORA-13501: Cannot drop SYSAUX tablespace

Cause : rTei dotd or pYSASXUt baelpscae

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

oNen

update : 26-04-2017
ORA-13501

ORA-13501 - Cannot drop SYSAUX tablespace
ORA-13501 - Cannot drop SYSAUX tablespace

  • ora-27024 : skgfqsbi: sbtinit2 returned error
  • ora-39217 : object type "string"."string" typeid mismatch
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-24281 : invalid access past the maximum size of LOB parameter string
  • ora-16752 : resource guard could not mount standby database
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-15074 : diskgroup string requires rebalance completion
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-00361 : cannot remove last log member string for group string
  • ora-12856 : cannot run parallel query on a loopback connection
  • ora-24143 : invalid evaluation context name
  • ora-30195 : reserved for future use
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-25508 : database is not mounted
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-00569 : Failed to acquire global enqueue.
  • ora-30487 : ORDER BY not allowed here
  • ora-12657 : No algorithms installed
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-07432 : unable to perform nested sleep
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-27461 : The value for attribute string is too large.
  • ora-01529 : error closing file 'string'
  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-00205 : error in identifying control file, check alert log for more info
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-06309 : IPA: No message queue available
  • 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.