Domdsmc DB2activatedbs

Purpose

The domdsmc db2activatedbs parameter activates DB2® enabled Notes® databases that are restored to an alternate database. This command copies the specified DB2 enabled Notes database into the Domino® DB2 database and brings the database online. When a list of database is activated and the /isolate parameter is specified, each DB2 enabled Notes database is activated to a new DB2 Group.

The DB2 enabled Notes databases in the alternate DB2 database are available for restore as long the alternate DB2 database is available. The alternate DB2 database is considered available when it is not manually deleted through DB2 server interface, overwritten by another restore operation, or removed from the list of DB2 databases (that contain DB2 enabled Notes databases) available for activation. See the Domdsmc DB2deletealternate command for information about how to remove a database from the activation list.

Parameters

*|dbname,dbname,...

Specifies the DB2 enabled Notes databases to activate. The DB2 enabled Notes databases are activated into the current DB2 Group.

/CONFIGfile=cfgfilename

Specifies the name of the Data Protection for IBM® Domino preferences file. The file name can include a fully qualified path. If you do not specify a path, it is assumed the preferences file in the directory where Data Protection for HCL Domino is installed.

The default preferences file is domdsm.cfg.

/DB2ALtdbname=database name

Specify the name of the alternate DB2 database to use for activation. If the /DB2ALtdbname parameter is not specified, the value of the /DB2ALtdbname configuration option (defined in the Data Protection for HCL Domino domdsm.cfg preferences file) is used. If /DB2ALtdbname is not defined in the preferences file, the alternate database name DOM_ALT is used.

/INTOPath=translogpath|pathname

Specifies the file path that is used for the restored transaction logs. The file path must be a fully qualified physical path. The translogpath variable that is shown in the syntax diagram represents the default location of the Domino server transaction log files and is not a keyword that can be specified on the command line. The default location of the Domino server transaction log files is defined by the TRANSLOG_Path variable in the notes.ini file.

/ISOLATE

Specify this parameter to activate the database into a new DB2 Group.

/LOCKGroup

Specify whether to lock the DB2 Group after the DB2 enabled Notes database is activated.

/LOGFile=logfilename

Specifies the name of the activity log that is generated by Data Protection for IBM Domino. The log file name is used for the current command and does not update the default log file that is stored in the preferences file. You can use the set command to change the default log file name that is stored in the preferences file. The command-line parameter can be used to override the default for one command run. If the specified file does not exist, it is created. If it does exist, new log entries are appended to the file. The file name can include a fully qualified path. If you do not specify a path, the file is written to the directory where Data Protection for HCL Domino is installed.

The default log file is domdsm.log.

When you are using multiple simultaneous instances of Data Protection for IBM Domino to run operations, use the /logfile parameter to specify a different log file for each instance. Using this parameter directs logging for each instance to a different log file and prevents interspersed log file records. Failure to specify a different log file for each instance can result in unreadable log files.

/LOGPRUne=60|n|No

Specifies whether to prune log entries. By default, log pruning is enabled and done daily. You can use the set command to do one of the following actions:

• Change the defaults so that log pruning is disabled
• Change the number of days log entries are saved

You can use the /logprune option to override these defaults for one command run. Note, when the value of /logprune is a number, the prune is done even if one is complete for the day.

You can specify:

60

Specifies that log entries are saved for 60 days before pruning.

n

Specifies the number of days to save log entries. The range of values is 0 - 9999. A value of 0 deletes all entries in the log except for the current command run entries.

No

Do not prune the log.

Changes to the value of the timeformat or dateformat parameter can result in an undesired pruning of the log file. If you are running a command that prunes the log file and the value of the timeformat or dateformat parameter changes, run one of the following to prevent pruning of the log file:

• Make a copy of the existing log file.
• Specify a new log file with the /logfile parameter or logfile setting.

/PICk=SHOWACtive|SHOWALl

Displays a list of database backups that match the dbname pattern that can be selected for restore. The pick list is displayed as a scrollable list from which you can select the database backups for restore.

You can specify:

SHOWACtive

Displays a list of active database backup versions.

SHOWALl

Displays a list of both active and inactive database backup versions. All the backup versions that match the dbname pattern are shown.

/Quiet

Specifies that status information does not display. However, the information is written to the activity log.

/REPlace=Yes|No

Specifies whether to replace existing databases on the target system.

You can specify:

Yes

Allows an existing database on the target system to be replaced during the restore process.

No

Prevents an existing database on the target system from being overwritten during the restore process.