How do I check the oracle client version?

How do I check the oracle client version installed from the OS level. I do know my database version I need to check which client is being used. Is there a table where this information is stored.

Add a comment

Help to improve this question by adding a comment

If you have an answer for this question, then please use the Your Answer form at the bottom of the page instead.

Assigned Tags

Related questions

8 Ответов

same was alredy discussed in the SAP WEB as general

you can find in st04-> detailed analysis menu->display V$ values->V$VERSION

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

Alert Moderator

You already have an active moderator alert for this content.

Add a comment

That is not correct.

The oracle client does not have to match the RDBMS version.

For example, Kernel 4.6D_EXT is linked against (uses) oracle client 9.2 but you could be using oracle 10g ( V$version will tell you that you are using 10.2.0.2, for example )

The note 521230 FAQ: Client software 9i or earlier on UNIX gives you an explanation and a list of what oracle client uses what kernel.

Currently, 46D_EXT and 6.40 needs 9.2 client and 700 uses 10 instantclient.

For 10g instant client is possible to know the exact version at OS level, you have to use genezi ( check note 819829 )

For 9.2, there is no such utility, therefore you will have to check the date and size and compare it with the ones delivered by SAP.

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

You can check it on System—>Status menu option. and then by clicking «Other kernel info» button next to «Navigate» button.

See in database information and check your db releases.

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

Alert Moderator

You already have an active moderator alert for this content.

Add a comment

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

You can check client version by running sqlplus -version from client machine.

When u install client it will create some log and xml files.Through those files also you can find your client version.

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

Alert Moderator

You already have an active moderator alert for this content.

Add a comment

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

disp+work.exe -V will tell you which OCI version was used during compiling and linking.

Oracle uses release independent DLL Names (Unix people would say Shared Libraries) and therefore the SAP Kernel will dynamically load any Oracle Client Version found in the standard DLL Load Path during startup.

If you have more versions installed on your computer and you are not shure which one is loaded you can use Process Explorer (freeware, see www.sysinternals.com) to find out which one is loaded. If they belong to an Oracle_home (up to release 9.2) refere to Oracle Universal Installers Inventory information in order to find out which exact version is used.

If an Oracle10 Instant Client is used, there is no corresponding Oracle_Home. In this case you can use Windows Explorer (right click on the DLL -for example oci.dll), select properties, the Version Tab and File Version).

But unfortunately Oracle is not updating the File Version every time they are patching something.

An SAP ABAP Server Integrated Resource is the version information disp+work.exe -V is listing (evquivalent to SM51 — Release Information).

Datenbank Client Library : OCI_10201_SHARE (10.2.0.2.0)

OCI_10201_SHARE is telling us the compile/link environment, the number in brackets (only available starting with Oracle10) tells us the the result of an Oracle Client GetVersion call. Unfortunately this one does also not reflect the installed Minipatch version up to now.

Here are some results on 10.2.0.2 Windows X86_64:

SM51: Datenbank Client Library : OCI_10201_SHARE (10.2.0.2.0)

Explorer (OCI.DLL located in the same directory as disp+work.exe):

Explorer (oraociicus10.dll — the instant client implementation, this version is the one actual since mini patch 10.2.0.2.5 and it was definitely changed in 10.2.0.2.5):

oracore10.dll — 10.2.0.1.0 Production

oranls10.dll — 10.2.0.1.0 Production

orasnls10.dll — 10.2.0.1.0 Production

oraunls10.dll — 10.2.0.1.0 Production

oravsn10.dll — 10.2.0.1.0 Production

oracommon10.dll — 10.2.0.1.0 Patch1

orageneric10.dll — 10.2.0.2.0 Patch2

oraclient10.dll — 10.2.0.2.0 Patch2

orapls10.dll — 10.2.0.1.0 Patch1

orasql10.dll — 10.2.0.1.0 Production

orahasgen10.dll — 10.2.0.1.0 Production

oraocrutl10.dll — 10.2.0.1.0 Production

oraocr10.dll — 10.2.0.1.0 Production

oraocrb10.dll — 10.2.0.1.0 Production

oranbeq10.dll — 10.2.0.1.0 Production

