470,620 Members | 1,677 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,620 developers. It's quick & easy.

DB2 UDB LUW DB2 LOG API : Table descriptor record (how to compose the )

The documentation (Administrative API Reference, 8.2, PDF format) says
page 520:

"The rest of the record is dependent upon the record type and the table
descriptor record defined for the table."

How can the record descriptor by composed for existing tables (not in
the log file as new entry) or is mentioned somewhere?

select colname, colno, rtrim(typename), length, scale,
coalesce(generated,' '),nulls, ... from syscat.columns where
TABSCHEMA= ? and TABNAME= ? order by colno

and first 1. fixed length columns from left to right
then 2. variable length columns from left to right
?
(as the insert log record has first fixed length columns, then variable
length columns).
Bernard Dhooghe

Oct 17 '06 #1
1 1997

Bernard Dhooghe wrote:
The documentation (Administrative API Reference, 8.2, PDF format) says
page 520:

"The rest of the record is dependent upon the record type and the table
descriptor record defined for the table."

How can the record descriptor by composed for existing tables (not in
the log file as new entry) or is mentioned somewhere?

select colname, colno, rtrim(typename), length, scale,
coalesce(generated,' '),nulls, ... from syscat.columns where
TABSCHEMA= ? and TABNAME= ? order by colno

and first 1. fixed length columns from left to right
then 2. variable length columns from left to right
?
(as the insert log record has first fixed length columns, then variable
length columns).
Bernard Dhooghe
It is

1. fixed block contains the data for fixed length columns and for the
columns with variable length, instead of the content there is the fixed
length data of 4 bytes (not null column) or 5 bytes (for null columns)
described as follows in the manual "All variable field types have a
4-byte fixed data portion in the fixed length section (plus a null
flag, if the column is nullable). The first 2 bytes (short) represent
the offset from the beginning of the fixed length section, where the
variable data is located. The next 2 bytes (short) specify the length
of the variable data referenced by the offset value." (page 523).
2. variable length block with the content of the variable length
columns

Bernard Dhooghe

Oct 20 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

15 posts views Thread by Paulo da Silva | last post: by
1 post views Thread by mksql | last post: by
3 posts views Thread by gipsy boy | last post: by
4 posts views Thread by lynology | last post: by
11 posts views Thread by Sala | last post: by
232 posts views Thread by robert maas, see http://tinyurl.com/uh3t | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.