Reply
Frequent Visitor
Posts: 15
Registered: ‎08-27-2015

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

Hi Viveka,

 

I'm definitely not an expert on Oracle databases or connecting to them.  I can only tell you what worked for me.  One thing I notice is that you installed the "Xcopy" files and I'm wondering if for some reason you didn't get all the files you need.

 

Also, there are several posts under the subject "Oracle" that have useful info that may help you.  If you do decide to reinstall the Oracle components, you need to uninstall what you've already done first.

 

Here's what I recently did on one of our machines that worked for me. 

  1. I downloaded the 64-bit ODAC121024_x64.zip file rather than the "Xcopy" file. 
  2. Put the zip file into a temporary directory and unzip it there.  Make sure that there are no spaces in the directory name or path to it.
  3. When you've unzipped it, you should see the "setup" application.  Run that and eventually you'll see the "configuration installer".  You should be able to stay with the defaults for most steps.
  4. When you get to the "DB Connection Configuration" step, it's important that you fill in the requested information.  Here are some tips.

    Connection Alias

    Enter what you want to name this database. When you get data in Power BI, you’ll use this as the “Server Name”.

    Port Number

    (default 1521) only change if necessary for your database

    Database Host Name

    This is how the database is found in your network. May be an IP address for the database server.

    Database Service Name

    (default to ORCL) This may be different for your database

     


    This is important since the installer sets up the tnsnames.ora file that the database client uses to connect with the Oracle database.
  5. After you made the entries, finish the installation process and reboot your machine.

You should now be able to get to your Oracle database with Power BI when you use "Get Data" and select the "Oracle" database option.

Frequent Visitor
Posts: 9
Registered: ‎06-17-2016

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

Hi Bfrancis,

 

I have installed 64-bit ODAC 12c Release 4 (12.1.0.2.4) Xcopy for Windows x64 as recommended by Power BI, Link

 

I have already reinstall the 64-bit ODAC 12c Release 4 (12.1.0.2.4) Xcopy two times, Now I will try your solution to install 64-bit ODAC121024_x64.zip but before that I am going to uninstall previously installed ODAC applications and install ODAC121024_x64.zip

 

Will let you know on this.

 

Regards,

Viveka

 

 

Established Member
Posts: 192
Registered: ‎01-08-2016

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

Hi Viveka, have you seen the email we sent to you? We had some additional instructions to get the trace files, because the traces you sent to us didn't have the error you've experienced.

 

Thanks

Frequent Visitor
Posts: 9
Registered: ‎06-17-2016

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

Hi Bfrancis,

 

Thanks a lot for your valuable solution and it works for me. I have uninstalled all oracle components and then install the ODAC121024_x64.zip and it works for me like a charm. 

 

Earlirt I have installed 64-bit ODAC 12c Release 4 (12.1.0.2.4) Xcopy for Windows x64 as recommended by Power BI, Link

 

Regards,

Viveka

Frequent Visitor
Posts: 16
Registered: ‎09-28-2016

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

worked for me!

 

Thanks

Visitor
Posts: 1
Registered: ‎02-16-2017

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

hi guys,

 

I had this exact error just now when trying to build relationship between tables. Follwoing some trial and error, I discovered that the drag and drop works by dragging the "many" column to the "one" column and not vice versa, which is what I was doing wrong initially! Odd! but here you go...

 

hope this helps someone else Smiley Happy

Frequent Visitor
Posts: 10
Registered: ‎03-03-2017

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

thanks this solution solved by issue, basically re-installing the oracle ODAC components solved the issue. Dont use the Xcopy version

Frequent Visitor
Posts: 10
Registered: ‎10-07-2015

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

The XCopy version works just fine, but you then have to manually

 

1) Add the ODAC root and \bin folder to your PATH environment variable.

2) Put a TNSNAMES.ora file in the Instant client's network\admin folder *OR* set up the TNSADMIN environment variable to point to your TNSNAMES.ora directory.

 

Hope this helps anyone else who doesn't need GBs of Oracle program bloat on their machine just to connect to a database!

Highlighted
Frequent Visitor
Posts: 10
Registered: ‎06-11-2017

Re: PowerBI desktop 64Bit oracle connection error Object reference not set to an instance of an obj

[ Edited ]

I was really hoping to get away with the XCOPY version as well, as all I need to do is set it up for use by the gateway and don't want to download and install GB's but so far unsuccessful. I get all kinds of "regedit" errors when I run the "install.bat" as admin in a command prompt. Forcing you to sign up for an account and then have this poorly documented process for installing drivers - clearly Oracle does not want people to use their software and I'll happily be migrating users. Almost as bad as SAP drivers (except them I could get to work in the end). Even PostgreSQL install was quick and easy.

 

How do you do nr2 you mention? I can't seem to find any files with extension .ora in the folder I extracted the source

 

"2) Put a TNSNAMES.ora file in the Instant client's network\admin folder *OR* set up the TNSADMIN environment variable to point to your TNSNAMES.ora directory.