DB2 Data Server Client 11.1 package not providing all tools - windows

My current task at my job is to install the DB2 11.1 Data Server Client for our users on windows 10. I grabbed the installer from IBM's site and installed it successfully, BUT it's only installing command line tools. When looking at the 9.7 package on a windows 7 workstation, it provides a bunch of GUI based tools. Can someone tell me where i'm going wrong? Has anyone had success installing 11.1 on Windows 10?

Db2-v11 clients for Linux/Unix/Windows no longer come with the old GUI tool known as the Control-Center.
Some Db2-client types still include the Replication-Center GUI. You need to choose your Db2-client type carefully.
The replacement for the Control Center is IBM Data Studio, which is a separate download, and also for some functionality the IBM Data Server Manager.
Data Studio 4.x download link
IBM Data Server Manager download link
Other companies supply alternative lightweight GUI client tools that work with Db2. For example Db-visualizer, Squirrel-SQL and many other Java based tools. Oracle SQL-Developer also works with Db2, as does Toad for Db2.
None of those tools third-party can cope with all the different variants of Db2-functionality, especially in the area of DPF or Purescale or latest variants of syntax for different platforms. Latest versions of IBM Data Studio try to cover most cases. But many of the third party tools are good enough for many simple use cases.

Related

Proper Oracle ODBC Driver Installation on 32 bit Windows 7

I am using an Excel VBA application to connect to an Oracle 12c database.
Excel is 2010, 32 bit, in Windows 7.
Many have advised Oracle Instant Client, but this has not worked for me. The installation requires a number of configuration steps that I cannot perform due to administrative restrictions on my workstation.
However, I have installed the ODAC 12.2c Release 1 and Oracle Developer Tools for Visual Studio (12.2.0.1.0), available HERE. This package includes the Oracle ODBC driver which works for my application. However, it contains several other components that I do not need, and throws some errors during installation that are disconcerting.
Can anyone tell me which of the following components I actually need to select in order to get the ODBC Driver?
Since I cannot get InstantClient to work with my companies restrictions, I'm now aiming to use this package, but hopefully to slim it down to just the component I need. I'm doing trial and error, but it's messy. The installation takes a long time and there's no uninstaller, so I have to manually delete the files after installation.
Thanks for any help you can provide!
The smallest solution is to download the
Instant Client Package - ODBC: Additional libraries for enabling ODBC applications (instantclient-odbc-nt-12.2.0.1.0-2.zip)
from Instant Client Downloads for Microsoft Windows 32-bit
You can also download the ODAC with Oracle Developer Tools for Visual Studio from ODAC Developer Downloads - Oracle Universal Installer
Get the full 32-bit Oracle client installer (not the ODAC) from here:
http://download.oracle.com/otn/nt/oracle12c/122010/win32_12201_client.zip
Do an silent install using this reponse file (edit as needed and save as client_install_32.rsp in the same directory as setup.exe)
Response file
setup.exe" ORACLE_HOME_NAME=OracleClient12201x32 -waitforcompletion -nowait -silent -responseFile client_install_32.rsp
The key config entry is this:
oracle.install.client.customComponents="oracle.rdbms.oci:12.2.0.1.0","oracle.network.client:12.2.0.1.0","oracle.odbc:12.2.0.1.0"

ODP .Net 12 using OraClient11

