Sunday, April 27, 2014

Windows Loopback Adapter - link to a nice post on the subject

Oracle advises to install a Loopback Adapter before installing DB, OBIEE, etc... on Windows.Each time I need it, I google for a link.

Few days ago I had a major disk crash (that lovely shade of blue on start-up of the computer. Yes, I planed a major backup that morning) and had to install the entire windows box again. Naturally I looked for a link about Loopback Adapters. This following post I liked better so I decided to add a link to it in my blog. Mostly for me:

Saturday, April 26, 2014

OBIEE - Installing patch set 11.1.1.7.140415 on Windows

Please note OBIEE Bundle Patch 11.1.1.7.151020 is available. You might prefer it.

The process is very similar to the previous patchset installations. I created it for myself, mostly for comfortable copy/paste of command lines.

As described in OBIEEBUNDLE PATCH 11.1.1.7.140415 AKA 11.1.1.7. (?) is available, first download the single big patch file of   Patch 18283508 and the small file of  Patch 16569379 (you need 16569379 only if you didn't install it with 11.1.1.7.1 ... or later, I’ll refer to it in the description, but you can disregard it if you already installed it).

Unzip the patches. You should have 2 directories named by the patch number.
Now in the directory 18283508, you have 8 zip files and a useful readme.htm. You are advised by the readme to move the 18283508 directory to  prod_mwhome\Oracle_BI1. Unzip all 8 zip files. At the moment you should have 8 directories under prod_mwhome\Oracle_BI1\18283508.

PLEASE read carefully section 3.1 if you are upgrading from 11.1.1.6.X. Especially 11.1.1.6.12.

In section 3.2 we are advised to check conflicts. I promise to do it later, after I set the path and Oracle_Home.

Next we are advised to do is to back up the Oracle BI system, including the following:
The <Oracle BI Home>\bifoundation\server directory.   
The <Oracle Instance>\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository directory.
The <Oracle BI Home>\bifoundation\jee\mapviewer.ear\web.war\WEB_INF\conf\mapViewerConfig.xml file, if you have modified it.
There is a tip: The location of the Oracle BI Home directory and the Oracle Instance directory depend on where Oracle BI was originally installed, and on the platform. For example:
        On UNIX, the Oracle BI Home directory might be prod_mwhome/Oracle_BI1
        On Windows, the Oracle BI Home directory might be
c:\prod_mwhome\Oracle_BI1
In my case it's D:\MWHOME\Oracle_BI1\bifoundation\server and D:\MWHOME\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository.
I prefer to backup D:\MWHOME\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog as well.
Please note: If you changed configuration files or added pictures not in AnalyticsRes folder (as described here, back the changes as well. They will be erased by the patch).

In point 3 you are advised to stop the BI System and told how to do it, step by step. It's all very nice but to me it looks simpler just to run "Stop BI Services" from the Start/All Programs/Oracle Business Intelligence menu. I guess we see the full details due to Linux needs (and anyway, it's very educational).

Point 4 advises to clear cache: from prod_mwhome\Oracle_BI1\bifoundation\web\catalogmanager\configuration\ (in my case D:\MWHOME\Oracle_BI1\bifoundation\web\catalogmanager\configuration\) you should delete 2 files (if they exist) org.eclipse.osgi  &  org.eclipse.equinox.app.

As you remember we have directory 18283508
with 8 sub-directories in  prod_mwhome\Oracle_BI1 (in my case D:\MWHOME\Oracle_BI1).
make sure the extracted directory 16569379 is under prod_mwhome\Oracle_BI1 as well, only if you didn't install this patch before (you did, if you installed 11.1.1.7.1  or later).

Open CMD prompt as Administrator on  prod_mwhome\Oracle_BI1. (Right Click with Shift pressed on the CMD or Right Click and CMD here as Administrator in the File Browser or check the start menu).

The readme states:

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/jdk
setenv PATH $JAVA_HOME/bin:$PATH
setenv PATH $ORACLE_HOME/OPatch:$PATH
 
On Windows: If the Oracle BI Home directory is C:\prod_mwhome\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 JAVA_HOME=%ORACLE_HOME%\jdk
set PATH=%JAVA_HOME%\bin;%PATH%
set PATH=%ORACLE_HOME%\OPatch;%PATH%
 (in my case the first line is set ORACLE_HOME=D:\MWHOME\Oracle_BI1)
