Re: unable to extend non-existent partition?

From: <Kenneth>
Date: Wed, 16 Mar 2005 21:56:35 GMT
Message-ID: <4238a8a6.1230421@news.inet.tele.dk>

On Wed, 16 Mar 2005 20:56:47 GMT, netcomradeNSPAM_at_bookexchange.net (NetComrade) wrote:

>I had the following error last night in alert log (this is 8.1.7.4)
>ORA-1692: unable to extend lobsegment APP2.LOB_FILE_DATA partition
>SYS_LOB_P494 by 25600 in tablespace
>APP2LOBDAT
>
>However, no such partition exist(s)
>
> 1* select table_owner from dba_tab_partitions where
>partition_name='SYS_LOB_P494'
>SQL> /
>
>no rows selected
>
>upon further investigation on the application end it was determined
>that it was really this partition that was 'corrupted' (couldn't be
>extended)
>SYS_P486
>
>The table is hash_partitioned on a number column, and LOBs are stored
>in a different tablespace from table.
>
>Is this a bug, or is oracle creating some partitions on the fly?
>

"On the fly" - no. But when a partitioned table is created with a LOB column, that lob-segment is partitioned along, equipartitioning it is called. But those lob-partitions are recorded in DBA_LOB_PARTITIONS (and not in DBA_TAB_PARTITIONS which is quite logical, after all) and that is where you will find your "missing" partition P494 :

Create table test
( c1 number(10),
  myblob BLOB
)
tablespace test
LOB (myblob) store as lobber
partition by HASH(c1)

(partition t1 tablespace test,
 partition t2 tablespace test,
 partition t3 tablespace test,

 partition t4 tablespace test
);

Tabel er oprettet.

SQL> SQL> select table_name ||' ' || column_name||' '||partition_name || ' ' || lob_name || ' '|| lob_partition_name from dba_lob_partitions;

TABLE_NAME||''||COLUMN_NAME||''||PARTITION_NAME||''||LOB_NAM

---

TEST MYBLOB T1 BLOBBER SYS_LOB_P25
TEST MYBLOB T2 BLOBBER SYS_LOB_P26
TEST MYBLOB T3 BLOBBER SYS_LOB_P27
TEST MYBLOB T4 BLOBBER SYS_LOB_P28

• Kenneth Koenraadt

Received on Wed Mar 16 2005 - 15:56:35 CST