nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Online RPD: Data Source missing after name change

Charles M

Hi All,

I seemed to have lost my data source, after inadvertently changing the name in the ODBC Data Source Administrator. I reverted it back to the original name, but it still doesn't show up when I try to open the RPD in online mode. The connection works fine from the ODBC Data Source Administrator ...

It used to be in the box, at the bottom here:

How can I get it back?

Regards,

Charles

Find more posts tagged with

Accepted answers

All comments

Gianni Ceresa

Dumb question: did you restart the Admin tool after editing/renaming the ODBC source? Because it seems it get the list when it load at the beginning but doesn't refresh it anymore.

But never got the case: if the ODBC connection uses the right driver and you run the right (matching version) Admin tool it must be there.

So if you have various Admin tool versions make sure the ODBC is using the right driver matching your server version and you have the same version Admin tool open.

Charles M

Hi Gianni,

I did restart the Admin tool a few times since this happened, but no luck

It does look like I may have another version of the Admin tool on my local machine. I'm reviewing the settings/configurations at this time

Thanks,

Charles

Charles M

I de-installed both versions (11.1.1.7.0 & 11.1.1.9.0), and then re-installed only the .9 version. But, I am still finding the same issue.

I found this note: Open Button is Greyed Out and User is Unable To Open OBIEE Repository in Online Mode (Doc ID 1598325.1). Yet, none of the solutions fixed the issue

By the way ... are the client tools "hard-coded" with the information specific to the instance that they were downloaded from? For example, if I downloaded the tools off of the 'Dev' instance, will it have only that information?

Thanks,

Charles

Gianni Ceresa

Charles M wrote:By the way ... are the client tools "hard-coded" with the information specific to the instance that they were downloaded from? For example, if I downloaded the tools off of the 'Dev' instance, will it have only that information>

No, the tool only filter available connection by "version" (driver used). It has no idea of the environment from which you took it (or it would come with an ODBC connection setup by default). Did you try creating a new ODBC connection to the same server with another name just as a test? I guess there was also at some point issues with 32bit vs 64bit : ODBC exists in the 2 versions, so your Admin tool if it's a 64bit it can only see the 64bit ODBC sources etc.

By the way: what's your OS?

Charles M

Thanks Gianni! Creating a new ODBC connection against the same server, with a different name worked. Now I can see that connection in the Online-mode dialogue box:

I'm not exactly sure how it got fixed. But, maybe creating the new connection after the new driver was installed made it work? I had seen that it was using the .7 version of the driver before, now it has the .9:

So, knowing all of this. Can I add 2 more connections? One for the UAT instance and another for production? The whole reason for getting into this in the first place was so that I could connect online to our different environments.

Regards,

Charles

Gianni Ceresa

Charles M wrote:So, knowing all of this. Can I add 2 more connections? One for the UAT instance and another for production? The whole reason for getting into this in the first place was so that I could connect online to our different environments.

Not only you can, but you must do it

Or you will really struggle if every time you need to edit the ODBC connection. You can have an infinite (ok, maybe not as many as that) ODBC connections, the only rule is they have a different name. So you can have all your environments defined with their own ODBC connection, that's generally how you do things (as long as you are allowed to connect online to all the environments, but that's more a process thing).

ODBC connections are all stored in the registry of your Windows, so you would need to go there inside to make sure everything was fine with your old one which has been renamed, but not worth the effort.

The ODBC connection name has no impact on anything, what matter is the driver used and the host to which it connect. So just delete the "invisible" one and problem solved

Charles M

Thanks a lot Gianni! Also, for the good explanations along with helping me troubleshoot this.

I'm going to delete the problem connection and call it a day for this one ...

Regards,

Charles

Gianni Ceresa

Charles M wrote:I'm going to delete the problem connection and call it a day for this one ...

Beer time, sounds fair

Charles M

Ha ... only "calling it a day" on this issue. Still have others to work on

Eventually, I'll get to beer time!