Cluster jndi error

          Hi:
          we have deploye samples cluster ejb teller and account to a cluster environment..one
          admin server and one manager server in the same machine(use multi-ip)..another
          manager server on another machine..two manager server join a cluster,we use weblogic6.0sp2,when
          we want see manager server's jndi tree .got the error messages..and I read from
          bea's online document..in a cluster environment ..any join cluster's manager server
          have the same jndi tree..but if admin server not in the cluster ,it's jndi tree
          will the same with the other manager servers?and how to deploye ejb to the cluster
          correclly?should i set call-by-reference to false in weblogic-ejb.xml?thanks your
          comment...
          javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException:
          failed to unmarshal interfa
          ce javax.naming.NamingEnumeration; nested exception is:
          java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          This error could
          indicate that a component was deployed on a cluster member but not other members
          of that cluster. Make sure th
          at any component deployed on a server that is part of a cluster is also deployed
          on all other members of that cl
          uster
          java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          This error could indicat
          e that a component was deployed on a cluster member but not other members of that
          cluster. Make sure that any c
          omponent deployed on a server that is part of a cluster is also deployed on all
          other members of that cluster
          at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:143)
          at weblogic.rjvm.MsgAbbrevInputStream.resolveClassOverride(MsgAbbrevInputStream.java:84)
          at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectI
          nputStream.java:276)
          at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1142)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:374)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:106)
          at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:122)
          at weblogic.jndi.internal.BindingEnumeration.readExternal(BindingEnumeration.java:55)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:103)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:114)
          at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:47)
          at weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:136)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:251)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
          at weblogic.jndi.internal.ServerNamingNode_WLStub.listBindings(ServerNamingNode_WLStub.java:374)
          at weblogic.jndi.internal.WLContextImpl.listBindings(WLContextImpl.java:293)
          at javax.naming.InitialContext.listBindings(InitialContext.java:399)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:74)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)

          Just the same happens to me. I think the problem is that the management server
          can not download the ejb stub from the other server. If you deploy the ejb also
          in the management server you solve the problem, but that's not the way it should
          work... I think this is a bug of weblogic.
          I've also found another nice one like that. I have 2 machines in cluster, and
          a third one out of the cluster, all of them running weblogic. A class running
          in this last weblogic makes a call to a bean that is deployed in the cluster (wants
          to act just as a client, like if you were testing your ejb from your machine against
          the servers). Then the same problem occurs, the client can not download the class
          as any RMI client does, showing you the same error. Actually any client not running
          within weblogic can do that, but when the weblogic classloader is in the middle
          that does not work.
          "weber" <[email protected]> wrote:
          >
          >Hi:
          > we have deploye samples cluster ejb teller and account to a cluster
          >environment..one
          >admin server and one manager server in the same machine(use multi-ip)..another
          >manager server on another machine..two manager server join a cluster,we
          >use weblogic6.0sp2,when
          >we want see manager server's jndi tree .got the error messages..and I
          >read from
          >bea's online document..in a cluster environment ..any join cluster's
          >manager server
          >have the same jndi tree..but if admin server not in the cluster ,it's
          >jndi tree
          >will the same with the other manager servers?and how to deploye ejb to
          >the cluster
          >correclly?should i set call-by-reference to false in weblogic-ejb.xml?thanks
          >your
          >comment...
          >
          >
          >
          >
          >
          >
          >javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException:
          >failed to unmarshal interfa
          >ce javax.naming.NamingEnumeration; nested exception is:
          >java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          >This error could
          >indicate that a component was deployed on a cluster member but not other
          >members
          >of that cluster. Make sure th
          >at any component deployed on a server that is part of a cluster is also
          >deployed
          >on all other members of that cl
          >uster
          >java.lang.ClassNotFoundException: examples.cluster.ejb.teller.TellerBeanEOImpl_WLStub:
          >This error could indicat
          >e that a component was deployed on a cluster member but not other members
          >of that
          >cluster. Make sure that any c
          >omponent deployed on a server that is part of a cluster is also deployed
          >on all
          >other members of that cluster
          >at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:143)
          >at weblogic.rjvm.MsgAbbrevInputStream.resolveClassOverride(MsgAbbrevInputStream.java:84)
          >at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectI
          >nputStream.java:276)
          >at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          >at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          >at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262)
          >at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
          >at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          >at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1142)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:374)
          >at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:106)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:122)
          >at weblogic.jndi.internal.BindingEnumeration.readExternal(BindingEnumeration.java:55)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:103)
          >at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:114)
          >at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:47)
          >at weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:136)
          >at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:251)
          >at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
          >at weblogic.jndi.internal.ServerNamingNode_WLStub.listBindings(ServerNamingNode_WLStub.java:374)
          >at weblogic.jndi.internal.WLContextImpl.listBindings(WLContextImpl.java:293)
          >at javax.naming.InitialContext.listBindings(InitialContext.java:399)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:74)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          >at weblogic.management.console.pages._jndi._nav.printContext(_nav.java:80)
          >

