My Oracle Support Banner

Unable To Login After Failover On Sun Cluster (Doc ID 1330112.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Applications Technology Stack - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.


R12.1.1 is installed in a virtual host environment on Sun cluster 3.2, using the logical hostname in the -servername parameter of rapidwiz. Initially both the virtual hosts (application and database) are configured on the same physical node and AppsLogin works. The logical host for the middle tier is then switched to a different physical node, but AppsLogin then fails with 500 Internal server error.

When Java Cache is disabled by setting LONG_JVM_RUNNING=false, then login works with the logical host switched to the second physical node.

javacache.log shows that the Java Cache has failed to initialize on the middle tier node and that discovery list has not found the new logical host correctly.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.