This content has been marked as final. Show 3 replies
The version number is 11R2.
The ssh keys are in $HOME/.ssh/known_hosts cf. authorized_keys and logging in to 'that_other_host' via 'ssh hostuser@that_other_host' works just like a charm. And as said above, registering the db with the scheduler agent on 'that_other_host' was no problem at all either.
But I now believe that this ssh stuff is not really relevant to the problem at hand. The credential is not for communicating with the scheduler agent on 'that_other_host', it is for making jssu (on 'that_other_host') able to su/sudo my OS commands. Right?