Largest tables... LOB Segment

HI,
ina CRM system, we would liket to start a data archiving project... but the 10 largets tables are lob segment.... so how can approch the project in this case?
Regards.

Hi,
Note 1438410  explicity indicates:
No documentation is available. We take no responsibility for the
correctness of the scripts and we will not provide any support for
these.
what you have to do is to read the script and figure out how to use it.
However, I have executed the script you mention on the sqlplus prompt and it does not request any sql_id.
Probably you refer to other script.
Nevertheless, the sql_id is an unique identifier for statements (that may or may be in the V$CURSOR) there are statements that retrieve information from the cache or from the history or ...
Usually you identify first an statement you want to analyze, and then you analyze it. Sometimes using the scripts on the mentioned note.
Other times some of those scrips can provide you with the information of "what" sql_ids look at, etc.

Similar Messages

  • Should we use LOGGING or NOLOGGING for table, lob segment, and indexes?

    We have some DML performance issue on cf contention over the tables that also include LOB segments. In this case, should we define LOGGING on tables, lob segments, and/or INDEXES?
    Based on the metalink note < Performance Degradation as a Result of 'enq: CF - contention' [ID 1072417.1]> It looks we need to turn on logging for at least table and lob segment. What about the indexes?
    Thanks!

    >
    These tables that have nologging are likely from the application team. Yes, we need to turn on the logging from nologging for tables and lob segments. What about the indexes?
    >
    Indexes only get modified when the underlying table is modified. When you need recovery you don't want to do things that can interfere with Oracle's ability to perform its normal recovery. For indexes there will never be loss of data that can't be recovered by rebuilding the index.
    But use of NOLOGGING means that NO RECOVERY is possible. For production objects you should ALWAYS use LOGGING. And even for those use cases where use of NOLOGGING is appropriate for a table (loading a large amount of data into a staging table) the indexes are typically dropped (or at least disabled) before the load and then rebuilt afterward. When they are rebuilt NOLOGGING is used during the rebuild. Normal index operations will be logged anyway so for these 'offline' staging tables the setting for the indexes doesn't really matter. Still, as a rule of thumb you only use NOLOGGING during the specific load (for a table) or rebuild (for an index) and then you would ALTER the setting to LOGGING again.
    This is from Tom Kyte in his AskTom blog from over 10 years ago and it still applies today.
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:5280714813869
    >
    NO NO NO -- it does not make sense to leave objects in NOLOGGING mode in a production
    instance!!!! it should be used CAREFULLY, and only in close coordination with the guys
    responsible for doing backups -- every non-logged operation performed makes media
    recovery for that segment IMPOSSIBLE until you back it up.
    >
    Use of NOLOGGING is a special-case operation. It is mainly used in Datawarehouse (OLAP systems) data processing during truncate-and-load operations on staging tables. Those are background or even offline operations and the tables are NOT accessible by end users; they are work tables used to prepare the data that will be merged to the production tables.
    1. TRUNCATE a table
    2. load the table with data
    3. process the data in the table
    In those operations the table load is seldom backed up and rarely needs recovery. So use of NOLOGGING enhances the performance of the data load and the data can be recovered, if necessary, from the source it was loaded from to begin with.
    Use of NOLOGGING is rarely, if ever, used for OLTP systems since that data needs to be recovered.

  • Truncate table will delete the corresponding LOB segment of table or not ?

    Hi All,
    I have few table with LOB segments, if i fire the truncate table on those table will it purge the LOB segment as well ?
    Approximately how much time will take to truncate 100gb LOB segments.
    Thanks

    903787 wrote:
    Hi ,
    1.Truncate will delete the LOB segment or not ?It won't delete the LOB segments but it should release most of the allocated space.
    >
    2.To reclaim space we need to run the below command, is it correct ?
    ALTER TABLE <table_name> MODIFY LOB (LOB_COLUMN) (SHRINK SPACE);
    Should not be needed in 11.2:
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production
    PL/SQL Release 11.2.0.2.0 - Production
    CORE    11.2.0.2.0      Production
    TNS for 32-bit Windows: Version 11.2.0.2.0 - Production
    NLSRTL Version 11.2.0.2.0 - Production
    SQL> select count(*) from user_segments;
      COUNT(*)
             0
    SQL>
    SQL> create table t(x clob);
    Table created.
    SQL> select segment_name, segment_type, bytes
      2  from user_segments;
    SEGMENT_NAME                             SEGMENT_TYPE            BYTES
    T                                        TABLE                   65536
    SYS_IL0000030908C00001$$                 LOBINDEX                65536
    SYS_LOB0000030908C00001$$                LOBSEGMENT              65536
    SQL>
    SQL> insert into t select lpad(segment_name,8192) from dba_segments;
    6312 rows created.
    SQL> commit;
    Commit complete.
    SQL>
    SQL> select segment_name, segment_type, bytes
      2  from user_segments;
    SEGMENT_NAME                             SEGMENT_TYPE            BYTES
    T                                        TABLE                  393216
    SYS_IL0000030908C00001$$                 LOBINDEX                65536
    SYS_LOB0000030908C00001$$                LOBSEGMENT           53477376
    SQL>
    SQL> truncate table t;
    Table truncated.
    SQL>
    SQL> select segment_name, segment_type, bytes
      2  from user_segments;
    SEGMENT_NAME                             SEGMENT_TYPE            BYTES
    T                                        TABLE                   65536
    SYS_IL0000030908C00001$$                 LOBINDEX                65536
    SYS_LOB0000030908C00001$$                LOBSEGMENT              65536
    SQL>
    SQL> alter table t modify lob(x) (shrink space);
    Table altered.
    SQL>
    SQL> select segment_name, segment_type, bytes
      2  from user_segments;
    SEGMENT_NAME                             SEGMENT_TYPE            BYTES
    T                                        TABLE                   65536
    SYS_IL0000030908C00001$$                 LOBINDEX                65536
    SYS_LOB0000030908C00001$$                LOBSEGMENT              65536
    SQL>

  • How to move lob segment in partitioned table

    On my Oracle 11.2, I have a partitioned table wich I would like to move to another tablespace
    After invoking script, there's still unmoved lob segment withing table
    CREATE TABLE BONGO.AAA_3
      ID       NUMBER,
      DATUM    DATE,
      OBJEKAT  BLOB
    TABLESPACE BONGODATA_HUGE
    PCTUSED    40
    PCTFREE    10
    INITRANS   1
    MAXTRANS   255
    LOGGING
    PARTITION BY RANGE (DATUM)
      PARTITION P_MAXVALUE VALUES LESS THAN (MAXVALUE)
        LOGGING
        NOCOMPRESS
        TABLESPACE BONGODATA_HUGE
    LOB (OBJEKAT) STORE AS
            (   TABLESPACE  BONGODATA
              ENABLE        STORAGE IN ROW
              CHUNK       8192
              RETENTION
              NOCACHE
              STORAGE    (
                          INITIAL          64K
                          NEXT             1M
                          MINEXTENTS       1
                          MAXEXTENTS       UNLIMITED
                          PCTINCREASE      0
                          FREELISTS        1
                          FREELIST GROUPS  1
                          BUFFER_POOL      DEFAULT
        PCTUSED    40
        PCTFREE    10
        INITRANS   1
        MAXTRANS   255
        STORAGE    (
                    INITIAL          64K
                    NEXT             1M
                    MINEXTENTS       1
                    MAXEXTENTS       UNLIMITED
                    FREELISTS        1
                    FREELIST GROUPS  1
                    BUFFER_POOL      DEFAULT
    NOCOMPRESS
    NOCACHE
    NOPARALLEL
    MONITORING;how to move this lob segment in partitioned table?
    or, is there some package for data move within tablespaces?
    regards

    tnx...
    now, I have another problem..
    I have a nested table within partitioned table, and I'm trying to move it to another tablespace.
    I tried to move child table (of nested type colum), but I didn't succedeed...

  • Problem creating LOB segment

    Hi all,
    I'm working with 11gR2 version in RAC environment with 2 nodes. I'm creating the schemes on my new database with empty tablespaces and 100Mb of initial free space. I'm having an error on the creation of this table:
    CREATE TABLE "IODBODB1"."DOCUMENTOS"
    (     "ID_DOC" NUMBER NOT NULL ENABLE,
         "ID_APP" NUMBER(5,0) NOT NULL ENABLE,
         "ID_CLS" NUMBER(6,0) NOT NULL ENABLE,
         "CREATE_FEC" DATE NOT NULL ENABLE,
         "LAST_MODIFIED_FEC" DATE NOT NULL ENABLE,
         "DOC_NAME" VARCHAR2(100 BYTE) NOT NULL ENABLE,
         "DOC_SIZE" NUMBER NOT NULL ENABLE,
         "DOC_DATA" BLOB NOT NULL ENABLE,
         "CLASE_FORMATO_FORMATO" VARCHAR2(150 BYTE),
         "REGULAR_NAME" VARCHAR2(100 BYTE) NOT NULL ENABLE,
         "USUARIO" VARCHAR2(25 BYTE),
         "USUARIO_LEVEL" VARCHAR2(5 BYTE)
    ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "ODBODB_TBD_DADES"
    LOB ("DOC_DATA") STORE AS BASICFILE (ENABLE STORAGE IN ROW CHUNK 8K PCTVERSION 10 NOCACHE LOGGING STORAGE( BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
    PARTITION BY LIST ("ID_APP")
    SUBPARTITION BY RANGE ("ID_DOC")
    PARTITION "PTL_DOCUMENTOS_FICTICIO" VALUES (0) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
    STORAGE(BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "ODBODB_TBD_DADES"
    LOB ("DOC_DATA") STORE AS BASICFILE (ENABLE STORAGE IN ROW CHUNK 8K PCTVERSION 10 NOCACHE LOGGING STORAGE(BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
    (SUBPARTITION "PTR_DOCUMENTOS_FICTICIO" VALUES LESS THAN (MAXVALUE) LOB ("DOC_DATA") STORE AS (TABLESPACE "ODBODB_TBL_LOBS" ) TABLESPACE "ODBODB_TBD_DADES" NOCOMPRESS ) );
    PARTITION "PTL_DOCUMENTOS_ALFIMG" VALUES (2) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
    STORAGE(BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "ODBODB_TBD_DADES"
    LOB ("DOC_DATA") STORE AS BASICFILE (ENABLE STORAGE IN ROW CHUNK 32K PCTVERSION 10 NOCACHE LOGGING STORAGE(BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
    (SUBPARTITION "STR_DOCUMENTOS_ALFIMG" VALUES LESS THAN (MAXVALUE) LOB ("DOC_DATA") STORE AS (TABLESPACE "BEALFIMG_TBL_ODB" ) TABLESPACE "BEALFIMG_TBD_ODB" NOCOMPRESS )
    The error is:
    ORA-03252: initial extent size not enough for LOB segment
    I can't understand how Oracle can't allocate enough extents to create the LOB segment, and I don't know to which LOB segment it refers because the sqlplus don't mark it with the error.
    Any ideas about this issue?
    Thanks in advance!
    dbajug

    Please, forget this post, I feel dumb... The LOB segment need to have same size of the rest of partition...

  • LOB Segments

    Hi
    How is the size of the LOBSEGMENT caluclated? We carried out an insert of around 50 odd columns into a table that contained a CLOB value, but we observed that LOBSEGMENT value was a very huge figure, around 400mb, though the entire data contained in the table would not exceed 50 mb. The LOBSEGMENT has an intial extent of 65536 bytes. If it goes on increasing, what will be its max limit?
    Initially, when the clobs were being created, we ran out of table space and therefore the rows did not get created. But the LOBSEGMENT was observed to be around 200 mb in size though there were zero rows in the table.
    Also, we did the clob manipulation using DBMS_LOB package and observed that midway during the generation of clob data, the session got killed somehow. And this happened four to five times during the clob creation.
    Please help :-)
    Thanks,
    Vinoj

    You can use DBA_LOBS to link tables and LOB columns:
    select table_name, column_name, segment_name
    from dba_lobs
    where segment_name = <...>The 10 biggest LOB segments with table and column info should be retrieved with:
    select * from (
    select
    l.owner,
    l.table_name,
    l.column_name,
    l.segment_name,
    round(s.bytes/1024/1024) as mb
    from dba_lobs l , dba_segments s
    where l.owner = s.owner
    and l.segment_name = s.segment_name
    order by s.bytes desc
    ) where rownum < 11;If you are using SAP you should contact SAP support to make sure any script is also supported by SAP.
    Edited by: P. Forstmann on 31 oct. 2011 17:29
    Edited by: P. Forstmann on 31 oct. 2011 17:30

  • LOB segment size is 2 times bigger than the real data

    here's an interesting test:
    1. I created a tablespace called "smallblock" with 2K blocksize
    2. I created a table with a CLOB type field and specified the smallblock tablespace as a storage for the LOB segment:
    SCOTT@andrkydb> create table t1 (i int, b clob) lob (b) store as
    t1_lob (chunk 2K disable storage in row tablespace smallblock);
    3. I insert data into the table, using a bit less than 2K of data for the clob type column:
    SCOTT@andrkydb> begin
    2 for i in 1..1000 loop
    3 insert into t1 values (mod(i,5), rpad('*',2000,'*'));
    4 end loop;
    5 end;
    6 /
    4. Now I can see that I have an average of 2000 bytes for each lob item:
    SCOTT@andrkydb> select avg(dbms_lob.getlength(b)) from t1;
    AVG(DBMS_LOB.GETLENGTH(B))
    2000
    and that all together they take up:
    SCOTT@andrkydb> select sum(dbms_lob.getlength(b)) from t1;
    SUM(DBMS_LOB.GETLENGTH(B))
    2000000
    But when I take a look at how much is the LOB segment actually taking, I get a result, which is being a total mystery to me:
    SCOTT@andrkydb> select bytes from dba_segments where segment_name = 'T1_LOB';
    BYTES
    5242880
    What am I missing? Why is LOB segment is being ~2 times bigger than it is required by the data?
    I am on 10.2.0.3 EE, Solaris 5.10 sparc 64bit.
    Message was edited by:
    Andrei Kübar

    thanks for the link, it is good to know such thing is possible. Although I don't really see how can it help me..
    But you know, you were right regarding the smaller data amounts. I have tested with 1800 bytes of data and in this case it does fit just right.
    But this means that there is 248 bytes wasted (from my, as developer, point of view) per block! But if there is such an overhead, then I must be able to estimate it when designing the data structures. And I don't see anywhere in the docs a single word about such thing.
    Moreover, if you use NCLOB type, then only 990 bytes fits into a single 2K chunk. So the overhead might become really huge when you go over to gigabyte amounts...
    I have a LOB segment for a nclob type field in a production database, which is 5GB large and it contains only 2,2GB of real data. There is no "deleted" rows in it, I know because I have rebuilt it. So this looks like a total waste of disk space... I must say, I'm quite disappointed with this.
    - Andrei

  • Fastest and easiest way to drop a tablespace with LOB Segments

    When I try to drop a tablespace I get a message that I can't cause it still contains LOB Segments. I searched to see what objects like tables or indexes are in that tablespace and there are none.
    Any one run into this? Any way to get around this issue?

    Sorry,
    Version = 10.2.0.4
    OS = Win2003 32bit
    Command used = DROP TABLESPACE IWORKS_LARGE_TABLES INCLUDING CONTENTS AND DATAFILES;
    Error Message = ORA-22868: table with LOBs contains segments in different tablespaces
    Objects currently in this tablespace:
    SQL> select s.segment_name, s.segment_type
      2    from dba_segments s
      3   where tablespace_name = 'IWORKS_LARGE_TABLES'
      4  ;
    SEGMENT_NAME                                                                     SEGMENT_TYPE
    SYS_IL0000060885C00008$$                                                         LOBINDEX
    SYS_LOB0000060885C00008$$                                                        LOBSEGMENT
    SYS_IL0000060918C00048$$                                                         LOBINDEX
    SYS_LOB0000060918C00048$$                                                        LOBSEGMENTI basically want to drop the whole tablespace but these objects are not allowing me to.

  • Move LOB segment

    Oracle 11.0.1.7:
    How can I move the lob segment: I am trying this
    CREATE TABLE PART_TMP(
      PAYLOAD_ID Number(19,0) NOT NULL,
      created_date timestamp(6),
      pay blob
    LOB ("PAY") STORE AS (DISABLE STORAGE IN ROW TABLESPACE EFE_LOB)
    PARTITION BY RANGE (payload_id)
    interval (2)
    SUBPARTITION BY HASH (payload_id)
    SUBPARTITIONS 64(PARTITION PART_TMP_p00 VALUES LESS THAN (1));
    alter table part_tmp move subpartition SYS_SUBP28243 update indexes; --This works
    --But this doesn't work. Is this the right way of moving LOB segment? Looks like Lobs segment doesn't move with above command.
    alter table part_tmp move LOB(pay) subpartition SYS_SUBP28243 update indexesI need to move SUBPARTTION and associated LOB SUBPARTITION. Could someone please help?

    There is a table which has a LOB and there are lot of deletes and updates happening daily .
    I need to shrink the space. When I use:
    alter table lob_test modify lob (data) (shrink space);
    It throws an error cannot use shrink clause on this table. Table as no function based indexes and segment space management for this tablespace is auto.
    Can any one tell what is the best approach to reclaim the space.
    Can any one tell can I use the alter table move online or needs downtime.
    Thanks

  • Unable to extend lob segment SAPSR4DB

    Hi All,
    I am getting the error u201Cunable to extend lob segment SAPSR4DBu201D when i try to import any dependency into my SC or during the Assembly of my SCA. Then we go and increase the space of the table, it starts working.
    I would like to know how to resolve this problem and if there is any setting to be made so that the contents of this table are cleared automatically after being used?
    Regards,
    Poojith MV

    Hi,
    Have you cheked SAP / BRTOOLS for a tablespace overflow ?
    Mark

  • Performance of LOB Segments for Blob Columns

    Hi,
    I am migrating 11,000 rows of tiff images from Informix to Oracle.In Informix the datatype for the image storage is Byte and Oracle we chose it to Blob.
    The Blob column is creating lob segment and lob index.
    When I do the migration I observe that the size of the lob segment object is increasing rather than the table object.
    So due to creation of this lob segment for the Blob column,will there be any performance issues while retrieval of images from the database and Inserting images into into the database.
    Can I get all the issues that can be encountered by storing data in blob column in terms of lob segment.
    This is very important information for us as the application has lot of SQL queries for retrieving and injecting images in the database.
    It will be really apprecialbe if you can provide Information about this.
    Thanks & Regards
    Ramanathan KrishnaMurthy

    I agree with D.Morgan that object type with 250 attributes is doubtful.
    I don't like object tables (tables with "row objects") too.
    But, your table is a relational table with object column ("column object").
    C.J.Date in An introduction to Database Systems (2004, page 885) says:
    "... object/relational systems ... are, or should be, basically just relational systems
    that support the relational domain concept (i.e., types) properly - in other words, true relational systems,
    meaning in particular systems that allow users to define their own types."
    1. How will Oracle store the data in the ADT column?...
    For some answers see:
    “OR(DBMS) or R(DBMS), That is the Question”
    http://www.quest-pipelines.com/pipelines/plsql/tips.htm#OCTOBER
    and (of course):
    "Oracle® Database Application Developer's Guide - Object-Relational Features" 10g Release 2 (10.2)
    http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14260/adobjadv.htm#i1006903
    Regards,
    Zlatko

  • Alter partitioned lob segment syntax - trouble

    Hi,
    I've created range partitioned table as follows:
    CREATE TABLE TAB_NEW
    ID NUMBER(10) NOT NULL,
    DANE CLOB
    PCTUSED 40
    PCTFREE 5
    INITRANS 1
    MAXTRANS 255
    STORAGE (
    INITIAL 1M
    NEXT 1M
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    PCTINCREASE 0
    FREELISTS 1
    FREELIST GROUPS 1
    BUFFER_POOL DEFAULT
    NOLOGGING
    NOCOMPRESS
    NOCACHE
    NOPARALLEL
    NOMONITORING
    TABLESPACE BAD
    partition by range(ID)
    partition p1 values less than (3047004) tablespace BAD LOB(DANE) store as DANEP1 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p2 values less than (6090036) tablespace BAD LOB(DANE) store as DANEP2 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p3 values less than (9158799) tablespace BAD LOB(DANE) store as DANEP3 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p4 values less than (12237772) tablespace BAD LOB(DANE) store as DANEP4 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p5 values less than (15271041) tablespace BAD LOB(DANE) store as DANEP5 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p6 values less than (18304310) tablespace BAD LOB(DANE) store as DANEP6 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p7 values less than (21342986) tablespace BAD LOB(DANE) store as DANEP7 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p8 values less than (24376274) tablespace BAD LOB(DANE) store as DANEP8 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p9 values less than (27409624) tablespace BAD LOB(DANE) store as DANEP9 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p10 values less than (30442947) tablespace BAD LOB(DANE) store as DANEP10 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p11 values less than (33476406) tablespace BAD LOB(DANE) store as DANEP11 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p12 values less than (36509752) tablespace BAD LOB(DANE) store as DANEP12 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p13 values less than (39543085) tablespace BAD LOB(DANE) store as DANEP13 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p14 values less than (42577960) tablespace BAD LOB(DANE) store as DANEP14 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p15 values less than (45611690) tablespace BAD LOB(DANE) store as DANEP15 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p16 values less than (48645056) tablespace BAD LOB(DANE) store as DANEP16 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p17 values less than (51678366) tablespace BAD LOB(DANE) store as DANEP17 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p18 values less than (54711686) tablespace BAD LOB(DANE) store as DANEP18 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p19 values less than (57747336) tablespace BAD LOB(DANE) store as DANEP19 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p20 values less than (60782373) tablespace BAD LOB(DANE) store as DANEP20 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p21 values less than (63816780) tablespace BAD LOB(DANE) store as DANEP21 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p22 values less than (66852173) tablespace BAD LOB(DANE) store as DANEP22 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p23 values less than (69888407) tablespace BAD LOB(DANE) store as DANEP23 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p24 values less than (72923756) tablespace BAD LOB(DANE) store as DANEP24 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p25 values less than (75960757) tablespace BAD LOB(DANE) store as DANEP25 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p26 values less than (78997758) tablespace BAD LOB(DANE) store as DANEP26 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p27 values less than (82034759) tablespace BAD LOB(DANE) store as DANEP27 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p28 values less than (85071760) tablespace BAD LOB(DANE) store as DANEP28 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p29 values less than (88108761) tablespace BAD LOB(DANE) store as DANEP29 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p30 values less than (91145762) tablespace BAD LOB(DANE) store as DANEP30 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p31 values less than (94182763) tablespace BAD LOB(DANE) store as DANEP31 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p32 values less than (97219764) tablespace BAD LOB(DANE) store as DANEP32 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p33 values less than (100256765) tablespace BAD LOB(DANE) store as DANEP33 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p34 values less than (103293766) tablespace BAD LOB(DANE) store as DANEP34 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p35 values less than (106330767) tablespace BAD LOB(DANE) store as DANEP35 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p36 values less than (109367768) tablespace BAD LOB(DANE) store as DANEP36 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p37 values less than (112404769) tablespace BAD LOB(DANE) store as DANEP37 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition p38 values less than (115441770) tablespace BAD LOB(DANE) store as DANEP38 (tablespace BAD chunk 8k NOCACHE NOLOGGING ),
    partition P_MAX values less than (maxvalue) tablespace BAD LOB(DANE) store as DANEPMAX (tablespace BAD chunk 8k NOCACHE NOLOGGING )
    what is the syntax to change lob segments to logging ?
    Tried with :
    alter table TAB_NEW modify partition p1 lob(dane) store as DANEP1 (logging)
    but no success (ORA-00906: missing left parenthesis).
    Regards.
    G

    Ok, got that:
    alter table TAB_NEW modify partition p1 lob(dane) (cache);
    cache makes logging implicit, with
    nocache You can have logging or nologging :)
    Regards.
    G

  • Critical_Segment LOB segment

    I am receiving this error: CRITICAL_SEGMENT, object: (LOB segment) SAPR3.REPOLOAD.SYS_LOB0000130701C00013$$, value: 1659040 KB * 2 / PSAPEL620D (> 2349048/680920/445376/168160/74600 KB)
    Can someone help me figure out what this is trying to tell me?

    This condition checks whether there are tables or indexes that can cause
    an overflow of the tablespace with the allocation of up to 5
    Next-Extents. As a default, all tables and indexes are checked against
    the same threshold value. However, you can define different threshold
    values for individual segments or tablespaces by specifying their names
    in the OBJECT field of the DBCHECKORA table (transaction DB17).

  • How to find the largest tables in EBS

    Hi gurus,
    Oracle EBS R12.1.2
    Linux x86-64
    RDBMS 11g
    How can I find the top 10 largest tables in EBS - in terms of size (KB/MB)? pls send me the Query and also direction from where (which Schema) should I run that query?
    -- TIA

    Hi;
    I suggest check below threads:
    How to know which is the largest table in my oracle database??
    Find Largest Tables in 9i Database
    Query to find biggest table in oracle ERP database?
    Those links should give you answer of your questions.
    Regard
    Helios

  • SOA 11g - XML_DOCUMENT lob segment unable to purge

    Hi All,
    I have SOA 11.1.1.6.0 on Linux x86-64 platform(Oracle Database 11.2.0.3)
    I'm using the Purge script/Procedure as advised in Note “Oracle Fusion Middleware (FMW) SOA 11g Infrastructure Database: Installation, Maintenance and Administration Guide [ID 1384379.1]”
    But this is not purging XML_DOCUMENT LOB segment which has grown too big. This is causing space issues.
    Can somebody advise if they have faced the same issue?
    Thanks,
    Prashanth

    Got it.. was successfull too.
    How To Free Space From LOB Segments in the SOA Schema [ID 1380989.1]

Maybe you are looking for