My Oracle Support Banner

EM 13c: BIP in a Multi OMS Setup is Shown as Failed in Weblogic Admin Console (Doc ID 2596413.1)

Last updated on NOVEMBER 14, 2019

Applies to:

Enterprise Manager Base Platform - Version 13.2.0.0.0 and later
Information in this document applies to any platform.

Symptoms

EM 13c:

In a multi OMS environment, BIP server status is showing as Failed in Admin Console intermittently.

$emctl status oms during that time shows BIP as UP.

Restarting the OMS fixes the problem. But after sometime, BIP status shows as failed in weblogic admin console.

During the time of this problem,

$../gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/BIP.out file reports following errors:

<Sep 17, 2019 5:50:10 AM PDT> <Error> <JTA> <BEA-110013> <An error occurred while writing transaction log: weblogic.store.PersistentStoreFatalException: [Store:280032]The store suffered a fatal error and it must be reopened..
weblogic.store.PersistentStoreFatalException: [Store:280032]The store suffered a fatal error and it must be reopened.
at weblogic.store.io.file.BaseStoreIO.checkOpened(BaseStoreIO.java:1100)
at weblogic.store.io.file.BaseStoreIO.create(BaseStoreIO.java:286)

<Sep 17, 2019 5:50:10 AM PDT> <Warning> <Store> <BEA-280062> <The store "_WLS_BIP" could not be shut down: weblogic.store.PersistentStoreException: java.io.IOException: close error, Error 0, errno=0
weblogic.store.PersistentStoreException: java.io.IOException: close error, Error 0, errno=0
at weblogic.store.io.file.Heap.close(Heap.java:1840)

Changes

 

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
References


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