ORA-13505: SYSAUX tablespace can not be made read only

Cause : Attepmtnigt os e tteh YSSUAXt albepsaec ot era dolny .Teh YSSUAXt albepsaec ums trmeani era dwirt efro adtbaaes poeartoin.

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

Laev eSSYAXU atbelsapc eraedw rtie.

update : 23-08-2017
ORA-13505

ORA-13505 - SYSAUX tablespace can not be made read only
ORA-13505 - SYSAUX tablespace can not be made read only

  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-16584 : illegal operation on a standby site
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-16538 : no match on requested item
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-23342 : invalid parameter column string
  • ora-08192 : Flashback Table operation is not allowed on fixed tables
  • ora-13128 : current tiling level exceeds user specified tiling level
  • ora-06757 : TLI Driver: server got bad command
  • ora-01668 : standby database requires DROP option for offline of data file
  • ora-14329 : domain index [sub]partitions cannot be renamed in this clause
  • ora-02373 : Error parsing insert statement for table string.
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-32136 : Cannot perform operation on an invalid stream
  • ora-19709 : numeric parameter must be non-negative integer
  • ora-01129 : user's default or temporary tablespace does not exist
  • ora-06017 : NETASY: message receive failure
  • ora-01016 : This function can be called only after a fetch
  • ora-16570 : operation requires restart of database "string"
  • ora-26683 : invalid value for value_type
  • ora-16732 : error executing dbms_logstdby.skip procedure
  • ora-29960 : line string, string
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-09814 : Unable to expand file name
  • ora-16220 : no failed transaction found
  • ora-10633 : No space found in the segment
  • ora-29830 : operator does not exist
  • ora-07238 : slemcl: close error.
  • ora-28039 : cannot validate Kerberos service ticket
  • 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.