Product Documentation

Database Administrator's Guide

Previous Topic

Next Topic

DIAGNOSTICS CHECK_KEY_MARKS

DIAGNOSTICS CHECK_KEY_MARKS

In V11.8 and later, a new diagnostic option, DIAGNOSTICS CHECK_KEY_MARKS, causes c-tree Server to check for unexpected transaction marks in a leaf node when it is about to be written to disk. If any unexpected marks are found, a message is written to CTSTATUS.FCS and a process stack trace is created. Sample message:

- User# 00032 CHECK_KEY_MARKS: index file lstrip.idx member 18 node 0x160000 mark 01 tranno 1 lowexc 0 key 1

The message shows the index file name, member number, node offset, transaction mark, transaction number, and the element number within the node of the key that has the unexpected mark.

The server now logs a process stack trace if it detects a call to set a transaction mark for a pending add with a transaction number of 1.

The diagnostic option can be changed at runtime.

TOCIndex