Error on installing Oracle Identity Manager 9.1.0.1 in WebLogic Server 11g
Hello friends.
Can you help solve this case:
I installed Oracle 9.1.0.1 on Oracle Identity Manager Weblogic Server 11g, completing the installation with the following errors: attach the log so I can guide the solution.
link of the complete log
http://textbin.com/1c824
Part of the log**************************************
With the Partitioning, OLAP, Data Mining and Real Application Testing options".>
####<Sep 30, 2011 4:23:04 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417784538> <BEA-001517> <Connection Pool "xlXADS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Sep 30, 2011 4:23:18 PM PET> <Info> <Common> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798143> <BEA-000628> <Created "30" resources for pool "xlXADS", out of which "30" are available and "0" are unavailable.>
####<Sep 30, 2011 4:23:18 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798147> <BEA-001124> <Created Connection Pool named xlXADS.>
####<Sep 30, 2011 4:23:24 PM PET> <Error> <Store> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804279> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804321> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Error> <JMS> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804381> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804385> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
Thanks
Hi Kevin,
Make your suggestion, delete the domain and reinstall Oracle Identity Manager, the result was the same error, this happens when I start the xlStartServer.sh
Exception in thread "QuartzWorkerThread-2" java.lang.OutOfMemoryError: PermGen space
at java.lang.reflect.Proxy.defineClass0(Native Method)
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:504)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown Source)
at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Exception in thread "QuartzScheduler_NON_CLUSTERED_MisfireHandler" java.lang.OutOfMemoryError: PermGen space
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
java.lang.OutOfMemoryError: PermGen space
^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Thanks
Edited by: JLK on Oct 2, 2011 11:35 PM
Edited by: JLK on Oct 2, 2011 11:37 PM
Similar Messages
-
Error while installing oracle identity manager
Im using windows installer. I get error below when installing Oracle Identity Manager, any idea to solve this?
Following Error occured during schema creation connected
ERROR loading database script C:\oracle identity manager\OIM9.0.1.1\installServer\Xellerate/db/oracle/xell.sql!
Please contact your DBA! ORA-06550: line 1,
column 7: PLS-00905: object KOD.PIN_OBJ is invalid ORA-06550: line 1,
column 7: PL/SQL: Statement ignored [12/13/06 11:36 AM]
------------------------------------------------------------------------------Hi,
I got the same error:
Following Error occurred during schema creation connectedError loading database scriptD:\appl\OIM_902_RC\OIM_902_RC\installServer\Xellerate/db/oracle/xell.sqlPlease contact your DBA!ORA-06550: line 1, column 7: PLS-00905: object VIM_ADMIN.PIN_OBJ is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored [12/8/06 5:57 PM]
But I could fix it by dropping the schema and recreate it by only executing the prepare_xl_db.sh script as dba user on database server:
1. Copy the scripts prepare_xl_db.sh and xell_db_prepare.sql from the distribution CD/Directory to a directory on the machine hosting the database where there is (as the account user performing this task) write permission.
2. Run the prepare_xl_db.sh script by entering the following command:
./prepare_xl_db.sh
3. Provide information appropriate for the database and host machine when the script prompts for the following items:
• The location of the Oracle home (ORACLE_HOME)
• The name of the database (ORACLE_SID)
• The name of the Oracle Identity Manager database user to be created
• The password for the Oracle Identity Manager database user
• The name of the tablespace to be created for storing Oracle Identity Manager data
• The directory in which to store the data file for the Oracle Identity Manager tablespace
• The name of the data file ( no need to append the .dbf extension)
• The name of the temporary tablespace
4. Check the prepare_xell_db.lst log file located in the directory where the xell_db_prepare script was run from to see execution status and additional information. -
Error when installing Oracle Identity Manager 9.1.0.1
Hello friends,
I installed Oracle Identity Manager 9.1.0.2 Oracle Weblogic Server on a cluster, at the time of treaties authenticated in the web console of Oracle Identity Manager, I get the following message:
A system error was encountered.
View the full log here
http://pastebin.com/ucN1LHP4
BUILD FAILED
/opt/oim/xellerate/setup/setup.xml:447: The following error occurred while executing this line:
/opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:357)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
... 16 more
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.Deployer.run(Deployer.java:72)
at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
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:597)
at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
... 28 more
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:70)
... 35 more
As I can solve this problem, not to reinstall everything again
thanksNot sure if I understand your issue correctly. Your deployment failed during the installation and you have started the servers and trying to login?
When installing OIM in a clustered WLS domain, the docs specify various cluster configurations needed to be completed in the WLS Admin Console before running the OIM installer. These steps DO NOT include starting up of the first managed server. In fact, if you start up the managed server then you may very well run into deployment issues after the OIM application is built. Instead, when installing OIM, the installer detects that not all nodes are on-line and so will queue the deployment for later. Deployment then takes place in later steps when you are instructed to restart the app server and start managed nodes.
Thus was your managed server running when you were doing the installation? That has caused the issue. I would suggest to dump this domain (save the .xldatabasekey) if you don't wanna to dump the database part and start the installation again BUT don't start the managed server while doing the installation.
HTH,
BB -
Error when installing Oracle Identity Manager
Hello,
I'm having a problem when trying to install Oracle Identity Manager. I am trying it now for consecutive two days and it is always the same problem.
I read this thread:
Problem installing Oracle Identity Manager Server (but still have no clue what to do).
I'm installing it in a virtual lab environment (Windows Server 2008 on WMware).
It is a fresh install.
Installing scenario:_
*1.* Oracle Database 10g (10.2.0.3)
*2.* Toad DBA Suite for Oracle
*3.* Oracle Weblogic Server 11g R1
*4.* Oracle Identity Manager v9.1.0.1
*5.*
Then i create a new Oracle database instance for Oracle Identity Manager as described here:
http://download-east.oracle.com/docs/cd/B32386_01/generic.902/b32140/database.htm
*6.*
Then i prepare the DB for Oracle Identity Manager by running:
prepare_xl_db.bat XELL C:\Oracle\product\10.2.0\db_1 xelsysadm password123 xeltbs C:\Oracle\product\10.2.0\oradata xeltbs_01 TEMP password123
as described here (Preparing the Database on Windows):
http://download-east.oracle.com/docs/cd/B32386_01/generic.902/b32140/database.htm
*7.*
I get no errors after running the script has finished
*8.*
Then i run Oracle Identity Manager v9.1.0.1\OIM9101\installServer\setup_server.exe
*9.*
I go throw the steps and after installing the following error pop ups:
Following Error occurred during schema creation connected*
Error encountered while loading database script*
+...\Oracle Identity Manager v9.1.0.1\OIM9101\installServer\Xellerate/db/oracle/xell.sql+
Contact your DBAORA-06550: line 1, column 7: PLS-00905: object SYSTEM.PIN_OBJ is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored [10/7/09 12:18 PM]*
*10.*
Then i click next and this message pop ups:
Oracle Identity Manager Installer has found that SetDBKey.bat failed.*
*11.*
Then the setup ends/aborts
Does anybody have any idea what this error is about and how to work around?
I would really appreciated it. I am getting desperate, because i don't know what i am doing wrong. Thank you very much in advance!daniel/maki,
I'm trying to install Oracle Identity Manager. After giving the inputs for all screen, in the end it give me error "SetDBKey.bat error"
My Products:
1. Oracle Database 10g (10.2)
2. Oracle Application Server 10g R3
3. Oracle Identity Manager v9.1.0.1
My Installation Steps:
1. Installed Oracle Application server and upgraded to 10.3.3
2. Installed Oracle Database 10g and created database idmda2
3. Prepared Database for OIM
prepare_xl_db.bat idmda2 C:\oracle\product\10.2.0\db_1 sysadm sysadm orctbs C:\Oracle\product\10.2.0\oradata orcltbs_01 TEMP test23
I get no errors after running the script has finished
4. Deployed the application XIMDD on OAS
verified for prerequisities
5. Then i run Oracle Identity Manager v9.1.0.1\OIM9101\installServer\setup_server.exe
At the "Provide databse connectivity information" screen I have used the "sysadm" which i used at the time of preparing the database for oim
I am not using "system" account and still i am getting "Oracle Identity Manager Installer has found that SetDBKey.bat failed" error.
What is that i am missing here?
6. Then the setup ends/aborts
Thank you very much in advance! -
Error while installing Oracle identity Management Suite 11.1.1.2.0.
Hi,
I am installing Oracle Identity Federation in that i am getting following issue while configuring the tools in Oracle Identity Management Suite 11.1.1.2.0.
"Error Starting Managed Server wls_oif1.
Cause:
An internal error has occured : Managed Server didn't start in RUNNING mode"
Can anyone please help me to solve this issue.
-SriHi,
The pre-req is that it should be minimum 2GB RAM.
Also please try starting the server manually and stop the server and then Retry in the install wizard.
Thanks,
Mahendra. -
Installing Oracle Identity Manager (9.1.0.2) in Weblogic 10.3.3
Hi friends,
I have a question about Oracle Identity Manager 9.1.0.2:
I can install this version of OIM; about Oracle Weblogic Server (10.3.3) or the latest version (10.3.4).
Greetingshi JLK...
did u installed oim 9.1.0.2 in weblogic 10.3.3?what is your os and db version?
please let me know the procedures...and experience.....what are the problems u faced and how u rectified.....
me also planning to do the installation.....
Regards,
jdev -
Error when installing Oracle Identity Management 11.1.1.6
Hi all.
I'm new on OIM 11g world. When I install OIM that guided by Documentation. But I usually get an error on Extend JRF phase, the error message on log is:
Action:
See logs for more details.
Step Extend JRF failed
Error Extending Targets With JRF Template.
Cause:
WLST Error. Problem invoking WLST - Traceback (innermost last):
File "/tmp/tmp1340370226976.py", line 8, in ?
File "/home/oracle/Oracle/Middleware/Oracle_IDM1/../oracle_common/common/wlst/oracle-jrf-config.py", line 80, in applyJRF
File "/home/oracle/Oracle/Middleware/Oracle_IDM1/../oracle_common/common/wlst/oracle-jrf-config.py", line 142, in jrf_applyJRFOnline
WLSTException: JRF component or service with type "AppDeployment" and name "DMS Application#11.1.1.1.0" is not found.I've tried to delete Domain, re-run the runInstaller script, but it's not work.
Can you help me to understand this error?
Any suggestion is appreciated
Cuong PhamWLST is a scripting tool that create and manage OIMDomain. It llooks like it's trying to invoke some Jython files(eg:/home/oracle/Oracle/Middleware/Oracle_IDM1/../oracle_common/common/wlst/oracle-jrf-config.py). For some reason it's not finding AppDeployment configuration. THis, probably, will create or manage OIMDomain thru WebLogic. Are you running in GUI mode or silent mode? I will suggest you try to install in silent mode and see if this error will happen.
Question: Are you installing it and configuring this Managed Server in cluster?
I hope this helps,
Thiago Leoncio. -
Problem installing Oracle Identity Manager Server 9.1
Hello,
I try to install oracle identity Manager Server 9.1, but I'm having a problem.
Oracle identity manager 9.03 is already installed with jboss-4.0.3SP1 and j2sdk1.4.2_15
and oracle 10.2.0
So I follow these steps to clean out the db:
1. Drop tablespace: drop tablespace oimtbs including contents;
2. Drop user: drop user oimuser cascade;
and ran prepare_xl_db.bat as instructed. No errors in the log.
I ran the DiagonasticDashboard : the db setup was fine.
When I ran the installer "setup_server.exe", i haved this message :
Folowing Error occured during schema creation
Error encountered while loading database script
E:\OIM_Install\OIM9100\installServer\Xellerate/db/oracle/xell.sql
Please contact your DBA!
maximum key length (1478) exceeded
Does anybody have any idea what this error is about ?
Thanks.Index IDX_LKV_LKV_ENCODED on Table LKV (Column :- LKV_ENCODED - VARCHAR2(3000)) is failing on 2k block size. Though all the Indexes are working fine with the 4k block size.
But OIM Dev team recommends to create the 8k block size for the Index storage.
Because the blocksize affects the number of keys within each index node, it follows that the blocksize will have an effect on the structure of the index tree. All else being equal, large blocksizes will have more keys, resulting in a flatter index than the same index created in a 2k tablespace. A large blocksize will also reduce the number of consistent gets during index access, improving performance for scattered reads access.
HOW TO CREATE THE INDEXES IN LARGER BLOCKSIZE TABLESPACE
In the existing database:-
Create a tablespace with the 8k blocksize, For Example
First,
Set the system cache size for that particular db block size
sql> alter system set db_8k_cache_size=100M;
sql> CREATE TABLESPACE db_8k_tablespace DATAFILE 'C:/oracle/product/10.2.0/oradata/8k_file.dbf' SIZE 100M BLOCKSIZE 8192;
Then
Reorganize the Index using command:-
sql> Alter Index <Index_Name> Rebuild tablespace <Tablespace_Name>
Regards,
Neeraj Goel -
Error when upgrading Oracle Identity Manager 9.1.0.1 to OIM 9.1.0.2
Hello friends,
I upgraded Oracle Identity Manager 9.1.0.1 to Oracle Identity Manager 9.1.0.2,after the running the command to apply the patch:
OIM_HOME/xellerate/setup/patch_weblogic.cmd/sh WEBLOGIC_ADMIN_PASSWORD OIM_DB_USER_PASSWORD
I get the error:
[wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, Xellerate, on targets:
[wldeploy] [BasicOperation.execute():447] : AdminServer
[wldeploy] Task 2 initiated: [Deployer:149026]deploy application Xellerate on AdminServer.
[wldeploy] dumping Exception stack
[wldeploy] Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy]
[wldeploy]
[wldeploy] There are 2 nested errors:
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
[wldeploy] and
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
[wldeploy] Target Assignments:
[wldeploy] + Xellerate AdminServer
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy]
[wldeploy]
[wldeploy] There are 2 nested errors:
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
[wldeploy] and
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
[wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
[ant] Exiting C:\oracle\xellerate\setup\weblogic-setup.xml.
BUILD FAILED
C:\oracle\xellerate\Setup\setup.xml:448: The following error occurred while executing this line:
C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
--- Nested Exception ---
C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
--- Nested Exception ---
weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Total time: 4 minutes 35 seconds
How do I deal with this question?
Thanks.This error generally occur if your server is up and you are running patch for upgrade, and its very common error.
follow the troubleshoot step and get it done.
page 36
Troubleshooting the Application of the Patch on Oracle WebLogic Server
http://docs.oracle.com/cd/E14899_01/doc.9102/e14764.pdf -
Error while installing oracle enterprise manager 11g
Hello,
I am trying to install Oracle enterprise manager 11g & keep on
getting following error at install progress stage :
Error in setting permission of file/directory
/u01/labuser/Oracle/Middleware/oracle_common/oui/jlib/emocmul.jar
with 3 options Retry,Ignore & cancel.
Could anyone guide why i am getting this error & how to fix this problem ?
Thank-You
Rahul Shah.Hi;
For your issue i suggest close your thread here as changing thread status to answered and move it to Forum Home » Enterprise Manager which you can get more quick response
Regard
Helios -
Error While Installing Oracle 9.2.0.1.0 on Win 2003 Server
Hi,
I am getting following error while installing Oracle 9.2.0.1.0 on Windos Server 2003-
ORA-12546: TNS: Permission Denied.
Above error pops-up during database configuration phase. Oracle docs says- "Acquire necessary privileges and try again." But I am installing as administrator.
Thanks in advance,
-SandeepI can't tell you why this error is occurring but you are installing a desupported version of the Oracle database that may well not be supported on your version of the o/s.
Check the support matrix and metalink and see if you can install a supported product such as 10.2. -
Problem installing Oracle Identity Manager Server
Hello,
this is my first time trying to install this product, and I'm having a problem.
I'm installing it on my development box - Windows XP.
I set up Oracle 10g Release 2, created a database instance,
and ran prepare_xl_db.bat as instructed. so far so good.
When I ran the installer "setup_server.exe"
it displayed this error message:
Following Error occured during schema creation connected
ERROR loading database script
.......\OIM9.0.1.1\installServer\Xellerate/db/oracle/xell.sql!
Please contact your DBA!
ORA-00600: internal error code, arguments: [12259], [], [], [], [], [], [], [] [10/18/06 6:16 PM]
so, I aborted the installation.
I recreated the database instance, and tried manually running xell.sql using sqlplus to see if I can reproduce the error, but it worked fine.
I only get the above error whenever I use the windows installer.
Does anybody have any idea what this error is about and how to work around?
I would really appreciated it. Thanks.HI,
As a check of db setup before installing the server
1. Did you run the DiagonasticDashboard to check if the db setup was fine?
if not it is worth the try.
Just for you info, proper way to run the prepare_xl_db.bat is
in the command prompt change the directory to where the prepare_xl_db.bat resides.
$<dir where bat exists> prepare_xl_db.bat orcl E:\oracle\product\10.2.0\db_1 oimuser abcd1234 oimtbs E:\oracle\product\10.2.0\oradata\orcl oimtbs_01 TEMP abcd1234
· Where prepare_xl_db.bat <ORACLE_SID> <ORACLE_HOME> <XELL_USER> <XELL_USER_PWD> <TABLESPACE_NAME> <DATAFILE_DIRECTORY> <DATAFILE_NAME> <XELL_USER_TEMP_TABLESPACE> <SYS_USER_PASSWORD> are the switch options.
· This will create the OIMUSER database account, create the OIMTBS tablespace, grant privileges to the user, and specify other database settings.
Install the Diagonastics Dashboard
Assuming you are using JBoss
Strop JBoss server
1. copy <OIM dir>:\OIM_Installs\oracle_identity_manager\DiagnosticDashboard\XIMDD.war <JbossDir>:\jboss-4.0.2\server\default\deploy
2. Start JBoss
3. Wait for JBoss to finish starting completely.
Verify database from Diag Dashboard
4. Access Diag Dashboard from your favouriate browser http://<Host>:<port>/XIMDD
5. In the browser, click Diagnostic Dashboard
6. Select the Test Name: Oracle Database Prerequisite Check and enter your db values.
7. click Verify and analyze the response
Hope this helps!
-Bala -
Error while installing OFM 11g - Oracle Identity management suite 11g
Hi,
I am getting following error while installing Oracle Identity management suite 11g (Oracle Internet Directory & Oracle Virtual Directory) on Red Hat Linux 5.0.
"Error in invoking target 'client_sharedlib' of makefile '/apps/idm/Oracle/OracleHome/Oracle_Home/rdbms/lib/ins_rdbms.mk"
the same error is repeating for others also i.e. 'all', 'install" etc.
Can you advice me how to overcome this?
Regards
ChintaHi Chinta,
Pl. check for all gcc and glibc OS packages compatibility with your your OS. This will solve your problem.
Also check that you are not installing a 32 bit IM software on a 64 bit machine or viceversa.
regards,
Sailesh -
Oracle Identity Manager Configuration Error
Versions I have used for the Installation:
Software Version
Oracle Database 11.2.0
Repository Creation Utility 11.1.1.5.0
Web logic 10.3.6
SOA Suite 11.1.1.6.0
Fusion Middle ware Installer 11.1.1.5.0
JDK Oracle Web-logic JRockit JDK or Sun JDK 1.6.0_29
Error : Config Action Oracle Identity Manager Configuration failed
Exception waring occurs in web logic Server :
<Aug 14, 2012 11:57:53 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Ser
ver started in RUNNING mode>
<Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141239> <The no
n-dynamic attribute AuthenticationProviders on weblogic.management.security.Real
mMBeanImpl@581c390c([OIDM]/SecurityConfiguration[OIDM]/Realms[myrealm]) has been
changed. This may require redeploying or rebooting configured entities>
<Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141238> <A non-
dynamic change has been made which affects the server AdminServer. This server m
ust be rebooted in order to consume this change.>
<Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141239> <The no
n-dynamic attribute ControlFlag on weblogic.security.providers.authentication.De
faultAuthenticatorMBeanImpl@80d076be([OIDM]/SecurityConfiguration[OIDM]/Realms[m
yrealm]/AuthenticationProviders[DefaultAuthenticator]) has been changed. This ma
y require redeploying or rebooting configured entities>
<Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141238> <A non-
dynamic change has been made which affects the server AdminServer. This server m
ust be rebooted in order to consume this change.>
Please give me a solution to resolve the issueEach version has its won libraries and certain bug fixes. It's always good to see certification matrix first for any software and proceed with installation as per certified components. Also, vendor support your project only if you are using their certified versions. :)
regards,
GP -
Oracle Identity Managment 9.1 jboss statup issue
I have installed oracle identity manager 9.1 using jboss. after complete installation, when I start my jboss, I am getting following message -
21:05:56,350 INFO [WEBSTARTUP] Scheduling Initiate Attestation
Processestask, class is com.thortech.xl.schedule.tasks.tcTskAttestation
21:05:56,372 INFO [WEBSTARTUP] Going to start Scheduler Cluster service
21:05:56,390 INFO [WEBSTARTUP] Going to start Scheduler Engine
21:05:56,397 INFO [QuartzScheduler] Scheduler
DefaultQuartzScheduler_$_NON_CLUSTERED started.
21:05:56,403 INFO [WEBSTARTUP] Scheduler started
21:05:56,446 INFO [TomcatDeployer] deploy, ctxPath=/xlWebApp,
warUrl=.../tmp/deploy/tmp6119252628294703623XellerateFull.ear-contents/xlWeb
App-exp.war/
and at this stage, it is getting stuck for too much time and I am getting message -
22:48:07,563 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space
I have assigned max heap size in my jboss run.bat => set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx1536m
Now I can not extend heap memory beyond this.. jboss give error while statup if I give more than this heap size.
can any body help me on this. I am not getting root cause for this.You also need to add the following JVM option: -XX:MaxPermSize=256m
Maybe you are looking for
-
Lightroom 5.5 is not cataloging all images in some folders
Version: Lightroom 5.5 CC 2014 System: Windows Pro 8.1 R2 64 bit When I last updated my catalog in Lightroom, I discovered that in at least two folders, Lightroom did not catalog all of the images in the actual folder on my computer. Because of the n
-
I was in the middle of the iOS 8 update and tried to turn my phone off (yes, I realize this was dumb) But what happened was it tried to reset. Now, my iphone 4s has the connect to itunes screen. I have tried to reset, recover, etc but I keep getting
-
Hopefully people use this as a sign to be more cautious of their online activities. Many people are under the assumption that their secret or personal information is safe because it is behind a password.
-
What is it? Exit Code: 34 Please see specific errors below for troubleshooting.
Exit Code: 34 Please see specific errors below for troubleshooting. For example, ERROR: -------------------------------------- Summary -------------------------------------- - 1 fatal error(s), 0 error(s) FATAL: Payload 'Camera Profiles Installer 8.0
-
Turned voice over on, used 3 fingers to turn it off
How do I get voice over to turn off, get screen unlocked that is now black? Hate this new software!