These are descriptions and cron entries for other various daily and nightly jobs that run against our servers.

A perl script on degas scrolls through the databases every 1/2 hour executing a "sp_spaceused syslogs" in each database and interpreting the output. If the log reaches 1000k, email is sent

Every 5 minutes, /export/syb_ops/misc.sybping.pl runs, which performs a socket-based connection to the server port each of our Sybase servers is configured to listen on. If the port fails a connect, we email a "down server" message.

We run two Sybase maintenance operations nightly on all supported servers: update statistics and sp_recompile. Update statistics updates the information in a table that the optimizer uses to run the most efficient query. sp_recompile tells the server to recompile every stored procedures and trigger the next time it executes, generally to take advantage of updated statistics. (nightly.sh is a front end to max:/export/syb_ops/nightly/nightly.pl)

Swatch is specifically called to review output files of these update statistics and sp_recompile jobs for errors symptomatic of other problems. This is also mentioned on the Swatch page under the non-perpetual topic.

This process rotates logs to log.X where X is the number associated with the age (1=youngest, 7=oldest). Needed because dali's prod11 backup server log, degas's crimson sybase errorlog and the datatools logs on degas and dali grow quickly

This script cleans up transaction log dumps based on success of nightly backup. With the advent of SQL backtrack, no mechanism exists to cleanup these files unless coded.

This process is needed b/c of log rotation. If you rotate the logs, swatch (unless restarted) continues to monitor old log. This is explained in the last question of the faq section of the swatch page. We don't restart any logs on pop or max because nothing in their configurations causes large log files.