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 : 27-06-2017

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

  • ora-16100 : not a valid Logical Standby database
  • ora-29394 : session id string and serial# string do not exist
  • ora-19570 : file number string is outside valid range of 1 through string
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-38778 : Restore point 'string' already exists.
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-27053 : blocksize in file header not a multiple of logical block size
  • ora-32613 : not a MODEL cell
  • 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-17620 : failed to register the network adapter with Oracle Disk Manager library: string
  • ora-19203 : Error occurred in DBMS_XMLGEN processingstring
  • ora-13523 : unable to allocate required space for return type
  • ora-19590 : conversation already active
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-27547 : Unable to query IPC OSD attribute string
  • ora-32621 : illegal aggregation in UNTIL iteration condition
  • ora-24782 : Cannot detach from a non-migratable transaction
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-26575 : remote database does not support replication parallel propagation
  • ora-01280 : Fatal LogMiner Error.
  • ora-29655 : USING clause is incompatible with its supertype
  • ora-22980 : must specify a set of attributes for the WITH OBJECT OID clause
  • ora-14401 : inserted partition key is outside specified partition
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-26650 : %s background process string might not be started successfully
  • ora-24301 : null host specified in thread-safe logon
  • ora-01977 : Missing thread number
  • 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.