Using the v3.4.26 version I've the impression that
the RunAndWait command used to run SQLPLUS with options
doesn't wait at all the end of this process.

What is going wrong ?

Robbert de GROOT
Paris - France

If you run a Windows version of SQLPLUS can launch sqlplusw and immediatelly exit. From the job point of the the started process gets completed and so the job gets completed. To avoid this use SQLPLUSW command directly.

: Using the v3.4.26 version I've the impression that
: the RunAndWait command used to run SQLPLUS with options
: doesn't wait at all the end of this process.

: What is going wrong ?

: Robbert de GROOT
: Paris - France

I'm (still) running oracle 7.3.4 and SQLPLUSW doesn't seem to exist

: If you run a Windows version of SQLPLUS can launch sqlplusw and immediatelly
: exit. From the job point of the the started process gets completed and so
: the job gets completed. To avoid this use SQLPLUSW command directly.

When you run that command manually, how the program name appears on the Processes tab in the Windows Tak Manager?

: I'm (still) running oracle 7.3.4 and SQLPLUSW doesn't seem to exist

I'm (still) running oracle 7.3.4 and SQLPLUSW doesn't seem to exist

: If you run a Windows version of SQLPLUS can launch sqlplusw and immediatelly
: exit. From the job point of the the started process gets completed and so
: the job gets completed. To avoid this use SQLPLUSW command directly.

Ok, I see what you mean : the program is launched as
SQLPLUS.EXE but is found in the Task Explorer (i'm
using the free Process Explorer of SysInternals (great suff)
as PLUS33W ... I'll go for that one in the 24x7
scripting and see what it brings.

: When you run that command manually, how the program name appears on the
: Processes tab in the Windows Tak Manager?

It works with PLUS33W ... great thanks for the help

: When you run that command manually, how the program name appears on the
: Processes tab in the Windows Tak Manager?

It should work.

: Ok, I see what you mean : the program is launched as
: SQLPLUS.EXE but is found in the Task Explorer (i'm
: using the free Process Explorer of SysInternals (great suff)
: as PLUS33W ... I'll go for that one in the 24x7
: scripting and see what it brings.