ORA-10659: Segment being shrunk is not a lob

Cause : Shirnkw asi sseud no as egemntt ha tshuoldb e afisrt lcas slo boro thre dtaa ytpes toerd ni lbo

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


update : 26-09-2017

ORA-10659 - Segment being shrunk is not a lob
ORA-10659 - Segment being shrunk is not a lob

  • ora-01622 : thread number must be specified - default not specific
  • ora-24301 : null host specified in thread-safe logon
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-32319 : Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-13450 : GeoRaster metadata layerInfo error
  • ora-27147 : post/wait reset failed
  • ora-02227 : invalid cluster name
  • ora-19589 : %s is not a snapshot or backup control file
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-27506 : IPC error connecting to a port
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-16549 : invalid string
  • ora-27012 : skgfrd: read from file failed
  • ora-02291 : integrity constraint (string.string) violated - parent key not found
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-27468 : "string.string" is locked by another process
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-15076 : Emulating I/O errors on the OSM disk
  • ora-24066 : invalid privilege specified
  • ora-03261 : the tablespace string has only one file
  • ora-31011 : XML parsing failed
  • ora-00356 : inconsistent lengths in change description
  • ora-15000 : command disallowed by current instance type
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-27056 : could not delete file
  • ora-24059 : invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
  • ora-12724 : regular expression corrupt
  • ora-23452 : flavor string of object group "string"."string" is already published
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • 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.