Error in installing Oracle Software while adding node in RAC

Hi All
Oracle Version: 11.1.0.6.0
Linux
In the RAC environment, I am in the process of adding a node to the existing rac environment.
I have succssfully installed cluster software in the new node. all gsd, ons and vip services are running perfectly for new node in the existing and new nodes.
Next step, I started installing oracle software by executing the script $ORACLE_HOME/oui/bin/addNode.sh.
Here after specifying the the new node information (public host, private host and vip details) and when I pressed next,
OUI is giving following error - "Error occured while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured".
I ran olsnodes -n, it is giving proper node number.
Can somebody help me in identifying the problem and solution.
Thanks

I am hitting the same issue, my problem was when I added the new node initially it fails because of the hint8-priv1. I followed the link below to remove and cleanup the last install. olsnode show only my existing nodes NOT including the new node.
http://download-west.oracle.com/docs/cd/B12037_01/rac.101/b10765/adddel.htm
then I ran
./addNode.sh -silent CLUSTER_NEW_NODES={hint-8} CLUSTER_NEW_PRIVATE_NODE_NAMES={hint8-priv1} CLUSTER_NEW_VIRTUAL_HOSTNAMES={hint8-vip}
I am getting this when use command line:
Error ocurred while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured.
SEVERE:Error ocurred while retrieving node numbers of the existing nodes. Please check if clusterware home is properly configured.
also run addNode.sh via GUI, the new node name still listed and can't continue.
BTW, adding new node should support online, shutdown is not required

