db2idrop - Remove instance command

You can only drop instances that are listed by db2ilist for the same DB2 copy where you are issuing db2idrop from.

On Linux and UNIX operating systems, this utility is located in the DB2DIR/instance directory, where DB2DIR represents the installation location where the current version of the DB2 database system is installed. On Windows operating systems, this utility is located under the DB2PATH\bin directory where DB2PATH is the location where the DB2 copy is installed.

Authorization

Root user authority on Linux and UNIX operating systems or Local Administrator on Windows operating systems.

Command syntax

For Linux and UNIX operating systems

>>-db2idrop--+-----+--+-----+--+-----+--InstName---------------><
             '- -d-'  '- -f-'  +- -h-+             
                               '- -?-'             

For Windows operating systems

>>-db2idrop--+-----+--+-----+--InstName------------------------><
             '- -f-'  '- -h-'             

Command parameters

For Linux and UNIX operating systems

InstName

Specifies the name of the instance.

-d

Enters debug mode, for use by DB2 database support.

-f

This parameter is deprecated.

Specifies the force applications flag. If this flag is specified all the applications using the instance will be forced to terminate.

-h | -?

Displays the usage information.

Usage notes

• Before an instance is dropped, ensure that the DB2 database manager has been stopped and that DB2 database applications accessing the instance are disconnected and terminated. DB2 databases associated with the instance can be backed up, and configuration data saved for future reference if needed.
• The db2idrop command does not remove any databases. Remove the databases first if they are no longer required. If the databases are not removed, they can always be catalogued under another DB2 copy of the same release and continued to be used.
• If you wish to save DB2 Text Search configurations and plan to reuse instance databases, you need to take the extra step of saving the config directory (on UNIX: instance_home/sqllib/db2tss/config and on Windows: instance_profile_path\instance_name\db2tss\config) or config directory contents before issuing the db2idrop command. After the new instance is created, the config directory can be restored. However, restoring the config directory is only applicable if the new instance created is of the same release and fix pack level.
• A non-root-installed instance cannot be dropped on Linux and UNIX operating systems. To remove this DB2 instance, the only option available to the user is to uninstall the non-root copy of DB2 by running db2_deinstall -a.
• On Linux and UNIX operating systems, if you are using the su command instead of the login command to become the root user, you must issue the su command with the - option to indicate that the process environment is to be set as if you had logged in to the system using the login command.
• On Linux and UNIX operating systems, you must not source the DB2 instance environment for the root user. Running db2idrop when you sourced the DB2 instance environment is not supported.

• On AIX® 6.1 (or higher), when running this command from a shared DB2 copy in a system workload partition (WPAR) global environment, this command must be run as the root user.

• On Windows operating systems, if the IBM® Tivoli® Monitoring for Databases: DB2 Agent is installed and the DB2 instance is dropped, the Monitoring Agent for DB2 is stopped. All files, services and registry entries created for the Monitoring Agent for DB2 instance are also deleted.
• On Windows operating systems, if an instance is clustered with Microsoft Cluster Service (MSCS), then you can uncluster that instance by issuing the db2mscs or db2iclus command prior to dropping the instance.