Download Oracle Database 11g Client (11.2.0.2.0) For Microsoft Windows 64-bit

1 view

Skip to first unread message

Message has been deleted

Edel Dieringer

unread,

Jul 9, 2024, 9:30:24 PM7/9/24

to baranfora

The most recent changes will be highlighted with a "New" or "Updated" icon to help you quickly identify the modifications. (For a history of modifications, see the Change Record Table at the bottom of the document.)

To help you plan ahead, below is a visual roadmap that captures Oracle Database Releases from 11.2 onward, showing the lifetime support stages (Premier, Extended, etc.) and the Error Correction windows for each release. Note, not all releases are eligible for Extended Support (i.e. 12.2.0.1, 18c, 21c).

download oracle database 11g client (11.2.0.2.0) for microsoft windows 64-bit

DESCARGAR https://shurll.com/2yOqPF

Oracle is mindful of the unprecedented economic and business disruption our customers faced in 2020. We decided to not promote our Database 20c Preview version to General Availability. Instead, we incorporated all of the 20c functionality into the 21c release and made 21c available initially in our Autonomous Database Free Tier so that all can test drive the new features and enhancements for free.

For questions related to certification combinations and Lifetime Support agreements with other Oracle products like Oracle E-Business Suite, Oracle JD Edwards, Oracle PeopleSoft, and Oracle Siebel, please contact your Oracle Account Representative.

These are server releases unless otherwise specified. Server releases always include the native word size client (e.g. 64-bit). Where the platform supports it, a 32-bit and 64-bit client is also part of the release.

1 Oracle Base Database Service (formerly Oracle Database Cloud Service) and Exadata Database Service (formerly Exadata Cloud Service and Exadata Cloud@Customer) follow the same support life and error correction schedule as on-premises dates unless otherwise noted in Table 1 above (for example, 11.2.0.4 MDS). Also, Extended Support is bundled with both the license-included and BYOL versions of these services and does not require additional fees. These services will not be covered under Sustaining Support and Oracle makes no commitment that any cloud service instances will continue to run after the end of their support life (Premier, extended, error correction, or MDS). We will not disable any installed databases upon the expiration of support, but the underlying infrastructure will continue to be updated. The infrastructure updates may render the unpatched databases inoperable. We make no commitment as to how long any unpatched databases will continue to run.

2 Oracle's current plan for Oracle Autonomous Database - Shared Exadata Infrastructure, Oracle Autonomous Database - Dedicated Exadata Infrastructure, Autonomous Database on Exadata Cloud@Customer services is to support Long Term Release versions for a similar period of time found for those major releases when deployed on-premises. The intent of this plan is to provide stability of service experience for the thousands of critical database deployments found in Oracle Cloud. Additionally, we will at times make available Innovation Releases as part of the Autonomous Database Cloud Services. Innovation Releases, when provided, will be supported for a shorter period of time as compared to a Long Term Release, similar to what is found for those releases when deployed on-premises. Oracle reserves the right to change this plan with changing business requirements. Any change will take into account that stability is of utmost importance to Oracle's many thousands of mission critical deployments.

Only significant changes to content (such as new or changed dates, new releases, or clarifications) beginning Jan 1, 2020 are listed below. Minor wording or formatting changes are not recorded.

Wording for Cloud services modified to say: These services will not be covered under Sustaining Support and Oracle makes no commitment that any cloud service instances will continue to run after the end of their support life (Premier, extended, error correction, or MDS).

Amended 12.1.0.2 EXS extension to specifically call out the Windows exception end date is the 'Patching/Error Correction end date'. In certify, the EXS date for Windows platforms will still show as July 31, 2022 due to a tool limitation but patching (including bundles) will stop July 31, 2021.

Restructured original document, removed older releases that are no longer covered under Premier or Extended Support, removed unnecessary information contained in other documents, Added estimated release dates for annual release 20c.

In ArcMap 10.8.1 we are faced with a "Cannot connect to database because the database client software failed to load. Be sure the database client software is installed and configured correctly." message when trying to register a 19c Oracle database with a 10.8.1 federated ArcGIS Server.

