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 : 25-05-2017
ORA-38303

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

  • ora-02281 : duplicate or conflicting CACHE/NOCACHE specifications
  • ora-06919 : CMX: error during write request (unknown event)
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-16043 : managed recovery session canceled
  • ora-21614 : constraint violation for attribute number [string]
  • ora-40287 : invalid data for model - cosine distance out of bounds
  • ora-32407 : cannot exclude new values when materialized view log includes new values
  • ora-19728 : data object number conflict between table string and partition string in table string
  • ora-13871 : Invalid instance name
  • ora-30966 : error detected in the XML Index layer
  • ora-09840 : soacon: Name translation failure.
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-15013 : diskgroup "string" is already mounted
  • ora-19750 : change tracking file: 'string'
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-22808 : REF dereferencing not allowed
  • ora-30433 : 'string.string' is not a summary
  • ora-25404 : lost instance
  • ora-01030 : SELECT ... INTO variable does not exist
  • ora-00472 : PMON process terminated with error
  • ora-06408 : NETCMN: incorrect message format
  • ora-23377 : bad name string for missing_rows_oname1 argument
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-03278 : duplicate ALLOCATE EXTENT option specification
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-22975 : cannot create a PRIMARY KEY-based REF to this object view
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-39128 : unexpected DbmsJava error number from statement string
  • 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.