Similar Messages

Cluster JNDI error in SOAP

          I am trying to deploy a Web Service EAR using stateless session beans across 2
          servers in a cluster. The Admin server is not part of the cluster. I am using
          WLS 7.0 SP1. I am getting this error in one of the server traces :
          <Conflict start: You tried to bind an object under the name XscGenericSOAPInterfaceXscGenericSOAPInterface.jarSOAPBusinessServiceOneEJB_EO
          in the JNDI tree. The object you have bound from striker.mk.telcordia.com is
          non clusterable and you have tried to bind more than once from two or more servers.
          Such objects can only deployed from one server.>
          How do I proceed?
          Thanks for all the help from this newsgroup.


Hi,
          SOAP has nothing to do with JMS, althout a SOAP message can be sent into
          JMS, nor really do EJBs have anything to with JMS directly, and this is
          the jms newsgroup. I think your problem is EJB related, try
          weblogic.developer.interest.ejb, or, since your using a web-service, try
          the weblogic.developer.interest.webservices newsgroup.
          Tom
          Suteertha Guha wrote:
          > I am trying to deploy a Web Service EAR using stateless session beans across 2
          > servers in a cluster. The Admin server is not part of the cluster. I am using
          > WLS 7.0 SP1. I am getting this error in one of the server traces :
          >
          > <Conflict start: You tried to bind an object under the name XscGenericSOAPInterfaceXscGenericSOAPInterface.jarSOAPBusinessServiceOneEJB_EO
          > in the JNDI tree. The object you have bound from striker.mk.telcordia.com is
          > non clusterable and you have tried to bind more than once from two or more servers.
          > Such objects can only deployed from one server.>
          >
          > How do I proceed?
          >
          > Thanks for all the help from this newsgroup.

"redeploying of ejbs is causing jndi errors

"we r having problems with redeploying an ejb jar file(1 bean) on the 6.0SP1 server cluster.there are 2 servers running on separate sun boxes and the autodeployment is turned off. the method i followed for redeployment was1.Undeployed the bean 2.added the changed ejb jar file to the applications directory3.redeployed the beanResult:1. Bean got undeployed on both servers.2. Bean got redeployed on only one server3. There was a stack trace with jndi errors on the other server.When i restart the server on which the deployment failed, the bean gets deployed when the server starts up.!Is this a server bug?The stack trace is given belowjava.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.lang.ClassNotFoundException: com.privacycouncil.tp.ejb.TPGeneratorBeanEOImpl_WLStub: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that clusterjava.lang.ClassNotFoundException: com.privacycouncil.tp.ejb.TPGeneratorBeanEOImpl_WLStub: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that clusterat weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:143)at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:87)at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:49)at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)at java.io.ObjectInputStream.readObject(ObjectInputStream.jav