DON'T leave empty spaces in the set, such as set ORACLE_HOME=   D:\MWHOME\Oracle_BI1. 
Right Click does the paste action in CMD window.

 Now if you remember we need to conflict detection from section 3.2.
Assuming we are in directory Oracle_BI1, run:

cd 18283508

cd 16913445
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\16997936
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\17300045
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\17891247
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\18290942
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\18290979
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\18291001
opatch prereq CheckConflictAgainstOHWithDetail -ph ./
cd..\18291015
opatch prereq CheckConflictAgainstOHWithDetail -ph ./

In all cases you should see:
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
 In point 10 we have 2 options: Run Once all 8 patches or do each manually.
Since I don't enjoy tedious manual labor, I preferred the first option.

We will return to the basic prod_mwhome\Oracle_BI1\18283508 directory and run opatch.

Enter the following commands:
 
cd ..
opatch napply –skip_duplicate

 


This time I installed the patch on fresh 11.1.1.7.0 installation, so I was asked once  "Do you want proceed?" on finished the installation without warnings.
 
If you installed one of the bundle patches before, you will be asked twice "Do you want proceed?"  The identical patches are skipped.
In that case the installation will finish with warnings (older patch screen bellow):


It's all because of previous patches components that are the same in this bundle.

In case you don't trust opatch or simply enjoy unnecessary work you can run each patch separately with opatch apply. PLEASE check,you need to install only the new versions and not all  8 you see. Wait for the  "Opatch Succeeded" and repeat in the next directory. (Repeat the Conflict Resolution list, just with opatch apply, instead of  opatch prereq CheckConflictAgainstOHWithDetail -ph ./)
As I said twice before, only if you didn't install 16569379 before,  go to directory 16569379 and Run opatch apply (in both types of installation).


You are advised to check all patches were applied using opatch lsinventory.

The next part has some manual labor (I use the readme numbers starting with 14):

14. Copy the BIPublisherDesktop32.exe and BIPublisherDesktop64.exe files from the prod_mwhome\Oracle_BI1\clients\bipublisher\repository\Tools directory to the prod_mwhome\user_projects\domains\bifoundation_domain\config\bipublisher\repository\Tools directory.
In my case, from D:\MWHOME\Oracle_BI1\clients\bipublisher\repository\Tools to D:\MWHOME\user_projects\domains\bifoundation_domain\config\bipublisher\repository\Tools.
(Should I copy ExcelAnalyzer.exe as well?)

15. Copy the msmdacc64.dll file from the <Oracle BI Home>\clients\bipublisher\repository\Admin\DataSource directory to the prod_mwhome\user_projects\domains\bifoundation_domain\config\bipublisher\repository\Admin\DataSource directory.
There seems to be a problem here since the source does not exist. I don't know if it's a documentation bug or missing file. Had the same thing in 11.1.1.7.1 and later.

16.  Remove the jsp_servlet subdirectory associated with Oracle BI Publisher (if it exists), as follows:

  A.  Go to the directory containing the jsp_servlet subdirectory (using a file manager application or the command line). If it exists, then the jsp_servlet subdirectory is located in one of the directories below the <Middleware Home>/<Domain Home>/servers/bi_server1/tmp/_WL_user/bipublisher_11.1.1 directory.

    For example:
        On UNIX: If the Middleware Home directory is /prod_mwhome and the Domain Home directory is /user_projects/domains/bifoundation_domain, then go to the following directory:
        /prod_mwhome/user_projects/domains/bifoundation_domainservers/bi_server1/tmp/_WL_user/bipublisher_11.1.1
        On Windows: If the Middleware Home directory is C:\prod_mwhome and the Domain Home directory is \user_projects\domains\bifoundation_domain, then go to the following directory:
        C:\prod_mwhome\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\bipublisher_11.1.1

B.  Look in each directory below <Middleware home>/<Domain home>/servers/bi_server1/tmp/_WL_user/bipublisher_11.1.1, and remove any jsp_servlet subdirectory that you find.

  17. If you backed up mapViewerConfig.xml because it had been modified, then copy the backed-up file to its original location at <Oracle BI Home>\bifoundation\jee\mapviewer.ear\web.war\WEB_INF\conf\.

Now you should be able to start the server, but before you do, there is one more part not in the readme file.

 You might remember the post of Abhinav Agarwal  Smart View Version to use with OBIEE 11.1.1.7.1.
You don’t have to repeat it if you have done it with 11.1.1.7.1 or later patches. Backup  <Oracle BI Home>\clients\epm\SmartView (In my caseD:\MWHOME\Oracle_BI1\clients\epm\SmartView),  extract the content of the Zip file to that directory. 

