Values In OBIEE 10g Multiselect Prompt Are Not Sorting in Alpha-Numeric Order In Large LOVs

Symptoms
When running an Oracle Business Intelligence Enterprise Edition (OBIEE) Dashboard with multi-select prompts that contain many values, the values in the list are not consistently alpha-numerically sorted.

The initial retrieval in the multi-select dialog box shows the values alpha-numerically sorted.  When the next set of values are retrieved, the values lose their sort order and are no longer alpha-numerically sorted.
Cause
This issue is described in the following known bugs:

Bug 8995183 – SORTING IN MULTISELECT PROMPT NOT WORKING AS EXPECTED
Bug 9787610, MULTISELECT PROMPT NOT SORTING PROPERLY WHEN CONTAINS MORE THAN 256 ITEMS
Solution
This issue is fixed in OBIEE 10.1.3.4.2.
If you are encountering this issue, you are urged to upgrade to version 10.1.3.4.2 to obtain the fix
for this bug and many other bugs.
For information on upgrading to this version, please see Note 1357872.1 How To Upgrade to
Oracle Business Intelligence Enterprise Edition (OBIEE) 10.1.3.4.2

If you are currently unable to upgrade to OBIEE 10.1.3.4.2, and require the fix in OBIEE 10.1.3.4.1, please do the following:
1.    Open a Service Request (SR) with Oracle Support and request the password for
Patch 9787610.

2.    Follow instructions for installing the patch as described in patch readme.txt file.
Oracle Support recommends that you first test this patch on a development or test server.
Once you are satisfied that the patch corrects the issue, you may promote the patch to
your production environment.

NOTE: If you are using any web server other than IIS, you will need to recreate and redeploy the
Analytics.war file after installing the patch.

For detailed instructions on how to do this in an OC4J environment, please see:

Note 1075754.1 Create and Deploy A New BIEE 10.1.3.4/10.1.3.4.1 ANALYTICS.WAR File.

References
BUG:8995183 – SORTING IN MULTISELECT PROMPT NOT WORKING AS EXPECTED
BUG:9787610 – MULTISELECT PROMPT NOT SORTING PROPERLY WHEN CONTAINS MORE THAN 256 ITEMS
NOTE:1075754.1 – How To Create And Deploy A New OBIEE 10.1.3.4.X ‘analytics.war’ File (for OC4J)
PATCH:9787610 – MULTISELECT PROMPT NOT SORTING PROPERLY WHEN CONTAINS MORE THAN 256 ITEMS

Applies to:
Business Intelligence Suite Enterprise Edition – Version: 10.1.3.4.1 [1900] to 10.1.3.4.1 [1900] – Release: to 10g
Business Intelligence Server Enterprise Edition – Version: 10.1.3.4.1 [1900] to 10.1.3.4.1 [1900]   [Release: 10g to 10g]
Business Intelligence Answers Option – Version: 10.1.3.4.1 [1900] to 10.1.3.4.1 [1900]   [Release: 10g to 10g]
Information in this document applies to any platform.
This knowledge document is a replacement for 952833.1 which has been deleted.

FOLDERS AND REQUESTS ARE NOT DISPLAYED AFTER UPGRADING TO 11.1.1.3.0.

You have an OBIEE 10.1.3.4.1. instance and a lot of folders and requests for the Administrator user.
You upgrade to 11.1.1.3.0, using the ua.bat tool. It finishes as complete and there are no errors in the the Upgrade Assistant (ua) log files:

 $OBIEE_HOME/upgrade/logs

For example
 C:\OBIEE_11g\Oracle_BI1\upgrade\logs

In OBIEE 11.1.1.3.0, when you log in as Administrator and go to the Catalog option, you are not able to see any folder or request.

Cause

The upgrade process, ua.bat, is not transferring the folders and request for the Administrator user.

This is due to the bug below


What were you trying to do?
---------------------------
Upgrade both repository and web catalog from 10.1.3.4.1 to 11.1.1.3.0.

What should have happened?
--------------------------
You should be able to see all folders and request you had in 10.1.3.4.1 after 
upgrading to 11.1.1.3.0.

What actually did happen?
-------------------------
For the Administrator account, after running the ua.bat for upgrading and 
finishing without error, when you log in with this account, it does not 
display  any folder or document for the Administrator user in 11.1.1.3.0, 
there are a lot of folders and request in 10.1.3.4.1.

What are the symptoms of the problem?
-------------------------------------
You have a web catalog in 10.1.3.4.1. When you log in as Administrator in 
this version you see a lot of folders and request for that user.

  You upgrade to 11.1.1.3.0 using the ua.bat utility. It finishes fine, 
completed without error. In the upgrade log file you can find some warnings 
that I am not sure they are related to this issue. You log in as 
Administrator in 11.1.3.0 and you cannot see any folder or request.

What changes have been made to the technical environment recently?
------------------------------------------------------------------
None.
-------------

Suggested workaround is the following:
In 10.1.3.4.1.
 ===============
 
 1) In Administration Tool, create a new user, 'new_account', under Manage-Security (if you are using other Security option, add the new user there).
 
 2) Using Catalog Manager, copy the content of the Administrator user into the new one.
 For instance:
 
 /-users-administrator
 into
 
  /-users-new_account
 
 3) Upgrade the Web Catalog using the ua.bat:
