run an external OS script in Oracle 10g
Michele Campagni
vmstat.sh: "/usr/bin/vmstat >> /tmp/vmstat.LST"
which have this permission:
-rwxr-xr-x 1 oracle other 47 Apr 3 05:13
/export/home/oracle/vmstat.sh
I try with this:
BEGIN
dbms_scheduler.create_job(job_name => 'myjob',
job_type => 'executable',
job_action => '/oracle/vmstat.sh',
enabled => TRUE,
auto_drop => TRUE);
END;
/
but oracle responds:
SQL> exec dbms_scheduler.run_job('VMSTAT_JOB');
BEGIN dbms_scheduler.run_job('VMSTAT_JOB'); END;
*
ERROR at line 1:
ORA-27369: job of type EXECUTABLE failed with exit code: Not owner
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 1
I'm using Solaris 10/Sparc and Oracle 10g.
what's the problem?
thanks
Sybrand Bakker
/oracle/vmstat.sh doesn't look exactly like to be the same file as
/usr/bin/vmstat.sh
Other than that: why on earth are you running vmstat in a *database*.
--
Sybrand Bakker, Senior Oracle DBA
Michele Campagni
>>I've difficult in executing an external OS script like this:
>>vmstat.sh: "/usr/bin/vmstat >> /tmp/vmstat.LST"
>>which have this permission:
>>-rwxr-xr-x 1 oracle other 47 Apr 3 05:13
>>/oracle/vmstat.sh
^^^^^^^^^^^^^^^^
>>
>>I try with this:
>>
>>BEGIN
>> dbms_scheduler.create_job(job_name => 'myjob',
>> job_type => 'executable',
>> job_action => '/oracle/vmstat.sh',
^^^^^^^^^^^^^^^
Mladen Gogala
> /oracle/vmstat.sh doesn't look exactly like to be the same file as
> /usr/bin/vmstat.sh
> Other than that: why on earth are you running vmstat in a *database*.
Database scheduler has a lovely GUI interface and is much more convenient
and user friendly then cron. The problem is the user used to run the job.
After a small bug in security, discovered by Peter Finnigan and the
exploit code published by some bozo on this very newsgroup, oracle changed
the user which executes the jobs. As of 10.1.0.4, external executable jobs
executed by Oracle scheduler should be owned by the user "nobody", not
user "oracle".
To save you the trouble of googling, yes, I was the bozo that has
published the exploit code for the scheduler bug. A friend of mine
was very angry with me because he had to stay late and patch his databases
to plug the hole, then easily exploitable thanks to yours truly.
Mladen Gogala
> ERROR at line 1:
> ORA-27369: job of type EXECUTABLE failed with exit code: Not owner
There is a note about that on Metalink:
Note:337005.1
Please, let me know if you need help with searching on Metalink.
Michele Campagni
news:pan.2006.04.22....@sbcglobal.net...
> executed by Oracle scheduler should be owned by the user "nobody", not
> user "oracle".
ok, now script run but oracle reports:
ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 1
I repeat: script run and works, but I still have this warning...
Mladen Gogala
Michele Campagni
> How about contacting Oracle support?
I don't think they can help me... I run Oracle from Simics (a computer
architecture simulator) for my thesis on alternative cache systems, so I
can't access to Oracle support (I think). I try access Metalink but I need
an account that I have not.
This also explains why I can't use GUI interface or other useful toys, I'm
emulating a Sparc Enterprise 6500 with serial console on ttya.
By the way I have tried giving "other" owner to my script and it has
worked...
Ronald Rood
Could it be that the script just returns an exit code (or none at all) ? The
oracle scheduler has funny reactions on them.
Try with explicit exit 0.
--
With kind regards / met vriendelijke groeten,
Ronald
Michele Campagni
news:0001HW.C07403C8...@news.individual.net...
> Try with explicit exit 0.
GREAT! It works!
Thanks!!!