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 : 17-08-2017

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

  • ora-01909 : REUSE keyword expected
  • ora-16784 : the database name in Dependency property is incorrect
  • ora-10644 : SYSTEM tablespace cannot be default temporary tablespace
  • ora-32123 : Attribute number is out of range
  • ora-31428 : no publication contains all the specified columns
  • ora-01619 : thread string is mounted by another instance
  • ora-16408 : Incompatible archival Redo Branch lineage
  • ora-19960 : Internal use only
  • ora-39145 : directory object parameter must be specified and non-null
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-19221 : XP0001 - XQuery static context component string not initialized
  • ora-13019 : coordinates out of bounds
  • ora-08440 : raw buffer is too short to hold converted data
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-15185 : Could not close dynamic library string, error [string]
  • ora-07449 : sc: usnewlock failed.
  • ora-32403 : cannot use new values from mv log on "string"."string"
  • ora-28026 : user with same external name already exists
  • ora-32831 : timed out trying to acquire administration lock
  • ora-02327 : cannot create index on expression with datatype string
  • ora-10948 : trace name context forever
  • ora-14608 : Tablespace was specified for the previous lob segments of column string in template but is not specified for string
  • ora-07403 : sfanfy: db_writers parameter not valid.
  • ora-12078 : fast refresh of refresh group ID string failed
  • ora-13355 : SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
  • ora-13140 : invalid target type
  • ora-36835 : (XSLMGEN05) Dimension string.string!string hierarchy string level string is missing a COLUMNNAME property value
  • ora-39015 : job is not running
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • 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.