Re: dbms_scheduler and external job
- From: Robert Freeman <robertgfreeman@xxxxxxxxx>
- To: jkstill@xxxxxxxxx, goran00@xxxxxxxxx
- Date: Fri, 28 Mar 2008 12:43:56 -0700 (PDT)
I assume that the Oracle owning account has permissions to run the script?
RF
Robert G. Freeman
Author:
Oracle Database 11g New Features (Oracle Press)
Portable DBA: Oracle (Oracle Press)
Oracle Database 10g New Features (Oracle Press)
Oracle9i RMAN Backup and Recovery (Oracle Press)
Oracle9i New Feature
Blog: http://robertgfreeman.blogspot.com (Oracle Press)
----- Original Message ----
From: Jared Still <jkstill@xxxxxxxxx>
To: goran00@xxxxxxxxx
Cc: Oracle L <oracle-l@xxxxxxxxxxxxx>
Sent: Friday, March 28, 2008 12:49:20 PM
Subject: Re: dbms_scheduler and external job
I have yet to try and do anything with dbms_scheduler, but one thing that
you might try is to run the shell script from cron.
If it won't work from cron, the issue is one of setting up the environment
inside the script.
HTH
Jared
On Thu, Mar 27, 2008 at 7:05 AM, goran bogdanovic <goran00@xxxxxxxxx> wrote:
Hi all,
While working with scheduler and external jobs on 11g (OS: RHEL 4 U6 - 64-bit)
I have encountered the error:
SQL> exec DBMS_SCHEDULER.run_job('FTJOB');
BEGIN DBMS_SCHEDULER.run_job('FTJOB'); END;
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 31854
Session ID: 295 Serial number: 20
- from trace fie:
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xC8]
[PC:0x1218199, Exception [type: SIGSEGV, Address not
mapped to object] [ADDR:0xC8] [PC:0x1218199, jslve_execute0()+3927]
Incident 24154 created, dump file:
/opt/oracle/diag/rdbms/stat/stat/incident/incdir_24154/stat_ora_31652_i24154.trc
ORA-07445:exception encountered: core dump [jslve_execute0()+3927]
[SIGSEGV][ADDR:0xC8] [PC:0x1218199] [Address not mapped to object] []
ssexhd: crashing the process...
Shadow_Core_Dump = partial
This job calls one bash shell script (which works fine when executed directly
from bash prompt). This kind of scheduler jobs afaik works fine in 10g.
It sounds like a bug to me.
Did anyone else have encountered similar error?
Thanks
goran
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Other related posts:
