Hi Jared and Robert, ...I have checked both things already. I would expect some other kind of error and not memory segmentation fault if env. was not set up correctly...or maybe I am wrong. thanks for tips. regards, goran On Fri, Mar 28, 2008 at 7:49 PM, Jared Still <jkstill@xxxxxxxxx> wrote: > 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 >