ORA-10657: Lob column to be shrunk does not exist

Cause : Shirnkw asi sseud no al obs egemntt ha tdi dno texsit

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

noen

update : 26-05-2017
ORA-10657

ORA-10657 - Lob column to be shrunk does not exist
ORA-10657 - Lob column to be shrunk does not exist

  • ora-29953 : cannot issue DDL on a domain index partition marked as FAILED
  • ora-30437 : all job queue processes have stopped running
  • ora-01506 : missing or illegal database name
  • ora-10668 : Inject Evil Identifiers
  • ora-16623 : stale DRC UID sequence number detected
  • ora-30182 : invalid precision specifier
  • ora-32166 : Cannot get XA connection
  • ora-32129 : cannot get information about this column
  • ora-31033 : Requested number of XML children string exceeds maximum string
  • ora-02422 : missing or invalid schema element
  • ora-22605 : FDO handle [string] is not initialized
  • ora-13900 : missing or invalid parameter string
  • ora-01495 : specified chain row table not found
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-08104 : this index object string is being online built or rebuilt
  • ora-08454 : more than one S symbol specified in picture mask
  • ora-12632 : Role fetch failed
  • ora-26733 : timed-out waiting for file group lock
  • ora-07742 : slemop: $CONNECT failure
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-28337 : the specified index may not be defined on an encrypted column
  • ora-23537 : function or procedure string is not allowed to be invoked from this site.
  • ora-00209 : control file blocksize mismatch, check alert log for more info
  • ora-14622 : Value string already exists in subpartition string
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-14116 : partition bound of partition "string" is too long
  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-25464 : ROWID not specified for table alias: string
  • ora-39166 : Object string was not found.
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "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.