You might want to delete the patch installation files from <Oracle BI Home> and free the 2.5GB of disk space.

Now you can start up the server. Before you do you might want to have a look at section 5.2 bellow (it requires you to stop the serer again). Bon Voyage.


Section 5.1: Copying BICharts.swf to Custom Directories

The Oracle white paper "Customizing Oracle Business Intelligence Enterprise Edition 11g" describes how to customize Oracle BI Presentation Services by storing custom skins, styles, and messages in a custom directory.

If the Oracle BI system has been customized as described in the white paper and custom skins are stored in one or more custom directories, then follow these additional instructions to complete the Suite Bundle Patch installation:

1.Copy the BIChart.swf file from the <Oracle BI Home>\bifoundation\web\appv2\res\sk_blafp\dvt directory to each custom directory in the BI System, replacing the existing file of that name.

    For example, on Windows, you might copy the BIChart.swf into the following custom directory:

    c:\prod_mwhome\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\analyticsRes\sk_mylookandfeel\dvt

 2. Stop and Start the Oracle BI Presentation Services system component using EM or by running:
opmnctl stopproc ias-component=coreapplication_obips1
opmnctl startproc ias-component=coreapplication_obips1

3. Clear the browser cache.




Section 5.2: Editing Settings in OracleBIJavahostComponent

If you installed (and followed instructions) 11.1.1.7.131017 or later, you already have done this part.

