Monday, May 27, 2013

OBIEE upgrade to

The Oracle Business Intelligence Patchset

Today am going to show you how to upgrade to upgrade.
This patchset is available for all customers who are using Oracle Business Intelligence Enterprise Edition,,, BP1,,,,, and
Note the following:
  • Oracle Exalytics customers must only install this Oracle Business Intelligence patchset if it is certified for the specific Oracle Exalytics Patch or Patchset Update that they are applying. For more information see Oracle Fusion Middleware Installation and Administration Guide for Oracle Exalytics In-Memory Machine and the Oracle Exalytics certification information.
  • Oracle Fusion Applications customers must not install this Oracle Business Intelligence patchset.
  • The Oracle Business Intelligence Patchset is cumulative and includes patches that you might have already applied to the BI System. Therefore, when you are installing the patchset, you might see warning messages indicating that earlier patches are being rolled back. These warnings simply indicate that oPatch is working correctly, and do not require any action.
  • If you have horizontally scaled out the BI system on to multiple machines, then you must apply the Oracle BI EE patches and the JDeveloper patch to all machines in the cluster.
  • Customers installing this Oracle Business Intelligence patchset on the HP Itanium platform must first download and apply patch 14016752 from My Oracle Support. Note that you must apply patch 14016752 before installing the Oracle Business Intelligence patchset. Follow the instructions in the Readme file for patch 14016752 carefully. In particular, be sure to set the ORACLE_HOME environment variable to the <Middleware Home>/<Oracle BI Home> directory (for example, prod_mwhome/Oracle_BI1) before applying patch 14016752.
  • When the patchset installation is complete and the BI System is running again, end users might experience unexpected behavior due to pre-existing browser sessions caching javascript from the earlier Oracle BI release. To avoid unnecessary support requests, ask all end users to clear their browser cache.
Patchset Installation Instructions
  1. Back up the Oracle BI System, including the following:
    • The ORACLE_HOME\bifoundation\server directory
    • The ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository
    • The ORACLE_BI_HOME\bifoundation\jee\mapviewer.ear\web.war\WEB_INF\conf\mapViewerConfig.xml, if you have modified it
  2. Download the following Oracle BI patch zip files from My Oracle Support into the Oracle BI Home directory:
    • 16287811
    • 16287778
    • 16237960
    • 16287840
    • 16287854
    • 16227549
    • 16287884
Like below :

The location of the Oracle BI Home directory depends on where Oracle BI was originally installed, and on the platform. For example:

For me :

C:\ Satya\OBIEE11G\Oracle_BI1

3. Download the following J Developer patch zip file from My Oracle Support:
  • 13952743

    4.   Stop the BI System (in the order shown):
  • BI system components:
    • On Unix, navigate to prod_mwhome/instances/<instance>/bin and enter the following at the command prompt:
      ./opmnctl stopall
    • On Windows, navigate to prod_mwhome\instances\<instance>\bin and enter the following at the command prompt:
      opmnctl stopall

 If you installed Software in your server then you need to stop the weblogic servcies as well.

  • WebLogic Managed Server(s):
    • On Unix, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and enter the following at the command prompt:
      ./ bi_server1
    • On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin and enter the following at the command prompt:
      stopManagedWebLogic.cmd bi_server1
  • WebLogic Administration Server:
    • On Unix, navigate to prod_mwhome/user_projects/domains/<domain_name>/bin and enter the following at the command prompt:
    • On Windows, navigate to prod_mwhome\user_projects\domains\<domain_name>\bin and enter the following at the command prompt:
      stopWebLogic.cmd -stop
 5.  Clear the files that are associated with the Oracle BI EE Catalog Manager binary cache as follows:
  1. Go to the ORACLE_BI_HOME/bifoundation/web/catalogmanager/configuration/ directory (using a file manager application or the command line). For example:
    • On Linux, AIX, or Solaris: If the Oracle BI Home directory is prod_mwhome/Oracle_BI1, then go to the following directory:
    • On Windows: If the Oracle Home directory is C:\satya\OBIEE11G\Oracle_BI1, then go to the following directory:
  2. Remove the following Catalog Manager cache directories (if they exist):
    • org.eclipse.osgi

 6.   In the Oracle BI Home directory, unzip each of the Oracle BI patch zip files into a subdirectory below the Oracle BI Home directory. For example:
  • On Linux, AIX, or Solaris: You might extract patch 16287811 into prod_mwhome/Oracle_BI1/16287811
  • On Windows: You might extract patch 16287811 into c:\satya\OBIEE11G\Oracle_BI1\16287811

