Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


GC_NAMEThere are two GC names. MEM_LOGICAL_AGER is a GC that deletes the old version of the index, and MEM_DELTHR is a GC that deletes the old version of the table record.
SCNOFTAILThe number of the oldest version most recent version among the old versions to be deleted , as identified by GC.
MINMEMSCNINTXSThe number of the oldest 'old version'.
GC_GAPEach GC means the amount of the old version to be deleted. The larger this value, the greater the amount of old version to be deleted. At this time, if scnoftail> minmemscnintxs, the deletion cannot proceed because of the active transaction. Conversely, if scnoftail <minmemscnintxs, the deletion is still in progress, but it can be judged that the old version to be deleted is increasing due to the completion of the update transaction.


The transaction that GC is waiting for refers to refer to a transaction that refers the transaction referring to the 'oldest version in Altibase'. If  If the GC does not work and waits indefinitely due to such a transaction, the memory usage can also increase infinitely, so it is one of the factors to check when the GC gap increases.

By executing the query below, the user can see the query executed in the session where the GC is waiting for the transaction. In  In addition, the index scan is good for distribution, but it can be useful usefully used when detecting a query that consumes queries that perform an index scan but consume instantaneous CPU because as it is no different from a full scan due to its poor distribution.

Please note that depending on the situation, it must be performed periodically and repeatedly because it may not be detected in one operation.