Good morning,
I'm not sure whether this will help you with the upgrade.exe Problem, but we're using the following mechanism to run sql files automatically:
(Maybe you can adapt this to suit your needs).
1) We have a file - let's call it "statement.sql" containg the sql statement we want to run automatically
statement.sql
-------------
spool /scripts/statement
set underline off
set heading off
set linesize 300
set pagesize 5000
set feedback off
SELECT
tournr,
weight,
TO_CHAR(tourend_datum,'DD.MM.YYYY') DD_MM_YYYY,
tourend_time,
FROM
db.tour tour,
spool off
2) We have a file - let's call it "statement" that's actually executing the file "statement.sql". This file not only executes the statement, but also puts the output into a txt file.
statement
---------
ORACLE_HOME=/usr/oracle/8; export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME/bin:/usr/lbin; export PATH
ORACLE_SID=<sid>; export ORACLE_SID
ORACLE_OWNER=<owner>; export ORACLE_OWNER
sqlplus << abgleich
user/password <-- here you have to enter your user and password in clear text !
@/scripts/statement.sql
quit
abgleich
tail +2 /scripts/statement1.lst > /statement2.txt
cat /statement2.txt|grep -v ^$ > /statement3.txt
rm /statement2.txt
chmod 777 /statement3.txt
3) We run the "statement" file periodically via crontab.
00 12 * * * /scripts/statement > /dev/null
Regards
Thomas