Saturday, February 25, 2012

oracle connection manager configuration help

Hi, I dont know if I should post this question here, or on oracle forums, but here goes ...
I made a simple package that performs 2 Excecute SQL Tasks, one task does a select query on a SQL Server DB Table, the other task does a select query on an Oracle DB Table.

The package runs fine in BIDS when debugging, but when I deployed the package to a file system and added it to an sql server agent Job, it all went wrong ...

I tried the ms oledb dataprovider (ole db) for oracle but also the oracleclient data provider (ado.net) but the package always fails.

The error messages in the logfile are these:

event OnError
computer ComputerName
operator NT AUTHORITY\SYSTEM
source Execute SQL Task PLSQL
sourceid {B29C4FC9-3345-4657-8680-F770B8C2E136}
executionid {7312A7EC-2555-4268-BB29-38659507BADD}
starttime 14/04/2006 16:40
endtime 14/04/2006 16:40
datacode -1073573396
databytes 0x
message Failed to acquire connection "aaa.bbb.oracleClient". Connection may not be configured correctly or you may not have the right permissions on this connection.

the OnError logrow for the package itself says almost the same.

Now my question is: What do I need to configure to get it all working? I think I need to configure the oracle db no? What should I configure? ...

Take a look at http://www.oracle.com/technology/tech/windows/odpnet/beta_doc/featADO20.htm

the <configuration> ... </configuration> in the Connection String builder section.

|||owkey the oracle client wasn't installed on the server where the packages were deployed and where ssis server is running. BUT the admin is not planning on installing them :s

So that leaves me with another question ... does anyone ever configured a ssis server on an other server than the server that contains the packages? The only thing that we configured was the ssis xml file called MsDtsSrvr.ini.xml, more information can be found here http://msdn2.microsoft.com/en-us/library/ms137789.aspx We also followed the tips on these sites http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=254204&SiteID=1 and http://sqljunkies.com/WebLog/knight_reign/archive/2006/01/05/17769.aspx but still we were unable to get it to work. The MSDB folder never shows any content even if something got deployed to that server.
So what we want to have:
Server1 who runs SSRS, SSIS and has oracle client installed.
Server2 who runs SQL Server, SQL Server Agent, SSAS, and packages are deployed here.
In the config file (of SSIS on Server1) we reference to the MSDB of Server2.
What is going wrong? What additional things need to be configured?

Some extra info: SP1 isn't installed yet because it is prerelease|||

You need SSIS to be installed on the server upon which the package is executing. You will also need the Oracle provider on that machine. If calling the package from SQL Agent on Server 2 then you need that stuff on Server 2. You obviously have SSIS on Server 2 already to have got as far as you did. If your plan was to off load SSIS work onto Server 1, then it needs to execute there.

Why not install SQL on Server 1, and just use the DB for logging and to support SQL Agent. You have licensed both Servers for full SQL Server, so why not use it. You may not wish to use the DB for more than that, but having a strict rule of no DB engine on a server means more hassle that it is worth. If you use a backup tool, then you probably already have a DB instance in one form or another! DB Instances don;t have to be resource hogs if you treat them right, and don't ask them to do large workloads.

No comments:

Post a Comment