Adjust the logging level that determines which events Sybase Control Center records in the server logs. This task requires you to restart Sybase Control Center.
If you are having a problem with Sybase Control Center, you might be able to discover the cause of the problem by changing the server logging level so that more events are recorded.
- Shut down Sybase Control Center.
- Restart Sybase Control Center using the -m option to change the logging level. In <SCC-installation-dir>/bin, enter:
scc -m <logging-level>
The logging levels are OFF (logs nothing), FATAL (logs only the most severe events), ERROR, WARN, INFO, DEBUG, and ALL (logs everything).
- Examine the server log for clues about what might be causing the problem.
- 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.
Example
These commands, which must be executed in the installation directory, start Sybase Control Center with the logging level set to debug:
Windows: bin\scc -m DEBUG
UNIX: bin/scc -m DEBUG