orantcp10.dll — 10.2.0.1.0 Production

oracommon10.dll from the rdbms server does report 10.2.0.2.0 Patch5 at the same time. compare it with the version information of oracommon10.dll included in oraociicus10.dll. Both patches are included in the same patchset (10.2.0.2.5).

there are two possible conclusions about this:

1. the version infomation is not very reliable.

2. the Oracle Patch and Build environment is not very reliable

Help to improve this answer by adding a comment

If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.

Alert Moderator

You already have an active moderator alert for this content.

What’s the best way to determine which version of Oracle client I’m running?

The subject says it all: What is the best way to determine the exact version of the oracle client I’m running? Our clients are all running Windows.

I found one suggestion to run the tnsping utility, without parameters, which does display the version information. Is there a better way?

Does the client install put this information in any sort of text file?

14 Answers 14

You can use the v$session_connect_info view against the current session ID ( SID from the USERENV namespace in SYS_CONTEXT ).

TNSPing command line will show the version. similarly, sqlPlus.exe will print its version. You can also go to the readme files in the ‘relnotes’ directory of your client install. Version 10.2 has a file named README_jdbc.txt, for example, which will tell you which version has been installed.

Issue #1: Multiple Oracle clients are installed.

A very common issue I see in my environment is that I see both workstations and (app) servers with multiple Oracle clients, sometimes as many as four, and possibly with different versions and architectures. If you are relying on the PATH and running a utility like SQLPLUS or TNSPING you’ll have one of two unacceptable results:

• either your PATH successfully resolves the executable and you get ONE version result
• or, the PATH didn’t resolve the executable, and you get no results.

Either way, you are blind to possibly multiple client installations.

Issue #2: Instant Client doesn’t have TNSPING, and sometimes doesn’t include SQL*Plus.

If a computer has the Oracle Instant Client (not the full client), then TNSPING is not included, and SQLPLUS is an optional-addon. So can’t rely on those tools being there. Furthermore, the Instant Client is sometimes installed as an unzip-and-go solution, so there’s no Oracle Inventory and nothing in HKLM.

Issue #3: Client was installed using «Custom», and ODBC, OLEDB, ODP.Net, and JDBC were not installed.

Obvious case, there will be no ODBC or JDBC readme’s to scrape version info from.

Solution:

One thing that the Instant client and the full client have in common is a DLL file called oraclient10.dll , oraclient11.dll , generally: oraclient*.dll . So let’s traverse the hard disk to find them and extract their version info. PowerShell is amazing at this and can do it in one line, reminds me of home sweet Unix. So you could do this programatically or even remotely.

Here’s the one-liner (sorry about the right scroll, but that’s the nature of one-liners, eh?). Supposing you’re already in a PowerShell:

And if you’re not in PowerShell, i.e. you’re simply in a CMD shell, then no problem, just call powershell » . » , as follows:

Example Outputs

Here’s some outputs from some of my systems. This bad citizen has 3 Oracle 11.2.0.3 clients. You can see that some of them are 32-bit and others are 64-bit:

Another system, this one has 10g client on the D:\

Caveats/Issues

This obviously requires PowerShell, which is standard in Windows 7+ and Server 2008 R2+. If you have XP (which you shouldn’t any more) you can easily install PowerShell.

I haven’t tried this on 8i/9i or 12c. If you are running 8i/9i, then there’s a good chance you are on an old OS as well and don’t have PowerShell and Heaven help you. It should work with 12c, since I see there is such a file oraclient12.dll that gets installed. I just don’t have a Windows 12c client to play with yet.

How do we check version of Oracle

How do we check version of Oracle on which we are working?

How do we check the version of the interface on which we are working?

6 Answers 6

select banner from v$version;

you can also use.

select version from PRODUCT_COMPONENT_VERSION where rownum = 1;

There are multiple ways, to list a few of them :

For serverside versions:

For client side versions, it depends on the client. i.e for python:

As a complement, if you are using an OCI-based client interface:

• OCIServerVersion will return the version string of the Oracle server
• OCIClientVersion will return the version string of your Oracle client

There are multiple ways to check the version in Oracle.

