Quick Beginnings for DB2 Universal Database for UNIX

Step 4. Remove DB2 Instances

You can optionally remove some or all of the DB2 Version 5 instances on your system. Once an instance is removed, all the DB2 databases owned by the instance, if any, will not be usable. Remove DB2 instances only if you are not planning to use DB2 Version 5 products, or if you do not want to migrate existing instances to a later version of DB2. See Chapter 6. Migrating from Previous Versions and Releases for more information on how to migrate or upgrade to higher versions of DB2.

To remove an instance, perform the following steps:

1. Log in as the instance owner.

2. Stop the instance by issuing the db2stop command.

3. Back up files in the INSTHOME/sqllib directory, if needed.

   You might want to save the database manager configuration file, db2systm, the db2nodes.cfg file, or user defined function or fenced stored procedure applications in INSTHOME/sqllib/function, where INSTHOME is the home directory of the instance owner.

4. Log off as the instance owner.

5. Log in as user with root authority.

6. Remove the instance using the db2idrop command. You can enter the DB2IDROP command as follows:

      DB2DIR/instance/db2idrop InstName
   

   InstName is the login name of the instance.
   

   	where DB2DIR	= /usr/lpp/db2_05_00	on AIX
   		= /opt/IBMdb2/V5.0	HP-UX, SCO UnixWare 7, Solaris, or SGI IRIX
   		= /usr/IBMdb2/V2.1	on SCO OpenServer
   		= /opt/IBMdb2/V2.1	on SINIX

7. Optionally, as a user with root authority, remove the instance owner's user ID and group (if used only for that instance). Do not remove these if you are planning to re-create the instance.

   This step is optional since the instance owner and the instance owner group may be used for other purposes.

The db2idrop command removes the instance entry from the list of instances and removes the INSTHOME/sqllib directory.

[ DB2 List of Books | Search the DB2 Books ]