Teaming Cluster ehcache error

Hi there,
I have a problem with the ehcache I guess. As soon as I activate Clustered Configuration the main context is no more initializing. I dont know whats wrong ?
My configuration for the cluster is listed at the bottom of this entry. Hopefully someone can push me in the right direction where to have a look and perhaps what to double check.
2010-03-04 13:12:14,391 DEBUG [main] [net.sf.ehcache.hibernate.EhCacheProvider] - Creating EhCacheProvider from a specified resource: /config/ehcache-hibernate-clustered.xml Resolved to URL: file:/opt/novell/teaming/apache-tomcat-6.0.18/webapps/ssf/WEB-INF/classes/config/ehcache-hibernate-clustered.xml
2010-03-04 13:12:14,419 DEBUG [main] [net.sf.ehcache.distribution.RMICacheManagerPeerLis tener] - Automatically finding a free TCP/IP port to listen on: 48757
2010-03-04 13:12:14,444 ERROR [main] [net.sf.ehcache.distribution.MulticastRMICacheManag erPeerProvider] - Error starting heartbeat. Error was: No such device
java.net.SocketException: No such device
netstat shows me a 0.0.0.0:4446 as stated in the ehcache-hibernate-cluster.xml as multicast Group Port
No binding to port 48757.
SLES 11 32 bit Apache Load balancer
SLES 11 32 bit First Lucene Server
SLES 11 32 bit Second Lucene Server
SLES 11 32 bit Oracle 10 Database Server
SLES 11 32 bit First Teaming Application Server 2.1 (Novell)
SLES 11 32 bit Second Teaming Application Server 2.1(Novell)
IBM JAVA 1-6-0 JDK Provided by SLES 11 SDK
(also tested with SUN Java)
Please do not hesitate to ask for some tests or further information.

BenjaminKnust,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

