[Info-ingres] Error from auditdb

[Paul White]

I reckon it happens when there is a usermod or sysmod on a table with a long byte field right?

Marty writes

> The alteration to iirelation affects only the rellow_logkeyfield. Anyone 
know what that refers to?

Here is what I found looking up rellow_logkey and "end mini"

https://github.com/fosslc/Ingres/blob/master/src/dbutil/duf/duve/duvechk.sc 
<https://github.com/fosslc/Ingres/blob/master/src/dbutil/duf/duve/duvechk.sc>

https://communities.actian.com/s/article/Tracing-Use-of-Transaction-Log-File 
<https://communities.actian.com/s/article/Tracing-Use-of-Transaction-Log-File>

https://docs.actian.com/actianx/11.1/index.html#page/CommandRef/verifylob_Command--Analyze_Long_Data_Types.htm 
<https://docs.actian.com/actianx/11.1/index.html#page/CommandRef/verifylob_Command--Analyze_Long_Data_Types.htm>


verifylob Command--Analyze Long Data Types

The verifylob utility analyzes errors in long data types (blobs and clobs).  It scans the specified blob table and examines the blob coupons and etab tables for errors. Rows with errors are dumped with error indicators.

Verifylob detects four types of errors:

•(D) Duplicate keys

•(L) Non matching lengths

•(O) Orphaned rows

•(R) Invalid iirelation rellow_logkey, rellow_logkey pair

Next step, I plan to track the entries going to the transaction log to see if both BM (Begin Mini) and EM (End Mini) are being written.
My hunch is the BM is not being written to the journals because I am sure I reached the transaction limit error in the rollforwarddb.

Paul

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20210506/85536ddb/attachment.html>