If you want to process the message log files programmatically, you can enable the messages to be output with an 8-character unique code. You can also disable the generation of message log files.
solidDB maintains the following message log files:
▪ solmsg.out: a log file for normal informational events, such as connects, disconnects, checkpoints, backups, failed logins, and so on
▪ solerror.out: a log file for unrecoverable (fatal) errors that typically cause the server to shut down abnormally
Additionally, solidDB can produce trace files (soltrace.out) for troubleshooting purposes.
You can view the message log files with a text editor.
The message log file size is controlled with the Srv.MessageLogSize parameter. When the maximum size of the message log file is reached, the current solxxx.out file is renamed to solxxx.bak, and a new solxxx.out file is started. To avoid overwriting the contents of the backup solxxx.bak message log the next time the maximum size of the message log file is reached, use the Srv.KeepAllOutFiles parameter to name the log files incrementally. For more information, see Srv section.
Enabling message codes in message logs
Each error and status message is identified with an 8-character unique code. If the message log files are processed programmatically, it is easier to parse them if the message codes are included. To enable the message code output, set the Srv.PrintMsgCode parameter to yes (the default value is no).
Disabling message log generation
To disable the generation of the solmsg.out and the solerror.out log files, set the Srv.DisableOutput parameter to yes (the default value is no).
Note Disabling the generation of log files makes it difficult to diagnose problems. Turning off message logging increases performance and reduces disk space usage. However, in most cases the improvement is minimal. Disabling generation of log files is useful only in unusual situations, such as when I/O is expensive (as it is in some systems that use flash memory), or in systems where data storage space is limited and the message log file accumulates indefinitely without being deleted.