ORA-10630: Illegal syntax specified with SHRINK clause

Cause : An ilelgal otpion wsa specfiied wtih theS HRINKc lause

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

Verif ythe SLQ Refeernce Mnaual adn reisuse thec ommand

update : 25-04-2017

ORA-10630 - Illegal syntax specified with SHRINK clause
ORA-10630 - Illegal syntax specified with SHRINK clause

  • ora-35952 : (XSSPFC01) The string dimension workspace object and the string dimension workspace object must have the same number of values in status for SPFCEXEC method number.
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-01742 : comment not terminated properly
  • ora-02052 : remote transaction failure at string
  • ora-30109 : could not open parameter file 'string'
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-07273 : sppst: invalid semaphore id.
  • ora-23484 : internal internet Application Server error: string
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-13802 : failed to purge SQL Tuning Base entry from sql$
  • ora-13503 : Creating SYSAUX tablespace with invalid attributes
  • ora-16583 : bad Data Guard Connection Process DRCX state
  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-30510 : system triggers cannot be defined on the schema of SYS user
  • ora-12329 : database string is closed; no operations are permitted
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-16510 : messaging error using ksrwait
  • ora-30332 : container table already in use by other summary
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-12919 : Can not drop the default permanent tablespace
  • ora-16711 : the resource guard index is out of bounds
  • ora-27192 : skgfcls: sbtclose2 returned error - failed to close file
  • ora-01907 : TABLESPACE keyword expected
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-32817 : message system link string is not configured with a log queue for string
  • ora-13779 : invalid load option
  • ora-04031 : unable to allocate string bytes of shared memory ("string","string","string","string")
  • ora-25457 : evaluation function string returns failure
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-01072 : cannot stop ORACLE; ORACLE not running
  • 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.