$ORACLE_HOME/bin/ua.bat
 
 
In 11.1.1.3.0.
 ==============
 
 4) Using Catalog Manager, copy the content of the 'new_account' user into the Administrator one.
 For instance:
 
 /-users-new_account
 
 into
 
 /-users-administrator
 
 5) Connect to OBIEE as Administrator and check you are able to see all folders and requests.

OBIEE 11g Upgrade Assistant (UA) Fails When Upgrading A 10g RPD File To OBIEE 11g

Applies to:

Business Intelligence Suite Enterprise Edition – Version: 11.1.1.3.0 [1905] and later   [Release: 11g and later ]
Information in this document applies to any platform.

Symptoms
On OBIEE 11.1.1.3, When attempting to upgrade a 10g RPD file via the Upgrade assistant
(ua.sh ) , the upgrade fails and the following error can be seen in the log file:

[BIEE] [ERROR] [] [upgrade.BIEE] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] oracle.as.management.opmn.optic.OpticException: Error in starting opmn server[[
Operation aborted because of a system call failure or internal error
at oracle.as.management.opmn.optic.OpmnAdmin.executeCommand(OpmnAdmin.java:310)
at oracle.as.management.opmn.optic.OpmnAdmin.startOpmnServer(OpmnAdmin.java:87)
at oracle.ias.upgrade.config.oraclebi.OPMNUtil.startOpmn(OPMNUtil.java:46)

[Framework] [ERROR] [UPGAST-00138] [upgrade.Framework] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] upgrade exception occurred
[Framework] [ERROR] [] [upgrade.Framework] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] Cause: An unexpected upgrade exception has occurred. Action: See the secondary error message for additional details.
[Framework] [ERROR] [] [upgrade.Framework] [tid: 18] [ecid: 0000IoEFnYP2RP1pNsXBie1D4VU2000009,0] Error in starting opmn server[[
Operation aborted because of a system call failure or internal error
]]

 

Cause

The system component services for BI components are not started.

The upgrade assistant is not able to communicate to OPMN.

Solution

  1. Start OPMN services via the command:

    [middleware_home]/instances/instance1/bin> opmnctl startall

  2. Confirm the status of opmn and the system components under the instance home with:

    [middleware_home]/instances/instance1/bin> opmnctl status

Note: You may  also start the System Components and check the status via Fusion Middleware Control

 

  1. Retry the RPD file upgrade.

 

How to Keep Track of OBIEE 10g Patches Applied? How To Handle Version.Txt Files When You Have Multiple Patches? Are Patches Cumulative?

Applies to:

Business Intelligence Server Enterprise Edition – Version: 10.1.3.2 to 10.1.3.4.2 [2405] – Release: 10g to 10g
Business Intelligence Suite Enterprise Edition – Version: 10.1.3.2 to 10.1.3.4.2 [2405]   [Release: 10g to 10g]
Information in this document applies to any platform.

Goal

– How to handle VERSION.TXT files when you have multiple patches?

– When Oracle supplies an OBIEE patch, its README file always says to replace the VERSION.TXT file on the [Oracle Home] directory with the one included.

– When you apply a second, unrelated patch to the environment why would we want to replace the entire VERSION.TXT file?

– Would you append the text in the second patch’s VERSION.TXT file to the first?

– How will this display on the Settings > Administration window when it displays the information in the Product Information box?

– Are OBIEE Patches cumulative?

Solution

This has been confirmed by Development.

1. Version.txt file should be replaced, following instructions in the readme files of each patch.
New version.txt file should not be appended to the end of the current one, but it should replace the current one.

2. Currently, for 10G versions, OBIEE patch installation does not provide for an automatic way of keeping track of the patches applied.

Nevertheless, Development is working to make 11g use opatch installer. Opatch provides a way to keep track of previous patches installed. There is no official date for 11G release.

3. It is recommended that you keep a record of the patches you have applied.
You could implement that in the way you prefer, but separated from OBIEE installation, and in addition to replace the version.txt file used in OBIEE.

For example, you could:
– Append the version.txt file to another file, with name version_history.txt or something like that, everytime you apply a patch.
OR
– When applying first patch, rename original version.txt from GA release to version0.txt and copy version.txt from the patch.
Then, when applying second patch, rename version.txt to version1.txt and copy new version.txt from the second patch, and so on.
OR
– copy new version.txt file to a file named like version_<YYYY_MM_DD>.txt, indicating the date when you applied it.
That way you can have in a single directory all the previous version.txt with its dates of installation.

4. OBIEE One-off patches are not cumulative at this time.

5. Production patches (the ones that do not require a password), normally, contain the fixes of older production patches.

6. When we create a new patch for you (that is when you report a new issue, never seen before, and then we create a fix for that and provide it to you) we ask you the list of one-off patches you have applied. Development uses it to create a merged patch including all those fixes plus the new one.

7. In the case a one-off patch is already available (so, it was not produced for you), you would need to open an SR to ask for a password to download it. In that same SR, please, provide the list of patches applied previously, so Support can determine if it is ok for you to apply the patch, or if a merged patch needs to be created for you.

8. When in doubt, ask ORACLE Support if a patch can be applied by you without conflict issues.