I think I'm going to take a few steps back and start from scratch as I
can't figure out how the 2 are conflicting.
Dave
On Fri, Apr 20, 2018 at 4:12 PM, Niall Litchfield <
niall.litchfield@xxxxxxxxx> wrote:
system.data.oracleclient is Microsoft's .net provider for Oracle. It's
complaining that it can't find appropriate Oracle Client libraries. If you
are setting ORACLE_HOME or similar that might cause that error. I know next
to nothing about SSMA, but there is an Oracle supplied .net set of
libraries that support Oracle much, much better than the MS ones did.
On Fri, Apr 20, 2018 at 12:52 AM, Dave Herring <gdherri@xxxxxxxxx> wrote:
I've got some sort of conflict between SQL Server SSMA conversion tool
and SQL Developer and I can't figure out where it is.
I'm in the process of generating assessment reports for the conversion of
around 130 databases and on a positive piece of this I've learned enough
powershell to script this. Each assessment is taking anywhere from 1/2 hr
to 2 hrs so I figured I'd grab the latest version of SQL Developer (18.2).
After getting SQL Developer to work I noticed that every SSMA execution
failed, giving the error: "NESTED System.Data.OracleClient requires Oracle
client software version 8.1.7 or greater.". The problem is I can't figure
out what the SQL Developer setup changed as all I did was unzip the
download under "C:\Oracle" and then start the executable to validate it was
working.
I removed "C:\Oracle\sqldeveloper", along with
%AppData\Roaming\sqldeveloper directories but the problem persists. My
guess is there's some sort of java-related change that happened or 32-bit
vs. 64-bit dll change but I can't figure it out. Anyone know all changes
that SQLDeveloper makes?
--
Dave
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
