on 07-31-2015 1:00 AM
Hi All,
We have a table with 'LONG VARCHAR FOR BIT DATA' where we exported and recreated the table using R3load then the same field got changed to this attribute 'BLOB(32768) INLINE LENGTH 4096 LOGGED COMPACT'.
We had seen a drastic reduction in the space occupied, it went down by almost 10 times post change to BLOB.
Can someone please throw some light on this behaviour please.
Below is the db2 version : "DB2 v10.5.0.3"
Why such a drastic reduction in space and also is this how it should behave?
Hi,
IBM does not recommend the use of LONG VARCHAR data type anymore, although it is still supported. BLOB is the one to be used instead.
Hope some other can give you more information about the space question.
Regards,
Hugo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
see the document
...
"To maximize the benefit of the LOB inlining feature, with the new DBSL patch all LONG data types will be replaced with LOB data types for new tables. "
...
The paper also contains some space measurements. In your case, the old table was probably also fragemented.
Regards,
Johannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.