For customers exporting data into Microsoft Excel: To improve the functionality of exporting data from analyses, dashboards, and other Oracle BI Presentation Catalog objects into Microsoft Excel, edit settings in OracleBIJavahostComponent by performing the following steps to complete the Suite Bundle Patch installation:

    1. Stop the server, (including Weblogic)

    2. Navigate to the /instances/instance1/config/OracleBIJavaHostComponent folder.

    3. Perform the following actions:

       a. In the config.xml file, configure the XMLP tag for large data as follows:

        <XMLP> <InputStreamLimitInKB>0</InputStreamLimitInKB>

        <ReadRequestBeforeProcessing>false</ReadRequestBeforeProcessing></XMLP>

        b . In the xdo.cfg file, change the setting for xlsx-keep-values-in-same-column to True.(See note
1632002.1 at Oracle Support if you don't know what they are talking about).

    4. Start the WebLogic Administration Server (and Managed Server and BI System).

Also see document "OBIEE 11g: How To Improve the Functionality of Exporting Data from Analyses, Dashboards, and other Oracle BI Presentation Catalog Objects into Microsoft Excel with OBIEE 11.1.1.7.131017 and Later (Doc ID 1595671.1)" at Oracle Support Site, about changing the value value="-server -Xmx2048M from value="-server -Xmx1024M in the file config.xml of opmn.

For Oracle Business Intelligence Client Tools only (not the Windows server): Having applied the Oracle BI EE Suite Bundle Patch 11.1.1.7.140415, you must also update each desktop installation of the Oracle Business Intelligence Client Tools (Oracle BI Administration Tool, Job Manager, and Catalog Manager in part 18291015, the 8th part of this bundle patch) as follows:

Deinstall the Oracle Business Intelligence Client Tools from every computer where the client tools have been installed by following the instructions in Chapter 5 of Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

Reinstall the Oracle Business Intelligence Client Tools on every computer where the client tools have been deinstalled by following the instructions in Chapter 5 of Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.

You didn’t do it? You might get OBIEE - NQSError 46036 in BI administration after patching BI Server

Wednesday, April 16, 2014

OBIEE BUNDLE PATCH 11.1.1.7.140415 AKA 11.1.1.7.6 (?) is available

Please note OBIEE Bundle Patch 11.1.1.7.151020 is available. You might prefer it.

OBIEE 11.1.1.7 new general bundle patch (number 6?), 11.1.1.7.140415 is available in Patch 18283508 it can be installed on any previous 11.1.1.7 release.

I had no problems downloading the patch this time. If you have problems, try an add-on to Firefox "DownloadThemAll".

The Patch is platform specific and is available for:
  • HP-UX Itanium
  • IBM AIX on POWER Systems (64-bit)
  • Linux x86
  • Linux x86-64
  • MS Windows (32-bit)
  • MS Windows (64-bit)
  • Oracle Solaris on SPARC (64-bit)
  • Oracle Solaris on x86-64 (64-bit)
You can read the readme file here.

Unlike 11.1.1.6 patches, this patchset is downloaded in a single big file+one bonus patch. So just for the record (since you don't need to download them separately):
Patch Abstract
16913445 Oracle Business Intelligence Installer (BIINST) - same as previous patches
18290942 Oracle Business Intelligence Publisher (BIP)
17891247 Enterprise Performance Management Components (BIFNDNEPM) - same as previous patch
18291001 Oracle Business Intelligence Server (BISERVER)
18290979 Oracle Business Intelligence Presentation Services (BIPS)
17300045 Oracle Real-Time Decisions (RTD) - same as previous patches
16997936 Oracle Business Intelligence ADF Components (BIADFCOMPS) - same as previous patches
18291015 Oracle Business Intelligence Platform Client Installers and MapViewer

As usual there is a bonus patch: Patch 16569379  (1111770)- Dynamic Monitoring Service patch. It is platform dependent. If you installed it with 11.1.1.7.1 or later, that's enough. It's the same.

Oracle BI EE Suite Bundle Patch 11.1.1.7.140415 contains no new features.
In the ReadMe here there are special instructions for upgrading from 11.1.1.6.X to 11.1.1.7.140415 at  "Section 3.1: For Customers Moving From 11.1.1.6.x to 11.1.1.7.140415". DON'T upgrade before you read and understand it.



Bugs fixes 

BI Publisher

 
New bug fixes in this patch are shown in the following list:
16749858: EXCEL 2007: COMPLETE DASHBOARD EXPORT: REPORT WITH IMAGE HAVE FORMATTING ISSUES

17159806: FIX FOR BUG 17159806

17286155: PSR:PERF:BI NEED TO OPTIMIZAE BUFFEREDRANDOMACCESSFILE WITH MBRANDOMACCESSFILE

17445201: ER: PLEASE SUPPORT <XDOFO:HTML2FO>...</XDOFO:HTML2FO> IN EXCEL OUTPUT

17452095: COLUMNS ARE WIDE WHEN ENTIRE DASHBOARD OR REPORT EXPORT TO EXCEL.

17969594: DATA MISSING IN EXPORTED EXCEL SHEET

18062505: DASHBOARD PROMPT WITH APOSTROPHE PASSED WITH BACKSLASH '\'

18085206: ADDITIONAL FIXES TO WIDE COLUMN IN EXPORT TO EXCEL 2007

18173301: FIX FOR BUG 18173301

BISERVER

New bug fixes in this patch are shown in the following list:

16286234: USAGE TRACKING ERROR_TEXT COLUMN IS ALWAYS NULL IN OBIEE 11G

16329965: ESSBASE ERROR:SYNTAX ERROR IN INPUT MDX QUERY ON LINE 17 AT TOKN FILTER

17741500: ESSBASE ASYMMETRIC QUERY FOR DIMENSION SCOPE PROPERTY

17822700: PROVIDE AN OPTION TO SPLIT / REDUCE FILTER METRICS

17834758: OBIEE 11G: SUBTOTAL GROUP BY CLAUSE CANNOT CONTAIN AN AGGREGATE EXPRESSION

18077422: 11.1.1.7131017 UPGRADE: DIFFERENT QUERIES/RESULTS GENERATED DUE TO FIX 16537281

18097445: PHYSICAL SQL GENERATED WITH SUB-QUERY INSTEAD OF LITERAL IN WHERE CLAUSE


Presentation Services

New bug fixes in this patch are shown in the following list:

13817474: NLS:SINGLE QUOTE DISPLAY AS &#39; WHEN TRY TO EDIT IT IN WRITE BACK

14051277: BUG LINK IS DISPLAYED HTML TAG WHEN PRINT PDF/EXPORT EXCEL

15901783: DEPLOYING ANALYTICS CAUSING SERVLET EXCEPTION IN SSL ENABLED ENVIRONMENT

16265749: TARGET LEVEL WITHOUT QLI THROWS ASSERTION FAILURE ERROR

16330099: FIX FOR BUG 16330099

16414928: SEG TREE WITH PROMPT RESULTS WRONG DATA COUNT

16667503: PROMPTS: RESET TO LAST APPLIED VALUE IS NOT WORKING

16687397: CRASH/500 ERR IF EXPORT PDF PIVOT HIERARCHY LEAF MBER IN SELECTION STARTWITH

16799640: ACCESS:AFTER RESET THEN DO TAB THE FOCUS SHOULD'NT GO TO SKIP TO CONTENT.

16871020: OBIEE 11.1.1.7:SEGMENT TREE DESIGNER DOES NOT REFLECT THE CORRECT COUNT STATUS

16910210: SUBJECT AREA DROPDOWN IN LISTFORMAT AND SEGMENT DOES NOT HIDE

17040062: MARKETING SEGMENT FUNCTION ADD AGGREGATE BY ON THE CRITERIA BLOCK NOT WORKING

17244742: UPDATE COUNT HANG IN OBIEE 11.X FOR COMPLEX SEGMENT TREES

17283098: OBIEE 11.1.17:EXPORT TO TAB DOESN'T MAINTAIN DECIMAL SEPARATOR

17315976: MIX OF LONG RUNNING AND SHORT CONDITIONAL SECTIONS QUERIES ISSUES

17320040: PAGE SCOPE FOR THE PROMPT DOES'NT REFLECT WHEN EXPORT EXCEL ENTIRE DASHBOARD.

17321928: RANDOM SPLIT NODE MOVED TO BOTTOM IN SEGMENT TREE DESIGN

17352492: RANDOM SPLITS SAMPLE GIVES WRONG NET COUNT

17374248: FOR PIVOT TABLE VIEW, INCLUDE/EXCLUDE COLUMN RUNTIME INTERACTION ISSUE

17389881: DASHBOARD NAME IS NOT RETAINED WHEN SAVED FROM EXPORT CURRENT PAGE

17444267: PROMPT CONSTRAIN ACTION RE-EVALUATES UNRELATED CONDITIONAL SECTIONS

17451042: TMP FILE DELETED FROM SERVER BEFORE IT DOWNLOADED ON BROWSER

17510731: PM: FOR NUMBER WITH NEGATIVE VALUES, KEEP FORMATTING AND DATA TYPE AS NUMBER.

17554844: VALIDATERPD UTILITY NEEDS A FLAG FOR READ-ONLY MODE

17567590: BOOKMARK DO NOT RETAIN THE COLUMN SELECTORS APPLIED TO UPGRADED REPORTS

17603023: DOWNLOADVIEW URL RESULTS IN 404 NOT FOUND ERROR

17604208: ISSUE RELATED TO A SEGMENT FILTER IN SETTING DESCRIPTOR ID

17663789: PM: RESOLVE BASIC HTML IN VIEWS FOR EXPORT/PRINT THAT HAVE CHECKBOX

17695606: FONT IS NOT CONSISTENT IN TITLE EXPORTED TO EXCEL

17703646: ACCESS: JAWS: PRINT/EXPORT OPTIONS ARE NOT GETTING SELECTED USING KEY-STROKES

17721940: SAVE AS' MISSING ON SEGMENT /TREE DESIGNER WHEN ACCESSED FROM SIEBEL MARKETING

17750217: REMOVE GDVARIANT BASED DL API CALLS IN RENDERERHELPER

17769001: DASHBOARD NAME AND PAGE NAME NEED TO BE READABLE BY JAWS

17801063: WHEN PASSING "" TO THE PROMPT IN GO URL DOESNT WORK IN 11.1.1.7.1

17820420: PIVOT WITH GREENBAR AND NO ROW EDGE TRIGGERING UNINITIALIZED INT

17847129: BISERVERXMLCLI GIVES NQSERROR: 37005 WITH XUDML FILES HAVING FOREIGN UTF-8 CHAR

17903230: JAPANESE CHARACTER CORRUPTED BY EXCEL 2007+ EXPORT.

18072075: EXPORT TO EXCEL 2007 IS NOT WORKING DURING ACT AS

18196471: DXE BRINGS IN ALL RECORDS IN DIRECT DATABASE REQUEST

Remember to upgrade the BI Administration Clients with the 18291015 patch content that comes in the bundle patch (not relevant for Windows servers).

You might want to look at note OBIEE 11g: How To Improve the Functionality of Exporting Data from Analyses, Dashboards, and other Oracle BI Presentation Catalog Objects into Microsoft Excel with OBIEE 11.1.1.7.131017 and Later (Doc ID 1595671.1)

Monday, April 7, 2014

OBIEE - Changing the search defaults to contains and no Match Case

This post (done on obiee 11.1.1.7.140114) describes how to change the the search default from "Srarts" to "Contains" and un-check the Match Case mark (as default).

This week 2 different customers requested the same: changing the search default to "Contains" with Match Case not marked. 
For example, this is the default:


Searching 'POD' will return nothing in default case but will work in the requested case.


The change, while possible is not desirable and I'm not sure it's supported.
It was described in the following blogs:
  • Changing the default to Contains is in OBIEE Eklavya blog (kalpesh-obiee-eklavya.blogspot.com) here. (the second part, the first is for OBIEE 10).
  • Removing the mark is described in the blog Oracle BI in Russian (obi2ru.blogspot.com) here. (Regarding this option, the changing in nqsconfig.ini of CASE_SENSITIVE_CHARACTER_COMPARISON = ON; to OFF, influences the sort rather than search, so not relevant in this case).
To summarize (see detailed instructions in the original blogs) you have to modify 2 java script file. Backup and causation are important. 
Remember that the files will be replaced in future patches. In those cases it's better to repeat the change rather that placing backup files, since the files might change as part of the patch.
Be aware, in one example, not so careful change of this sort, caused the Subject Area content to be empty in Answers. Not ideal situation. 

When you backup, if you do it by copy/paste in the same folder. please change the file extension. As a rule of thumb, don't leave unnecessary .js and .xml files in OBIEE installation.

To change the search from "Starts" to "Contains" we need to change their order in 2 files: 
  • MiddleWareHOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\b_mozilla\common\availabledatabrowser.js
  • MiddleWareHOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\b_mozilla\uicomponents\obips.DropDown\obips.dropdownsearchdialog.js
On my machine those are the files:
  • D:\or\MWHOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\b_mozilla\common\availabledatabrowser.js
  •  D:\or\MWHOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\b_mozilla\uicomponents\obips.DropDown\obips.dropdownsearchdialog.js
* I'm not sure the first file change is needed.  Changing only obips.dropdownsearchdialog.js seems to do the work. I'm still investigating.

In both* replace (DO NOT copy / paste from here, it's not a working code)
var d=new Array();
d.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource
("kmsgSearchStringStarts").getString(),"beginsWith"));
d.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource
("kmsgSearchStringContains").getString(),"contains"));

