Originally Posted by Orange Sunshine
Any other reason you guys can think of that the script would execute fine on the oracle box but not via ssh from my resin box? OR, any suggestions as to how I can do something similar in another way?
Well, not sure if it will work for your situation and requirements, but how about starting the script locally, not remotely?
E. g. you still go ahead and copy your script over as required. However, you do NOT start it from your remote connection. How about setting up a script on the target machine, that is run by cron locally on that machine, that starts your script?
E. g. setup a cron that runs each five minutes. All it does is call your script that has been copied in whenever like you detail in your above messages. This way, from everything on the target machine's viewpoint, the script starts up LOCALLY, via cron, so it should have all the permissions it needs? Just write the cron script locally "as" the user which runs Oracle.
You can then add refinements such as having the cronned script just die quietly if your "command script" is not present in a certain folder. This way you can precisely control when and what is executed, simply by copying over the script, leaving for at least 6 minutes (thus ensuring execution somewhere in that time window, by cron, of the script) and then deleting it remotely?
You can do all this quite easily with PHP for example, as regards making an FTP connection to copy the file to a certain location, then deleting it after a time delay... you can even farm that time delay functionality out to the cron on your remote system?
The idea of course being to NOT try to run the script remotely, but having it run locally as the correct user Oracle runs as anyway. This should short-circuit any permission complaints, I hope...