Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 17 Oracle Analytics Lounge
- 218 Oracle Analytics News
- 44 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 81 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
How to find Catalog version in OBIEE 11.1.1.7.0
Hi,
We are upgrading OBIEE 11g to 12c. As part of upgrade per-requisite it is mentioned like "Sometimes when customers upgraded to 11.1.1.7 from previous 11g version, they did not run the full catalog upgrade. The consequence is that the version stored in the catalog is 11.1.1.3, 11.1.1.5, or 11.1.1.6, even though the catalog is being used on 11.1.1.7 environment."
How can we find current catalog version ?
Please advise!
Sometimes when customers upgraded to 11.1.1.7 from previ
ous 11g version, they did not run the full catalog upgrade. The consequence is that the version stored in the catalog is 11.1.1.3, 11.1.1.5, or 11.1.1.6, even though the catalog is being used on 11.1.1.7 environment.
Answers
-
It's not about finding the current version as the problem is often that 80% of the catalog is on the right version but you still have objects with a older version.
So just check/update the full catalog.
If you login to OBIEE, go to the Administration page and then click on "Scan and Update Catalog Objects That Require Updates" you align all the catalog objects.
The page will take care to scan objects and update what needed.
0 -
Sunday night OBI Jeopardy:
"What is contained within the root.atr file?"
0 -
The XML also contains an optional version reference:
For example 11.1.1.7 was only "201201160" and now 12c accept "201201160" or "201302130".
Doesn't look like it's something linked with the "Scan and Update Catalog Objects That Require Updates" as running it doesn't update this number, but can maybe have in impact in future releases if they need to fix a XML reference and so will use this attribute to detect objects requiring the fix or things like that ...
0 -
.atr files are easier Gianni ;-)
0 -
They are different
OBIEE actually use the .atr file for the check, the XML is probably there for future usage if needed (bug fixing requiring a mass change of XML to be fixed).
But the main point is still that it's not something to be checked by hand as it must be checked for everything ! Every single file in the catalog, even the hidden ones managing security etc. So use the OBIEE Administration page, click, close your eyes and .... voilà: done ! (with a link to a list of updated objects).
0 -
Yeah but the .atr version stamp also reflects what happens when you run OBIPS with instanceconfig.ini set to UpgradeAndExit.
0 -
Hi,
As per root.atr file it is showing below information :- We are curently on 11.1.1.7.0 version.
Build% 11.1.1.7.0 (Build 130303.2025 64-bit) Please advise if its ok and we can go ahead for migration tool process.
Thanks,
Mukesh
0 -
Please read what has been posted !
Gianni Ceresa wrote:It's not about finding the current version as the problem is often that 80% of the catalog is on the right version but you still have objects with a older version.So just check/update the full catalog.If you login to OBIEE, go to the Administration page and then click on "Scan and Update Catalog Objects That Require Updates" you align all the catalog objects.The page will take care to scan objects and update what needed.
So ....
Mukeshs wrote:As per root.atr file it is showing below information :- We are curently on 11.1.1.7.0 version.Build% 11.1.1.7.0 (Build 130303.2025 64-bit)Please advise if its ok and we can go ahead for migration tool process.
Did you open all the .atr files of your catalog ? Including the system and security objects?
I don't guess so, that's why there is a really useful simple page in the admin where with a click you check and update everything, in just one click.
So make that click and look at what you have on your screen.
0 -
Thanks Gianni & Christian for your useful advise!
0 -
Oracle says:
"Before upgrading from OBIEE 11g to OBIEE 12c, ensure that your 11.1.1.7 | 11.1.1.9 catalog is the correct version.
This is accomplished by running a full catalog upgrade (not Scan and Update in the Answers Administration link) on your current 11g catalog environment."
and
"When the full catalog upgraded is not executed, the result is the version stored in the catalog is not correct (i.e. 11.1.1.3, 11.1.1.5, or 11.1.1.6), even if the catalog is being used on an 11.1.1.7 environment."
So to be sure - you have to run the full upgrade by setting <UpgradeAndExit>true</UpgradeAndExit> in the instanceconfig.xml
I ran into this problem 2 times - there were serveral upgrades of BI System as written in the Oracle's comment above - but never a full catalog upgrade!BTW - Read the full document: "OBIEE 12c Pre-Upgrade Alert: Before Upgrading To 12c, Ensure your 11g Catalog Is Upgraded To the Correct Version (Doc ID 2068965.1)"
0
