It can be due to incorrect ownership or permissions on db2sysc executable.
Check the file permission in <instance_home>/sqllib/adm - It should be "-r-sr-s---" and owned by root:db2grp1 (in your case)
Log in as root and update the instance (db2iupdt).
Check the permission of db2sysc executable in <instance_home>/sqllib/adm directory - it should be "-r-sr-s---".
If its different,
- login as root
- change directory to /usr/opt/db2_08_01/instance
- Update the instance - ./db2iupdt db2inst1
Before the instance update ensure all DB2 interprocess communications are cleared for the instance to be updated. As the instance owner, run: <instance_home>/sqllib/bin/ipclean.
Check the file permission in <instance_home>/sqllib/adm - It should be "-r-sr-s---" and owned by root:db2grp1 (in your case)
Log in as root and update the instance (db2iupdt).
Check the permission of db2sysc executable in <instance_home>/sqllib/adm directory - it should be "-r-sr-s---".
If its different,
- login as root
- change directory to /usr/opt/db2_08_01/instance
- Update the instance - ./db2iupdt db2inst1
Before the instance update ensure all DB2 interprocess communications are cleared for the instance to be updated. As the instance owner, run: <instance_home>/sqllib/bin/ipclean.
本文转自gnuhpc博客园博客，原文链接：http://www.cnblogs.com/gnuhpc/archive/2012/12/21/2828292.html，如需转载请自行联系原作者
