Object | Action | Database administration command | Description |
---|---|---|---|
Hosts | Manage DB2 pureScale Host Maintenance Mode | db2cluster with one of the following options
|
Either puts or removes the target host from
maintenance mode. The target host must be in maintenance mode to apply
software updates to DB2 cluster services. The host must have a least one DB2 pureScale instance, and at least one profile was created and connected. |
Verify DB2 cluster services status | db2cluster with one of the following options
|
Verify the status and configuration of DB2 cluster services. The task assistant can
do the following tasks:
|
|
Manage DB2 cluster services configuration | !db2cluster -cm -set -option -pprimary | Sets a new preferred primary value for DB2 cluster services.
The option specifies which cluster caching facility DB2 cluster services will attempt to start in
the primary role. Attention: Make sure to check that the
preferred primary value was changed after you run the command by looking
at the output of the command in the SQLResults view. The db2cluster
command is not recognized by DB2 CLP,
so the command will run as an external command. DB2 CLP always reports success for any external
command irrespective of the actual result of the external command.
This behaviour will be addressed in future releases.
|
|
Instances | Configure | UPDATE DATABASE MANAGER CONFIGURATION | Modifies individual entries in the database manager configuration file. |
Quiesce | QUIESCE | Forces all users off the specified instance and puts the instance into quiesced mode. | |
Start | db2start | Starts the DB2 instance. | |
Stop | db2stop | Stops the DB2 instance. | |
Unquiesce | UNQUIESCE | Restores user access to instances that were quiesced for maintenance or other reasons. | |
Databases | Backup | BACKUP DATABASE | Creates a backup copy of a database or table space. |
Configure | UPDATE DATABASE CONFIGURATION | Modifies individual entries in a specific database configuration file. | |
Configure Automatic Maintenance | UPDATE DATABASE CONFIGURATION | Enables or disables the various automatic maintenance activities that can be performed and defines a maintenance interval and window in which the activities can occur. Maintenance activities can occur during the maintenance window only if DB2 determines that the maintenance is required. | |
Configure Database Logging | UPDATE CONFIGURATION LOGGING | Modifies the data logging options for your database, such as the type of logging to use, the size of the log files, and the location where log files will be stored. | |
Create | CREATE DATABASE | Creates a database with either automatic or manual storage. | |
Drop | DROP DATABASE | Deletes the database contents and all log files for the database, uncatalogs the database, and deletes the database subdirectory. | |
HADR Setup | Various | Sets up the High Availability Disaster Recovery (HADR) feature for your database. The HADR feature ensures that changes to the database can be replicated to a standby database. The standby database takes over in the event of a failure on the primary system. | |
HADR Manage | START HADR, STOP HADR, TAKEOVER HADR | Starts and stops HADR operations on either the primary or standby database. You can also instruct the standby database to take over as the new primary database in the event of a failure on the primary system. | |
List or Force Applications | FORCE APPLICATIONS | Forces local or remote users or applications off of the system to allow for maintenance on a server. | |
Manage Storage | ALTER DATABASE ADD STORAGE | Specifies that one or more new storage locations are to be added to the collection of storage locations that are used for automatic storage table spaces. | |
Quiesce | QUIESCE | Forces all users off of the specified database and puts the database into quiesced mode. | |
Recover | RECOVER DATABASE | Restores and rolls forward a database to a particular point in time or to the end of the logs. | |
Restart | RESTART DATABASE | Restarts a database that has been abnormally terminated and left in an inconsistent state. | |
Restore | RESTORE DATABASE | Re-creates a damaged or corrupted database that was backed up with the DB2 backup utility. | |
Roll Forward | ROLLFORWARD DATABASE | Recovers a database by applying transactions that were recorded in the database log files. | |
Cancel Roll Forward | ROLLFOWARD DATABASE with CANCEL option | Cancels the roll-forward recovery operation. The database is put in restore pending status. | |
Complete Roll Forward | ROLLFORWARD DATABASE with COMPLETE option | For databases that were archived and restored, but did not have the logs rolled forward, rolls forward the logs. The logs can be rolled forward to a point in time or to the end of the log. | |
Start | ACTIVATE DATABASE | Activates the specified database and starts all necessary database services so that the database is available for connection and use by any application. | |
Stop | DEACTIVATE DATABASE | Deactivates the specified database. | |
Unquiesce | UNQUIESCE | Restores user access databases that were quiesced for maintenance or other reasons. | |
Table spaces | Backup | BACKUP | Creates a backup copy of a table space. |
Restore | RESTORE | Re-creates a damaged or corrupted table space that was backed up with the DB2 backup utility. The task assistant does not support restoring multiple table spaces. | |
Rollforward | ROLLFORWARD DATABASE | Recovers a table space by applying transactions that were recorded in the log files. | |
Cancel Roll Forward | ROLLFOWARD DATABASE with CANCEL option | Cancels the roll-forward recovery operation. One or more table spaces are put in restore pending status. | |
Complete Roll Forward | ROLLFORWARD DATABASE with COMPLETE option | For table spaces that were archived and restored, but did not have the logs rolled forward, rolls forward the logs. The logs can be rolled forward to a point in time or to the end of the log. | |
Tables | Export Table | EXPORT | Exports data from a table to one of several external file formats. |
Optim™ High Performance Unload | db2hpu | Uses Optim High
Performance Unload commands to unload data from a DB2 table or to copy data from source tables
to target tables by using temporary files to store the data. You can
also migrate data from one database system to another. To specify Optim High Performance Unload as the unload method, Optim High Performance Unload for Linux, UNIX, and Windows must be installed on each database system that is involved in the unload or migration. |
|
Import Table | IMPORT | Inserts data from an external file with a supported file format into a table. | |
Load Table | LOAD | Loads data into a DB2 table. | |
Reorg Table | REORG TABLE | Reorganizes a table. | |
Reorg Index | REORG INDEX | Reorganizes all of the indexes that are defined for the table. | |
Run Statistics | RUNSTATS | Updates the statistics about the characteristics of a table, its indexes, or both. | |
Set Integrity | SET INTEGRITY | Brings tables out of set integrity pending state, places tables in set integrity pending state, places tables into full access state, or prunes the contents of staging tables. | |
Packages | Rebind | REBIND PACKAGE | Re-creates a package without needing the original bind file. |