Recently digging into the strategy and best practice of installing the OBIEE Applications, mainly the DAC and Informatica  components, I see two common issues arise more often that any others.  One has to do with the Informatica Integration Service not matching the correct locale such at UTF-8 or MS Windows Latin, etc. preventing it from starting and the other has to do with the Informatica or DAC user not able to call the core integration tools pmrep and pmcmd.  This issue is common on Linux/Unix environments but not so much on a Windows server environment.

Read the full story

Let it be know that when it comes to X Windows technology and connecting a from Windows workstation to a remote Linux/Unix machine, my support goes to XMing.  Now that is not to say that XMing doesn’t have its issues like all other XWindow client technologies.  But it is clean, it offers a nice install package and provides, in the world of open source, very good documentation.  And as a real quick refresher for those that don’t do much Linux or Unix, it is a best practice to lock down your servers and limit connectivity only to those that really need access. That being said, Linux and Unix when being installed have the option of being installed with a GUI interface for the OS or not.  Often times the really astute (geeky) IT pros select the latter and no GUI access is available.   More to the point, in order to install such software as required by Oracle and some other software teams, only a GUI interface such as the Oracle Universal Installer, is available. To accomplish the install on the remote computer from a Windows workstation you need an X Windows client, such as XMing.

Confronted the other day with just such an install, Oracle client and the Datawarehouse Administration Console (DAC), I put my good friend XMing to work.  Let’s talk about that for a moment.  When using XMing, I choose to use it with a solid telnet tool that we all know and love, PuTTy.  PuTTy basically has a setting to forwards the X11 (X Windows) from your remote session to your local/workstation machine.  Ultimately connecting is accomplished in a few steps:

1. Set the DISPLAY var of your remote user profile to the IP of the machine/workstation you are remoting from. many examples on the web show “localhost” but if you are conducting a VPN session to a remote Windows server then you may not be able to get away with just localhost and will need to enter the exact IP of that machine on the network.  For example, if you workstation you are on has an IP of 216.55.55.55 then enter that IP address suffixed with “:0.0″ (e.g.: 216.55.55.55:0.0) in the DISPLAY var of your remote user profile.  Also enter this in the “X Display Location” of your PuTTy session.
2. Execute the command xhost + and/or xhost + IP address
3. Before you need to run a GUI program from the remote linux/Unix machine, launch XMing’s XLaunch application.
   • As a gotcha to this, you may need to select the option to enable “No Access Control” in order to by pass connectivity errors from the workstation rejecting requests from the remote server.

Recently my need to install the Datawarehouse Administration Console (DAC) cause me issues on a VPN session for a remote connect to a Linux server.  Ultimately after completing the above major steps in initiating an X Windows session, the when I ran the installer command for the software, the X Windows session would start and disappear.   It would stay visible just long enough for the OUI (Oracle Universal Installer) to start and haphazardly enough when I clicked the “Next” button to continue the install the X Window would close as would the XMing application.  I checked the logs and the logs only noted successfully connectivity and GUI transfer from the remote machine.  No errors were in the log.

Ultimate what fixed the issue was for me to launch a session of the XLaunch application and before I ran the installer command from the remote PuTTy session window, I right clicked on the Windows Taskbar icon for XLaunch and opened the log file.  I left the log file open and then executed the install command in my PuTTy session.  Somehow some way the X Window and the GUI remote install stayed alive  and I was able to complete the installation.  I think that somehow the XMing application was getting hit with some exception that would otherwise cause it to abend but due to the log file being open, the main application could not close.  Or, something like that.  I was using XMing version 6.9.0.3.1 for this implementation.

The latest version of the Oracle BI Applications, 7.9.6 and 7.9.6.1 have not been out for that long.  That goes as well for the newest version of the DAC clearly. And, perhaps it is that this release is so new and there are just enough changes that several bugs still got out in this release.  Although these bugs are subtle and minor, they will pop-up on you in the damnedest of places, just when you thought you were sailing along swimmingly.

Now, if you read the systems requirements documentation word-for-word upon each and every OBI Apps release, no matter how minor the release, you may not need this information.  But, if you are human, you may have missed the tiny section on page 12 of the related release document, http://download.oracle.com/docs/cd/E14847_01/bia.796/e14221.pdf. This page briefly highlights the fact that a DAC patch, 8760212, is required for this release of OBI Apps. It’s a DAC patch.
Read the full story

Working on a OBI Apps project, I was getting the DAC configurations ready and bumped into the following error message, stating “Error whle calculating build information!”.  The message stated “MESSAGE:::No physical folder information found for PLP”.   This occured when I was trying to build my newly created execution plan.

Solution

I had created a new execution plan and added my subject area(s) but forgot to click the “Generate” button on the Parameters sub-tab after I had selected the subject areas that I wanted built for that particular execution plan.  To fix the error, I just highlighted the newly created execution plan, clicked the Parameters sub-tab and clicked “Generate ”

This is a very low level issue for the DAC but the issue and solution were worth mentioning.  This occured on the DAC Windows client version 10.1.3.4.1.