DevOps, CI/CD and Automation

Hi Guys:

Our environment is like this:

Oracle Server: 9i
Oracle Client: Windows 2008 Sever with sql server 2008
Oracle ODBC: 11g R2 (32 bit)

We fetch the data from sql server 2008 by using old DTS, and the daily fetch will be around 500,000 rows

The DTS sometimes successfully run, and some times failed with randomly throw out following exceptions from trace file, When we reduce the Fetch Buffer Size from 64,000 to around 15,000 the successful rate improved a lot, but not 100%:

(4248) [29-OCT-2010 21:31:24:906] nsprecv: 01 00 00 00 00 36 4F 52 |.....6OR|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 41 2D 30 31 30 31 33 3A |A-01013:|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 20 75 73 65 72 20 72 65 |.user.re|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 71 75 65 73 74 65 64 20 |quested.|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 63 61 6E 63 65 6C 20 6F |cancel.o|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 66 20 63 75 72 72 65 6E |f.curren|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 74 20 6F 70 65 72 61 74 |t.operat|
(4248) [29-OCT-2010 21:31:24:906] nsprecv: 69 6F 6E 0A |ion. |

ORA-01013:.user.requested.cancel.of.current.operation

///////////////////////////////////////////////////////////////
Error found. Error Stack follows for thread #: 5652
id:0
Operation code:77
NS Error 1:12630
NS Error 2:0
NT Generic Error:0
Protocol Error:0
OS Error:0
NS & NT Errors Translation
12630, 00000 "Native service operation not supported"
// *Cause: An operation requested by a user is not supported by the services component.
// *Action: This may be an internal error if the operation should have supported.
/
00000, 00000 "Not An Error"
// *Cause: Everything is working as it should.
// *Action: Dont worry: Be happy.
/
00000, 00000 "Not An Error"
// *Cause: Everything is working as it should.
// *Action: Dont worry: Be happy.
/
///////////////////////////////////////////////////////////////

Native service operation not supported
Cause: An operation requested by a user is not supported by the services component.
Action: This may be an internal error if the operation should have supported.

Is there any way that we can tracing who is close the connection and why?

Cheers