OBIEE 12c: Not able to connect Catalog Manager from Client machine on client windows 10

user12018538

Hello,

When I run the catalog manager, I get the error message below and the attachment.

What should I do so that I can use the catalog manager?

Configuration :

Oracle Business Intelligence Catalog Manager On : 12.2.1.0

Client OS : Windows 10

Java jre1.8.0_231

database server: Oracle serveur 11g

JAVA_HOME=C:\Program Files\Java\jdk1.8.0_231\jre

Path=C:\ORA12\product\12.2.0\client_1;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;

Error :

C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\web\catalogmanager>set DOMAIN_HOME=C:\Oracle\Middleware\Oracle_Home\domains\bi\bin\\..

C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\web\catalogmanager>call C:\Oracle\Middleware\Oracle_Home\domains\bi\bin\\..\..\..\bi\bifoundation\web\catalogmanager\runcatinternal.cmd

Instance Name is missing. Using default Instance Name: obips1

env:

"PATH: C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\server\bin;C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\web\bin;C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\odbc\lib;C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\lib;C:\Oracle\Middleware\Oracle_Home\bi\lib;C:\Oracle\Middleware\Oracle_Home\bi\..\lib   ;C:\Informatica\PowerCenter10.2\clients\tools\datadirect;D:\utilisat\XS2E0674\Mes documents\vtom\VTOM\BIN;D:\utilisat\XS2E0674\Mes documents\vtom\ABM\BIN;C:\ORA12\product\12.2.0\client_1;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\PuTTY\;C:\Program Files\TortoiseSVN\bin;C:\Users\xs2e0674\AppData\Local\Microsoft\WindowsApps;;\bin"

"INSTANCE_NAME: obips1"

"MW_HOME: C:\Oracle\Middleware\Oracle_Home\bi\.."

"ORACLE_INSTANCE: "

"BI_PRODUCT_HOME: C:\Oracle\Middleware\Oracle_Home\bi"

"DOMAIN_HOME: C:\Oracle\Middleware\Oracle_Home\domains\bi\bin\\.."

"ORACLE_BI_APPLICATION: "

"COMPONENT_TYPE: "

"COMPONENT_NAME: "

"ORACLE_BIPS_INSTANCE_CONFIGDIR: C:\Oracle\Middleware\Oracle_Home\domains\bi\bin\\..\config\fmwconfig\biconfig\OBIPS"

"ORACLE_BIPS_INSTANCE_DIAGNOSTICSDIR: C:\Oracle\Middleware\Oracle_Home\domains\bi\bin\\..\servers\obips1"

"ORACLE_BIPS_INSTANCE_TEMPDIR: C:\Oracle\Middleware\Oracle_Home\domains\bi\bin\\..\servers\obips1\tmp   "

"JAVA_HOME: C:\Oracle\Middleware\Oracle_Home\bi\..\oracle_common\jdk\jre"

+ attachement

Joel

Can you change your JAVA_HOME to C:\Program Files\Java\jdk1.8.0_231

https://support.oracle.com/knowledge/Enterprise%20Performance%20Management%20and%20Business%20Intelligence/2537688_1.htm…

Gianni Ceresa

Hi,

Are you sure about the problem?

You say you can't launch (start) Catalog Manager, while your screenshot (in French) says it couldn't connect to the OBIEE server.

In general you get that message after starting Catalog Manager and entering the details to connect to an online OBIEE server, but Catalog Manager doesn't seem to have any problem itself ...

Joel

That’s one reason why it’s good to be multilingual!

user12018538

I change my JAVA_HOME to C:\Program Files\Java\jdk1.8.0_231 but I still can't connect to the catalog manager!

JAVA_HOME=C:\Program Files\Java\jdk1.8.0_231

user12018538

How can I connect to the catalog manager? For information, under windows 7 with the client 11.1.1.7, I have no problem to connect with the same settings!

Thanks for your help

[Deleted User]

You keep changing the issue which isn't good forum etiquette to begin with and aren't being very precise. Please be more specific and stick to an issue at a time.

Also:

I think your font isn’t large enough yet

Gianni Ceresa

"same settings" : you are trying to connect to an OBIEE 11.1.1.7 with the 12.2.1.0 Catalog Manager? Because it doesn't work like that ...

Relax, take a step back and simply describe what you are trying to do because right now it's fairly confusing.

You have a Windows 10 desktop/laptop/environment, you install the 12.2.1.0 Client tools which give you Catalog Manager 12.2.1.0.

To what are you trying to connect? What exact version is that server? What is the history of that server? Fresh install? SSL yes or no?

Well ... tell us a bit more because we don't see your screen

user12018538

Thank for your help !

Previously I had a Windows 7 computer with a client in 11.1.1.7. Everything (catalog manager) worked perfectly.

The server (11G release 11.1.1.7) is under SUN SOLARIS. The server installation was done in 2015 and can't migrate to the higher version.  There is no SSL.

The client 11.1.1.7. is not compatible with Windows 10.
So I downloaded the new client in 12.2.1.0.

Now, I tying to connect to an OBIEE serveur  with the 12.2.1.0 Catalog Manager.

The job manager is ok just like Administration.  But the catalog manager starts but I can't connect because I have the error present as an attachment.

Can you help me please?

Thanks a lot.

Gianni Ceresa

Install Virtualbox on your Windows 10, create a VM using Windows 7 and install the 11.1.1.7 Client tools.

This the the way to go for your need.

You can't use 12c tools for an 11.1.1.7 server. Any RPD you save with a 12c Admin tool will never work on your 11g server, the BI Server will not start.

Job manager works because it's showing things mainly and that part didn't really change.

Catalog manager can't work because the 12c catalog is different in format than the 11g one. The .atr files changed their syntax and even it it opens it will not work.

That's why the 12c Catalog Manager try to use a never version of webservice which wasn't available on 11.1.1.7 and this is why you have that error.

There is really no workaround, you are using a super old OBIEE server and therefore you must keep using the same old tools. A virtual machine with a old OS is the only way to have them working.

Gianni Ceresa

user12018538 wrote:The server (11G release 11.1.1.7) is under SUN SOLARIS. The server installation was done in 2015 and can't migrate to the higher version. 

It's weird that in 2015 the choice has been for OBIEE 11.1.1.7 as 11.1.1.9 was already available and even the very first 12c was released in October 2015.

Maybe it's time to talk about upgrade to 12c again, it works on Solaris as well if you really have to stick to that kind of server. (Il n'y a pas trop d'autre solution à ce point, 11.1.1.7 est hors tout support!)