"we r having problems with redeploying an ejb jar file(1 bean) on the 6.0SP1 server cluster.there are 2 servers running on separate sun boxes and the autodeployment is turned off. the method i followed for redeployment was1.Undeployed the bean 2.added the changed ejb jar file to the applications directory3.redeployed the beanResult:1. Bean got undeployed on both servers.2. Bean got redeployed on only one server3. There was a stack trace with jndi errors on the other server.When i restart the server on which the deployment failed, the bean gets deployed when the server starts up.!Is this a server bug?The stack trace is given belowjava.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.lang.ClassNotFoundException: com.privacycouncil.tp.ejb.TPGeneratorBeanEOImpl_WLStub: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that clusterjava.lang.ClassNotFoundException: com.privacycouncil.tp.ejb.TPGeneratorBeanEOImpl_WLStub: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that clusterat weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:143)at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:87)at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:49)at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)at java.io.ObjectInputStream.readObject(ObjectInputStream.jav

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

JNDI Error when Oracle BPM Process invokes an EJB Service Adapter

Hi All,
I am trying to invoke an EJB Service from my Oralce BPM process/workflow. I have provided the JNDI name in EJB service adapter in Jdeverloper also. Even though I have configured the JNDI in weblogic server properly, i am getting some JNDI invocation error (FabricInvocationException) as below.
Can somebody help me on this.
Non Recoverable System Fault :
*<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>oracle.fabric.common.FabricInvocationException: Exception creating jndi context for ejb invocation:</summary></part><part name="detail"><detail>Unable to resolve 'XXXXXXInterfaceRemote'. Resolved ''</detail></part><part name="code"><code>null</code></part></remoteFault></bpelFault>*
Edited by: 920456 on Apr 2, 2013 2:09 AM

