There is slight inconsistency between the Conflict Resolution part (section 2.2) and (section 5). Nothing grand, but my version is slightly different.
My OBI installation is at D:\MWHOME12 where the MWHOME12 is already the Oracle_Home (The usual installation might be Oracle/Middleware/Oracle_Home).
Step1: Stop OBI:
At <ORACLE_HOME>\user_projects\domains\<domain_name>\bitools\bin run stop.cmd
in my case D:\MWHOME12\user_projects\domains\bi\bitools\bin\ & stop.cmd
Step2: Uznip the patch file under Oracle_Home:
In my case folder 22734181 created in D:\MWHOME12
Step3: Set environment variables at command prompt:
Open Command prompt
Please note the JAVA_HOME line is not like the readme
In my case:
On UNIX: 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/oracle_common/jdk
setenv PATH $JAVA_HOME/bin:$PATH
setenv PATH $ORACLE_HOME/OPatch:$PATH
Step4: Run Conflict resolution
opatch prereq CheckConflictAgainstOHWithDetail -ph .\22734181(changed readme)
Assuming it passed:
Step5: Install patch
answered both questions yes (after you stopped the server)
Step6: Start the server:
At <ORACLE_HOME>\user_projects\domains\<domain_name>\bitools\bin run start.cmd
in my case D:\MWHOME12\user_projects\domains\bi\bitools\bin\ & start.cmd
Few things to note:
1. The patch does not cover the admin tool. All the known problems there, remain (see section 10 in the readme).
2. The version number of OBI does not seem to change after the patch.