Oracle maintains version information in V$VERSION, PRODUCT_COMPONENT_VERSION data dictionary Views, or Metadata Table. Just run a query against these views to find out the database version.

Use dbms_utility.Db_version package to check oracle version

Not the answer you’re looking for? Browse other questions tagged sql oracle version or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.4.16.39093

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Check Oracle Version

1. If you just want to check the version information of the Oracle database, simply connect and login to the Oracle database with SQL *Plus. Upon login, you will see:

SQL*Plus: Release 9.2.0.6.0 – Production on Tue Oct 18 17:58:57 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 – 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 – Production

The first italic number is the version of the SQL*Plus client and the second italic number is the version of Oracle database which you are connected to .

2. Retrieve the version information from v$version table by using SQL*Plus. In this table you can find version information on Oracle, PL/SQL, etc.

To retrieve the version information for Oracle, you execute the following SQL statement:

It should return something like this:

Banner
————————————————————————————–
Oracle9i Enterprise Edition Release 9.2.0.1.0 – 64bit Production

3. Version information can also be checked from Installed Products from the Oracle Universal Installer. It will tells you what products is installed on the machine and also its version information too.

In Unix, the installer is located at $ORACLE_HOME/bin/runInstaller.

In Windows, access the installer by Start -> All Programs -> Oracle Installed Products -> Universal Installer.

3 Oracle Database Preinstallation Tasks

This chapter describes the tasks that you must complete before you start Oracle Universal Installer.

This guide contains information required to install Oracle Database 12 c . Ensure that you review information related to the platform on which you intend to install Oracle Database 12 c .

To use Oracle Automatic Storage Management (Oracle ASM) or Oracle Restart, you must first install Oracle Grid Infrastructure for a standalone server before you install and create the database. Otherwise, you must manually register the database with Oracle Restart. See «Installing Oracle Grid Infrastructure for a Standalone Server for an Existing Database»

To install Oracle Grid Infrastructure for a standalone server, see «Requirements for an Oracle Grid Infrastructure for a Standalone Server Installation» and to install Oracle Grid Infrastructure for a cluster, see Oracle Grid Infrastructure Installation Guide for Microsoft Windows x64 (64-Bit) before you proceed with the database preinstallation tasks.

This chapter includes information about the following topics:

3.1 Oracle Database Hardware Requirements

This section describes hardware component and hard disk space requirements.

3.1.1 Hardware Component Requirements for Windows x64

The following table lists the hardware components that are required for Oracle Database on Windows x64.

Table 3-1 Windows x64 Minimum Hardware Requirements

Processor: AMD64 and Intel EM64T

Physical memory (RAM)

Virtual memory (swap)

If physical memory is between 2 GB and 16 GB, then set virtual memory to 1 times the size of the RAM

If physical memory is more than 16 GB, then set virtual memory to 16 GB

Typical Install Type total: 10 GB

Advanced Install Types total: 10 GB

See Table 3-2 for details.

1024 X 768 minimum

3.1.2 Hard Disk Space Requirements

This section lists the minimum system requirements for Windows platforms that use the NT File System (NTFS). Oracle strongly recommends that you install the Oracle database home, Oracle database binaries, and trace files on Oracle ACFS or NTFS; the database files themselves must be placed on Oracle ASM if using Oracle ACFS; otherwise they can be placed on NTFS. Usage of Oracle ACFS and Oracle ASM or NTFS is recommended to ensure security of these files.

The NTFS system requirements listed in this section are more accurate than the hard disk values reported by the Oracle Universal Installer Summary window. The Summary window does not include accurate values for disk space, the space required to create a database, or the size of compressed files that are expanded on the hard drive.

The hard disk requirements for Oracle Database components include 32 MB to install Java Runtime Environment (JRE) and Oracle Universal Installer on the partition where the operating system is installed. If sufficient space is not detected, installation fails and an error message appears.

Table 3-2 lists the disk space requirements on NTFS for Windows x64. The starter database requires 720 MB of disk space.

The figures in these tables include the starter database.

Table 3-2 Windows x64 Minimum Disk Space Requirements on NTFS

Requirement	Value