Translate

Wednesday, 16 May 2012

OBIEE 11.1.1.6.2 Patch Now Available



Who Should Apply This Patch
----------------------------

This patch is highly recommended for all the customers (except Exalytics customers) who are using Oracle

Business Intelligence Enterprise Edition 11.1.1.6.0 and 11.1.1.6.1. Exalytics Customers must not apply this patch.

This patch is primarily intended to improve quality as it includes some high priority bugs.

Please see the Fixed Bugs list for the detail.

Customers who are currently using a version earlier than Oracle Business Intelligence Enterprise Edition 11.1.1.6.0

should not apply this patch.


Important Information for Customers using Oracle Business Intelligence Enterprise Edition Suite version 11.1.1.6.0 and 11.1.1.6.1
-------------------------------------------------------------------------------------------------------------------------------
Oracle Business Intelligence Enterprise Edition customers currently running version 11.1.1.6.0 and 11.1.1.6.1

may encounter patch conflicts if this patch is applied.

A patch conflict occurs when two or more patches have some files in common but contain independent fixes,

resulting in a roll back of previously applied fixes. It is very important that customers currently running version

11.1.1.6.0 pay attention to any notifications regarding conflicting patches presented by Opatch during application

of this patch, as these patches will be rolled back if patch application continues.  Any patch rolled back due to the application

of this PSU must be re-built for this patch before you can reinstall that fix. Open a service request with Oracle Support

 to request a merged patch if required.

********************************* NOTE *************************************************
* When applying this patch, the patch will complete with the following warning message.*
* These warnings are expected and can be ignored                                       *
*                                                                                      *
*      Inventory check OK: Patch ID 13884769 is registered in Oracle Home inventory    *
*      with proper meta-data.                                                          *
*      Files check OK: Files from Patch ID 13884769 are present in Oracle Home.        *
*      -----------------------------------------------------------------------------   *
*      The following warnings have occurred during OPatch execution:                   *
*      1) OUI-67644:                                                                   *
*      Given patch "13884769" is a bug superset of patch "13742915" but is not a       *
*      file superset.                                                                  *
*                                                                                      *
*      -----------------------------------------------------------------------------   *
*      OPatch Session completed with warnings.                                         *
*                                                                                      *
*      OPatch completed with warnings.                                                 *
********************************* NOTE *************************************************








Bugs Fixed By This Patch:
-------------------------------------------------------------------------------------------------------------------------------
13529697: METADATA DICTIONARY NOT PROPERLY GENERATED WITH HYPHENS IN NAMES
13902810: CAN'T CREATE EXPRESSIONS IN RPD WITH COLUMN FROM ESSBASE - INVALID EXPRESSION
13705487: HIERARCHY OBJECTS ARE MISSING AFTER MERGING RPDS
9665267: COMPARE RPD AND PATCH GENERATION
12977729: HIERARCHICAL COL DRILLING ON MORE THAN ONE PAGE OF RESULTS LOSES FOCUS ON DRILL
13688544: 'CASE WHEN' CHANGES TO 'CASEWHEN' IN XML AND CAUSES ERROR WHEN SET XML
13523548: ERROR OUT WHEN USING MULTIPLE DOUBLE COLUMNS IN SAVED FILTERS
13098323: AN ARITHMETIC OPERATION IS BEING CARRIED OUT ON A NON-NUMERIC TYPE
13350175: ADDING FILTER TO DIFFERENT LEVELS OF A HIERARCHY GETS IGNORED IN MDX
13511930: NEW COLUMN CREATED BASED ON TWO DIFFERENT DIMENSIONS RETURNS INCORRECT RESUTLS
13522060: RPD SESSION VARIABLE UNABLE TO IDENTIFY THE DYNAMIC SCHEMA NAMES FOR OLAP
13542805: BAD CACHE ENTRY BEING GENERATED
13626491: CONSISTENCY CHECK UPDATE FOR FACT JOINS DIRECTLY WITH A NON LEAF TABLE
13708781: ORACLE OLAP PARENT-CHILD QUERY PERFORMANCE ISSUE - LIMIT TO BOTTOMDESCENDANTS
13479613: CANNOT MODIFY REPORT/DASHBOARD WHEN USER HAS READ-WRITE BUT NO DELETE PERMISSION
13529494: REPORT NOT GENERATED WHEN HTML CONTAINS INVALID ATTRIBUTES
13391941: QUERY BUILDER - COLUMNS THAT HAVE SPACES ARE NOT DISPLAYED
13840200: VERSION OF CATMAN SHOWS 11.1.1.6.0 after applying 11.1.1.6.2 opatch