I know that the request may look somehow weird but I am trying to develop a .Net application using EF and Visual Studio 2010 against a ORACLE 10g DB.
Initially I tried with EF4 which is the embedded one in VS2010 and with ODP11 I am able to make it work. But due to some specific bugs in EF4 (StoreGeneratedPattern bug) I want to go to EF5 or EF6.
While "googleing" a bit I was able to Install EF6 using the nugets and adding the context generator for EF using the following explanation:
https://msdn.microsoft.com/en-us/data/jj206878.aspx
The problem here is that the system is not able to find a proper ODP provider for Entity Framework as I only have ODP11 installed.
Again after investigating a bit :) I saw I need ODP12 which will have full support to EF. My problem here is that all servers will be working with OraClient 11g against a Ora10g DB... I know there is no major problem (at least for the use I need) to use Ora11Client with a Ora10Server but what about ODP? I cannot change the Oracle client and I am wondering whether I can face any issue by having my application developed with ODP12 and being executed in a machine with Ora11g Client.
Is anyone having some advice on this?
Thanks a lot in advance!!
It's my understanding that the managed driver for 12 (Oracle.ManagedDataAccess and Oracle.ManagedDataAccess.EntityFramework available on NuGet) will connect to 10.2 and above and does not require ANY client installed on the computer as it contains the client it needs. It just gets installed in the app's bin directory. Be aware though that it doesn't seem to currently work with .NET 4.0 in case you're still targeting that. The 4.0 version of Oracle.ManagedDataAccess.EntityFramework shows up on NuGet as a beta version and is actually compiled against .NET 4.5.
ODP.NET 12.x has a dependency on the Oracle 12 client software so you cannot use it with the 11 client stack. You can use ODP.NET 12 to connect to databases going back to version 10.2.
You can embed the ODP.NET, unmanaged client stack in your app by using the Xcopy download, or you could use the ODP.NET, Managed Driver which is just one DLL and less than 10 MB in size.
Oracle has the concept of an "Oracle Home" (subdirectories) to allow multiple versions of software to run side by side. So that version 11 Client on your servers can exist alongside with the version 12 software you deploy there.

Install Performance Tools for SQL Server 2008

We have SQL Server 2005 Enterprise Edition here.
I have been using SQL Server Management Studio 2008 for connecting to our Data Source - this has been working fine for the last year.
When I first got here, I found an article on this site that stated that to install Management Studio, you just down the SQL Server Express 2005/2008 installer. Once installed, it will give you access to features according to the SQL Server version of the Data Source (this worked a treat).
I now need to use SQL Profiler, but it isn't present in SQL Server 2008 Management Studio.
Through searching online, I apparently need to tick the "Management Tools - Complete" option - but this option is not present on the installer.
I am using SQLEXPRWT_x64_ENU.exe to attempt to install this but the feature is not present, it only has "Management Tools - Basic" available.
There does not seem to be a way to point the installer at my Data Source, so that it can see that it will be used with an Enterprise licensed server.
I have tried downloading various versions, but still the "Complete" option is missing.
Is there an installer that I can download with this option enabled, or do I have to ask my support services team to speak to Microsoft to provide a special installation program for me to get this facility?
Any help on this issue will be greatly appreciated.
MS does not provide the SqlProfiler with Express versions of Sql Server. I have been looking for a profiler alternative myself, found ExpressProfiler on Codeplex but its a bit crude and not very configurable. This one works quite nicely: http://www.codeproject.com/Articles/784905/Real-time-Tracing-With-SQL-Server-Express

Why is the SQLite provider missing from the Server Explorer Add Connection dialogue?

I am following the article Using SQLite Embedded Database with Entity Framework and Linq-to-SQL, and have tried installing the SQLite provider, first using the System.Data.SQLite NuGet package, and then by installing the provider via the Setups for 32-bit Windows (.NET /Framework 4.0) installer package (for v1.0.79). After both installs, and a system restart, I still see no SQLite Database File provider in the Add Connection dialogue from Server Explorer.
I can proceed by manually creating a connection string and using external tools to create my SQLite database file, but I still would like to know what is wrong why I do not have the advertised design time support for SQLite despite having installed the latest provider. What could be wrong here?
Ensure the data tools for visual studio were installed correctly as per:
http://www.basarat.com/2010/05/sqlite-for-visual-studio-2010.html
There are various fixes listed, making sure there weren't older tools installed first, etc.
I'm going to give it a try, but the article may help you out.

