July 3, 2008 at 6:44 am
i've experienced a strange phenomenon. i couldn't write use tables on an AS400 as destination for my package. The funny thing is that with some tables it worked and with some none. So i thought about journaling and all this stuff but they where exactly the same. the only difference was that the names of the working tables had a a length <= 10 and the non working ones have longer names. when i choose 'table or view' as data access mode i can select the table (even if it has a long name), but then i cannot define any mappings. when i use SQL Command as data access mode i can define mappings, but when running the package the destination componenten fails (it makes no difference if i use the long alias name of a table or the system name, which is limited to 10 chars). but when the table name is <= 10 chars (obviously then the system name and the alias name are exactly the same) everything works as expected.
Has anyone experienced this problem too? in my current package i could rename the target table, but there will be a lot of other packages where the target table is connected to other systems so renaming is no real solution for me. I'm using IBM DB" UDB for iSeries IBMDA400 OLE DB Provider. unfortunately i cannot test the Microsoft OLE DB Provider for DB2 because i work on SQL Server Standard Edition
July 3, 2008 at 9:34 am
I have not had this problem, but from the description, I would suspect it is a driver issue more than it is an SSIS issue. You should check for similar issues related to the driver you are using.
July 3, 2008 at 10:07 am
is there a driver alternative if i'm using the standard edition?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply