By default, database server messages are sent to the database server messages window. You can send the output to a log file using the -o option. Run the following command to output to a log file named mydbserver_messages.txt:
dbsrv16 -o mydbserver_messages.txt -c ...
You can control the size of the database server message log file, and specify what you want done when a file reaches its maximum size:
Use the -o option to specify that a database server message log file should be used and to provide a name.
Use the -ot option to specify that a database server message log file should be used and provide a name when you want the previous contents of the file to be deleted before new messages are sent to it.
In addition to -o or -ot, use the -on option to specify the size at which the database server message log file is renamed with the extension .old and a new file is started with the original name.
In addition to -o or -ot, use the -os option to specify the size at which a new database server message log file is started with a new name based on the date and a sequential number.
You can specify a separate file where startup errors, fatal errors, and assertions are logged using the -oe option.
It is recommended that you do not end the database server message log file name with .log because this can create problems for utilities that perform operations using the transaction log.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|