× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I have a table with 2 clob columns on the row.
both are 5242880 (5.2mb) in size...
A few other columns on the row - nothing notable in size.

I have a procedure that looks like this...
This saves one of the columns...
There is another procedure just like this that saves the other.
The code is the same in both.

// declared in copybook...
// dcl-s g_5000000 varchar(5000000) inz;
// dcl-s g_clob sqltype(clob:5242880) inz;


dcl-pi;
i_5000000 like(g_5000000) value;
end-pi;

g_clob_data = i_5000000;
g_clob_len = %len(%trimr(i_5000000));

exec sql
insert into myTable(myClob)
values (:g_clob);


When I test this to ensure spaces are not written and padded to the clob
column, I'm not seeing that my trims are preventing it.

clear table
I run one transaction that inserts 2 rows into the table
(so 2 rows = 4 clob columns populated)
divide table size by row count?

I'm seeing
table size = 17436672
row count = 2

which comes to around 8mb per row

Why is it storing so much???
My clob contents (actual data) is less than 2048 chars each.

tia

Jay

It is

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.