Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Not able to run SSIS package in 64 bit server Expand / Collapse
Author
Message
Posted Wednesday, April 13, 2011 8:05 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 28, 2011 1:14 PM
Points: 19, Visits: 129
I created some SSIS packages. I am able to run these packages in BIDS without any issue. When the DBA tries to run the packages in the 64bit server, he is getting an error:

The connection type "MSORA" specified for connection manager "Att_CPErrBatch" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

I have set Project Property Run64BitRuntime to True.

Any help would be apprieciated.

Thanks.

Post #1092847
Posted Wednesday, April 13, 2011 2:08 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:20 AM
Points: 10,206, Visits: 13,151
The driver for ORacle may not be 64 bit so you may need to run the job on the 64-bit server using 32 bit DTEXEC.exe found in the Program File (x86) path.



Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #1093167
Posted Thursday, April 14, 2011 12:24 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:15 AM
Points: 13,017, Visits: 10,800
Small sidenote:
the property Run64BitRuntime is only for running packages in BIDS. This has no effect on packages deployed to another machine.

So either download a 64-bit Oracle driver (here) or follow Jack's advice and run the package in 32-bit.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1093325
Posted Thursday, April 14, 2011 8:14 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 28, 2011 1:14 PM
Points: 19, Visits: 129
Thanks both of you for your replies. I will try running the packages with dtexec (32 bit version).
Post #1093545
Posted Friday, April 15, 2011 5:36 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 11:24 AM
Points: 2, Visits: 46
The MSORA is Microsoft's Oracle driver. There is not a 64bit version of the driver.

I would highly recommend using the Oracle's OLEDB driver when developing the package in BIDS so that you can utilize the Oracle driver on the server.

If you are loading data into Oracle, the OLEDB destination object will be very slow since there isn't a fast load option. Anything over 30K rows will be painfully slow, If you are using 2008 R2 you can utilize the new Oracle Connectors which has a fast load option. If you are using 2005 then you will need to look into using SQLLDR, an Oracle utility similar to BCP.

Post #1094450
Posted Sunday, May 1, 2011 12:55 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 6:39 AM
Points: 68, Visits: 153
Hi there!

I have exactly the same problem as you. How did you manage to solve it?

Best wishes

Mark Thornton
Post #1101262
Posted Monday, May 2, 2011 2:25 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 28, 2011 1:14 PM
Points: 19, Visits: 129
The package was using Attunity Driver. The DBA had to install both 32 bit and 64 bit Attunity Drivers at his end. After that we were able to run the package.
Post #1101929
Posted Monday, May 2, 2011 11:15 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 5, 2011 4:21 AM
Points: 4, Visits: 41
in my case the attunity was 20 times faster than MS oracle driver
Post #1102100
Posted Monday, May 2, 2011 11:42 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:15 AM
Points: 13,017, Visits: 10,800
Jan Eberle (5/2/2011)
in my case the attunity was 20 times faster than MS oracle driver


That is good to know. I'll recommend this driver more often :)




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1102115
Posted Tuesday, May 3, 2011 1:58 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 6:39 AM
Points: 68, Visits: 153
< The package was using Attunity Driver. The DBA had to install both 32 bit and 64 bit Attunity Drivers at his end. After that we were able to run the package.>

Where did he install the 64-bit driver? On the Oracle machine, or the SQL Server machine?

I tried installing the 64-bit driver on the SQL Server machine, but merely progressed to getting a different error.
Post #1102153
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse