I have a simple clover graph that calls a stored procedure. I have it scheduled to run right at 00:00. It is important that this job runs right at this time. There have been many cases in which the graph runs a few second early (as much as 15 seconds). The ETL web portal shows that the job has been running at its normal time, however I can see that this is not the case based on time stamps the the procedure creates in the database.
Has any one experienced an issue like this. Where you able to resolve it and how?
Hi
If the CloverETL Server runs on a different machine than the database server, it is possible that these machines have slightly different system times and that could cause the inconsistency. In this case you should synchronize both machines with the same NTP server. If this is not the case and both are running on the same machine, I would need more information about it.
1. What database are you using (name, version)?
2. What version of Designer and CloverETL Server are you using?
3. What time does your stored procedure use to create a timestamp (system etc.)? Could you please send me a sample of the code which is responsible for making the timestamp (SQL)?
Thank you in advance.
Hi
If the CloverETL Server runs on a different machine than the database server, it is possible that these machines have slightly different system times and that could cause the inconsistency. In this case you should synchronize both machines with the same NTP server. If this is not the case and both are running on the same machine, I would need more information about it.
1. What database are you using (name, version)?
2. What version of Designer and CloverETL Server are you using?
3. What time does your stored procedure use to create a timestamp (system etc.)? Could you please send me a sample of the code which is responsible for making the timestamp (SQL)?
Thank you in advance.
“cholastal”
Thank you very much for the reply, it was indeed a case of the Clover system clock not being in sync with my database