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

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

  • ora-38608 : FI itemset minimum-length(string) should not be greater than maximum length(string)
  • ora-02452 : invalid HASHKEYS option value
  • ora-06003 : NETASY: port write failure
  • ora-30120 : 'string' is not a legal oracle number for 'string'
  • ora-30690 : timeout occurred while registering a TCP/IP connection for data traffic detection
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-38411 : invalid datatype for the column storing expressions
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-12730 : invalid equivalence class in regular expression
  • ora-19105 : invalid XQueryX: expected text node - got string
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-24154 : rule string.string already in rule set string.string
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-09270 : szalloc: error allocating memory for security
  • ora-24000 : invalid value string, string should be of the form [SCHEMA.]NAME
  • ora-01944 : IDENTIFIED EXTERNALLY already specified
  • ora-12505 : TNS:listener does not currently know of SID given in connect descriptor
  • ora-39112 : Dependent object type string skipped, base object type string creation failed
  • ora-24231 : database access descriptor (DAD) string not found
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-01138 : database must either be open in this instance or not at all
  • ora-24145 : evaluation context string.string already exists
  • ora-14081 : new partition name must differ from the old partition name
  • ora-14126 : only a may follow description(s) of resulting partitions
  • ora-27161 : request for Oracle binary information failed
  • ora-01135 : file string accessed for DML/query is offline
  • ora-36404 : (XSSPROP04) Property string cannot be applied to an undimensioned (scalar) TEMPORARY variable.
  • ora-09752 : pw_attachPorts: port_allocate failed.
  • ora-01327 : failed to exclusively lock system dictionary as required by build
  • ora-00211 : control file does not match previous control files
  • 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.