My Oracle Support Banner

BAM 12c servers going to failed status after upgrading BAM (Doc ID 2100009.1)

Last updated on APRIL 16, 2018

Applies to:

Oracle BAM (Business Activity Monitoring) - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms


BAM servers are going to WARNING status and in the BAM log files the following STUCK threads are observed:

STUCK THREAD
-----------------------

", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
oracle.beam.cqservice.ha.HACQLProcessor.waitQueryStatusRestore(HACQLProcessor.java:1034)
oracle.beam.cqservice.ha.HACQLProcessor.restoreQuery(HACQLProcessor.java:1209)
oracle.beam.cqservice.ha.HACQLProcessor.onRestore(HACQLProcessor.java:677)
oracle.beam.cqservice.ha.HAEventProcessor$RestoreWork.run(HAEventProcessor.java:351)
weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
weblogic.work.ExecuteThread.run(ExecuteThread.java:263)



Changes

Environment was upgraded from 12.1.3.0.1 to 12.1.3.0.4  or 12.2.1.X

Also a large data object was found.

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
Changes
Cause
Solution


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