I’m having an issue with many of my tasks getting “hung” in the system. I can’t seem to find any reason because when I cancel the task and manually run the automation file, it runs in less than a minute. It happens randomly and only with tasks that are executed by Toad Data Point 3.5. Any thoughts or known issues? I don’t think it is an issue with my windows scheduler because I have 50+ tasks that run access databases for various outputs that do not get hung up.
What I mean by hung up, is it shows “Running” for hours and hours and hours, sometimes even from a previous day and sometimes even when the output was completed.
We found that on TDP 3.5 and earlier when scripts were kicked off very closely together they could hang if both scripts were compiling at the same time. We addressed this issue in TDP 3.6. Upgrade to TDP 3.6 or spread your schedules out farther to prevent collision.
Reply by Debbie Peabody
We found that on TDP 3.5 and earlier when scripts were kicked off very closely together they could hang if both scripts were compiling at the same time. We addressed this issue in TDP 3.6. Upgrade to TDP 3.6 or spread your schedules out farther to prevent collision.
Can you send me the Automation log file so I can see where it hangs? If it hangs before the log file is created then go and look at the execution status in windows task manager. I need to determine how far it got before it hung
Reply by Debbie Peabody
Can you send me the Automation log file so I can see where it hangs? If it hangs before the log file is created then go and look at the execution status in windows task manager. I need to determine how far it got before it hung
Hopefully, the log file will be present in the folder "C:\Users[YourUserName]\AppData\Roaming\Quest Software\Toad Data Point 3.5\Automation". The file name should reflect the name of your Automation Script with a .log extension. Please send us the log file if it exists.
If there is no log file, please take a look at the Windows Task Scheduler to see the execution status of the task (the task name should match the automation script name).
How to Access and Retrieve Scheduled Task Data
After the scheduled script runs or hangs for a while, go to Start -> "Task Scheduler"
I believe these two pieces of information will be helpful in our investigation.
Thanks everyone for your input. I upgraded to 3.6 in hopes this issue does not continue. Does anyone know if I uninstall 3.5 will it cause any issues in any area for 3.6? I’ve just noticed some things in 3.6 point to my 3.5 directory, and if 3.5 had bugs in it, I’d rather just uninstall all together.
Tools - Options - Database - Oracle, file name under external application pointing to C:\Program Files (x86)\Dell\Toad Data Point 3.5\QSR\qsr.exe. This may be meaningless but it still stood out to me.
All of my .sql and .tas files also continue to open in 3.5 and not 3.6, even after reconfiguring the “open with” option from Windows.
upgrading to 3.6 will not neccessarily change a job scheduled to run on 3.5 to run on 3.6 automatically. If you edit the old 3.5 job schedule in 3.6 that should change it.
Yes, some functionality in newer version continue to reference older version and this is by design. But “All of my .sql and .tas files also continue to open in 3.5 and not 3.6, even after reconfiguring the “open with” option from Windows” seems like a bug. I created QAT-4233 to track it.
Reply by Igor Manokhin
Yes, some functionality in newer version continue to reference older version and this is by design. But "All of my .sql and .tas files also continue to open in 3.5 and not 3.6, even after reconfiguring the "open with" option from Windows" seems like a bug. I created QAT-4233 to track it.
