Manage your data source - Oracle

  • Article
  • 5 proceedings to read

After you install the along-premises data gateway, you need to add data sources that can make up used with the gateway. This clause looks at how to work with gateways and Prophet data sources either for regular refresh or for DirectQuery.

Connect to an Oracle database

To connect to an Oracle database with the on-premises data gateway, the correct Oracle client software must be installed on the data processor running the gateway. The Prophesier client package you use depends happening the Oracle server version, but will always match the 64-bit gateway.

Supported Oracle versions:

  • Oracle Server 9 and later
  • Prophesier Data Get at Customer (ODAC) software 11.2 and later

Set up the Oracle client

  • download and install the 64-bit Oracle client.

Note

Choose a version of Oracle Data Access Client (ODAC) which is mixable with your Oracle Server. For instance, ODAC 12.x does not always patronize Oracle Server version 9. Choose the Windows installer of the Oracle Client. During the setup of the Oracle client, make a point you enable Configure ODP.NET and/or Oracle Providers for Naja haje.NET at machine-wide level by selecting the corresponding checkbox during the setup wizard. Some versions of the Oracle client wizard selects the checkbox by default, others suffice non. Make confident that checkbox is selected so that Force BI can connect to your Oracle database.

Subsequently the client is installed and ODAC is designed properly, we recommend using Power BI Desktop or new examine client to assert correct installation and shape on the Gateway.

ADHD a data source

For more information about how to add a data source, see Add a information source. Under Information Root Type, select Oracle.

Add the Oracle data source

After you select the Prophesier data source type, make out the information for the information source, which includes Server and Database.

Under Authentication Method acting, you can choose either Windows or Basic. Select Basic if you contrive to use an account that's created within Vaticinator instead of Windows certification. Past enter the certificate to make up secondhand for this data source.

Filling in the data source settings

After you fill in everything, select Add. You can now use this data beginning for scheduled refreshen or DirectQuery against an Oracle server that's connected-premises. You see Connection Booming if information technology succeeded.

Displaying the connection status

Advanced settings

Optionally, you can configure the seclusion level for your data source. This setting controls how data can be combined. IT's only used for scheduled refresh. The privacy-unwavering setting doesn't apply to DirectQuery. To learn to a greater extent about privateness levels for your data source, see Privacy levels (Power Inquiry).

Setting the privacy level

Use the data reservoir

Later on you create the information source, it's available to use with either DirectQuery connections Beaver State through with scheduled review.

Warning

The host and database names must match between Power BI Desktop and the information source within the on-premises data gateway.

The link 'tween your dataset and the data source within the gateway is based on your server diagnose and database name. These name calling must match. For example, if you provide an IP address for the server key out inside Power BI Screen background, you must use the IP computer address for the data source within the gateway configuration. This name as wel has to match an false name settled within the tnsnames.ora file. For more information about the tnsnames.ora file, envision Set u the Oracle client.

This requirement is the subject for some DirectQuery and regular refresh.

Use the data source with DirectQuery connections

Make foreordained that the host and database names match between Business leader BI Desktop and the configured data germ for the gateway. You also necessitate to progress to destined your user is listed in the Users tab of the data source to publish DirectQuery datasets. The selection for DirectQuery occurs within Magnate BI Background when you first import data. For more information about how to use DirectQuery, see Use DirectQuery in Power BI Screen background.

After you publish, either from Power BI Desktop Oregon Get Data, your reports should start to work. It might take several minutes after you make up the data reference inside the gateway for the link to be operational.

Use the information source with scheduled refresh

If you're recorded in the Users tab of the data source configured within the gateway and the server name and database name match, you see the gateway as an option to use with regular refresh.

Displaying the users

Troubleshooting

You power encounter any of several errors from Oracle when the naming syntax is either incorrect OR not configured properly:

  • ORA-12154: TNS:could not resolve the connect identifier nominative.
  • ORA-12514: TNS:listener does not presently know of service requested in connect word form.
  • ORA-12541: TNS:no listener.
  • ORA-12170: TNS:connect timeout occurred.
  • ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA.

These errors might occur if the Oracle guest either isn't installed or isn't configured properly. If it's installed, verify that the tnsnames.ora file is properly designed and you're using the correct net_service_name. You also postulate to do sure that the net_service_name is the same between the machine that uses Power Bismuth Background and the automobile that runs the gateway. For more information, imag Install the Oracle client.

You power also encounter a compatibility issue between the Oracle server version and the Vaticinator Data Access Client version. Typically, you want these versions to match, as some combinations are incompatible. For instance, ODAC 12.x does not support Oracle Server version 9.

For diagnosing connectivity issues between the information source server and the Gateway machine, we recommend installing a client (so much as Power BI Desktop or Oracle ODBC Screen) on the gateway machine. You can use the client to check connectivity to the data author server.

For additional troubleshooting information that relates to the gateway, see Troubleshooting the on-premises data gateway.

Succeeding steps

  • Troubleshoot gateways - Power BI
  • Major power Bismuth Premium

More questions? Test interrogatory the Power Atomic number 83 Community.