OBIEE 12.2.1.4 Migration from 11.1.1.7 Question

KRC Eric

For clarification, can anyone confirm the following regarding our converted 11g to 12c OBIEE system & the Compatibility Framework for Oracle BI Server?

1) When we first created the 12c BI server, compatibility mode to 11g is not set by default.

2) It is my observation that because we migrated our 11g system to the new 12c, compatibility mode got set to 11.1.1.9 by the migration tool.  This is based on the current values in our NQSConfig.INI and bi-config.xml files & the fact that NQSConfig.INI compatibility takes precedence over bi-config.xml:

Current value in the NQSConfig.INI file:

[COMPATIBILITY]

COMPATIBLE_RELEASE = "11.1.1.9";

Current value in the bi-config.xml file:

<bi:compat-mode-11g>false</bi:compat-mode-11g>

3) In OEM for OBIEE, under the BI instance>Configuration>General Configuration, the dialogue box for 11g Compatibility mode is unchecked.

4) According to the Oracle Documentation (Fusion Middleware Migration Guide for Oracle Business Intelligence)

https://docs.oracle.com/middleware/1221/core/BIMIG/GUID-BBA360BD-D784-400B-BB0C-D976D8CB495D.htm#BIMIG-GUID-BBA360BD-D78…

"The NQSConfig.INI file does not contain the COMPATIBLE_RELEASE parameter by default. The global bi:compat-mode-11g is the default flag and it applies to all Oracle BI EE components. When the bi:compat-mode-11g element in the bi-config.xml file is set to true, the BI Server compatibility framework behaves as if the COMPATIBLE_RELEASE were set to 11.1.1.9 and it disables any features or bug fixes that would cause major compatibility issues during migration from 11g to 12c. However, if you explicitly edit the NQSConfig.INI file to set the COMPATIBLE_RELEASE parameter or any other compatibility flag, then the setting in the NQSConfig.INI file takes precedence over the global bi:compat-mode-11g flag specified in the bi-config.xml file."

5) Based on my interpretation of the documentation & our current NQSConfig.INI settings, we are now running our BI system in 11g compatibility mode.  If we want to test our migrated BI system dashboards & Answers requests under a true 12c environment, we need to remove the COMPATIBLE_RELEASE = "11.1.1.9"; entry from the NQSConfig.INI file and bounce services.   Am I interpreting this correctly?

6) Has anyone had a need to run BI in 11g compatibility mode?

Thanks!

Eric

Christian Berg-0racle

Hi Eric,

a) Long story short: If compatibility mode is set, then something is rotten at the core since you will never be able to say "we're really on 12 and things are running smoothly"

b) Migration tool - in itself a source of so many problems.

c) Yes. OUT with it.

User_HE5XF

https://community.oracle.com/tech/apps-infra/discussion/comment/15063869#Comment_15063869

We are experiencing the same issue. If we do not set the compatibility mode, the formatting is off on many of our reports. Is this expected behaviour? Any tips to trouble shoot this issue?

Christian Berg-0racle

https://community.oracle.com/tech/apps-infra/discussion/comment/16774615#Comment_16774615

If you have an issue please open your own thread where you clearly and precisely specify your issue and give a fully detailed explanation of the exact versions used etc. Not just a one-time.

This thread is belonged to someone else and is done and answered. Please don't hijack threads.

KRC Eric

Hi User_HE5XF,

I have no problem answering. I had to go back & check. It looks like we left COMPATIBLE_RELEASE = "11.1.1.9" on our Dev/Test system but commented it out on our Production system & worked through the issues. Hidden Columns on pivot tables had to be fixed. Uncheck the ‘Hide’ attribute on Column Properties / Column Format tab and ‘exclude’ the column from any table views that do not want to see it.

We did have to eliminate the standard PDF headers / footers on reports designed for Excel download. I can't quite remember but we may have removed the report filter display at the bottom of reports. The PDF output was wrapping the last digit of a number to the next row. That appeared to be a problem on reports imported from 11g with alternate row ‘green-bar’ highlighting. The solution is to disable ‘row styling’ on the table properties and uncheck ‘wrap text’ on the column properties, although native 12c reports default to ‘wrap text’ and seem to work just fine in PDF output.

BI Publisher templates do not wrap on 12c like 11g. We shortened template names where possible.

Hope this helps!

Eric

User_HE5XF

https://community.oracle.com/tech/apps-infra/discussion/comment/16774709#Comment_16774709

Thanks a ton Eric. I am sorry for the delay and ackowledging your reply. We will try this and see how it works for us.

User_HE5XF

https://community.oracle.com/tech/apps-infra/discussion/comment/16774645#Comment_16774645

Thanks, Christian