Tuesday, March 19, 2013

MODIFYING THE STORAGE FOR LOB SEGMENTS


This morning i got an alarm for a lob segment which was reaching its max extents , i checked for the available free space in the tablespace where the lob segment was available  , the tablespace was filled by only 50%.
So the next solution was to modify/increase the MAX EXTENTS storage clause for the lob segment .

Here is how i did it .

1) CHECKING THE LOB SEGMENT DETAILS  : 


select tablespace_name,segment_type,max_extents,next_extent,extents from dba_segments where segment_name='SYS_LOB0000007907C00009$$';

2) IDENTIFYING THE TABLE NAME AND COLUMN NAME : 


select owner||'.'||table_name "TABLE", column_name, segment_name from all_lobs where segment_name='SYS_LOB0000007907C00009$$';

3) MODIFYING THE STORAGE CLAUSE:


alter table owner.tablename modify lob (COLUM_NAME) (storage (maxextents unlimited ) );

Monday, March 11, 2013

IMP-00037: Character set marker unknown

                   IMP-00037: Character set marker unknown


Today while i was doing a migration from a 9i database 11g R2 database i received the error  IMP-00037 : Character Set marker unknown and the import terminated .

Here is how i rectified the issue .

SOURCE BOX : AIX 

TARGET BOX : Linux 

This issue usually arises  when the dump is corrupted .

In my case the it wasn't the corruption. 

To reduce the file size the dump file is compressed by the Unix COMPRESS utility .

In the Linux server (target) i did not un-compress  it , so the import failed . 

To resolve this i used the GUNZIP Linux utility and the re-imported the data and it completed successfully .