[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.

My creative CC for teams gives an error code (-60) download corrupted when trying to install any app from the CC on my desktop. Any help?

My creative CC for teams gives an error code (-60) download corrupted when trying to install any app from the CC on my desktop. Any help?

Rasco1 it sounds like your managed network needs to be configured to allow you to download successfully. You can find more details in Error downloading Creative Cloud applications - http://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html.

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.

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

We have cluster sql error 19019

we have two node, recently we move the storage to another new one, then we get the following error in the cluster events:
online thread; could not connect to server but server is considered up.

5. in another part of the same application try to enter other data it give me "SQL server error".
I would suggest to run profiler trace and find what's the exception/error raised in SQL. You should also see some error in application log.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

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

Cluster startup error

I am trying cluster to setup a cluster on a fresh install of WLS 8.1, I get trhe following error while starting weblogic server.
<Jan 17, 2006 8:45:52 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:02 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:12 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:22 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:32 PM PST> <Error> <EmbeddedLDAP> <BEA-171519> <Could not obt
ain an exclusive lock to the embedded LDAP data files directory: .\MedRecAdmin-F
irstAttempt-1\ldap\ldapfiles because another WebLogic Server is already using th
is directory. Ensure that the first WebLogic Server is completely shutdown and r
estart the server.>
<Jan 17, 2006 8:46:32 PM PST> <Critical> <WebLogicServer> <BEA-000364> <Server f
ailed during initialization. Exception:weblogic.server.ServiceFailureException:
Could not obtain an exclusive lock to the embedded LDAP data files directory: .\
MedRecAdmin-FirstAttempt-1\ldap\ldapfiles because another WebLogic Server is alr
eady using this directory. Ensure that the first WebLogic Server is completely s
hutdown and restart the server.
weblogic.server.ServiceFailureException: Could not obtain an exclusive lock to t
he embedded LDAP data files directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es because another WebLogic Server is already using this directory. Ensure that
the first WebLogic Server is completely shutdown and restart the server.
at weblogic.ldap.EmbeddedLDAP.ensureExclusiveAccess(Ljava/lang/String;)V
(EmbeddedLDAP.java:960)
at weblogic.ldap.EmbeddedLDAP.initialize()V(EmbeddedLDAP.java:222)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:815)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run([Ljava/lang/String;)I(T3Srvr.java:343)
at weblogic.Server.main([Ljava/lang/String;)V(Server.java:32)
>
<Jan 17, 2006 8:46:32 PM PST> <Emergency> <WebLogicServer> <BEA-000342> <Unable
to initialize the server: weblogic.server.ServiceFailureException: Could not obt
ain an exclusive lock to the embedded LDAP data files directory: .\MedRecAdmin-F
irstAttempt-1\ldap\ldapfiles because another WebLogic Server is already using th
is directory. Ensure that the first WebLogic Server is completely shutdown and r
estart the server.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.server.ServiceFailureException: Could not obtain an
exclusive lock to the embedded LDAP data files directory: .\MedRecAdmin-FirstAtt
empt-1\ldap\ldapfiles because another WebLogic Server is already using this dire
ctory. Ensure that the first WebLogic Server is completely shutdown and restart
the server.'
Reason: weblogic.server.ServiceFailureException: Could not obtain an exclusive l
ock to the embedded LDAP data files directory: .\MedRecAdmin-FirstAttempt-1\ldap
\ldapfiles because another WebLogic Server is already using this directory. Ensu
re that the first WebLogic Server is completely shutdown and restart the server.
***************************************************************************

I am trying cluster to setup a cluster on a fresh install of WLS 8.1, I get trhe following error while starting weblogic server.
<Jan 17, 2006 8:45:52 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:02 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:12 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:22 PM PST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not o
btain an exclusive lock for directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es. Waiting for 10 seconds and then retrying in case existing WebLogic Server is
still shutting down.>
<Jan 17, 2006 8:46:32 PM PST> <Error> <EmbeddedLDAP> <BEA-171519> <Could not obt
ain an exclusive lock to the embedded LDAP data files directory: .\MedRecAdmin-F
irstAttempt-1\ldap\ldapfiles because another WebLogic Server is already using th
is directory. Ensure that the first WebLogic Server is completely shutdown and r
estart the server.>
<Jan 17, 2006 8:46:32 PM PST> <Critical> <WebLogicServer> <BEA-000364> <Server f
ailed during initialization. Exception:weblogic.server.ServiceFailureException:
Could not obtain an exclusive lock to the embedded LDAP data files directory: .\
MedRecAdmin-FirstAttempt-1\ldap\ldapfiles because another WebLogic Server is alr
eady using this directory. Ensure that the first WebLogic Server is completely s
hutdown and restart the server.
weblogic.server.ServiceFailureException: Could not obtain an exclusive lock to t
he embedded LDAP data files directory: .\MedRecAdmin-FirstAttempt-1\ldap\ldapfil
es because another WebLogic Server is already using this directory. Ensure that
the first WebLogic Server is completely shutdown and restart the server.
at weblogic.ldap.EmbeddedLDAP.ensureExclusiveAccess(Ljava/lang/String;)V
(EmbeddedLDAP.java:960)
at weblogic.ldap.EmbeddedLDAP.initialize()V(EmbeddedLDAP.java:222)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:815)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run([Ljava/lang/String;)I(T3Srvr.java:343)
at weblogic.Server.main([Ljava/lang/String;)V(Server.java:32)
>
<Jan 17, 2006 8:46:32 PM PST> <Emergency> <WebLogicServer> <BEA-000342> <Unable
to initialize the server: weblogic.server.ServiceFailureException: Could not obt
ain an exclusive lock to the embedded LDAP data files directory: .\MedRecAdmin-F
irstAttempt-1\ldap\ldapfiles because another WebLogic Server is already using th
is directory. Ensure that the first WebLogic Server is completely shutdown and r
estart the server.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.server.ServiceFailureException: Could not obtain an
exclusive lock to the embedded LDAP data files directory: .\MedRecAdmin-FirstAtt
empt-1\ldap\ldapfiles because another WebLogic Server is already using this dire
ctory. Ensure that the first WebLogic Server is completely shutdown and restart
the server.'
Reason: weblogic.server.ServiceFailureException: Could not obtain an exclusive l
ock to the embedded LDAP data files directory: .\MedRecAdmin-FirstAttempt-1\ldap
\ldapfiles because another WebLogic Server is already using this directory. Ensu
re that the first WebLogic Server is completely shutdown and restart the server.
***************************************************************************

Team Calendar - WEBMO Error

When reviewing the Team Calendar in MSS I am getting the following error:
No data for infotype 0001, personnel no. 00000000 in period 05.07.2009 - 05.07.2009 (WEBMO not found)
How do I resolve this error?
Thanks
WB

Bill,
check this sap note 1292967.
some config has to be done under Integration with other mysap.com components - Business Packages/Functional Packages - Manager Self services(mySAP ERP) - Working Time - Team Calendar
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on Jul 6, 2009 1:59 AM

Failover cluster validation errors

We are trying to set up a failover cluster file server between two domain controllers running Windows Server 2012 RC.
When we go through the Validate Configuration wizard, we receive the following errors messages against the Active Directory configuration (names have been changed).
"It could not be determined whether node computer1.example.com is a read only domain controller because of this error: The object does not exist."
and
"Node(s) computer1.example.com computer2.example.com cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers."
Does anyone have any ideas why this might be happening? Replication and DNS appear to be working fine for all other services.

I did some tracking down of the problem, and it appears that it stems from the cluster not being able to retrieve the node names. The function specifically is called GetFqdnNodeNamesFromCluster( ).
It can be seen if you run "Get-ClusterLog" while the cluster is in the process of being created. This error seems to be the root of the cluster creation failure. Here is a stacktrace:
PS C:\Users\gamroot> Get-ClusterLog -v
VERBOSE: Connecting to cluster on local computer TESTNODE1.
VERBOSE: at MS.Internal.ServerClusters.Cluster.GetNodes()
at Microsoft.FailoverClusters.PowerShell.FCCmdlet.GetFqdnNodeNamesFromCluster(Cluster cluster, Boolean onlineOnly)
at Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand.WrappedProcessRecord()
at Microsoft.FailoverClusters.PowerShell.FCCmdlet.ProcessRecord()
VERBOSE: at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
at MS.Internal.ServerClusters.SafeFilteredEnumHandle..ctor(Cluster cluster, Boolean filterCoreGroups, Boolean
filterCoreResources)
at MS.Internal.ServerClusters.SafeClusterEnumHandle..ctor(Void* enumHandle, Cluster cluster, ClusterEnumType
enumType, SafeClusterEnumHandleOptions options, SafeClusEnumHandleType safeClusEnumHandleType)
at MS.Internal.ServerClusters.NativeMethods.ClusterOpenEnum(Cluster cluster, ClusterEnumType enumType,
SafeClusterEnumHandleOptions options)
at MS.Internal.ServerClusters.Cluster.GetNodes()
VERBOSE: at MS.Internal.ServerClusters.ClusterRegistryKey.GetValue(String name)
at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
VERBOSE:
Get-ClusterLog : Failed to retrieve the list of nodes for 'TESTCLUSTER1'.
Could not retrieve the core cluster group for the cluster 'TESTCLUSTER1'.
An error occurred while querying the value 'ClusterGroup'.
Element not found
At line:1 char:1
+ Get-ClusterLog -v
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [Get-ClusterLog], ClusterCmdletException
+ FullyQualifiedErrorId : NotFound,Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand

Windows Failover Cluster Manager Error

I have a node that is not able join the Hyper-V cluster that it was previously running in the cluster without problems.
The cluster service encountered an unexpected problem and will be shut down. The error code was '2'.
C:\Windows\Cluster>clussvc.exe -s
-----------------------------+ LOG BEGIN +-----------------------------
[CS] Starting clussvc as a service
[CS] cluster service logging level is 5
[CS] Caught exception ERROR_FAILED_SERVICE_CONTROLLER_CONNECT(1063)' because of 'StartServiceCtrlDis
patcher( ServiceTable )'
    000007fe:fda6aa7d( ERROR_MOD_NOT_FOUND(126) )
    00000000:0018f5d0( ERROR_MOD_NOT_FOUND(126) )
    00000000:0018fbb0( ERROR_MOD_NOT_FOUND(126) )
    00000000:ffd1a368( ERROR_MOD_NOT_FOUND(126) )
    00000000:0018f5a0( ERROR_MOD_NOT_FOUND(126) )
    00000001:e06d7363( ERROR_MOD_NOT_FOUND(126) )
[CS] About to exit process...
C:\Windows\Cluster>
thank you for any guidance you may provide
ron
Ron Finnegan DHHS NIH NIMH LNT

Hi Ron,
Thank you for the reply.
Have you installed this hotfix?
http://support.microsoft.com/kb/975486
Related information:
http://blogs.technet.com/b/rspitz/archive/2010/08/26/the-cluster-service-service-terminated-with-service-specific-error-183-0xb7.aspx
http://technet.microsoft.com/en-us/library/cc756369(WS.10).aspx
Tim Quan
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact [email protected]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
your question. This can be beneficial to other community members reading the thread.

SQL 2012 Cluster install - error msg

Hi
I am in the process of installing SQL server 2012 cluster, on the Instance configuration page where i gave "SQL Server Network Name" as "appsqlclsA" and the "Named Instance" as "Ins01". I am getting the below
error msg, i am not sure exactly what permissions i need.
"The SQL Server failover cluster network name "appsqlclsA" is not valid. The name must be a valid DNS and Wins name.
So what i understand is i do not have permission to create the virtual sql name account "appsqlclsA"" in the AD.
But i need help finding exactly what permission i need.
Thank you for your help

Take a look at this
TechNet article for assigning permissions in Active Directory to create the virtual computer object. Either you are granted the appropriate permissions or the virtual computer object be pre-staged prior to installation
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

DAG Failover Cluster Service Errors

Hi all,
I have six Exchange 2013 SP1 mailbox servers installed on Server 2008 R2 configured in two seperate DAG's (3 and 3).
I'm using a single NIC on all the servers for replication and server connectivity.
I pre-staged the DAG computer object in AD (and assigned permissions), and configured DNS entries for both (confirmed and resolvable). I also configured the DAG network subnet and DAG IP address via EAC.
At the moment I have active DB's on each server and then a passive copy on each other server, and all instances are healthy.
However, when I look in the WFC on each server, there are a ton of errors in the cluster event logs. All of the nodes show up as green, along with the cluster network, but the cluster shows "The cluster network name is not online".
Cluster resource 'Cluster Name' in clustered service or application 'Cluster Group' failed.
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'contoso.com' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'DAG$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
I've removed and re-added DNS records, and double checked the permissions on the CNO object. What else can I do?

Hi,
Its not a good idea to add a static DNS-Record for the DAG - Remove it and on the member holding the PAM, run ipconfig /registerdns.
Martina Miskovic
It also turns out that the CNO objects were never re-enabled by Exchange during the DAG creation process. Once I followed your steps above, and manually enabled the object in AD, the DNS entries auto-populated and everything came online.
Thanks for the help!

OIF Cluster KeyStore Error

Hello
I am trying to setup a second node to my Oracle federation server (11.1.1.5) and in the weblogic startup I am getting the below errors. Do you know what could be causing this error?
[2012-02-03T15:52:58.004-05:00] [wls_oif2] [ERROR] [FED-20000] [oracle.security.fed.sec.key.select.KeystoreStore] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1031485b6ba3e9c8:-59423aa9:13544fd638e:-8000-0000000000000002,0] [APP: OIF#11.1.1.2.0] Cannot open the key store.
[2012-02-03T15:52:58.004-05:00] [wls_oif2] [ERROR] [FED-20000] [oracle.security.fed.sec.key.select.CryptoStore] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1031485b6ba3e9c8:-59423aa9:13544fd638e:-8000-0000000000000002,0] [APP: OIF#11.1.1.2.0] Cannot open the key store.
Not sure what could be causing this but any help you can give would be aprpeciated.
Thanks
Nick

Hi, could you please clarify/elaborate what you did to fix it.
I 'm seeing the exact same problem with the second node in the OIF cluster. In my case the 'conftmpdatastore' is already assigned to cluster_oif but I still see the following errors towards the last phase of the startup of WLS_OIF2:
<Mar 8, 2012 1:14:58 AM PST> <Error> <oracle.security.fed.sec.key.select.KeystoreStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:14:58 AM PST> <Error> <oracle.security.fed.sec.key.select.CryptoStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:03 AM PST> <Error> <oracle.security.fed.sec.key.select.KeystoreStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:03 AM PST> <Error> <oracle.security.fed.sec.key.select.CryptoStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:06 AM PST> <Error> <oracle.security.fed.sec.key.select.KeystoreStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:06 AM PST> <Error> <oracle.security.fed.sec.key.select.CryptoStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:10 AM PST> <Error> <oracle.security.fed.sec.key.select.KeystoreStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:10 AM PST> <Error> <oracle.security.fed.sec.key.select.CryptoStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:14 AM PST> <Error> <oracle.security.fed.sec.key.select.KeystoreStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:14 AM PST> <Error> <oracle.security.fed.sec.key.select.CryptoStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:18 AM PST> <Error> <oracle.security.fed.sec.key.select.KeystoreStore> <FED-20000> <Cannot open the key store.>
<Mar 8, 2012 1:15:18 AM PST> <Error> <oracle.security.fed.sec.key.select.CryptoStore> <FED-20000> <Cannot open the key store.>
I looked at the FED-20000 error from the link sent by an earlier poster that says this error can be ignored if during install. But this is after install.
I suspect the problem is that the installer asks for the PKCS password during install of the first OIF node. See step 12 under section 16.2 at this manual page.
http://docs.oracle.com/cd/E21764_01/core.1111/e12035/oif.htm#BAJFJBGG
However there is no equivalent step for the second node installation (i.e. 16.3 in the above page). May be there is a manual way to tell the second node about the PKCS store
password.
http://docs.oracle.com/cd/E21764_01/core.1111/e12035/oif.htm#BAJFJBGG

Teaming Cluster ehcache error

Similar Messages

Maybe you are looking for