March 2, 2009 at 8:02 am
Hi,
I have a SSIS Package which is Having a Dataflow task in a Container,which Transaction Option is "Required" and the Dataflow task Transaction Option is "Supported" for both Isolation Level "ReadUncommitted" . SSIS exec successfully, if I have both Source & Traget DB in the local system and its rolling backs all the transaction in the case of error.
But if i changed my Target to different DB (in Prod i have to refer difference Server/DBs) SSIS is failing with following error(s).
[OLE DB Command INSERT INTO Generic_Answers 1 [4255]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "TargetDb1" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
[DTS.Pipeline] Error: component "OLE DB Command INSERT INTO Generic_Answers 1" (4255) failed the pre-execute phase and returned error code 0xC020801C.
-------
Earlier I was using the SQL Transaction in my SSIS (using Exec SQL Task) but this also failed, because the Multiple Insert Stmts across various Tables is causing Exclusive lock on table(s).
past 2,3 weeks I was googling, and i did all MSDTC and all related configs. But still i got stuck in the begin stage itself. Please help me on this issue, if any one got any kind of solution....
Thanks
Rijosh
March 2, 2009 at 12:13 pm
Try removing exclusive locking from tables in your Data flow tasks.
March 3, 2009 at 12:23 am
Hi,
thanks for the reply.
Could you pls make it clear more...is that a Dataflow property wt you are saying? ,cos i couldnt see any option in it & if you are saying abt the Lock what we are specifying in the OLEDB source, then that is not selected. and here i am using Nolock keyword for all my select stmts. I am using OLEDB command to do Update, Insert & DEL. and its getting locked in a particular table Insert.
March 3, 2009 at 11:35 pm
I got a solution to make my SSIS work.
Here in my SSIS the process was always getting stuck in the same place wr a table Insert was happening.
So I checked for Constraints in this table and i got to knw there are two foregin key relations to the main two tables which is also part of my transaction. due to this my related table was not able to update/insert
I have removed the foregin key relations to make my SSIS works.
so I will remove the relation before the Dataflow & Once everything commited I will add the relation back.
Note : - Here I am considering the Same SQL side transaction. not the SSIS side.
Hope this will help some of you...
Thanks
Rijosh
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply