SystemAction: The server does not update the activity log.
User Response: Anauthorized administrator can issue the DEFINE
LOGVOLUME command to add volumes for use by the log, and can issue the
EXTEND LOG command to extend the size of the log so that the new volumes are
used.
ANR2011W Server is out of DB space in adding entries to theActivity Log. Console
messages will not be logged until DB space is available.
Explanation: The process that monitors the default (console) output stream and
maintains the activity log cannot update the activity log due to a lack of database
space.
SystemAction: The server does not update the activity log.
User Response: Anauthorized administrator can issue the DEFINE DBVOLUME
command to add volumes for use by the database, and can issue the EXTEND DB
command to extend the size of the database so that the new volumes are used.
ANR2012W Activity log process has encountered unexpected table data output in the
default output stream.
Explanation: The process that monitors the default (console) output stream and
maintains the activity log has detected invalid data in the console stream.
SystemAction: The server stops updating the activity log.
User Response: Contactyour service representative.
ANR2013E The activity log process has encountered unexpected output data in the console
output stream. The process will be restarted.
Explanation: The process that monitors console output and maintains the activity
log has detected invalid data (unknown data type) in the console stream.
SystemAction: The server restarts the activity log recording process. While the
process is restarting, the server may not be able to record some console messages in
the activity log.
User Response: Theserver may be low on available memory.Allocate additional
storage to the server.For details, issue HELP MEMORY to display the information
online or see “AppendixA. Allocating Additional Server Memory”.
ANR2014E Activity log pruning process could not be started, due to an internal error.
Explanation: The process that removes expired records from the server activity
log cannot begin execution due to a server internal error.
279
Tivoli Storage Manager Messages
3. Common and Platform
Specfic Messages