The Oracle database, ArcGIS Desktop, and ArcGIS Server are on separate VMs. The ArcGIS Desktop VM has the 32-bit database client installed. While the ArcGIS Server VM has the 64-bit client installed. We restarted each VM after the database client installs, but are still faced with the same error.

Do you have the sqlnet.ora and tnsnames.ora files configured and in the corresponding folder?
Also check the communication between the servers and the instance, and verify the port it uses (you could use a telnet port). It depends on the client you installed, but you could also use in cmd > tnsping (configured in the tnsnames file).

Use SQLPlus to test the connection to the Oracle Database, do this on the ArcMap machine and on the ArcGIS Server machine, that is the first step to test if the Oracle Client is working fine, if you are using Oracle Instant Client then make sure to download SQLPlus for Oracle Instant Client and unzip that on the same location of the Oracle Instant Client software, also double check if you set the correct PATH variable, there is one for the system and one for the user. I hope this helps.

Note: if you are using TNSNAMES.ORA file then make sure the file is under the correct location, then test the database connection with SQLPlus to make sure the TNSNAMES.ORA file is working.

How do I ensure that my Oracle Net files like "tnsnames.ora" and "sqlnet.ora" are being used in Instant Client?
Files like "tnsnames.ora", "sqlnet.ora" and "oraaccess.xml" will be located by Instant Client by setting the TNS_ADMIN environment variable or registry entry to the directory containing the files.
Use the full directory path; do not include a file name.
Alternatively create a subdirectory "network/admin" under the Instant Client directory for the Oracle Net files. This is the default location and so no TNS_ADMIN variable is required.
*/
--under $ORACLE_CLIENT_HOME/network/admin create a file named sqlnet.ora and add this line to enable windows authentication and save the file

Thanks a lot for the SQLPlus tip. We were able to identify that our ArcGIS Server was resulting in an access denied message when launching sqlplus unless running it from the cmd prompt as an admin. What we ended up doing was uninstalling the oracle client on the server and reinstalling it not as an admin. We were able to register the database successfully, but still are receiving an error code when publishing relating to the database not being registered. "error 001272: analyzer errors were encountered (codes = 90)"

Click Validate All

Note: if your map document has layers from different geodatabase connection users then you must register each one as a new Data Store in Server Manager.

Please, read carefully the database connection best practices in the link below.
Database Connections Best Practices

Thanks for the documentation, but these steps have been already taken. The only difference is I completed them in the ArcCatalog pane from ArcMap. I successfully registered the database with ArcGIS Server and they validate successfully.

All layers come from a single geodatabase connection user and upon "Analyze" in the Service Editor window, no errors appear denoting a unregistered layer. Below is the error that pops up when publishing.

But I'm still getting "DataSource.Error: The provider being used is deprecated: 'System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.'. Please visit =272376 to install the official provider."

What worked for us here was uninstalling 12.2 and then installing 12.1 . We grabbed the newest link off the oracle site without thinking about it, but I guess microsoft specifies the version for a reason. Powerbi doesn't appear to play nicely with 12.2

I couldn't get Power BI Desktop to work with the Oracle19 ODAC tools. However a clean install of The full ODAC tools for 12.2.0.1.1 did work. I didn't need to install an "Oracle Client" at all.

NOTE: Make sure to check the box about installing the drivers machine wide.

So it seems Power BI Desktop doesn't see the drivers because Oracle no longer installs them at the machine level. If someone smarter than me with ODP.NET knows how to add that machine level configuration, I would be interested in trying it out.

I have ODAC 19.3 working with some help from google. I'm going to post it as a new topic, rather than hide it down here, so that it's easier to find. Once I've posted it I will come back add add a link to it.

So, I am really new to this stuff and there seems to be several files to download, can you refer me to the link in Oracel or file name of what I should download? Thanks for responding, your post is a few years old now lol

Is this what you refer to as oracle home the the ODAC should have installed in client_1 folder. How do I achieve this in the installation? (I guess I have to specify some other than the default path).

I have installed a complete test environment on my virtual PC consisting of oracle database, oracle business intelligence servers. So I probaly have another scenario than end users that do not run the DB server and fusion middelware on the computer.

I have had a lot of problems during installation of these components but have always figures a way around it, so I guess you have found the answer to this final issue of the Power BI / Oracle test envrionment installation.