Query runs from command line, but not from scheduler

Question

We use Control-M to schedule shell scripts to be run on a Solaris server. Some of the scripts have to access an Oracle database and in that case our security team will include the DB user and password in the script, then encrypt it and the sys admin team schedules the encrypted shell script with Control-M. That works fine, but we've been trying to have the DB user and password on a separate encrypted file so that we don't have to ask for file encryption every time it's necessary to modify a script (this is a test environment).
We have the script at ~/system_name/scripts, the query at ~/system_name/sql and the encrypted file and key at ~/system_name/keys. The SQLPlus call in the script is:
${ORACLE_HOME}/bin/sqlplus "`decrypt -a 3des -k ./../keys/key.3des.system -i ./../keys/login.system`"@instance_name <<EOF
@${DIR_SQL}/TEST_QUERY.SQL
quit
EOF
The security analyst has tested is successfully from command line, but when we schedule it with Control-M the job abends and we get the following in the sysout:
+ decrypt -a 3des -k ./../keys/key.3des.system -i ./../keys/login.system
decrypt: cannot open ./../keys/key.3des.system
decrypt: invalid key.
+ /u00/app/oracle/product/11.1.0/db_1/bin/sqlplus @instance_name
+ 0<<
@/sistemas/hmp/system_name/sql/TEST_QUERY.SQL
quit
SQL*Plus: Release 11.1.0.6.0 - Production on Mon May 3 09:41:55 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SP2-0310: unable to open file "instance_name.sql"
Enter user-name: SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER|SYSASM}]
where <logon> ::= <username>[<password>][@<connect_identifier>] [edition=valu\
e] | /
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER|SYSASM}]
where <logon> ::= <username>[<password>][@<connect_identifier>] [edition=valu\
e] | /
Enter password:
ERROR:
ORA-12545: Connect failed because target host or object does not exist
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
0000000080
Any ideas?

Answer 1

Looks like the command is being split in some way - the connection to sqlplus is being made before it completes the whole string
It appears to be seeing the @instance_name as a script to execute rather than a db to connect to.
Is the database on the same server as the script?
If so, try setting your environment to the correct databsae, so that you can omit the @instance_name part of the syntax and see if it helps
Also just noticed the failure to open the decrypt script. It would appear uyou are not using a full path name. Have you checked which directroy the scheduled job starts in? You may need to look at running some environment specific scripts first.
Edited by: LindaA on 05-May-2010 07:43