With 
var d=new Array();
d.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource
("kmsgSearchStringContains").getString(),"contains"));
d.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource
("kmsgSearchStringStarts").getString(),"beginsWith"));

What you actually do is changing the order between
d.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource
("kmsgSearchStringStarts").getString(),"beginsWith"));
and
d.push(newobips.FormFields.Option(obiprp.PromptComponents.Utilities.getPromptResource
("kmsgSearchStringContains").getString(),"contains"));

While you are in MiddleWareHOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\b_mozilla\uicomponents\obips.DropDown\obips.dropdownsearchdialog.js file,you can also change the Match Case part, as described in obi2ru (DO NOT copy / paste from here, it's not a working code):
{var c=this.bCaseInsensitiveSearch;
var d=this.bCaseInsensitiveSearch;
this.matchCase=new obips.FormFields.Checkbox
("matchCase","matchCase","matchCase",obiprp.PromptComponents.
Utilities.getPromptResource("kmsgSelectionsMatchCase").getString(),d,c);

To 
{var c=this.bCaseInsensitiveSearch;
var d=false;
this.matchCase=new obips.FormFields.Checkbox
("matchCase","matchCase","matchCase",obiprp.PromptComponents.
Utilities.getPromptResource("kmsgSelectionsMatchCase").getString(),d,c);

No need to restart the BI server, but clearing the browser cache might be a good idea (Ctrl+Shift+Del in most browers).

The result is the following default:


Unable to Sign In with weblogic after upgrade

This post describes what to do when you can't log with weblogic user after patch installation. It's mostly a reminder to myself.
Weblogic user name is only a common example here.

I have an OBIEE system where I modified weblogic user logging level in the RPD.
After a bundle patch installation I tried to log on with weblogic user to OBIEE and see:
"Unable to Sign In
An invalid User Name or Password was entered"

I know the user is valid and it logs on well to EM and Console.

This is because the weblogic user in the RPD and the actual user lost their GUID synchronization. So I have to delete the weblogic user in the RPD and set it's log level again.

Backup the RPD file.

Open On Line Administration Software (offline is OK mostly as well).
Go to Manage / Identity.

If you can't see weblogic user on the right,
Select Action / Set Online User Filter
Write * for all or weblogic (for weblogic).

See the weblogic user (on the right) and delete it. It doesn't do any harm, since OBIEE 11 does not manager users in the RPD.
Save and check the Sign in.

We might want to set the logging level to the user again.