Skip to main content
SnapManager Oracle

Collecting additional log information for easier debugging

Contributors NetAppZacharyWambold

If you need additional logs to debug a failed SnapManager operation, you must set an external environment variable server.log.level. This variable overrides the default log level and dumps all the log messages in the log file. For example, you can change the log level to DEBUG, which logs additional messages and can assist in debugging issues.

The SnapManager logs can be found at the following locations:

  • SnapManager_install_directory\log

To override the default log level, you must perform the following steps:

  1. Create a platform.override text file in the SnapManager installation directory.

  2. Add the server.log.level parameter in the platform.override text file.

  3. Assign a value (TRACE, DEBUG, INFO, WARN, ERROR, FATAL, or PROGRESS) to the server.log.level parameter.

    For example, to change the log level to ERROR, set the value of server.log.level to ERROR.


  4. Restart the SnapManager server.

Note If the additional log information is not required, you can delete the server.log.level parameter from the platform.override text file.

SnapManager manages the volume of server log files based on the user-defined values of the following parameters in the smo.config file:

  • log.max_log_files

  • log.max_log_file_size

  • log.max_rolling_operation_factory_logs