we are looking to upgrade all of our environments, the first server to go is our sql box to 2008…later our DI box will go as well, but at present this cannot be upgraded (politics !!)…however, I am having problems getting DI to speak to the repositories I have migrated to sql 2008 as part of the testing process…
I have followed advice in the posts listed below and was wondering if anyone had any suggestions and what else I could try as I still get the message that
So far I have tried replacing the sqljdbc.jar located in C:\Program Files\Business Objects\Data Integrator 11.5\ext\lib, I have also downgraded Java and restarted both the DI services and the Tomcat server but to no avail.
Packages created DI will read and write to the new server, but I can’t seem to get the repositories to work…Any suggestions ??
Currently running DI 11.5.1.5 on Windows Server 2003 R2 trying to talk to SQl Server 2008 SP2 on Windows Server 2008 R2.
SQL Server 2008 is not supported as repo in DI 11.5, so if the problem is happening because of some changes that are required in DI to make it work with SQL Server 2008, then that is not possible
if the problem is with SQL Server 2008 configuration, driver is not installed etc, then check if you are able to create a system DSN and connect to SQL Server 2008 database, if error first fix those errors
is SQL Server 2008 Driver installed on this server ?
replacing sqljdbc.jar is required for Management Console not for JobServer and Designer which will use ODBC connectivity
Thanks for your response Manoj_d - I can create and connect with a system DSN fine - so from your post it is an issue with DI ? And I am guessing that this means there is no solution ?
Could cause problems for me, but what is life without challenges !!
Dave, I have 11.5, 11.7, 12.1 and 12.2 running on my laptop (each in their own Win XP Virtual Machine) connecting to a MS SQL Server 2008 database also running on the laptop (in the host O/S, not a VM). All of these versions of DI/DS connected just fine after I installed the SQL Server Client. Look for SQLNCLI.MSI on the Microsoft web site. I did not have to create any DSN - system or otherwise - to connect from DI/DS. Be sure you install the 32 bit version of the client as DI/DS is a 32 bit application in Windows. (4.0 changes this)
Are you able to open a connection to the database server using the SQLCMD tool? I have that tool installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn. It was most likely installed when I also installed the MS SQL Server Management Studio.
Anyhow, it sounds like the driver isn’t even being loaded so perhaps DI can’t find it. Is it in the path? It should have been installed to the windows system directory (c:\windows\system32 on XP). The file name is SQLNCLI10.DLL. If that doesn’t work then install the 2005 client instead. The 2008 server should accept a connection from a 2005 client.
Just to be precise:
Management Console = tomcat = jdbc
Designer & JobServer = C++ = database driver
So if it is the management console, we can stop thinking about the SQL Server driver, it has to be JDBC. Can you do a quick search in the DI directory if there are other SQL server jdbc jar files? Also note, the jdbc driver got renamed with SQL Server 2008 and hence just copying the jar file with the new name would not help, it’s not picked up. You have to replace the old jar file with the new.
And the jdbc driver of 2005 cannot connect to SQL Server 2008, that was my finding when I looked at the topic.
(BOB member since 2006-07-13)
(BOB member since 2007-09-12)
(BOB member since 2004-12-17)