Skip to end of metadata
Go to start of metadata

 

Overview

In altibase_boot.log, a large number of messages with the title "reset Mutex Statistics" may be recorded. This document provides a brief description of this message.

 

Situation

The following message may be repeatedly recorded in altibase_boot.log.

Message format

--- reset Mutex Statistics ---
TRY_COUNT: 2102048999
LOCK_COUNT: 2147483647
MISS_COUNT: 59144056
------------------------------

 

Cause

This message is output when the values of the try_count, lock_count, and miss_count columns of the v$mutex performance view table exceed the maximum value and the values are initialized.

V$MUTEX table structure

iSQL> desc v$mutex;
[ ATTRIBUTE ]
-----------------------------------------------------
NAME TYPE
-----------------------------------------------------
NAME VARCHAR(64)
TRY_COUNT INTEGER // If the integer maximum value (2147483647) is exceeded, it will be logged.
LOCK_COUNT INTEGER
MISS_COUNT INTEGER
SPIN_VALUE INTEGER
TOTAL_LOCK_TIME_US BIGINT
MAX_LOCK_TIME_US BIGINT

Column description

Icon
  • try_count = number of mutex lock attempts
  • lock_count = number of successful mutex locks
  • miss_count = number of waits because the mutex lock was not held

v$mutex records mutex information related to concurrency control in the database. If the values of the columns continue to increase and exceed the maximum value, a value overflow occurs. When the maximum value of integer type is reached, the corresponding value is recorded in altibase_boot.log, then initialize to 0.

 

Solution

When the maximum number of columns that can store mutex-related information is reached, the information is recorded in altibase_boot.log, and there is no particular problem or action required.

  • No labels