Hi, I'm using FreeTDS to synchronise a SQL Server 7 database with a MySQL one via a Perl script. I realise this means that this isn't strictly a Sybase question, therefore, but felt there might be mmore chance of finding people familiar with FreeTDS here than on either the SQL Server or the MySQL forums.
The synchronisation process takes just short of an hour to run, when successful. If I run the script manually, it performs it's duty as required, finishing about 55 minutes after I start it (although it does throw out a "cs_diag(CS_INIT) failed" error at the start, which does not seem to affect execution).
If I set it to run as a cron job, however (by installing the job in the same user's crontab, as I use to launch the program from the command line, and executing exatly the same arguments, etc.) it fails somewhere after about 36+ minutes with a "error_handler: Data-conversion resulted in overflow." message. Now, this may be a Vixie cron problem: God knows, Vixie cron has enough ideosyncracies that most have long since become 'features'. However, I was wondering what these actual messages might signify andd if there was a way to overcome them.
The synchronisation process takes just short of an hour to run, when successful. If I run the script manually, it performs it's duty as required, finishing about 55 minutes after I start it (although it does throw out a "cs_diag(CS_INIT) failed" error at the start, which does not seem to affect execution).
If I set it to run as a cron job, however (by installing the job in the same user's crontab, as I use to launch the program from the command line, and executing exatly the same arguments, etc.) it fails somewhere after about 36+ minutes with a "error_handler: Data-conversion resulted in overflow." message. Now, this may be a Vixie cron problem: God knows, Vixie cron has enough ideosyncracies that most have long since become 'features'. However, I was wondering what these actual messages might signify andd if there was a way to overcome them.