DTS Scheduling OLE db error - DB2 Client access

Printable View

02-13-2000, 06:01 PM
Robb Sinclair

DTS Scheduling OLE db error - DB2 Client access

I have a DTS package that executes when run manually. It is a OLEdb (ODBC) to client access (db2). When I try to schedule it the package fails.

Other packages SQL - SQL are fine to schedule or to run man.

I have played with the Persist Security Info advanced properties of the connection to no avail.

Any assistance would be great.

Thanks

Robb M Sinclair
Newcomp Solutions Inc
02-14-2000, 06:40 PM
Tiger

DTS Scheduling OLE db error - DB2 Client access (reply)

Hi there,

I guess you define the DTS package and run manually on your desktop. If so,
You have to define the same ODBC on the machine that SQL server resides. Because the scheduled job runs on the server not on your desktop.

I wish this could solve your puzzle.

------------
Robb Sinclair at 2/13/00 6:01:35 PM

I have a DTS package that executes when run manually. It is a OLEdb (ODBC) to client access (db2). When I try to schedule it the package fails.

Other packages SQL - SQL are fine to schedule or to run man.

I have played with the Persist Security Info advanced properties of the connection to no avail.

Any assistance would be great.

Thanks

Robb M Sinclair
Newcomp Solutions Inc
02-14-2000, 07:57 PM
zak

DTS Scheduling OLE db error - DB2 Client access (reply)

Hi there,

I would surey like to help you, But I couls not get your problem exactly,

Can you explain what exactily you are trying to do and What error do you get.
Get me the error which is stored in transaction log of sql server.

regards,
zak

------------
Tiger at 2/14/00 6:40:25 PM

Hi there,

I guess you define the DTS package and run manually on your desktop. If so,
You have to define the same ODBC on the machine that SQL server resides. Because the scheduled job runs on the server not on your desktop.

I wish this could solve your puzzle.

------------
Robb Sinclair at 2/13/00 6:01:35 PM

I have a DTS package that executes when run manually. It is a OLEdb (ODBC) to client access (db2). When I try to schedule it the package fails.

Other packages SQL - SQL are fine to schedule or to run man.

I have played with the Persist Security Info advanced properties of the connection to no avail.

Any assistance would be great.

Thanks

Robb M Sinclair
Newcomp Solutions Inc