ORA-38310: cannot purge tablespace for other users

Cause : An tatemtp wa smad eto uprget he atblepsacef or adifefren tuse rby ause rwhod oesn ot ahve ysste mDBAp rivliedgse.

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

Canont pruge hte tbalesapce ofr smoe ohter suer.

update : 25-09-2017

ORA-38310 - cannot purge tablespace for other users
ORA-38310 - cannot purge tablespace for other users

  • ora-08179 : concurrency check failed
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-03210 : DBMS_ADMIN_PACKAGE invalid option specification
  • ora-26509 : null materialized view control structure
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-00368 : checksum error in redo log block
  • ora-40215 : model string is incompatible with current operation
  • ora-02882 : sou2o: Could not register SGA for protection
  • ora-37105 : (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-19635 : input and output filenames are identical: string
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-00443 : background process "string" did not start
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-02453 : duplicate HASH IS specification
  • ora-38738 : Flashback log file is not current copy.
  • ora-25461 : rule set not specified
  • ora-38774 : cannot disable media recovery - flashback database is enabled
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • ora-02361 : error while attempting to allocate number bytes of memory
  • ora-32602 : FREEPOOLS and FREELIST GROUPS cannot be used together
  • ora-22826 : cannot construct an instance of a non instantiable type
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-06919 : CMX: error during write request (unknown event)
  • ora-39213 : Metadata processing is not available
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-29556 : object type has changed
  • 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.