Skip to content

M141 - Admin / Betrieb DBM

Start / Stop DBM

db2 START DBM

db2 STOP DBM FORCE

Connect to database / Disconnect from database

db2 CONNECT TO DBBW001

db2 CONNECTION RESET

Run SQL script from CLI

db2 -tvsf script.sql

Grant privileges to a user for a table

db2 "GRANT SELECT, INSERT, UPDATE, DELETE ON BIBLIO.TARTIKEL TO USER bbwuser;"

then proceed to check privileges: db2 SELECT * FROM SYSCAT.TABAUTH;

Backup database

Offline

db2 backup database DBBW001 to /bbw/DBbackup

Online

db2 backup database DBBW001 online to /bbw/DBbackup

Restore database

The location specified after 'FROM' must be a directory, not a file.

Make sure to select the timestamp that is equivalent to the one of your desired backup.

db2 "RESTORE DB DBBW001 FROM /bbw/DBbackup/ TAKEN AT 20230417084512"

Update database config

From first test:

db2 update db cfg for dbbw001 using LOGRETAIN RECOVERY

db2 update db cfg for dbbw001 using AUTO_MAINT OFF

db2 update db cfg for dbbw001 using AUTO_DEL_REC_OBJ ON

From Ueb4

db2 update db cfg for dbbw001 using NEWLOGPATH '/bbw/activelog1'

db2 update db cfg for dbbw001 using MIRRORLOGPATH '/bbw/activelog2'

db2 update db cfg for dbbw001 using LOGARCHMETH1 DISK:/bbw/archlog1

db2 update db cfg for dbbw001 using LOGARCHMETH2 DISK:/bbw/archlog2

db2 update db cfg for dbbw001 using LOG RETAIN RECOVERY

db2 update db cfg for dbbw001 using AUTO_DEL_REC_OBJ ON

Search DBM config

the parameter 'logprimary' is an example of a parameter to search for.
make sure to specify the correct database after 'for'

db2 get db cfg for dbbw001 | grep -i logprimary

Rollforward database after restore

This is only necessary if the specified database is enabled for roll-forward recovery and it has been restored but not rolled forward.
see https://www.ibm.com/docs/en/db2/10.5?topic=messages-sql1000-sql1249#sql1117n for more detail

db2 rollforward db DBBW001 to end of logs and stop