← Back to team overview

canonical-partner-dev team mailing list archive

[Bug 853750] [NEW] Wrong owner on symlink make IBM DB2's administrative instance fail to start

 

Public bug reported:

On db2exc 9.7.4-0lucid3, the init script tries to start the administration instance by:
- su-ing to the admin instance user
- calling "db2admin", which is in ~/das/bin/db2admin, which is in the PATH
This fails with the message "-su: das/bin/db2admin: Permission denied".
Calling /opt/ibm/db2/V9.7/das/bin/db2admin does not fail.
My guess is that it's because:
- ~/das/bin is a symbolic link owned by root
- but ~/das has the sticky bit, so only root can follow the symbolic link
Possible fixes :
- install the symbolic link with the instance admin user as owner
- OR calling /opt/ibm/db2/V9.7/das/bin/db2admin in the init script
- OR adding /opt/ibm/db2/V9.7/das/bin/db2admin to the PATH for the admin instance user
Lionel Sausin

** Affects: db2exc (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

- Wrong owner on symlink make administrative instance fail to start
+ Wrong owner on symlink make IBM DB2's administrative instance fail to start

-- 
You received this bug notification because you are a member of Canonical
Partner Developers, which is subscribed to db2exc in Ubuntu.
https://bugs.launchpad.net/bugs/853750

Title:
  Wrong owner on symlink make IBM DB2's administrative instance fail to
  start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/db2exc/+bug/853750/+subscriptions


Follow ups

References