My Oracle Support Banner

Error While Starting Weblogic Server; Unexpected current owner (Doc ID 1467136.1)

Last updated on JANUARY 02, 2024

Applies to:

Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.

Symptoms

During a maintenance window; ASAP, WebLogic and the Database were stopped and started again. After restart, ASAP application was coming up properly, however, WebLogic Server had issues.

The following error was seen while starting the ASAP WebLogic server

ERROR
-----------------------
JDBC store "<ENV_ID>.JMSJDBCStore" in this server is not the owner of database table "WLStore". Unexpected current owner is "[name={server=asap_server!host=xxx.xxx.xxx.xx!domain=asap_domain!store=dev1.JMSJDBCStore!table=WLStore}:random=-107624883271660245:timestamp=1339562772326]", expected current owner is "[name={server=AdminServer!host=127.0.0.1!domain=asap701domain!store=<ENV_ID>.JMSJDBCStore!table=WLStore}:random=1614724227071378890:timestamp=1339562449654]".>
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="<ADMIN_SERVER_NAME>" store="<ENV_ID>.JMSJDBCStore" table="WLStore")
  at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:1991)
  at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnership(JDBCStoreIO.java:2231)
  at weblogic.store.io.jdbc.JDBCStoreIO.updateTableOwnershipFromTimer(JDBCStoreIO.java:2178)
  at weblogic.store.io.jdbc.ReservedConnection.timerExpired(ReservedConnection.java:436)
  at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
  Truncated. see log file for complete stacktrace

 

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


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