7. At the command prompt, change directory to the Oracle BI Home directory using the command appropriate for the operating system.
For example:
  • On Linux, AIX, or Solaris: If the Oracle BI Home directory is prod_mwhome/Oracle_BI1, then enter the following:
    cd c:\satya\OBIEE11G/Oracle_BI1
  • On Windows: If the Oracle BI Home directory is C:\prod_mwhome\Oracle_BI1, then enter the following:
    cd c:\satya\OBIEE11G\Oracle_BI1

8. At the command prompt, set the ORACLE_HOME, PATH, and JAVA_HOME environment variables as appropriate for the operating system.
For example:
  • On Linux, AIX, or Solaris: If you are using a command shell derived from the C shell, then set the environment variables by entering the following:
    setenv ORACLE_HOME $PWD
    setenv PATH $ORACLE_HOME/bin:$PATH
    setenv JAVA_HOME $ORACLE_HOME/jdk
    setenv PATH $JAVA_HOME/bin:$PATH
    setenv PATH $ORACLE_HOME/OPatch:$PATH
  • On Windows: If the Oracle BI Home directory is C:\satya\OBIEE11G\Oracle_BI1, then set the environment variables by entering the following:
    set ORACLE_HOME=C:\prod_mwhome\Oracle_BI1
    set PATH=%ORACLE_HOME%\bin;%PATH%
    set PATH=%JAVA_HOME%\bin;%PATH%
    set PATH=%ORACLE_HOME%\OPatch;%PATH%

    You have to set two System variables like below.

 10.  At the command prompt, for each of the extracted Oracle BI patch directories (starting with 1 of 7, then 2 of 7, and so on):
  1. Change directory to the extracted patch directory.
    For example:
    • On Linux, AIX, or Solaris: If you extracted patch 16287811 into prod_mwhome/Oracle_BI1/16287811, then enter the following:
      cd prod_mwhome/Oracle_BI1/16287811
    • On Windows: If you extracted patch 16287811 into C:\satya\OBIEE11G\Oracle_BI1\16287811, then enter the following:
      cd c:\satya\OBIEE11G\Oracle_BI1\16287811
  2. Apply the patch using the command: opatch apply
  3. When the message "Opatch Succeeded" is displayed, repeat the previous steps for the next patch directory until all the patches have been applied.

     11.   Verify that the Oracle BI patches have been applied successfully as follows:
  4. At the command prompt, change directory to the Oracle BI Home.
  5. Run the following command to list the patches that have been applied to the Oracle home that is
    specified by the ORACLE_HOME environment variable (currently the Oracle BI Home):
    opatch lsinventory
  6. Confirm that all the Oracle BI patches shown in Section 1 appear in the list of applied patches (along with any other patches that have previously been applied to the BI System).

     Stall the all OBIEE related services including web logic.

    If you want check current obiee version please use below command in command mode in windows .

    Putty in Linux/Unix/Aix.

    C:\Oracle\Middleware\Oracle_BI1\OPatch>opatch version
    OPatch Version:

    Hope this help's

    Satya Ranki Reddy

Saturday, May 25, 2013

Dashboard Custom Jave and HTML Scripts

Dashboard Custom Java Scripts Style

Insert text box onto Dashboard and "Contains HTML Markup" must be ticked. then the following statements can be used independently.

Create a Title With a Nice Line Underneath

<table class="TitleTable" cellspacing="0" style="" width="100%">
<td class="TitleCell" style="" title="">Dashboard Menu</td>
<td class="TitleNameCell" style="" title=""></td>

Out Put:

Satya Ranki Reddy


OBIEE 11g Dashboard Background image change

OBIEE 11g Dashboard Background Image or Watermark

I have implemented on Windows 64bit

1. Make sure analyticsRes folder is active in weblogic for customizations

Check out the section Exposing a Static Directory in WebLogic Server

I normally use this location for customizations or images etc..


(Remember i will make this deployment accessible from the following location setting is ticked) when deploying analyticsRes folder in weblogic.

2. Upload your image file to the Linux box for OBIEE within anaylticsRes folder.

3. Edit or create an OBIEE Dashboard and insert a Text Box within the text box paste the following code

<script type="text/javascript">var obj = document.getElementById('DashboardPageContentDiv'); = "url('/analyticsRes/satya.jpg') white center no-repeat fixed"</script>

Remember to tick the html box . Save your dashboard.
I uploaded an image called satya.jpg.

When you view your dashboard your image will be in the background.

Hope this help's


Linux 64bit OBIEE installation


Hardware Requirements:
Hardisk required around 40gb (Including installation files etc)
Ram = 4gb minimum
Download of Installation Files:

Libraries for this installation are available from here if any are missing:

Xming installation has already been completed the instructions can be found on a separate
Xming is used to render the graphical interface from the Linux Server that you will be
installing OBIEE on.

Pre Requisites:

On Linux, running Oracle Business Intelligence Installer as the root user is not

Make sure there is a user available with the oinstall group and dba group memberships

Create MiddlewareHome Directory in a location where there is sufficient space available

Use the command df –h to check space available to you for the install and space for the
installation files.

When you have found the directory where you would like to install then create a middleware

Creation of the Middleware Home directory:

mkdir -p /Middleware

chown -R oracle:oinstall /u01/satya//Middleware

chmod -R 775 /u01/satya//Middleware

When installation starts it will run a pre-req check on the system to make sure all libraries
needed for the install are available. You can either use YUM or the above link in the document
to download the required libraries identified during the pre-req check.

Libraries for Linux Redhat:

If Libraries need to be installed cancel the install – Download and install the libraries using the
commands below

Install :



Set the Ulimit Parameters (Soft and Hard Limits)

set the /etc/security/limits.conf file

oracle soft nofile 4096
oracle hard nofile 65536

If you have set the Ulimits in the conf file above then the Linux instance will need a bounce for
the settings to be set on boot up.

Temporarily to run install you can execute the below command as installation user

To see if you have set the ulimit correctly the command to use is : ulimit –a

ulimit -a|grep open

If you don’t set the Ulimit parameter you will get a fail on the OBIEE installation pre req
checks like below

Click cancel and start again by setting the U LIMIT

Creating an RCU on Database:

As we are running OBIEE on Linux 64 Bit platform we have to create the RCU from a
Windows Machine. We are using windows 7 for this. This utility can be run any time prior to
the OBIEE installation and the Database user must have sysdba privilege on the required
Database. Database version we are using is 11G


Start the rcu.bat

Refer my blog for RCU installation:    ( Scroll down little bit you will find the RCU installation step by step) --- RCU installation similar to all environment). 

OBIEE Installation:

Unzip the installation files on the Linux box

When you issue the first unzip command it will create a bishiphome directory and with in

create sub directories for the disks

If you do not have enough disk space on the Linux box you can keep deleting the installation

zip files after you unzip them

Below are the commands for unzipping the installation files

• unzip
• unzip
• unzip
• unzip
• unzip

Start the Installation process

Please refer to the xming document on how to start the service on the linux box for the GUI to
render on your windows computer. You can do silent installation but you will still need to
render the GUI so you can get a one off silent install script.

Start the xhost command on ther server

export DISPLAY= (youripaddress:0:0)


Navigate to the following directory on the server


Initiate the installation by giving the following command on the server


If the xhost is set up correctly then you should see the installation window popping up on your
windows machine as below

Specify Inventory Directory

Click Ok

Tick Continue and OK

Installer Starts Main GUI for Installation.

Step 1 : Installer release Notes etc

Click Next

Step 2 : Software Updates

Skip Software Updates and Click Next

Step 3: Installation Type : Enterprise Installation

Click Enterprise Install and Click Next

Step 4: The Prequisite checks start here

If any pre –req checks fail ( Then cancel correct them and restart the installer) . If all ok then
click Next.

Step 5 : Weblogic User and Scale Out

Fill in Weblogic Passwords and Click Next

Step 6: Specify Installation Location

Point to Middleware Directory Created earlier on install guide. And Click Next

Step 7: Select Components to Install

Click Next

Step 8/9: Fill in Database Details related to RCU Created

The same for MDS and & BIPLATFORM schemas created in RCU Process.
Fill in Database Type : Oracle Database
Connect String : Description as above
BIPLATFORM : Schema as created when creating RCU and password used and click Next
Click Next for MDS Schema as defaults.

Step 10: Auto Port Configuration

Click Next

Step 11: Oracle Security Updates

Untick support box as above and click next

Click Yes

Step 12: Generate a Response File (Silent Install File) & Summary

Here you can generate a response file (Silent Install File) Click save and save to a location for
another installation if needed.

Click Install

Step 13: Installation Has Started Copying Of Files

Install stage of copying files has started, post install scripts and one off patches etc.
Once at 100% the copying is complete.

Step 14: Installation Has Started Configuring OBIEE

This is where the Installer is Configuring OBIEE and weblogic and Fusion
Middleware etc.
Make sure everything is Success, Everything will be working as expected.
Click Next
Step 15: Installation Result Summary Screen

Save the Completion Summary to the box and copy all the URL’s Needed etc to launch
That’s it for the installation . Run the EM make sure everything is ok. If not go into Weblogic
and start any other deployments needed.
Click Finish
Browser Path – Just Ignore it