Is ODP.NET required for Oracle 11g Client?

I may be asking the wrong question here, I'm willing to change it if so.
I have a project that is using the Microsoft.NET Oracle provider (our plan is to change to ODP but we haven't done so yet).
I am trying to get this project to build on a windows 2008 (x64) build server. It builds just fine but our unit tests fail when they hit stuff on the Oracle database.
I had initially installed the 32bit oracle 9i client which is what we currently use on our winxp dev boxes and the previous 2003 build server. But now this gets a message like: Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.
We tried compiling to the x86 platform but that didn't change the error message.
I now have the 11g 64 bit client installed but I am getting a message saying System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.
So what Oracle install should I be using?
Edit:
I was able to get this to work. Turned out it was the testing causing the problem, by forcing NUnit to run in 32bit mode: Link I was able to get the tests to work using the old 32 bit driver. This would be a crappy answer to the question so I am not using it but will gladly award the correct answer to anyone putting in some good info on transitioning to Oracle 64bit drivers.
When it comes to Oracle, I like to use Oracle Instant Client :
You don't have to install anything on the target machines (including dev boxes !).
You can make sure that your application will run with the specific client you picked.
You could even easily have multiple applications work with different client versions on the same computer.
As a downside, it adds a significant weight to your application (~19Mb minimum).
Check What is the minimum client footprint required to connect C# to an Oracle database? for more information. To know how to set up a Visual Studio project that will work on x86 as well as x64 machines, check my blog post Oracle Instant Client in Visual Studio.
I'm adding a new answer since as of this fall (2012) the ODP Managed Code Beta is available. See this link for more information. It is for us highly stable and we are using it in production, mainly because of these reasons:
No installation (except for entity framework where a simple registration is needed)
It is smaller than the unmanaged version, the footprint is approx 6 MB.
It is NOT "bit sensitive", ie Any CPU will finally work with ODP :)
More intuitive mapping C# types <-> Oracle types (and it solved some problems with EF and model generation from database)
Supports EZCONNECT (all versions of the unmanaged ODP did not), ie no more tnsnames.ora hassles.
But for transitioning to 64 bit, download the managed ODP driver and change the Oracle.DataAccess reference to Oracle.ManagedDataAccess and recompile :)
I think the message "System.Data.OracleClient requires Oracle client software version 8.1.7 or greater" it's similar to "Oracle client not installed, installed but not found or installed but it's needed 8.1.7 or greater".
Check on regedit if the values are right under the key:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraOdac11g_home1
Where OraOdac11g_home1 depends on the Oracle Home name for your installation.
Also, try to connect through Visual Studio to see if its possible.
I have had an issue which could relate to what you are seeing.
I initially had the just the Oracle 10g client installed on my machine and the .Net Oracle.DataAccess component version number was 10.2.0.100 - this was for .Net runtime v1.0.3705
I installed ODP.Net and the Oracle.DataAccess component version is now v2.102.2.20 and runs on .Net runtime v2.0.50727 - I cant find the reference as to why Oracle did this - it was something to do with bringing version numbers in line with the runtime version
It took me a day to work this out. We dont use the 11g client yet and I havent used the 8i client for ages so I dont know what the version numbers would be for those clients, but I'd check it if I were you what.
In short, Oracle back-tracked the component version numbers which could be making your 11g component appear out-of-date as opposed to Oracle 8i components
I have found many times that the error "requires Oracle client software version 8.1.7 or greater" is a notoriously misleading error. From distant memory I seem to remember that this usually indicates a file IO permissions problem. I think it may be that the ASP.NET worker process (or whichever identity an application is running under) requires some sort of read or write permission to a folder in the oracle client folder hierarchy...
This can be a cause of multiple oracle homes in the environment. Remove the older version oracle home in your build system. try generating the build again with the single home. There are some issues with 9i version ODP.NET and 10G/11G connectivity

Resources