Hi @Jaco P. ,

You can actually fix the issue with your local Windows machine BI catalog manager by applying the same path you linked (the one you applied on the server).

I just did it and it works fine

Of course this isn't an official supported way, so backup any file you are going to edit before to edit them (or be ready to reinstall the OBIEE clients in case it goes wrong).

What I did is download the patch you linked for Windows x64, extract the content and just do the same work as opatch does on the server ...

Inside etc/config/actions.xml you see what the patch must do (replace files), on a local client install it must replace 4 files in 2 JAR and that's it !

These 2 JAR are:

\bi\bifoundation\web\catalogmanager\plugins\catalogmanager.jar

\bi\bifoundation\web\catalogmanager\plugins\com.siebel.analytics.web.catalogmanager_1.0.0.jar

(do a backup of these 2 so you can revert in few clicks)

Using winrar I opened the files (they are just ZIP in the end) and replaced com/siebel/analytics/web/catalogmanager/PluginManager.class and com/siebel/analytics/web/catalogmanager/SOAPConnectionManager.class in the first one with the 2 same files you extracted from the patch (they are in \files\oracle.bi.fndn\12.2.1.2.0\bi.symbol\bifoundation\web\catalogmanager\plugins\catalogmanager.jar\com\siebel\analytics\web\catalogmanager).

In the 2nd JAR (com.siebel...) the thing is that you have to change files inside catalogmanager.jar which is into the com.siebel.analytics.web.catalogmanager_1.0.0.jar, but again same work: using winrar I deleted original files inside the JAR and add the ones I got from the patch.

After replacing the 4 .class in the 2 JAR I don't have the error anymore using the Catalog Manager on my local Windows machine.

@Rizwan M : as the patch was posted in relation to an error when looking at permissions I can't say if it's going to fix your problem as well or not ... If still stuck with the error you can definitely give it a try (takes 5 minutes or less) and you will be fixed.

Ah, interesting they suggest to hack their JAR as apparently it's one of the most illegal things ever

Based on past past releases the client tool isn't patchable as there are few pieces of opatch but not the main files, so they just have to release a new one. But I guess they will just wait for the next release and in the meantime do a copy/paste of the answer for all the SR