Ignore this .. Just click Cancel
If Xming window is stuck after cancel then that’s fine. Just close it.
Test your URL’s from your completion summary and everything is up and running. Next is the
customization and security aspect.
Linux Bash Profile Example:

# .bash_profile
# File Descriptor Limit
ulimit -n 10240
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
# User specific environment and startup programs
export NLS_LANG
export TNS_ADMIN=/u01/MiddlewareHome/Oracle_BI1/network/admin
export JAVA_HOME=/u01/MiddlewareHome/Oracle_BI1/jdk/bin
export MW_HOME=/u01/MiddlewareHome
export DOMAIN_HOME=$MW_HOME/user_projects/domains/bifoundation_domain
export WL_HOME=$MW_HOME/wlserver_10.3
export ORACLE_HOME=/u01/MiddlewareHome/Oracle_BI1
export PATH

Hope this help's

Satya Ranki Reddy

Thursday, May 23, 2013

OBIEE 11g RPD password Change via command mode

Change the OBI Repository Password from the Command mode

In OBIEE there is new BI Server utility called obieerpdpwdchg to change the RPD password from command mode. Please follow the steps to change the repository password using the obieerpdpwdchg utility, and then deploy the modified repository in Fusion Middle ware Control.

Step 1:

  •  Run bi-init to launch a command prompt. 
  • You can find the bi-init command from 

      Client installations: ORACLE_HOME/bifoundation/server/bin

Simple/Software/Enterprise other installations: ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup

Execute bi-init.cmd  to display a command prompt that is initialized to your Oracle instance like below

Once done above step.

Step 2:

  •  At the command prompt, type obieerpdpwdchg with the following arguments: 
  •  -I name_and_path_of_existing_repository 
  •  -O name_and_path_of_new_repository 

Then, enter the current (old) password and the new password when prompted. The repository password must be longer than five characters and cannot be empty. For example:

obieerpdpwdchg -I C:\SampleAppLite_BI0001.rpd -O C:\New_SampleAppLite_BI0001.rpd
Give password for repository: Admin123
Give password for repository: satya123

  • 3. Open a Web browser and log in to Fusion Middleware Control from the computer where the updated repository is located. 
  • 4. In the navigation tree, expand Business Intelligence and then click coreapplication to display the Business Intelligence Overview page. 
  • 5. Display the Repository tab of the Deployment page. 
  • 6. Click Lock and Edit Configuration. 
  • 7. Click Browse next to Repository File. Then, select the updated repository file and click Open. 
  • 8. Enter the new (updated) repository password in the Repository Password and the Confirm Password fields. 
  • Make sure to specify the password that has been set in the repository. If the passwords do not match, the Oracle BI Server fails to start, and an error is logged in nqserver.log.

Hope this help's


Monday, May 20, 2013

Calculation Two Dates Time Difference

Calculation Two Dates Time Differences

I have seen several posts in OTN for calculation Tow dates time differences.


cast(floor(TIMESTAMPDIFF(sql_tsi_second, "- SNP_SESSION".SESS_BEG, "- SNP_SESSION".SESS_END)/ 3600) as char) || ':' ||
cast(floor(mod(TIMESTAMPDIFF(sql_tsi_second, "- SNP_SESSION".SESS_BEG, "- SNP_SESSION".SESS_END),3600) /60)as char) || ':' ||
cast(mod(TIMESTAMPDIFF(sql_tsi_second, "- SNP_SESSION".SESS_BEG, "- SNP_SESSION".SESS_END),60) as char)

Please refer the below thread.



NodeManager setup and WebLogic startup with NodeManager

This is detailed guide for setting up the WebLogicServer NodeManager service and managing the WebLogicServer instance using this service. Also this post provides you an explanation on how to setup WebLogic Server processes to be automatically managed by Node Manager, when an OS instance is rebooted. When an OS instance is rebooted, WebLogic Server will return to the state as it was prior to the reboot.

Assuming the WebLogic Server installation has been done and a domain has been setup with the base configuration as you would like.

Note: Any information below should be updated to match your directory structures and information.
       - %WL_HOME% - C:\oracle\Middleware
       - %DOMAIN_NAME% - base_domain
       - %DOMAIN_HOME% -  C:\oracle\Middleware\user_projects\domains\base_domain 
       - %MACHINE_NAME% - localhost
       - Admin Server [Running] and ManagedServer [shutdown] in the domain

