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 : 26-06-2017
ORA-10630

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

  • ora-39094 : Parallel execution not supported in this database edition.
  • ora-00386 : use_indirect_data_buffers not supported
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-02278 : duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
  • ora-16703 : cannot set property while the database is enabled
  • ora-02719 : osnfop: fork failed
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-27125 : unable to create shared memory segment
  • ora-38481 : ADT "string" is used for a dependent object.
  • ora-01183 : cannot mount database in SHARED mode
  • ora-30974 : invalid Path Id Index option for XML Index
  • ora-08270 : sksachk: Illegal archival control string
  • ora-19256 : XQ0036 - missing type definitions in imported module
  • ora-00823 : Specified value of sga_target greater than sga_max_size
  • ora-02315 : incorrect number of arguments for default constructor
  • ora-30400 : identical JOIN KEY clauses
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-39018 : master process received invalid message number string
  • ora-03283 : specified datafile string does not exist
  • ora-16604 : unable to describe template using package "string"
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-12820 : invalid value for DEGREE
  • ora-19040 : Element string does not match expected string.
  • ora-12600 : TNS: string open failed
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-12163 : TNS:connect descriptor is too long
  • ora-31052 : Cannot delete ACL with other references
  • ora-36316 : (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.
  • ora-06711 : TLI Driver: error on bind
  • 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.