This bad citizen has 3 Oracle 11.2.0.3 clients. Here's some outputs from some of my systems. Supposing you're already in a PowerShell: gci C:\,D:\ -recurse -filter 'oraclient*.dll' -ErrorAction Silentl圜ontinue | % | ft -Property FileVersion, FileName -AutoSize"
Here's the one-liner (sorry about the right scroll, but that's the nature of one-liners, eh?). So you could do this programatically or even remotely. PowerShell is amazing at this and can do it in one line, reminds me of home sweet Unix. So let's traverse the hard disk to find them and extract their version info. 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. Obvious case, there will be no ODBC or JDBC readme's to scrape version info from. Issue #3: Client was installed using "Custom", and ODBC, OLEDB, ODP.Net, and JDBC were not installed. Furthermore, the Instant Client is sometimes installed as an unzip-and-go solution, so there's no Oracle Inventory and nothing in HKLM. So can't rely on those tools being there. If a computer has the Oracle Instant Client (not the full client), then TNSPING is not included, and SQLPLUS is an optional-addon. Issue #2: Instant Client doesn't have TNSPING, and sometimes doesn't include SQL*Plus. or, the PATH didn't resolve the executable, and you get no results.Įither way, you are blind to possibly multiple client installations.either your PATH successfully resolves the executable and you get ONE version result.If you are relying on the PATH and running a utility like SQLPLUS or TNSPING you'll have one of two unacceptable results:
Issue #1: Multiple Oracle clients are installed.Ī 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.
0 kommentar(er)