Installing the NodeManager service

      1. Open the Command Prompt
      2. Run %WL_HOME%\wlserver_10.3\server\bin\setWLSEnv.cmd to set Weblogic Environment variables like WL_HOME, JAVA_HOME, PATH, CLASSPATH etc..
      3. Edit the installNodeMgrSvc.cmd to bind to a hostname for remote starts
          set NODEMGR_HOST=localhost
      4. Now run the %WL_HOME%\wlserver_10.3\server\bin\installNodeMgrSvc.cmd
          Validate the service from the services list as well using the services.msc utility
      5. Start the NodeManager service named as above “Oracle WebLogic NodeManager…”
      6. Make sure starting the NodeManager service should create a file under %WL_HOME%\wlserver_10.3\common\nodemanager

Setup NodeManager to restore servers to their last known state after a reboot
      1. Open located at %WL_HOME%\wlserver_10.3\common\nodemanager
      2. Set CrashRecoveryEnabled property value to true
      3. Set StartScriptEnabled property value to true to invoke the startWeblogic script
      4. Set StopScriptEnabled property value to true to invoke the stopWeblogic script and get the managed servers to shutdown cleanly
      5. Restart of NodeManager service for each change to this file

Setup the machine
      1. Login to the AdminServer console
      2. Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Machines
     3. Create a new machine
          Name : localhost
          OS     : Other - as my operating system is Windows 
      4. Create one machine for each instance of OS for a different host.
      5. Assign the ManagedServer to machines based on which machine the ManagedServer is hosted. Take Lock & Edit and navigate through %DOMAIN_NAME% -> Environment -> Machines -> %MACHINE_NAME% -> Configuration tab -> Servers tab
       6. Do not forget to save and Activate the changes.

Enrolling the domain with NodeManager     

       1. Open command prompt
       2. Run %DOMAIN_HOME%\bin\setDomainEnv.cmd to set domain specific environment variables
       3. Start WLST using java weblogic.WLST
       4. At WLS prompt connect to AdminServer using 
           connect ('weblogic','weblogic','t3://localhost:7001')
       5. Run nmEnroll(domainDir='C:/oracle/Middleware/user_pro

           Make sure that you use forward slashes "/" instead of backward "\" as WLST does not recognize forward slashes
           If you use backward slashes "\" you get the below error.
        6. Once the domain is successfully enrolled with NodeManager the should be updated too with below values.
            #Thu Apr 28 11:54:41 MDT 2011

            Also NodeManager should be reachable in AdminServer console. To validate this, 
            a. Login to AdminServer console
            b. Navigate through
%DOMAIN_NAME% -> Environment -> Machines -> %MACHINE_NAME% -> Monitoring -> Node Manager Status

Server Startup Configuration

      1. Login to the AdminServer console
      2. Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Servers -> ManagedServer_1 -> Configuration tab -> Server Start tab
       3. Take Lock & Edit and input values as appropriate.
           Java Home - C:\oracle\Middleware\jdk160_14_R27.6.5-32 
               Java Vendor - Sun - As I am using Sun JDK 
               BEA Home - C:\oracle\Middleware 
               Root Directory - C:\oracle\Middleware\user_projects\domains\base_domain 
               Classpath - Can be left blank as we have configured the to use startWeblogic script in  Setup NodeManager to restore servers to their last known state after a reboot  step 3 and you can setup necessary values in that script. 
               Arguments - Can be left blank as we have configured the to use startWeblogic script in  Setup NodeManager to restore servers to their last known state after a reboot  step 3 and you can setup necessary values in that script. But i am using memory arguments as input here "-Xms64m -Xmx128m" 
               Security Policy File - C:\oracle\Middleware\wlserver_10.3\server\lib\weblogic.policy 
               User Name - weblogic 
               Password - weblogic 
               Confirm Password - weblogic
        4. Save and activate the changes
        5. Repeat steps 1-4 for each ManagedServer in the domain.

NodeManager Domain Username and password

        1. Login to the AdminServer console
        2. Click on Domain name in the Domain Structure and navigate through %DOMAIN_NAME% -> Security tab -> General tab -> Advanced link 
        3. Take Lock & Edit  and input the NodeManager username/password/confirm passwords fields and these could be unique from your weblogic console password. I have chosen to input same as my console credentials username: weblogic & password: weblogic. This setup would help user who use WLST to connect to NodeManager via nmConnect()
        4. Save and Activate the changes

Finally the setup is complete and now its time to start your ManagedServer in Admin console using NodeManager.

Starting the ManagedServer using the NodeManager setup

        1. Login to the AdminServer console
        2. Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Servers -> ManagedServer_1 -> Control tab -> Start/Stop tab
        3. Under the Server Status section select the ManagedServer and click on start button
            When prompted to confirm the Action to be performed, click yes button
         4. Monitor the server logs and after a while the server should be in RUNNING state