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 : 24-04-2017
ORA-38303

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

  • ora-10931 : trace name context forever
  • ora-39202 : Data cannot be filtered or selected in string jobs.
  • ora-19664 : file type: string, file name: string
  • ora-31048 : Unsaved resources cannot be updated
  • ora-39171 : Job is experiencing a resumable wait. string
  • ora-10947 : trace name context forever
  • ora-27453 : %s is an invalid job or program argument name.
  • ora-14636 : only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
  • ora-06564 : object string does not exist
  • ora-31486 : cannot support column string in this configuration
  • ora-12724 : regular expression corrupt
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-29906 : indextype string.string does not exist
  • ora-31638 : cannot attach to job string for user string
  • ora-19953 : database should not be open
  • ora-14273 : lower-bound partition must be specified first
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-01030 : SELECT ... INTO variable does not exist
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-29545 : badly formed class: string
  • ora-12161 : TNS:internal error: partial data received
  • ora-16786 : resource guard cannot access Data Guard broker metadata
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-22617 : error while accessing the image handle collection
  • ora-01891 : Datetime/Interval internal error
  • ora-09766 : osnmop: buffer allocation failure.
  • ora-24032 : object string exists, index could not be created for queue table string
  • ora-12165 : TNS:Trying to write trace file into swap space.
  • 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.