General 11.1.6.2 patch installation instructions:
--------------------------------------------------------------------------------------------------------

-----------------------11.1.1.6.2 Install Instructions:
==============
Moving from Oracle BI EE 11.1.1.6.0 or 11.1.1.6.1 to Oracle BI EE 11.1.1.6.2 is a two stage process:
Stage 1: Apply the Oracle BI EE 11.1.1.6.2 patches to the existing Oracle BI EE 11.1.1.6.0 or 11.1.1.6.1 system.
Stage 2: Apply a JDeveloper patch to the newly patched Oracle BI EE system.


Stage 1: Apply the Oracle BI EE 11.1.1.6.2 patches to the existing Oracle BI EE 11.1.1.6.0 or 11.1.1.6.1 system
---------------------------------------------------------------------------------------------------------------------------

1. Download the following patch zip files from My Oracle Support:

* 13932572
* 13887566
* 13926409
* 13892934
* 13916045
* 13884769
* 13794002


2. Copy the downloaded patch zip files into the Oracle BI Home directory.

3. Stop the following (in the order shown):
* BI system components, by typing the following at the command prompt: opmnctl stopall
* WebLogic Managed Server(s)
* WebLogic Admin Server

4. In the Oracle BI Home directory, unzip each of the patch zip files.

(Each zip file is extracted into a subdirectory below the Oracle BI Home directory.)

5. At the command prompt, change directory to the Oracle BI Home directory using the command appropriate for the operating system.
For example:
* on Linux, if the Oracle BI Home directory is Middlewarehome/Oracle_BI1, type the following:
       cd Middlewarehome/Oracle_BI1

* on Windows, if the Oracle BI Home directory is C:\mwhome\Oracle_BI1, type the following:
       cd c:\mwhome\Oracle_BI1

6. At the command prompt, set the environment variables as appropriate for the operating system.
For example:
* On Linux, set the environment variables by typing 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:\mwhome\Oracle_BI1, set the environment variables by typing the following:
       set ORACLE_HOME=C:\mwhome\Oracle_BI1
       set PATH=%ORACLE_HOME%\bin;%PATH%
       set JAVA_HOME=%ORACLE_HOME%\jdk
       set PATH=%JAVA_HOME%\bin;%PATH%
       set PATH=%ORACLE_HOME%\OPatch;%PATH%

7. At the command prompt, for each of the extracted patch directories.
a. Change directory to the extracted patch directory.
b. Open the readme.txt file in the extracted patch directory.
c. Follow the instructions in the readme.txt file to apply the patch.
d. If prompted, provide appropriate responses.
e. When the message 'Opatch Succeeded' is displayed, repeat the above steps for the

next patch directory until all the patches have been applied.

Note that the patches shown in step 1 can be applied in any order.

8. When all the patches have been applied, start the following (in the order shown):
* WebLogic Admin Server
* WebLogic Managed Server(s)
* BI system components, by typing the following at the command prompt: opmnctl startall

9. Verify the patches have been applied successfully as follows:
a. At the command prompt, change directory to one of the extracted patch directories.
b. Run the following command to list the patches that have been applied to the Oracle home specified by the

ORACLE_HOME environment variable (currently the Oracle BI Home):
        opatch lsinventory
c. Confirm that all the patches shown in step 1 appear in the list.


Stage 2: Apply a JDeveloper patch to the Oracle BI EE 11.1.1.6.2 system
------------------------------------------------------------------------------------------------------------

1. Download the following JDeveloper patch zip file from My Oracle Support:
* 13952743

2. Copy the downloaded JDeveloper patch zip file into the Oracle Common Home directory.

3. Stop the following (in the order shown):
* BI system components, by typing the following at the command prompt: opmnctl stopall
* WebLogic Managed Server(s)
* WebLogic Admin Server

4. In the Oracle Common Home directory, unzip the JDeveloper patch zip file.

(The zip file is extracted into a sub-directory below the Oracle Common Home directory.)

5. At the command prompt, change directory to the Oracle Common Home directory using the command appropriate for the operating system.
For example:
* on Linux, if the Oracle Common home directory is Middlewarehome/oracle_common, type the following:
       cd Middlewarehome/oracle_common
* on Windows, if the Oracle Common home directory is C:\mwhome\oracle_common, type the following:
       cd c:\mwhome\oracle_common

