My Oracle Support Banner

LMHB trace files got too large due to messages reported in LMHB every 2 seconds (Doc ID 2794022.1)

Last updated on AUGUST 08, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 19.6.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Below messages keep reporting in LMHB trace file in every 2 seconds.


** 2021-06-30T14:56:18.370213+08:00
kjgcr_SlaveReqBegin: failed to queue message to slave, status 4
kjgcr_SlaveEmancipatedCall: Failed to call slave
kjgcr_SlaveEmancipatedCall: Failed to free wmsg 0x273ac0f30

*** 2021-06-30T14:56:18.380165+08:00
kjgcr_ServiceGCR: Failed to Start GCR slave Watcher. Status 3 returned.

*** 2021-06-30T14:56:20.334208+08:00
kjgcr_SlaveReqBegin: failed to queue message to slave, status 4
kjgcr_SlaveEmancipatedCall: Failed to call slave
kjgcr_SlaveEmancipatedCall: Failed to free wmsg 0x273ac0ea0


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.