Hi All,
I have a Job which Inserts around 5 Million records in a table. This job have been executed fine several times and takes around 1 Hour but suddenly during our last execution this job was executing for almost 3 Days but still didnt finished. Finally we stoped this job and re-run it after which it was executed successfully within an hour.
When the job executed for 3 Days we had checked the details and found that the row transfer was stuck at around 2 million rows after which no rows went in the target table but still the job was showing status as running. Also no error was thrown in the DS Director logs so we are not able to find the exact reason why it went in infinite execution mode.
Can any one list down the possible reasons why such thing happened so that we can analyze in that direction?
Thanks in Advance.
Running but Not Running
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 822
- Joined: Sat Sep 17, 2005 5:25 pm
- Location: USA
Another reason could be that the system ran out of resources and is paging as things free up. Depending on the system, this can basically lock the processor, RAM and hard drive just doing the continuous swapping.
Merry Christmas!
Merry Christmas!
Bestest!
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services
"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"