OracleDatabase@Azure delivers all the performance, scale, and workload availability advantages of Oracle Database on OCI with the security, flexibility, and best-in-class services of Microsoft Azure, including best-in-class AI services like Azure OpenAI. This combination provides customers with more flexibility regarding where they run their workloads. It also provides a streamlined environment that simplifies cloud purchasing and management between Oracle Database and Azure services.
The new service delivers a fully integrated experience for deploying, managing, and using Oracle database instances within Azure. It enables organizations to drive breakthroughs in the cloud using their existing skills to leverage the best of Oracle and Microsoft capabilities directly within the Azure portal.
As a result of this expanded partnership, customers will have the choice to deploy their Azure services with their fully managed Oracle Database services all within a single datacenter, including support for Oracle Exadata Database services, Oracle Autonomous Database services, and Oracle Real Application Clusters (RAC). Oracle and Microsoft have also developed a joint support model to provide rapid response and resolution for mission-critical workloads.
Additionally, Oracle and Microsoft have significantly simplified the purchasing and contracting process. Customers will be able to purchase Oracle Database@Azure through Azure Marketplace, leveraging their existing Azure agreements. They will also be able to use their existing Oracle Database license benefits including Bring Your Own License and the Oracle Support Rewards program.
About Oracle
Oracle offers integrated suites of applications plus secure, autonomous infrastructure in the Oracle Cloud. For more information about Oracle (NYSE: ORCL), please visit us at
www.oracle.com.
Power BI Desktop needs the Oracle data providers installed at the machine level. After ODAC 12.2, Oracle removed this option from the install, which means out of the box Oracle 18.x and 19.x ODAC installs are not seen by Power BI Desktop. I've spent the last 24 hours installing and uninstalling various versions of ODAC trying to get them to work with Power BI Desktop.
I'm limiting this to the 64bit install (Because that is what I have) and .NET 4.0, becuase that is what Power BI Desktop needs.
I can now report I have ODAC 19.3 working with Power BI Desktop (May 2021). This is thanks to Google and a lot of digging around. I've put a link to the original article I found that helped me get the data providers installed, as this was not my own work! (Power BI Github comment ), I'm just documenting it here for others.
Check your Windows environment variables. Is the Oracle client you are trying to use the first oracle path in the PATH variable? Do you have TNS_ADMIN defined and pointing to a valid tnsnames.ora directory?
After all the hours spent trying to solve this issue it was my companies rolled out version of PBI Desktop. It was right in the article I had read 100 times but skimmed over because I have PBI desktop pushed to my machine. I had to have IT remote in to install.
If you downloaded Power BI Desktop from the Microsoft Store, you might be unable to connect to Oracle databases because of an Oracle driver issue. If you encounter this issue, the error message returned is: Object reference not set. This is an issue with how Oracle driver works in Windows UWP Apps. To address the issue, you have to do the following:
The cx_Oracle module loads Oracle Client libraries which communicateover Oracle Net to an existing database. Oracle Net is not a separateproduct: it is how the Oracle Client and Oracle Database communicate.
Add Oracle 21, 19, 18, 12 or 11.2 client libraries to your operating systemlibrary search path such as PATH on Windows or LD_LIBRARY_PATH onLinux. On macOS use init_oracle_client() in yourapplication to pass the Oracle Client directory name, seeUsing cx_Oracle.init_oracle_client() to set the Oracle Client directory. This is also usable on Windows.
Instant Client on Windows requires an appropriate Microsoft WindowsRedistributables, see Installing cx_Oracle on Windows. On Linux, the libaio(sometimes called libaio1) package is needed. Oracle Linux 8 alsoneeds the libnsl package.
Version 21 client libraries can connect to Oracle Database 12.1 or greater.Version 19, 18 and 12.2 client libraries can connect to Oracle Database 11.2or greater. Version 12.1 client libraries can connect to Oracle Database 10.2or greater. Version 11.2 client libraries can connect to Oracle Database 9.2or greater.
Locate your Oracle Database username and password, and the databaseconnection string. The connection string is commonly of the formathostname/servicename, using the hostname where the database isrunning, and using the service name of the Oracle Database instance.
cx_Oracle requires Oracle Client libraries. The libraries provide thenecessary network connectivity to access an Oracle Database instance.They also provide basic and advanced connection management and datafeatures to cx_Oracle.
cx_Oracle uses the shared library loading mechanism available on eachsupported platform to load the Oracle Client libraries at runtime. Itdoes not need to be rebuilt for different versions of the libraries.Since a single cx_Oracle binary can use different client versions andalso access multiple database versions, it is important yourapplication is tested in your intended release environments. NewerOracle clients support new features, such as the oraaccess.xml external configurationfile available with 12.1 or later clients, session pool improvements,improved high availability features, call timeouts, and other enhancements.
The cx_Oracle function clientversion() can be used todetermine which Oracle Client version is in use. The attributeConnection.version can be used to determine which Oracle Databaseversion a connection is accessing. These can then be used to adjust applicationbehavior accordingly. Attempts to use Oracle features that are not supported bya particular client/server library combination will result in runtime errors.
This will download and install a pre-compiled binary if one isavailable for yourarchitecture. If a pre-compiled binary is not available, the sourcewill be downloaded, compiled, and the resulting binary installed.Compiling cx_Oracle requires the Python.h header file. If you areusing the default python package, this file is in the python-develpackage or equivalent.
If you use optional Oracle configuration files such as tnsnames.ora,sqlnet.ora or oraaccess.xml with Instant Client, then put the filesin an accessible directory, for example in/opt/oracle/your_config_dir. Then use:
Alternatively, put the files in the network/admin subdirectory of InstantClient, for example in /opt/oracle/instantclient_21_1/network/admin.This is the default Oracle configuration directory for executables linkedwith this Instant Client.
Alternatively, for version 18 and earlier, every shell runningPython will need to have the environment variableLD_LIBRARY_PATH set to the appropriate directory for theInstant Client version. For example:
Alternatively, put the files in the network/admin subdirectory of InstantClient, for example in /usr/lib/oracle/21/client64/lib/network/admin.This is the default Oracle configuration directory for executables linkedwith this Instant Client.
This will download and install a pre-compiled binary if one isavailable for yourarchitecture. If a pre-compiled binary is not available, the sourcewill be downloaded, compiled, and the resulting binary installed.
Using cx_Oracle requires Oracle Client libraries to be installed.These provide the necessary network connectivity allowing cx_Oracleto access an Oracle Database instance. Oracle Client versions 19, 18,12 and 11.2 are supported.
If you use optional Oracle configuration files such as tnsnames.ora,sqlnet.ora or oraaccess.xml with Instant Client, then put the filesin an accessible directory, for example inC:\oracle\your_config_dir. Then use:
Alternatively, put the files in a network\admin subdirectory ofInstant Client, for example inC:\oracle\instantclient_19_11\network\admin. This is the defaultOracle configuration directory for executables linked with thisInstant Client.
If you use optional Oracle configuration files such as tnsnames.ora,sqlnet.ora or oraaccess.xml with Oracle Instant Client, then put thefiles in an accessible directory, for example in/Users/your_username/oracle/your_config_dir. Then use:
Alternatively, put the files in the network/admin subdirectory of OracleInstant Client, for example in/Users/your_username/Downloads/instantclient_19_8/network/admin. This is thedefault Oracle configuration directory for executables linked with thisInstant Client.
For other installation options such as installing through a proxy, seeinstructions above. Make sure the Oracle Client libraries are in the systemlibrary search path because cx_Oracle 7 does not support thecx_Oracle.init_oracle_client() method and does not support loading theOracle Client libraries from the directory containing the cx_Oracle modulebinary.
On Windows, if you are not usinginit_oracle_client(), then restart your command promptand use set PATH to check the environment variable has the correctOracle Client listed before any other Oracle directories.
On Linux, check the LD_LIBRARY_PATH environment variable containsthe Oracle Client library directory. If you are using Oracle InstantClient, a preferred alternative is to ensure a file in the/etc/ld.so.conf.d directory contains the path to the Instant Clientdirectory, and then run ldconfig.
3a8082e126