When you get an error message that a dependent library is missing, it is helpful to verify the exact environment variable settings being used by Harvest. Here is an easy way to do that.
CA Harvest SCM all versions on Linux or Unix platforms
# make sure you're logged in as the user that owns the $CA_SCM_HOME folder and files (for example, if your “owner” userid is “cascm”):
su - cascm
# cd to the bin folder
# make a copy of one of the command scripts and rename it "test"
cp hdbsetup test
# comment out the last line of the script that starts with "exec "
sed -i 's/exec /#exec /g' test
# add a new last line to run the "env" command - returns the current environment variable settings
sed -i -e '$a\env' test
# execute the new script