Starting and stopping an instance (an instance = database) in Oracle is done with the ALTER DATABASE command, which is NOT the case with DB2. Make sure you want to shut down the instance, not just a database. This will shut down all databases in the instance.

[db2inst1@nodedb21 ~]$ db2stop SQL1064N DB2STOP processing was successful.

In DB2, a START DBM/STOP DBM is done at the instance level, so all databases from the instance are started/shut down.

Certain parameter changes necessitate rebouncing a database. Remember, in DB2 there may be more than one database per instance. If you need to start/stop a single database from an instance you use the activate/deactivate database command.

[db2inst1@nodedb21 ~]$ db2 connect reset DB20000I The SQL command completed successfully.[db2inst1@ nodedb21 ~]$ db2 deactivate database pos DB20000I The DEACTIVATE DATABASE command completed successfully. 

Adding or dropping containers (Oracle datafile) is done with DB2's ALTER TABLESPACE command. However, you cannot rename a container.

db2 ALTER TABLESPACE NAV_TBLS DROP ( FILE '/data/db2/db2inst1/NODE0000/nav/nav_tbls.dbf' ) 

Log files are managed by the get/update database configuration command.

db2 update db cfg using newlogpath /data/db2/NODE0000/pos/ db2logdir deferred

A backup should be made after changing the logging mode. Within the control center, you will be prompted to make a backup after changing the logging mode.

There is no equivalent to Oracle's control files in DB2, so there is no replacement to manipulate those kinds of files in DB2.

You can also issue QUIESCE INSTANCE and all databases will be in quiesced mode. Only users having SYSADM, SYSMAINT, or SYSCTRL authorization can access the databases and their objects. In the same fashion, UNQUIESCE INSTANCE restores access at the instance level and all its databases to regular users.

However, you can use the QUIESCE DATABASE command to quiesce a single database. The force connections option allows disconnecting users from the database. When the database is in a quiesced mode, you can still perform administrative tasks on it. You need to issue the UNQUIESCE DATABASE command, which restores user access to the database.

DB2's RESTORE DATABASE command is used to recover from a backup. It covers all the recovery aspects of Oracle's recover database command.

HADR is DB2's counterpart of Oracle's Data Guard technology. It enables to have a secure copy of a database in a remote location, so in case a disaster occurs, the remote site can take over data processing for this database. It works in the same way with regards to sending transaction logs to a remote server and applying the logs on another database. It has its own set of commands and is not part of the alter database syntax.