Hi All,
Still i am facing the above stated challenge, i am getting a JNDI error when i am trying to call it from Oracle BPM process.
can somebody tell me Does Oracle SOA Suite - EJB Adapter version 3.0 has any runtime bugs ? etc.
Bcoz in the below link it is given something like EJB Version 2 Are Not Supported During Runtime. So, i want to check whether any bugs.
[Oracle SOA EJB Adapter Version bugs|http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps5-1455925.html#intadapt]
Regards,
Satya

HttpClusterServlet and cluster JNDI tree

          Hello,
          Our ear is being deployed in a clustered environment. The ear contains a jar
          (multiple ejbs), a web app war, and a webservice war. The httpClusterServlet
          proxy is being run in a server outside the cluster, on port 80. When our servlets
          try to do a JNDI lookup for any of the ejbs, a Naming Exception is thrown. The
          URL for the InitialContext provider is using port 80. So I assume that the lookup
          request is going to the proxy server, which isn't aware of the cluster JNDI tree.
          Aside from moving the proxy inside the cluster (the server configuration is being
          controlled by another developer), is there anyway to resolve this? Changing the
          URL of the provider for the lookups would require knowing the ports of the cluster
          servers.
          Thanks,
          Bob


          Hello,
          Our ear is being deployed in a clustered environment. The ear contains a jar
          (multiple ejbs), a web app war, and a webservice war. The httpClusterServlet
          proxy is being run in a server outside the cluster, on port 80. When our servlets
          try to do a JNDI lookup for any of the ejbs, a Naming Exception is thrown. The
          URL for the InitialContext provider is using port 80. So I assume that the lookup
          request is going to the proxy server, which isn't aware of the cluster JNDI tree.
          Aside from moving the proxy inside the cluster (the server configuration is being
          controlled by another developer), is there anyway to resolve this? Changing the
          URL of the provider for the lookups would require knowing the ports of the cluster
          servers.
          Thanks,
          Bob

Stub out Error Cluster from Error Code.vi?

When I profile my application, I find that the biggest consumer of CPU time is the Error Cluster from Error Code.vi, called from a number of locked NI libraries. How can I stub out this .vi, replacing it with basically a pass-through? I tried creating a project specific .vi with the same name, and when I open my project all the project and vi.lib .vis used link to it, but they all come up broken and have to be re-linked, which I can't do in the locked .vis (I matched the ins and outs and connector pattern). I can't edit the Error Cluster...vi directly, getting a message about the .vi being used by another application even with a clean start of LV and going directly to that .vi in the library (and I would prefer to not mess with the vi.lib version anyway). Any suggestions? Thanks. LV 2011.
Matt

If you have the LLB manager open it reserves your VI in a different appliation instance, therefore it is locked and no editing. Simply close the LLB manager and you can whack away at that VI.
I doubt that the shared clone setting plays much of a role here, there are some deeper issues. A rather amusing VI in a few ways:
In order to show the VI Title instead of the Name you Open a VI reference which is going to stick you into the root loop. 10 reentrent clones simply means 10 copies waiting in line for the root loop. A non-reentrent version would simply have 10 copies waiting to run. Minus the root loop issue, reentrency is the way to go, and on a desktop machine shared clones is typically quite effective.
It can't be a slow VI, look Trim Whitespace was inlined manually to avoid a performance hit! In a loop maybe, but really, shaving off the overhead of a single subVI? That's optimization.
But wait, all of that and much, much more is given right back by the use of Delete From Array to remove the first element of the Array. Bad on so many levels. Delete From Array is a data copy machine, and now you are doing one needlessly. Array subset is your friend here, tells the compiler you are only reading, nothing to get excited about. Pull it outside the case structure, you are ditching the first element twice in the two branches.
Concatenating strings in a loop, also a recipe for fun. Often there are ways to leverage Array to Spreadsheet string for better performance, or build a string array and then concatenate at the end. Probably not a big deal here, how big are call chains really, but if you are inlining subVIs by hand then you should really be frying the bigger fish.
I find myself in your shoes fairly often. Some clunker in vi.lib causes a bug or sluggish performance. You either ditch the NI code and roll your own, or make it work on your machine but not others, or chalk it up to the cost of doing business. I have tried on numerous occasions to suggest that all patches to vi.lib be made readily and freely available to all previous versions of LV that are compatible. Let's say this VI got tweaked so it was a bit more performant for you, at least enough to be viable. Then you could happily use the patched version in LV11, and if you went to a different machine you would simply make sure vi.lib was up-to-date. These types of patches could roll out incrementally as needed, less need to cross your fingers that you won the CAR lottery with each new version of LV. (I guess most lottery winners don't shell out $$$ to collect their "winnings" though).
After all that what would I do here? I would wrap that sucker inside a disable structure (provide minimal functionality, like pass through caller name, code and error instead). Then I would check the performance again. Now you have a data point as to whether or not it is worth it to proceed.

Service Pack and JNDI Errors

Hi all, hope someone can help. I just upgraded to WL60 with SP1 and now all my
EJB are getting JNDI errors cant resolve name. Path and Classpaths have not changed,
in fact nothing has changed expect for the upgrade. Can anyone tell me what has
changed. I looked at the docs but didn't see anything significant. Thanks in
advance. JAS

Can you show us the error messages and asscoiated stack traces and the code
that is producing them?
JAS wrote:
Forgot to mention, I was using WL6.0 before.
"JAS" <[email protected]> wrote:
Hi all, hope someone can help. I just upgraded to WL60 with SP1 and
now all my
EJB are getting JNDI errors cant resolve name. Path and Classpaths have
not changed,
in fact nothing has changed expect for the upgrade. Can anyone tell
me what has
changed. I looked at the docs but didn't see anything significant.
Thanks in
advance. JAS

How to Uninstall SQL instance on active-passive SQL server , which failed during Cluster Setup (Error-Failed at Validate Active Directory Configuration)

How to Uninstall SQL instance on active-passive SQL server , which failed during Cluster Setup (Error-Failed at Validate Active Directory Configuration)
active-passive SQL server cluster setup failed due to some steps missed in initial cluster setup,
now i have unistall sql instance from nodes,
Your help will higly appriciated.
Regards,
Anish
Asandeen

