Changing a Server’s Logging Level

Adjust the logging level that determines which events are recorded in the server logs. This task requires you to restart Sybase Control Center.

1. Shut down Sybase Control Center.
2. Restart Sybase Control Center using the -m option to change the logging level. In <SCC-installation-dir>/bin, enter:

   scc -m <logging-level>

   These are the logging levels, from highest to lowest. The higher the level, the more serious an event must be to be logged. Each level includes all the levels above it—for example, if you set the logging level to warn, you log events for the warn, error, and fatal levels.

   OFF	Nothing is logged. This is the highest rank.
   FATAL	Logs only very severe error events that lead the server to abort.
   ERROR	Logs error events that might allow the server to continue running.
   WARN	Logs potentially harmful situations. Warn is the default logging level during normal operation (that is, after system initialization).
   INFO	Logs informational messages that track the progress of the server in a coarse-grained fashion. Info is the default logging level during the system initialization process.
   DEBUG	Logs a larger set of events that provides a finer-grained picture of how the server is operating. This level is recommended for troubleshooting.
   ALL	Logs all loggable events. This is the lowest rank.

3. Examine the server log for clues about what might be causing the problem.
4. When you have resolved the problem, set the logging level back to warn, the default. Your log may become unmanageably large if you leave it at the debug or all level.

Windows: bin\scc -m DEBUG
UNIX: bin/scc -m DEBUG