cancel
Showing results for 
Search instead for 
Did you mean: 

Why no "LONG-LOG migration" occurred when I did table reorgan. ?

Former Member
0 Kudos

Hello, according to SAP Note 835552, having reorganization on a table with LONG columns, its LONG columns will be converted to LOB automatically.

However, yesterday, I used BRTools to reorganize a SAP table and got the following error :

BR0280I BRSPACE time stamp: 2011-08-22 15.26.45

BR1108I Checking tables for reorganization...

BR1110W Table SAPPRD.IWB0CONT1 has a LONG (RAW) column

BR1111I Reorganization of table SAPPRD.IWB0CONT1 will be skipped

BR0280I BRSPACE time stamp: 2011-08-22 15.26.45

BR1113E All tables have been skipped for reorganization

BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action

BR0280I BRSPACE time stamp: 2011-08-22 15.26.45

BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:

My configuration : Oracle 10g 10.2.0.4.0, BRTools 7.0.

Why BRTools didn't convert the LONG column to LOB automatically ?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ming,

No, reorganization does not convert LONG2LOB, automatically. You should perform this conversion first with the command, below;

brspace -f tbreorg -a long2lob -t "*" [-n <new_tsp> [-i <ind_tsp>]] [-p<par_degree>]

Then you can reorganize the table with "lob" field.

Check the note 646681 - Reorganizing tables with BRSPACE.

Please read carefully the statement in the note 835552 - Oracle Database 10g: LONG-LOB migration

During a reorganization of this type, LONG columns are automatically converted into LOB

columns. This special online reorganization is therefore called 'LONG-LOB migration'.

Best regards,

Orkun Gedik