My Oracle Support Banner

MetaSolv Solution Application Server Startup Error - <BEA-280072> <JDBC store "pluginStore" failed to open table "pluginStore_{NUMBER VALUE}WLStore". [Store:280064]Expected empty table. (Doc ID 2006237.1)

Last updated on NOVEMBER 14, 2023

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.


After upgrading the production environment and restarting the server, the WebLogic Administration Console shows the nur.ear deployment in a Health status of "Warning" and the PlugInMBean reason being "MDB application nur is NOT connected to messaging system." The behavior is accompanied by JDBCStoreExceptions thrown in the ${MSLVHOME}/${SERVER_NAME}/appserver/logs/${SERVER_NAME}.mss.log during server startup.

NOTE: The MetaSolv Solution Application Server does start with its state changed to RUNNING and started in RUNNING mode.  The errors appear to have no impact to the MetaSolv Solution client.  Users can connect to the server and perform normal functions. 


WebLogic Administration Console Summary of Deployments Monitoring tab

WebLogic Administration Console Settings for nur Monitoring tab Health tab

Errors in the ${MSLVHOME}/${SERVER_NAME}/appserver/logs/${SERVER_NAME}.mss.log during startup

Steps to Reproduce





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

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