6. At the command prompt, set the environment variables as appropriate for the operating system.
For example:
* On Linux, set the environment variables by typing 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 Common Home directory is C:\mwhome\oracle_common, set the environment variables by typing the following:
       set ORACLE_HOME=C:\mwhome\oracle_common
       set PATH=%ORACLE_HOME%\bin;%PATH%
       set JAVA_HOME=%ORACLE_HOME%\jdk
       set PATH=%JAVA_HOME%\bin;%PATH%
       set PATH=%ORACLE_HOME%\OPatch;%PATH%

7. At the command prompt:
a. Change directory to the extracted JDeveloper patch directory.
b. Apply the patch using the command:
       opatch apply
c. If prompted, provide appropriate responses.
d. When the message 'Opatch Succeeded' is displayed, move on to the next step.

8. When the JDeveloper patch has been applied, start the following (in the order shown):
* WebLogic Admin Server
* WebLogic Managed Server(s)
* BI system components, by typing the following at the command prompt: opmnctl startall

9. Verify the patch has been applied successfully as follows:
a. At the command prompt, change directory to the extracted JDeveloper patch directory.
b. Run the following command to list the patches that have been applied to the Oracle home specified by

the ORACLE_HOME environment variable (currently the Oracle Common Home):
        opatch lsinventory
c. Confirm that the patch shown in step 1 appears in the list.


Patch Installation instructions specific to patch 13884769:
-------------------------------------------------------------------------------------------------------------------------------
1. Stop all BI Services, including BI Server, BI Administration Tool, BI Javahost, BI Scheduler
2. Backup ORACLE_HOME\bifoundation\server
3. Backup ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository
4. Follow manual script steps below to resolve bug 13840200: VERSION OF CATMAN SHOWS 11.1.1.6.0 after applying 11.1.1.6.2 opatch
5.  Apply patch using Opatch
6. Start all BI Services
7.  Determine the AdminService application's .ear file location:
    a.  Login to Weblogic Console as the Administrator user
    b.  Under Deployments, click on the adminservice(11.1.1)  name link
    c.  Note the path of the AdminService.ear file 
    d.  Return to the Summary of Deployments page       
8.  Stop the AdminService application
9.  Delete the AdminService application
10. Install the AdminService application using the same .ear file as noted step 7 above.
    **IMPORTANT** 
    When installing, you must change the name from it's default value of AdminService to AdminService_11.1.1.  Without the
    correct version number appended, the web service will not work properly.  Defaults may be used for all the other settings
11. After installation is complete, apply the changes and restart the AdminService.



Scripts to resolve bug 13840200: VERSION OF CATMAN SHOWS 11.1.1.6.0 after applying 11.1.1.6.2 opatch
-------------------------------------------------------------------------------------------------------------------------------
For Linux:   cleancat.sh
================================
#!/bin/sh
# Cleanup catman binary cache
echo "Cleaning up Catalog Manager binary cache"
rm -rf $ORACLE_HOME/bifoundation/web/catalogmanager/configuration/org*
echo "Done"


For Windows:    cleancat.cmd
================================
echo off
echo Cleaning up Catalog Manager binary cache
IF EXIST
%ORACLE_HOME%\bifoundation\web\catalogmanager\configuration\org.eclipse.osgi
(
rmdir /S /Q
%ORACLE_HOME%\bifoundation\web\catalogmanager\configuration\org.eclipse.osgi
)

IF EXIST
%ORACLE_HOME%\bifoundation\web\catalogmanager\configuration\org.eclipse.equino

x.app (
rmdir /S /Q
%ORACLE_HOME%\bifoundation\web\catalogmanager\configuration\org.eclipse.equino

x.app
)
echo Done

Post-Installation Instructions
-----------------------------------------------------------------------------------------------------------------------------

Restart all servers (AdminServer and all Managed server(s)).


Deinstallation Instructions
-----------------------------------------------------------------------------------------------------------------------------

If you experience any problems after installing this patch, remove the patch as follows:

1. Make sure to follow the same Prerequisites or pre-install steps (if any) when deinstalling a patch.
   This includes setting up any environment variables like ORACLE_HOME and verifying the OUI inventory before deinstalling.

2. Change to the directory where the patch was unzipped.

   $cd PATCH_TOP/<%BUG_NUMBER%>


3. Run OPatch to deinstall the patch.

   Run the following command:
   $opatch rollback -id 6521146 -jre $ORACLE_HOME/jdk/jre


Post Deinstallation Instructions
-------------------------------------------------------------------------

Restart all servers (AdminServer and all Managed server(s))

No comments:

Post a Comment

Google Big Query Clone / Copy DataSets / Tables - PROD --> TEST --> DEV Projects

Google Big Query Cloning of Datasets & Tables across GCS Projects. We searched the internet and could not find a simple cloning / ...