com.bea.wli.init.WLIDBCreateException

At least one WLI data base object (TABLE WLI_USER) was missing

Samebug tips0

There are no available Samebug tips.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web12

  • Stack trace

    • com.bea.wli.init.WLIDBCreateException: At least one WLI data base object (TABLE WLI_USER) was missing at com.bea.wli.init.WLIDBCreate$WLIDataSource.checkDBObjects(WLIDBCreate.java:875) at com.bea.wli.init.WLIDBCreate.init(WLIDBCreate.java:994) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.bea.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:324) at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:189) at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.java:229) at weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.java:160) at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.java:36) at weblogic.t3.srvr.StartupClassService$1.run(StartupClassService.java:121) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.t3.srvr.StartupClassService.invokeStartupClass(StartupClassService.java:116) at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:88) at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330) at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590) at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568) at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711) at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690) at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525) at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947) at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908) at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481) at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271) at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    No Bugmate found.