Hello,
Please refer to the following link about remove a node of SQL Server Failover Cluster Instance:
http://msdn.microsoft.com/en-us/library/ms191545.aspx#Remove
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Jndi error in crystal report connecting to jsp

hi
getting error while connecting my report to jsp
Error is JNDI error means i m unable to connect to oracle server using my jsp
if any one have answer than provide me
thanks& regards
ramesh

Rethink your design. Unless this is a trivial application, a JSP should not be initiating database connections (or really performing any JNDI lookups at all). JSP's are part of the view. In model-view-controller architectures, which normal web applications attempt to implement, it is the model's responsibility to connect to a database to fetch relevant data. In its simplest form, this means you at least write a helper class to perform the JNDI DataSource lookup and return the data via a public method. Ideally, you have enough of these classes that they are not simply helper classes, but rather a full-fledged model tier. See tutorials here and on the net about MVC architecture.
As to your specific issue, it could be any number of issues. Are your deployment descriptors (web.xml, serverl.xml, weblogic.xml, etc.) set-up correctly? Is there a typo between the names declared? What does your JNDI lookup URI contain? Is there an error there? What is the code you are using to perform the lookup? What does the actual exception stack trace contain? We will need some or all of the above information to actually diagnose the source of the error.
However, first, redesign your JSP. :^)
- Saish

Reg. JNDI error when starting monitor server

Hi all,
I am installing CCMS for our CRM4.0 Server. At one point of the installation, it asks to start the monitor server. When I start the monitor.bat it throws a error saying "<b>Cannot Connect to Cluster , beacuse of null. ID003814 : JNDI exception in getinitialContext of InitialContextFactoryImpl</b>".
Can anyone please throw some light on this?
Thanks in advance,
Krishna Karthik P

Stop the existing IS & AS as root or kill the (ois_server,aaa_server) process manually since the pid, pid_watchdog process are catch hold by root user. Logon as normal oracle user and issue the command start_ois_sever_nptl.

Weblogic JNDI error

Am unable to start jms subscriberes.
i get below error
javax.naming.NameNotFoundException: While trying to lookup 'TOPIC.XYZ didn't find subcontext 'TOPIC'. Resolved ''
     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.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I checked my settings in the code and am using the correct TOPIC name .
Any suggestions would be very helpful
Thanks,
Vij

newbiejava wrote:
I checked my settings in the code and am using the correct TOPIC name .
Any suggestions would be very helpfulI'm not promising that I'll be one of the individuals to try to help, but for starters don't you think what you posted so far is completely insufficient? Don't you think showing what you think is the relevant code and configuration would be more relevant than just saying you already think you're doing it right?
All that's left for someone remote so far, is to say: Well obviously you're doing something wrong. But since we don't know what you're really doing, we can't tell you.

Helps for WLP9.2 in a cluster: deploy errors, propagation errors