Similar Messages

  • Error While Adding Node on RAC

    Hi Friends,
    Environment:SUN Solris 10
    Cluster Version:10.2.0.3
    database Version:10.2.0.3.0
    Due to H/W failure one of our RAC node(prod1) got formatted.
    We have deleted the node(prod1) from RAC successfully.
    Following the below link..
    http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/adddelunix.htm#BEIBBADI
    But When i am again trying to add the node i am facing the below issue..
    while doing Adding an Oracle Clusterware Home to a New Node Using OUI in Interactive Mode
    1.Ensure that you have successfully installed Oracle Clusterware on at least one node in your cluster environment. To use these procedures as shown, your $CRS_HOME environment variable must identify your successfully installed Oracle Clusterware home.
    2.Go to CRS_home/oui/bin and run the addNode.sh script.
    3.The Oracle Universal Installer (OUI) displays the Node Selection Page on which you should select the node or nodes that you want to add and click Next.
    4.Verify the entries that OUI displays on the Summary Page and click Next.
    5.Run the rootaddNode.sh script from the CRS_home/install/ directory on the node from which you are running OUI.
    6.Run the orainstRoot.sh script on the new node if OUI prompts you to do so.when i am doing the step 6 on the new node, i am facing the below error..
    bash-3.00# /software/oracle/oraInventory/orainstRoot.sh
    Changing permissions of /software/oracle/oraInventory to 770.
    Changing groupname of /software/oracle/oraInventory to oinstall.
    The execution of the script is complete
    bash-3.00# /software/oracle/product/crs/root.sh
    WARNING: directory '/software/oracle/product' is not owned by root
    WARNING: directory '/software/oracle' is not owned by root
    "/opt/oracle/voting/voting1" does not exist. Create it before proceeding.
    Make sure that this file is shared across cluster nodes.Please share your views and suggest what to do in this situation...
    Regards
    Umesh
    Edited by: Umesh Gupta on Aug 22, 2011 12:43 PM

    Helios- Gunes EROL wrote:
    Hi;
    Please check your voting disk
    See:
    http://www.oracledba.org/11g/rac/11g_RAC_Admin_Utilities.html#Viewing_Votedisk_Information:
    Regard
    HeliosHere are the results..
    $./crsctl query css votedisk
    0.     0    /opt/oracle/voting/voting1
    located 1 votedisk(s).
    $ocrcheck
    Status of Oracle Cluster Registry is as follows :
             Version                  :          2
             Total space (kbytes)     :     301852
             Used space (kbytes)      :       3016
             Available space (kbytes) :     298836
             ID                       :   66623280
             Device/File Name         : /opt/oracle/ocr/ocr1
                                        Device/File integrity check succeeded
                                        Device/File not configured
             Cluster registry integrity check succeededbut from this i could not identify which raw disk is used as Voting and OCR
    Regards
    Umesh

  • Errors when installing Oracle Client 10.2.0.2.0 on zLinux (Red Hat)

    I am receiving errors when installing Oracle Client 10.2.0.2.0 (Administrator) on zLinux. During the install I receive two notifications for File Not Found when the installer tries to create the link for lib32/libclntsh.so.10.1. I hit ignore on the pop-ups and the install completes. The Oracle Net Configuration Assistant then fails to launch with the following error:
    Output generated from configuration assistant "Oracle Net Configuration Assistant":
    Command = /opt/oracle/product/10.2.0/db_1/bin/netca /orahome /opt/oracle/product/10.2.0/db_1 /orahnam Oracle_home /instype custom /inscomp client,oraclenet,ano /insprtcl tcp /cfg local /authadp NO_VALUE /nodeinfo NO_VALUE /responseFile /opt/oracle/product/10.2.0/db_1/network/install/netca_clt.rsp
    UnsatisfiedLinkError exception loading native library: njni10
    Configuration assistant "Oracle Net Configuration Assistant" failed
    The "/opt/oracle/product/10.2.0/db_1/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.
    I have seen multiple threads relating to very similar errors, but none of the fixes that were suggested have worked. I have double checked the required Red Hat packages and made sure they were all installed on the server. All of the prerequisite checks for the installer are successful. Any assistance would be of most helpful!

    Worked with my Linux system admin and figured out that we were indeed missing some packages. There are 390 and 390x rpm's for Red Hat on System Z, i.e. 64 bit and 32 bit versions. Since we are running a 64 bit os some of those 32 bit packages did not get installed. Since our roles are split up, I am kind of blind as to the OS setup so I was not able to catch the problem. It is truly puzzling as to why Oracle would need 32 bit packages even though Oracle client is 64 bit. Regardless, after adding the 32 bit rpm's the installer was able to perform the linking operation that was failing, and the network configuration script ran successfully.

  • Error after installing Oracle Enterprise Linux (Release 5) on Dell T 110

    eth0      Link encap:Ethernet  HWaddr 00:15:17:F7:81:53 
              inet addr:192.1.1.11  Bcast:192.1.1.255  Mask:255.255.255.0
              inet6 addr: fe80::215:17ff:fef7:8153/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100
              RX bytes:0 (0.0 b)  TX bytes:15868 (15.4 KiB)
              Memory:dfcc0000-dfce0000
    eth1      Link encap:Ethernet  HWaddr B8:AC:6F:92:C2:0C 
              inet addr:192.1.1.9  Bcast:192.1.1.255  Mask:255.255.255.0
              inet6 addr: fe80::baac:6fff:fe92:c20c/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:263812 errors:0 dropped:0 overruns:0 frame:0
              TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:18959341 (18.0 MiB)  TX bytes:9476 (9.2 KiB)
              Interrupt:169 Memory:dfbf0000-dfc00000
    lo        Link encap:Local Loopback 
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:1393 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1393 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:4035655 (3.8 MiB)  TX bytes:4035655 (3.8 MiB)Any help please. I am a first time Linux user.
    Thanks
    A/A

    This looks like a follow up of Re: Error after installing Oracle Enterprise Linux (Release 5) on Dell T 110
    Can you give more details what you are trying to do or trying to accomplish. Where are you trying to ping to?
    It could be that you have not defined your gateway or DNS server for name to IP mapping. What is the output of
    # netstat -rn
    # cat /etc/resolv.conf

  • Who will install ORACLE software on linux production environment?

    Hi Friends,
    there is a doubt for me on ORACLE software installation. i.e. who will install ORACLE software on linux production environment. either system admin or else ORACLE DBA.
    If DBA means, whether system admin will share the oracle root password.,
    If SYS admin means how DBA parameters during installation.
    Regards
    Sakthivel G

    NEW2DBA wrote:
    Hi Friends,
    there is a doubt for me on ORACLE software installation. i.e. who will install ORACLE software on linux production environment. either system admin or else ORACLE DBA.
    If DBA means, whether system admin will share the oracle root password.,
    If SYS admin means how DBA parameters during installation.I have a doubt - about needing any parameters during a software-only install.
    Since every version of Oracle available now (except 11.2) needs patches, a new installation should not create the database right away. Therefore, a software-only install is the most reasonable thing to do. And if no DB configuration parameters are required at s/w-only time, then it makes somewhat sense for the SysAdmin to do the install.
    Therefore, it makes sense to me that the two groups (DBA and SA) might want to work ... together. (ROFLMAO)

  • Oracle Universal Installer Error when Installing Oracle database Software

    Hi Guru's
    we are installing SAP ECC 6.0 on Linux:Oracle, we start the installation fine until we reach the oracle software installation step. we login as ora<sid> then set the DISPLAY variable setenv DISPLAY 192.168.1.155:0.0
    The csh shell is the one that is being used we find this after executing echo $SHELL, when we execute echo $DISPLAY it returns 192.168.1.155:0.0.
    When we run ./RUNINSTALLER it then returns Failed the DISPLAY variable is not set correctly, to check if it working execute xclock, we run that and it displays the clock.
    what could be the problem with this installation.

    I am trying to install Oracle 10g on Suse Linux and I am getting the
    following error...
           Checking monitor: must be configured to display atleast 256
    colors Failed <<<<  >>>> could not execute auto check for display colors
    using command /usr/X11R6/bin/xdpyinfo check if DISPLAY variable is set.
    I checked the DISPLAY variable and it is set right.

  • 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
    thanks

    Not 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 in Installing Oracle 9iAS 1.0.2.2.1 on win 2000

    While installing Ora 9iAS 1.0.2.2.1 on win2K, It gives me following error and stops..
    Not all the dependencies for the component Oracle Enterprise Manager Common Files 2.2.0.0.0 are found. Missing Component oracle.swd.jre 1.1.8.10.0.
    This product is installed on the machine and the path variable also contains the entry for it.
    Any ideas ????

    Hi,
    Are you installing from Software CD?
    If you have downloaded it from the OTN, check the size of Software. This error is thrown when the downloaded software is not proper or corrupted.
    Try downloading the compatiable OS specific software again. Check the size of the software and install it again.
    -Priyanka

  • Tnsnames.ora error when installing oracle 9i developer suite

    Hi,
    Can anyone answer this question: I recently installed
    oracle 9i and i'm getting a tnsnames.ora error when connecting to the database. Can anyone tell me what parameters to modify in the tnsnames.ora and sqlnet.ora files and what values to put in these parameters. Also,
    i'm trying to create a net_service_name in oracle net manager(in configuration/management tools) and I can't figure out the service name for versions of Oracle 8i or later. Can someone tell me what this is because the program is asking for a service name. I need this info
    for connecting to the database by username/password@net_service_name. Please respond soon.
    Thank you.
    T. Patel

    Go Net8Assistant. Follow the tree Net8Config -&gt;Local -&gt; Service Naming. In this node you will find all instances set (SIDs) and by clicking on them you will see in the right hand part of the screen if they were set or not in tnsnames.ora.
    Another way: Usually the database service name is OracleServiceSID. Go Control Panel -&gt; Administrative Tools -&gt; Services and check out the Oracle Service name. Take the SID from there to tnsnames.ora.
    You should have write down the name you was asked for while you were installing Oracle (or the default name that the installer put for you).
    Hope this will help you
    Alexandra

  • Root.sh failed throws error when installing Oracle Grid Infrastructure 11.2

    Hi,
    root.sh failed with the following error when installing / configuring the oracle grid infrastructure version 11.2.0.1 for standalone on RHEL 6
    Now product-specific root actions will be performed.
    2011-10-10 11:46:55: Checking for super user privileges
    2011-10-10 11:46:55: User has super user privileges
    2011-10-10 11:46:55: Parsing the host name
    Using configuration parameter file: /apps/opt/oracle_infra/crs/install/crsconfig_params
    Creating trace directory
    LOCAL ADD MODE
    Creating OCR keys for user 'oracle', privgrp 'oinstall'..
    Operation successful.
    CRS-4664: Node vmhost1 successfully pinned.
    Adding daemon to inittab
    CRS-4124: Oracle High Availability Services startup failed.
    CRS-4000: Command Start failed, or completed with errors.
    ohasd failed to start: Inappropriate ioctl for device
    ohasd failed to start: Inappropriate ioctl for device at /apps/opt/oracle_infra/crs/install/roothas.pl line 296.
    I followed the steps / solution provided in the ID 1069182.1. But no use.
    Are there any workaround?
    Thanks
    -KarthicK
    Edited by: user11984375 on Oct 10, 2011 7:06 AM

    Check the logfiles under $GRID_HOME/log/<node_name>/cssd/
    I had seen the same problem and the following resolved the problem for me.
    [root@rac1 ~]# rm -f /usr/tmp/.oracle/* /tmp/.oracle/* /var/tmp/.oracle/*
    [root@rac1 ~]# > $ORA_CRS_HOME/log/<node_name>/cssd/<node_name>.pid
    HTH,
    Raj Mareddi
    http://www.freeoraclehelp.com

  • Error in Installing Oracle 10g Express Edition Universal on WIndows2003

    While Installing Oracle 10g XE Universal On WIndows 2003 Server Standard Edition(Which is a standalone Machine). I got an following Error:
    Error No: 0x80040707
    Error Description: DLL Function Call Crashed: GetHostnameDll.getHostname.
    Plz find some solution for the above problem.

    Hi
    Here's the resolution that can work for you:
    Disable the "Print Spooler" service before running the installer.
    1.Open Control Panel: Start --> Settings --> Control Panel
    2.Double-click "Services"
    3.On the list of NT Services, right-click "Print Spooler"
    4.Select "Stop"
    5.Select "Properties"
    6.Under Startup Type, select "manual" or "disabled"
    7.Reboot your NT Server
    8.After rebooting, verify that the Print Spooler is still "stopped".
    9.Delete Program Files\Common Files\Installshield\Engine folder
    10.Re-run the installer.
    11.After installation, re-set the Print Spooler service to Startup type "Automatic" and start the service.
    Also, have a look at the installshield page: http://consumer.installshield.com/kb.asp?id=Q108167
    -Priya

  • 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

  • Error in Installing Oracle 9i on redhat 7.2 -- jre was not found again!

    I'm installing Oracle 9i on redhat 7.2. The machine I'm installing it on is an AMD k-6 500 mhz pc. While attempting to install Oracle 9i
    I think I'm successful (well, maybe not) except for the fact that the oui reports the following error:
    "configuration tool oracle net configuration assistant failed. jre was not found
    in /home/ora1/jre/1.1.8/bin/../bin/i586/green_threads/jre"
    Now, I know about the i686/i586 scenario, and I have a 586 pc. I got the more common error message:
    "jre was not found in /tmp/OraInstall/jre/bin/i586/green_threads" (also for ../lib/..)
    and I set up symbolic links for that and re-ran the runInstaller. Everything I've tried so far has been unsuccessfull.
    Can anyone help? Thanks.
    BTW: What does it mean when the path has double dots (i.e. bin/../bin) in it?. That confuses me a bit.

    I had a similar problem when running jre in linux.
    Any help really appreciated.
    [root@Linux bin]# jre
    jre was not found in /usr/local/bin/../bin/i686/green_threads/jre
    [root@Linux bin]#
    [root@Linux bin]# uname -a
    Linux Linux 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 i686 i386 GNU/Linux[root@Linux bin]#

  • How to install oracle software on AIX server

    Hi
    I have one remote AIX 5.3 server .
    On this I want to install oracle 9.2 software.
    I connect by putty to get this server but How i can get graphical interface of oracle installation?
    when i run run installer, that give error it can not recognize x window .
    Please guide me.
    Thanks.

    What I normally do is:
    - start via the putty session (loged in with the software install user) vncserver
    - give a password for the user.
    - on your desktop client you startup vnc viewer (can be downloaded free from internet)
    - use the machine ip/name and the earlyer given password
    - you have a graphical environment on AIX
    Regards, Gerwin

  • Solaris 8 in ultra 2 got panic and auto reboot when install Oracle software

    Dear all,
    I installed Solaris 8 by selecting 'Entire Solaris Software Group' and select 32 bit support only in an old ultra II machine. Then I tried to install Oracle 8.1.7 in the same machine but machine always got panic and started auto reboot when Oracle installed about 17% or 20% or even 70% (I tried install the minimum of Oracle).
    What is the problem? Anyone can help?
    Thanks in advance,
    Vicky

    I think you need to check the parameters like SHMMAX etc in /etc/system file as recommanded by oracle if not already added you need to add them .Oracle manuals have a list of these parameters and don't forget to reboot and boot with boot -r after adding these parameters.
    Make sure you have sufficient memory or some patch recommanded by Oracle .
    Hemant
    http://www.adminschoice.com

Maybe you are looking for