SQL code SQL1032N tells you that db2 is not up (no db2start command was issued to bring up the instance). So, db2stop command failed (as quite expected). The truth is that there is no need to stop db2 if it is not up and running. So, you may ignore the error message you received from the db2stop command and start your backup procedures.
Note: If you expected the db2 to be up before issuing the db2stop command, then some thing went wrong. Either some body else shut down the instance earlier or db2 automatically stoped the engine due to
some unrecoverable error. Look at the db2diag.log file for more details.
Thanks for your help, what applies to our situation is what you referrd to in your Note. We expected it to be up but apparently it was down. The db2diag.log file was uninformative and it is still a mystery as to why the database was down at that point in time.
If you think DIAGLOG file does not contain enough information, you may want to update the DBM CFG to change the diagnostic option to 4 so that you will have enough info to trace the problem (if it happens again in the future).
To do this follow these steps (UNIX users only):
1. Login as the instance owner
2. Execute the "db2profile" script to setup the environment
3. Issue the following command:
db2 update dbm cfg using DIAGLEVEL 4
4. stop and start the instance to take effect the new DIAGLEVEL.
Note: Option "4" puts out maximum info (including any startup and
shutdown commands issued against the instance).