ORA-38303: invalid option for PURGE TABLESPACE

Cause : Either a token other than USER was found following the tablespace name or some text was found following USER .

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

Place nothing or only USER after the tablespace name

update : 26-06-2017
ORA-38303

ORA-38303 - invalid option for PURGE TABLESPACE
ORA-38303 - invalid option for PURGE TABLESPACE

  • ora-26519 : no memory available to allocate
  • ora-12483 : label not in OS system accreditation range
  • ora-07619 : $IDTOASC failed translating an integrity level
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-29839 : failed to validate implementation type
  • ora-28665 : table and partition must have same compression attribute
  • ora-14316 : table is not partitioned by List method
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-32345 : fail to refresh the materialized view string.string due to the changed synonym
  • ora-08275 : Environment variable unset
  • ora-01262 : Stat failed on a file destination directory
  • ora-31484 : source database version must be at least 9.2.0.6 or greater
  • ora-19266 : XQ0046 - invalid URI
  • ora-12438 : repeated policy option: string
  • ora-12653 : Authentication control function failed
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-01097 : cannot shutdown while in a transaction - commit or rollback first
  • ora-01579 : write error occurred during recovery
  • ora-23353 : deferred RPC queue has entries for object group "string"."string"
  • ora-22884 : object modification failed
  • ora-01058 : internal New Upi interface error
  • ora-13837 : invalid HASH_VALUE
  • ora-36683 : (XSDPART21) Partition string dimensioned by more than one composite.
  • ora-01144 : File size (string blocks) exceeds maximum of string blocks
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-12335 : database (link name string) is not open
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-32767 : No server connection for this operation
  • ora-12205 : TNS:could not get failed addresses
  • 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.