Posted: Thu Jul 25, 2002 7:01 am
Karthik,
Hi.Though u have not mentioned the type of RDBMS , I presume that it might be Oracle or SQL Server etc.
SQL Server has time outs, you may need to reset that settings.
If you are reading from DBs resting on servers which may have high CPU utilization, there might be an issue.
Try resetting time out - do some manual reading on the DB - especially query response times
Try running the jobs in sequence with one read and one look up ie split the job .
All the best
Srinivas.B
Dubai
Mobile :00971507380893
Hi.Though u have not mentioned the type of RDBMS , I presume that it might be Oracle or SQL Server etc.
SQL Server has time outs, you may need to reset that settings.
If you are reading from DBs resting on servers which may have high CPU utilization, there might be an issue.
Try resetting time out - do some manual reading on the DB - especially query response times
Try running the jobs in sequence with one read and one look up ie split the job .
All the best
Srinivas.B
Dubai
Mobile :00971507380893