Catalog downgrade from OBIEE 12.2.1.1.0 to 12.2.1.0.0 — Oracle Analytics

Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Catalog downgrade from OBIEE 12.2.1.1.0 to 12.2.1.0.0

Received Response
41
Views
7
Comments
Ibag
Ibag Rank 3 - Community Apprentice
edited Aug 13, 2024 6:12PM in Oracle Analytics Cloud and Server

Dear Experts,

Is there a way to downgrade webcatalog from a higher version to a lower version with utility.?(As we downgrade rpd model). If so please let me know.

Thanks in advance for your help.

Regards,

Ibag

Answers

  • rmoff
    rmoff Rank 6 - Analytics Lead

    Nope. XML hacking only; completely unsupported and at your own risk.

  • Gianni Ceresa
    Gianni Ceresa Mod

    Did it really change a lot? I don't really see what doesn't work from a XML point of view, the .atr can be the one complaining maybe ...

  • rmoff
    rmoff Rank 6 - Analytics Lead

    Sorry yes you're right - version number is held in the .atr. XML hacking just to remove unsupported content, of which as you say there wasn't much difference in the two releases.

  • Ibag
    Ibag Rank 3 - Community Apprentice

    Hi,

    Thanks for your replies, but I don't see any xml associated with atr file. Instead of it is available in catalog file(ex: catalog,catalog.atr), but in that there is no xml version details. Pl find below screenshots. 1st from atr file. 2nd from catalog file. 2nd file just says xml version 1.0, but while unarchiving in OBIEE I am getting below error: "Expected Min 11 and Max 15, but provided 16", something like this. Can we trace where xml version getting encrypted? can we modify xml. Any possible way to do this?

    pastedImage_0.png

    pastedImage_1.png

  • Gianni Ceresa
    Gianni Ceresa Mod

    That's what we said with @rmoff earlier....

    The XML probably works without problems (99%), the issue is in the .atr file. Don't even try to look inside, it's a binary file ...

    Everything (every single object!!) in the webcatalog has an .atr file associated with it, the .atr contains permissions, object type and few other things (owner etc.)

    In your own screenshot you see the .atr file track the version the object has been created, that's only the visible part, the unreadable binary code code does probably contains this "16" the error complains about.

    What you can try to validate that the XML work is that you create in your 12.2.1.0.0 an analysis by hand and then take the XML of your 12.2.1.1.0 of an analysis and paste it into the Advanced tab. There you will be fixed if the XML is compatible or has a version or something like (pretty sure it doesn't and it will work without problems).

    The .atr files there isn't a lot you can do about them, after all they are binaries ...

  • Ibag
    Ibag Rank 3 - Community Apprentice

    Thanks Gianni Ceresa,

    Copying XML would work, but there are hundreds of reports to migrate. This is going to be huge junk.

  • rmoff
    rmoff Rank 6 - Analytics Lead

    Why are you even in the position to be migrating hundreds of reports *back* a version?