ORA-22868: table with LOBs contains segments in different tablespaces

Cause : An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment.

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

Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace.

update : 25-06-2017
ORA-22868

ORA-22868 - table with LOBs contains segments in different tablespaces
ORA-22868 - table with LOBs contains segments in different tablespaces

  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-29558 : JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-26056 : Requested direct path operation on a view is not supported.
  • ora-13295 : geometry objects are in different coordinate systems
  • ora-13831 : SQL profile name specified is invalid
  • ora-26715 : time limit reached
  • ora-33000 : (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of string.
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-07474 : snclrd: close error, unable to close sgadef.dbf file.
  • ora-15041 : diskgroup space exhausted
  • ora-22330 : cannot alter a type that is not valid
  • ora-14006 : invalid partition name
  • ora-16547 : cannot disable the primary database
  • ora-15103 : conflicting or duplicate REPAIR options
  • ora-21300 : objects option not installed
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-02052 : remote transaction failure at string
  • ora-06535 : statement string in string is NULL or 0 length
  • ora-01049 : Bind by name is not spupportted in streamed RPC
  • ora-19923 : the session for row with id string is not active
  • ora-16094 : database shutdown during archival operation
  • ora-37108 : (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
  • ora-34344 : (MXDSS03) Analytic workspace string is not attached.
  • ora-12034 : materialized view log on "string"."string" younger than last refresh
  • ora-02212 : duplicate PCTFREE option specification
  • ora-12480 : specified clearance labels not within the effective clearance
  • ora-01969 : You must specify RESETLOGS or NORESETLOGS
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-19569 : no device is allocated to this session
  • 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.