When you issue the command "dasdrop", you may receive the following output:
-bash: line 1: db2admin: command not found
db2set MsgRC=1303, P1='', P2='' DBI1070I Program dasdrop completed successfully.
Then if you issue the command "daslist", you see that the DAS is still there.
There are entries left in the global registry that need to be removed.
The global registry (not to be confused with the global profile registry which is manipulated with the db2set command) is found in /var/db2/global.reg (or /var/opt/db2/global.reg on HP-UX). The global registry is only found on UNIX® servers. The /var/db2/global.reg is created when the DB2 Administration Server is created.
If for some reason you can't find the global.reg file, use the utility db2greg -g to show you the location of the file. The db2greg utility is located in the $DB2DIR/bin directory, where $DB2DIR represents /usr/opt/db2_08_01 on AIX®, and /opt/IBM/db2/V8.1 on Linux®, HP-UX and Solaris. If you have a FixPak or modification level installed in an alternate path, the $DB2DIR directory is /usr/opt/db2_08_FPn on AIX and /opt/IBM/db2/V8.FPn on Linux, HP-UX and Solaris, where n represents the number of the FixPak or modification level.
To determine whether the global registry is the cause of your problem, check whether it still contains a DAS record (it should not, since the dasdrop utility indicated that the DAS was successfully dropped).
Use the db2greg -dump command to dump the registry's content to the screen. Confirm whether the DAS record exists. For example, look for rows where the first value is Service ("S") or Instance ("I") and the second value is "DAS":
$ db2greg -dump
On a working system with a DAS there will be a Service record and an Instance record. When the DAS is dropped these two entries should be removed automatically from global.reg. If these exist even after you have "successfully" dropped the DAS, then they need to be removed using db2greg.
The problem can be resolved by logging in as root and deleting the invalid entry from the global registry. In general, though, you should only follow these steps if requested to do so by DB2 Customer Support. Caution should be used when altering the global registry.
Entries can be deleted from the global registry as follows:
db2greg -delinstrec instancename=<DAS name>
1. Display the contents of the global.reg registry and verify that there are two DAS records similar to the ones shown:
# db2greg -dump
2. Remove the DAS "Service" record (change the field values as appropriate from step 1)
# db2greg -delservrec service=DAS,version=18.104.22.168,installpath=/opt/IBM/db2/V8.1/das
3. Remove the DAS "Instance" record (change the field values as appropriate from step 1)
# db2greg -delinstrec service=DAS,instancename=dasusr1
After cleaning up the global registry, you should no longer see the dropped DAS listed via the daslist command.