This content has been marked as final. Show 8 replies
below is link
Re: what is wrong? dbms_scheduler
Most important, in windows must be: job_action => 'C:\windows\system32\cmd.exe',
all scheduler scripts must be triggered by windows command line with parameter /c
Hope to help you.
Hello, Krzysztof. Thank you for the reply.
Just like you, I've tried lots of tutorials and read several posts made by others, but I just can't get it right.
Well... I had already tried setting the job action as a call to CMD, but I was using '/q' as argument number 1 and '/c' as argument number 2. Now I'm trying it with no '/q' argument but things are still the same. The one thing I find really odd about it, is that I have the very same job working just fine at one server, where I run the batch as the job action. All the other places I created this job it does not work at all!
To make a long story short, right now this is the scenario:
The job does run;--
The batch file is executed;
The .exe file appears at the task manager list os processes, but doesn't do what it is supposed to;
On the other hand, if I manually run the batch through Windows Explorer, it works just fine.
Any other ideas?
could you present short piece of yr script from batch file, please?
I think that you are trying run script by some program. As you can see in my above link, there is:
I passed full path to program which supposed to make code. Please check paths in batch file.
C:\oraclexe\app\oracle\product....\bin\rman target sys/password@XE ...
I read it, but to be honest I didn't quite understand it...
Me batch file is very simple and short:
The '1' and '2' parameters are codes that the .exe receives in order to generate a few reports. In other words, the batch runs the executable twice, sending different parameters.
Again, through Windows Explorer it works just fine...