Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Question
If a FULL database backup is not taken in time to prune the archive logs before the directory becomes full.
Either the active log becomes full, or the active directory becomes full of the logs that could not be archived.
The result is that the Tivoli Storage Manager server shuts down.
Cause
Tivoli Storage Manager server shuts down and archive log directory and active log directory are full. The server
cannot be started again.
Answer
When the archive log directory or active log directory fills up, or when the pre-allocated active logs fill up, the
Tivoli Storage Manager shuts down. In order to get the Tivoli Storage Manager server up and running, you
must update the DB2 configuration to change the location of the active log directory to a new location. This will
allow to active logs to free up space and then the Tivoli Storage Manager server can start. You can then clear
the archive log directory by issuing database backups. Complete the following procedure:
1. Create a temporary directory large enough to place the active logs.
See dsmserv.opt for value of ACTIVELOGSIZE.
2. Open a DB2 command prompt:
Windows:
Go to Start > All Programs > IBM DB2 > DB2COPY1 > Command Line Tools > Command Window Administrator.
AIX/Linux/Unix:
1. Open a terminal session.
2. Log in as the Tivoli Storage Manager instance user.
3. Update the DB2 configuration to specify the new location for active log directory that you just created. From
the DB2 command prompt, issue the following commands:
set db2instance=SERVER1
db2start
db2 update db cfg for tsmdb1 using newlogpath <path_from_step1>
Verify that the path was updated
db2 connect to tsmdb1
db2 get db cfg for tsmdb1 | grep NEWLOGPATH
db2 terminate
4. The active log files will not be removed until the following 'activate' command is issued.
First perform a deactivation to ensure that the database is not already activated:
db2 deactivate db tsmdb1
Then run the activate command:
db2 activate db tsmdb1
Note: The active logs will be COPIED and RENAMED (not moved) to the new temporary directory that you
specified in step 1.
5. You have 2 options to prune the archive logs to get the Tivoli Storage Manager sever back up and running:
Historical Number
Technotes (troubleshooting) # 1394424
Product Alias/Synonym
TSM