I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1     WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1.     Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2.     Bea private patch: RSGT, fixed cluster deployments.
3.     Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4.     IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2     Common problems and their fixes
2.1     Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove file: <domain>/config/config.lok
b.     Edit file: <domain>/config/config.xml
c.     Remove all elements of: <app-deployment> ? </app-deployment>
d.     Start the Admin server
e.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2     The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1.     Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Perform these clean up steps on one or both managed instances:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3.     The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3     Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove directory: <domain>/servers/AdminServer/data/ldap
b.     Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c.     Start the Admin server
d.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/servers/<managed_name>
b.     rm ?rf data
This forces the re-down load of the LDAP directory.
c.     Start each managed server.
d.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4     The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1.     Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2.     Set the correct DB access password encryption in the jdbc/*.xml files.
a.     cd <domain>/bin
b.     . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c.     java weblogic.security.Encrypt <the_db_password>
d.     Edit the returned string into every <domain>/config/jdbc/*.xml
e.     Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3.     Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4.     Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5.     Start the managed instances.
2.5     Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir     directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.

I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
1     WLP 9.2 Environment
The cluster environment where these symptoms are frequently seen is described by the following:
1.     Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
2.     Bea private patch: RSGT, fixed cluster deployments.
3.     Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
4.     IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
2     Common problems and their fixes
2.1     Failed deploy (Install) of a new portal application via the cluster console.
Problem symptoms:
After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove file: <domain>/config/config.lok
b.     Edit file: <domain>/config/config.xml
c.     Remove all elements of: <app-deployment> ? </app-deployment>
d.     Start the Admin server
e.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
You can now use the console to Install your applications.
2.2     The portal throws framework / container exceptions on one managed instance.
Problem symptoms:
If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
Fix steps:
1.     Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Perform these clean up steps on one or both managed instances:
a.     cd <domain>/config
b.     rm ?rf *
This forces the re-down load of the cleaned up config.xml.
c.     cd <domain>/servers/<managed_name>
d.     rm ?rf tmp cache stage data
This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
e.     Start each managed server.
f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
3.     The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
2.3     Content propagation fails on the commit step.
Problem symptoms:
In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
Important issue:
This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
Note:
The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
Fix steps:
1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
a.     Find the PID to kill: lsof ?C | grep <listen port number>
b.     kill <pid>
c.     Run kill again and if the pid is still running then do: kill -9 <pid>
2.     Admin server:
a.     Remove directory: <domain>/servers/AdminServer/data/ldap
b.     Run this SQL script after you edit it for your schema:
delete from yourschema.P13N_DELEGATED_HIERARCHY;
delete from yourschema.P13N_ENTITLEMENT_POLICY;
delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
delete from yourschema.P13N_ENTITLEMENT_ROLE;
delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
commit;
c.     Start the Admin server
d.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
3.     Both Managed servers:
a.     cd <domain>/servers/<managed_name>
b.     rm ?rf data
This forces the re-down load of the LDAP directory.
c.     Start each managed server.
d.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
2.4     The enterprise portal DB fails and needs to be restored OR switch DB instances
Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
Note:
The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
Steps:
The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
1.     Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
This is where you may give in and use weblogic/weblogic.
2.     Set the correct DB access password encryption in the jdbc/*.xml files.
a.     cd <domain>/bin
b.     . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
c.     java weblogic.security.Encrypt <the_db_password>
d.     Edit the returned string into every <domain>/config/jdbc/*.xml
e.     Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
3.     Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
4.     Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
5.     Start the managed instances.
2.5     Install patches on a host that does not have internet access
The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir     directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.

Cluster Installation Error while running root.sh

Hi all,
Please help
I tried to install clusterware but when i run root.sh on first node it shows as below
[root@rac11g1 etc]# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory to 770.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete
[root@rac11g1 etc]# /u01/crs/oracle/product/11.1.0/crs/root.sh
WARNING: directory '/u01/crs/oracle/product/11.1.0' is not owned by root
WARNING: directory '/u01/crs/oracle/product' is not owned by root
WARNING: directory '/u01/crs/oracle' is not owned by root
WARNING: directory '/u01/crs' is not owned by root
WARNING: directory '/u01' is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting up Network socket directories
Oracle Cluster Registry configuration upgraded successfully
The directory '/u01/crs/oracle/product/11.1.0' is not owned by root. Changing owner to root
The directory '/u01/crs/oracle/product' is not owned by root. Changing owner to root
The directory '/u01/crs/oracle' is not owned by root. Changing owner to root
The directory '/u01/crs' is not owned by root. Changing owner to root
The directory '/u01' is not owned by root. Changing owner to root
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: rac11g1 rac11g1-priv rac11g1
node 2: rac11g2 rac11g2-priv rac11g2
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Now formatting voting device: /dev/sdd1
Format of 1 voting devices complete.
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
rac11g1
Cluster Synchronization Services is inactive on these nodes.
rac11g2
Local node checking complete. Run root.sh on remaining nodes to start CRS daemon
On the Second Node
[root@rac11g2 crs]# ./root.sh
WARNING: directory '/u01/crs/oracle/product/11.1.0' is not owned by root
WARNING: directory '/u01/crs/oracle/product' is not owned by root
WARNING: directory '/u01/crs/oracle' is not owned by root
WARNING: directory '/u01/crs' is not owned by root
WARNING: directory '/u01' is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting up Network socket directories
Oracle Cluster Registry configuration upgraded successfully
The directory '/u01/crs/oracle/product/11.1.0' is not owned by root. Changing owner to root
The directory '/u01/crs/oracle/product' is not owned by root. Changing owner to root
The directory '/u01/crs/oracle' is not owned by root. Changing owner to root
The directory '/u01/crs' is not owned by root. Changing owner to root
The directory '/u01' is not owned by root. Changing owner to root
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: rac11g1 rac11g1-priv rac11g1
node 2: rac11g2 rac11g2-priv rac11g2
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Now formatting voting device: /dev/sdd1
Format of 1 voting devices complete.
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
rac11g2
Cluster Synchronization Services is inactive on these nodes.
rac11g1
Local node checking complete. Run root.sh on remaining nodes to start CRS daemon
When i run root.sh on first node it shows that the second node is not active which is accceptable
but when i run on second node it shows that fisrt node is not active
please help i'm stuck here from past 2 days
Bala
Edited by: Bala0575 on Jun 16, 2010 3:48 AM

Did you run cluvfy.sh before performing the instalation, if so did it report any errors. I would suggest running it now in "pre crsinst" mode and report any findings back. If CVU says everything is good then I would recommend talking to Oracle Support.
It looks like CSS is running on node1 at the end of its root.sh, yet its dead when root.sh is run on node 2.... makes me wonder if its root.2h on node2 thats killing it.
Run "cluvfy stage -pre crsinst" and post the output back to the forum please?
Yours,
Bob

JNDI error while generating pdf from crystal reports in java

Hi, i want to generate PDF from crystal reports in java. I have the .PDF file with database configured into the report. Following details are available in report.
1. Server Name      = testdb
2. Database Name = testdb
3. User
4. Password
I am using CR XI.
In CRConfig.xml i had given following details.
<JDBC>
     <CacheRowSetSize>100</CacheRowSetSize>
     <JDBCURL>jdbc:oracle:thin:@192.218.216.102:1521://TESTDB</JDBCURL>
     <JDBCClassName>oracle.jdbc.driver.OracleDriver</JDBCClassName>
     <JDBCUserName>user</JDBCUserName>
     <JNDIURL>password</JNDIURL>
     <JNDIConnectionFactory></JNDIConnectionFactory>
     <JNDIInitContext>/</JNDIInitContext>
     <JNDIUserName>testdb</JNDIUserName>
     <GenericJDBCDriver>
          <Default>
               <ServerType>UNKNOWN</ServerType>
               <QuoteIdentifierOnOff>ON</QuoteIdentifierOnOff>
               <StoredProcType>Standard</StoredProcType>
               <LogonStyle>Standard</LogonStyle>
          </Default>
     </GenericJDBCDriver>
</JDBC>
When i am calling from java as standalone, i am getting following error.
JRCAgent1 detected an exception: Error finding JNDI name (testdb)
at com.crystaldecisions.sdk.occa.report.lib.ReportSDKException.throwReportSDKException(Unknown Source)      at com.businessobjects.reports.sdk.b.i.if(Unknown Source)
Can anyone let me know where is the problem?

Actually, the question boils down to; does the framework support the fonts?
I believe that my question re. this working in the designer was valid. The designer does not use the framework, so if it works there, it is either a framework issue or a runtime print engine issue.
I believe if you use the code below, it will list fonts available to the framework:
foreach(FontFamily ff in FontFamily.Families)
System.Diagnostics.Debug.WriteLine(ff.Name);
For more information see kbase [1198306 - Crystal Report displaying incorrect font in Microsoft Visual Studio .NET|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_dev/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333133393338333333303336%7D.do]
Ludek

Cluster jndi error

Similar Messages

Maybe you are looking for