FMW 11g – Upgrading Sun JDK

Recently I upgraded a Fusion Middleware Environment from 11.1.1.2 to 11.1.1.3.  As part of this, java had to be upgraded since the version I was on, 1.6.0_16 is not certified for 11.1.1.3.

I checked the Fusion documentation, WebLogic documentation and about the only thing I could find was:

Upgrading Sun JDK in the Oracle Home Directory

Basically it says to install the new JDK version in the same location as the existing JDK.  Well, that wouldn’t be a problem, other than in my infinite wisdom I installed it under the directory name jdk1.6.0_16.    Putting a new version, 1.6.0_22 in that directory could be confusing and not a best practice.  If I had my time back I would have named the directory jdk1.6 and this wouldn’t be an issue.

So how do I fix it?   I searched all the weblogic domain configuration files, startup scripts and console but could only find references to the JDK directory in two files.

1. One reference in $WLS_HOME/common/bin/commEnv.sh
   
   JAVA_HOME="/var/u01/app/oracle/product/jdk1.6"
   
   
2. Two references in $WEBLOGIC_DOMAIN_HOME/bin/setDomainEnv.sh
   
   
SUN_JAVA_HOME="/var/u01/app/oracle/product/jdk1.6"             JAVA_HOME="/var/u01/app/oracle/product/jdk1.6"

Note: If you have multiple weblogic domains you will need to change each domains setDomainEnv.sh file.

I bounced the domains and checked the start logs to verify that the new java home was being used.    For example, if I grep  the AdminServer log for my domain:

grep  jdk1.6 /u01/app/oracle/product/fmw11g/user_projects/domains/SOAdomain/servers/AdminServer/logs/AdminServer.log


now shows references to the new JDK home.  Some lines, but not all:

java.runtime.version = 1.6.0_22-b04
java.version = 1.6.0_22


You can grep it for your old version as well to make sure it isn’t being referenced.

I also opened an SR to make sure that there weren’t other files that should be modified.   Oracle Support didn’t say there were but did say that I could re-open the SR if I encountered any issues.  Not sure if thats a good thing or not.  ;)

OBIEE: Unable to Login. Access Prohibited.

In a TEST environment today users reported they were unable to login.


The NQServer log showed:

2010-11-03 17:03:00
     [nQSError: 13011] Query for Initialization Block 'Authentication' has failed.


At first I thought it was an issue talking to our IDM Server since we just set it up that integration today, but it was quickly ruled out.   Finally I found the following post on Oracle’s Forums where a user accidentally denied access to dashboards in the Privilege Administration Screen.

A forum member suggested appending some parameters to the URL which brings you directly to the Privilege Administration screen:

http://obieeserver:port/analytics/saw.dll?PrivilegeAdmin&_scid=1cJYoJX6psU&Done=Admin

Much to my relief it worked!   For some reason access to Dashboards was not permitted:



I’m not sure why but I enabled it for everyone and passed it back to the OBIEE Administrator to reset the privileges.   At the time he was importing a catalog.. I’m not very familiar with that part of OBIEE so i’m not sure if that was the culprit.

TEMP Space issues while installing WebLogic?

Trying to install WebLogic today and I hit the following:



By default the installer extracts files to /tmp with a directory name in the format of bea<numbers|timestamp?>.tmp and uses 918M of space on Linux. 

Usually you can use the OS environment variable TMPDIR to specify another temporary directory but I guess since this is a java program its ignored.

Instead you have to pass a parameter to Java when you launch the installer.

$JAVA_HOME/bin/java -Djava.io.tmpdir=/var/tmp -jar wls1032_generic.jar