The DB2 connection
was lost following a database restore operation.
Explanation
The server database was restored, but the DB2® connection failed. For this
reason, if the path to the DB2 log
directory was changed as part of a DB restore operation, the database
path to the log directory was not updated automatically.
System action
The server database is restored.
User response
If the path to the DB2 log
directory did not change, no action is needed. If the path to the DB2 log directory changed, you must
manually update the path when the server is started. To update the
path, connect to the DB2 database
and change the configuration, as described in the following example:
- Start DB2: db2start
- Connect to TSMDB1: db2 connect to TSMDB1
- Update the DB2 database
configuration: db2 update db cfg using NEWLOGPATH (log path from server
options, e.g. /ALOG/tsminst1)
- Terminate the connection to TSMDB1: db2 terminate
- Recycle DB2: db2stop/db2start
- Verify that the new log path is in takes effect: db2 connect to
TSMDB1; db2 get db cfg | grep "Path to log files ( on UNIX ) "
- Verify that the new log path is in takes effect: db2 connect to
TSMDB1; db2 get db cfg | find "Path to log files ( on Windows ) "