Installation in VMware Oracle Identity Manager (9.1.0.0)
Hello everyone,
I'm quite unfamiliar with the Oracle products but I try to install the Identity Suite by following the available documation. Unfortunately there are some special points they missed but I already find them out in this forum. But now I'm despairing at one step in the OIM installation.
When I have to provide the OC4J connection settings I got everytime the error message that the OAS hasn't found in the specified path. For my understanding this path and the path to the jdk is provided in the step before and I could pass the step, so the path I provided must be wright.
Have anyone some hints how I can check the existing installation?
Here some further information from my installation:
OS: Windows 2003 SP2
OAS: Oracle Identity Management Infrastructure and Oracle Identity Federation (windows_x86_oim_oif_101401)
OC4J: self created, may be incomplete
If further informations are important to narrow down the problem please ask for.
Thanks in advance :)
Edited by: user10182133 on 26.08.2008 01:49
You need OAS 10.1.3.3 for OIM 9.1. Download SOA suite from http://download.oracle.com/otn/linux/ias/101310/soa_linux_x86_101310_disk1.cpio. Install it and apply the metalink note Note:553266.1 to upgrade to 10.1.3.3. Then create your own oc4j instance following OIM 9.1 installation manuals
Similar Messages
-
Can Oracle Identity Manager be installed on windows vista operating system
can Oracle Identity Manager be installed on windows vista operating system?? I get the following error while installing OIM 9.1.0 on Weblogic application server 10.3.
userLanguage = en
userCountry = US
java.io.FileNotFoundException: <Installation Directory>\xellerate\logs\setup_weblogi
c.log (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileReader.<init>(Unknown Source)
at com.thortech.xl.installer.event.InstallScript.checkSetupLogStatus(Ins
tallScript.java:2280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.invokeJavaMet
hod(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.executeAction
(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.run(Unknown S
ource)
at com.installshield.event.ThreadPool.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at com.thortech.xl.installer.event.InstallScript.onExecutingPostInstallM
essage(InstallScript.java:1919)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.invokeJavaMet
hod(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.executeAction
(Unknown Source)
at com.installshield.event.ActionSequenceEngine$ActionTask.run(Unknown S
ource)
at com.installshield.event.ThreadPool.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Edited by: user10691333 on 28 Aug, 2011 12:05 PMhttp://www.oracle.com/technetwork/middleware/ias/downloads/idm-certification-101401-083012.html
This is the cert matrix of OIM. Please check if you are using the right OS version. -
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. -
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
-
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 -
Integrating Oracle Identity Manager 9.1.0.2 with third reported
Hi Friends,
I have installed Oracle Identity Manager 9.1 integrated with various connectors, for that I need to customize some reports. My question is that reports can integrate Oracle Identity Manager 9.1.0.2, according to its parent company certification
Thanks for the supportHi JLK,
Glad to know that OIM 9.1.0.2 working for you. I had no success in installing and configuring 9.1.0 with SQL db 2000.
Please have look at my thread OIM 9.1.0 installation- Unable to access Admin console
If you could throw me pointera or provide assistance that would be great. Thx in advance. -
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 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)
>
ThanksHi 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 -
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 -
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 Manager looking for OracleAS 10.1.3.x
Hi,
I need to install the following products on 2 servers
Oracle Identity Management Suite (OID, DAS, SSO) as a OracleAS Active-Active Cluster.
Oracle Identity Manager in Cluster
Oracle Access Manager in Cluster
Oracle Virtual Directory in Cluster
with F5 load balancers
A bit complex configuration, but think i can achieve it. I completed the first task successfully but now I am facing a problem when i wanted to install the Oracle Identity Manager 9.1 on the existing OracleAS cluster. OIM is looking for a 10.1.3.x version of OracleAS where as the Oracle Identity Management suite is shipped with OracleAS 10.1.0.2 version. we went ahead with the installation process as there was no reference of application server version in the Oracle Identity Management Certification matrix and the OracleAS 10.1.3.4 certification document below mentioned that IM 10.1.4.0.1 is shipped with 10.1.3.x version.
http://www.oracle.com/technology/software/products/ias/files/oracle_soa_certification_101310.html
Can anyone guided me how should i go ahead with this.
Thanks & Regards
Ramesh GKCheck this OIM on OAS issues
SOA suite is using jdk 1.5.x , Identity Management Suite is using jdk 1.4.x. My advice is to use OC4J from SOA Suite. Open a SR to confirm this. Some OIM required patch for OC4J are only for 10.1.3.x and can't be applied to OC4J from Identity Management Suite, also you can't not use the same database for OIM and IDM repository if you are using multilanguage installation. -
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! -
Certified operating system for Oracle Identity Management 10g (10.1.4.0.1)
Hello,
I have a question regarding the certified operating system for Oracle Identity Management 10g (10.1.4.0.1)
http://www.oracle.com/technology/software/products/ias/files/idm_certification_101401.html
- for an Intel EM64T 64 bit machine
for the application server database it is stated that we need
Windows 2003 R1 (64 bit OS)
and the application server platform is certified with
Windows 2003 R1 with SP1 or higher (64 bit OS)
an installation of application server platform + database on a single Intel EM64T with Windows 2003 R1 with SP1 is not certified ? or with other words, if I add Sp1 to 2003 than the application server database is not on a certified platform ?
thanksHi Florin
My guess is that you are looking at the Oracle Identity Federation certification section in the link for the IDM certification.
The IDM certification for windows is in par. 2.3
For a 64 bits machine it specifies that you need Windows 2003 R2 to run it. And it is only certified for an Oracle database version 9.0.3.1. The footnote says:
Oracle Database includes Oracle 9i 9.2.0.8, Oracle 10g 10.1.0.5, Oracle 10g 10.2.0.1, and Oracle 10g 10.2.0.2
so I would go for the latest Oracle database version 10g 10.2.0.2. However the link with the Oracle database versions only notes an Oracle database version 10.2.0.1 available for Windows 64 bit. A quick lookup under the certifify tab in metalink shows that Oracle 10g R2 is certified for Windows 2003 10g R2 and that there is a 10.2.0.2 patch set that can be applied upon the Oracle database 10.2.0.1 base release. Don't forget to apply the latest CPU after this is done.
I have this from the documentation links you added in your question. I have not installed IDM 10.1.4 on Windows 64 bit myself.
Cheers -
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 -
Unable to log-in in Oracle Identity Manager Design Console
Hello,
I successfully installed OIM9.1.0.1 Identity Manager on Jboss4.2.3.GA App server and could login to OIM using http://llocalhost:8080/xlWebApp on my window Server 2003 system without any problem.
Then I installed the Design Console on my window XP system. However, after successfully installing the Design Console, I could not login using the xelsysadm user ID.
I checked to make sure that xlconfig.xml contains the right URL file under oim_designConsole directories.
The error I get from the Design Console login window is:
Internal Login
Oracle Identity Manager Design Console Could not log you in.
In the dos-command window, I got the error:
WARN,22 Apr 2009 16:31:52,160,[org.jboss.remoting.marshal.MarshalFactory],Could
not find marshaller for data type 'invocation'. Object in collection is null
WARN,22 Apr 2009 16:31:52,160,[org.jboss.remoting.marshal.MarshalFactory],Found
marshaller fully qualified class name within locator parameters, but was unable
to load class: org.jboss.invocation.unified.marshall.InvocationMarshaller
WARN,22 Apr 2009 16:31:52,160,[org.jboss.remoting.marshal.MarshalFactory],Could
not find marshaller for data type 'invocation'. Object in collection is null
java.lang.reflect.UndeclaredThrowableException
at $Proxy0.create(Unknown Source)
at com.thortech.xl.dataaccess.tcDataBaseClient$1.run(Unknown Source)
at Thor.API.Security.LoginHandler.jbossLoginSession.runAs(Unknown Source
at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown So
urce)
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.client.base.tcAppWindow.internalLogin(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.login(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.<init>(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.main(Unknown Source)
Caused by: org.jboss.remoting.marshal.InvalidMarshallingResource: Can not find a
valid marshaller for data type: invocation
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.jav
a:78)
at org.jboss.remoting.Client.invoke(Client.java:226)
at org.jboss.remoting.Client.invoke(Client.java:189)
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(Un
ifiedInvokerProxy.java:184)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerIntercep
tor.java:227)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.jav
a:167)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.
java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:5
5)
at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:169)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
I would really appreciate your help in this regards.
Thanks for helping me resolve this issue.
Regards,
DhirendravBackup the original file log4j-1.2.8.jar in oimclient/xlclient/ext
copy the log4j.jar from JBOSS folder - JBOSS/server/default
Paste the file in client folder with original log4j-1.2.8.jar
Rename log4j.jar file to log4j-1.2.8.jar
start ur JBOSS.. this shd work.
Maybe you are looking for
-
Error while creating database 10g
Hi,everyone I am installing oracle 10g db on Win2k sp4 platform ,while after i have completed software configuration i dicided to use dbca to create database,however i always got the "Ora-03114"error,end of communication channel,anyone have any idea?
-
Trying to install Windows 7 or 8 on old MBP
Hi all i've tried for 6 hrs today... no way out. I'm trying to revamp an old MBP Core Duo 2,1 Ghz, with Windows 7 (or 8.1, it's the same). Downloaded both ISO version of Windows installer. - Tried with USB stick -> Non-system disk error - Tried with
-
Firefox and PDF download problems -- hanging and failures
I am working in Windows XP and Firefox 12.0. We post our multi-page newsletter to our website in PDF, and then use a list to send a link to access it. When attempting to download using Firefox, the document will download all or part of the first page
-
On sites with forums how can I add type in bold and/or italics?
When posting on a websites forum how can I post words in bold or italics.
-
I have the JDK 6u1 installed and also I know that the documentation is available at http://java.sun.com/javase/reference/api.jsp But how do I download the docs on my PC,I mean what's the link??