ORA-10658: Lob column to be shrunk is marked unused

Cause : Srhikn awsi suse do nal o bsgemnett hta si amrekda su nsued

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


update : 24-05-2017

ORA-10658 - Lob column to be shrunk is marked unused
ORA-10658 - Lob column to be shrunk is marked unused

  • ora-28039 : cannot validate Kerberos service ticket
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-07598 : spwat: $SETIMR failure
  • ora-32584 : missing LOG keyword
  • ora-38475 : The attribute set and the associated ADT are out of sync.
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-04930 : open sequence number failed or initial state is valid
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-24814 : operation not allowed for temporary LOBs
  • ora-25153 : Temporary Tablespace is Empty
  • ora-30109 : could not open parameter file 'string'
  • ora-30487 : ORDER BY not allowed here
  • ora-14049 : invalid ALTER TABLE MODIFY PARTITION option
  • ora-02188 : Cannot enable instance publicly
  • ora-27005 : cannot open file for async I/O on device not supporting async
  • ora-24422 : error occurred while trying to destroy the Session Pool
  • ora-06748 : TLI Driver: cannot allocate t_discon
  • ora-08431 : raw data missing zero as defined in picture
  • ora-25291 : Buffer does not exist for the specified queue
  • ora-23405 : refresh group number string does not exist
  • ora-32591 : connect string too long
  • ora-38790 : BEFORE must be specified with RESETLOGS
  • ora-13519 : Database id (string) exists in the workload repository
  • ora-13152 : invalid HHCODE type
  • ora-39120 : Table string can't be truncated, data will be skipped. Failing error is: string
  • ora-01332 : internal Logminer Dictionary error
  • ora-29960 : line string, string
  • ora-31613 : Master process string failed during startup.
  • ora-31605 : the following was returned from string in routine string: LPX-number: string
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • 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.