URGENT : dbms_job

Question

Hello every body.
I work with oracle 8i server 8.1.7 .
I created procedures and job . Here are the codes :
create or replace procedure importer_remise_transac(p_fichier varchar2)
is
v_file UTL_FILE.FILE_TYPE;
v_buff long;
v_affect varchar2(25);
v_long_fichier number;
v_fichier_char char(1);
v_position_last_bar number;
nb_bar number := 0;
v_path varchar2(2000);
v_fichier varchar2(255);
v_id_terminal number;
v_num_serie number;
v_id_commercant number;
procedure p_affect(p_data varchar2)
is
type tab_ty is varray(10) of varchar2(16);
v_tab tab_ty := tab_ty(null,null);
v_data varchar2(16);
v_long number;
k number := 1;
begin
select length(p_data) into v_long from dual;
for i in 1..v_long loop
if substr(p_data,i,1) = ';' then
v_tab(k) := v_data;
v_data := '';
k := k + 1;
else
v_data := v_data||substr(p_data,i,1);
end if;
end loop;
v_tab(k) := v_data;
select id_terminal into v_id_terminal from terminal where num_terminal = (v_tab(10)||v_tab(4));
select num_serie into v_num_serie from carte where num_carte=v_tab(5) and id_emetteur=(select id_emetteur from emetteur where num_emetteur=substr(v_tab(10),1,3));
select id_commercant into v_id_commercant from commercant where num_commercant=v_tab(10);
insert into transaction(ID_TRANSACTION,
TYPE_TRANSACTION,
NUM_TRANSACTION,
DATE_TRANSACTION,
ID_TERMINAL,
NUM_SERIE,
HEURE_TRANSACTION,
MONTANT_TRANSACTION,
ID_COMMERCANT)
values(seq_transaction.nextval,
v_tab(1),
v_tab(2),
to_date(v_tab(3),'DDMMRR'),
v_id_terminal,
v_num_serie,
v_tab(8),
v_tab(9),
v_id_commercant);
commit;
end;
begin
select length(p_fichier) into v_long_fichier from dual;
for i in 1..v_long_fichier loop
select substr(p_fichier,-i,1) into v_fichier_char from dual;
if v_fichier_char = '\' and nb_bar = 0 then
v_position_last_bar := v_long_fichier-i+1;
nb_bar := 1;
end if;
end loop;
select substr(p_fichier,1,v_position_last_bar) into v_path from dual;
select substr(p_fichier,v_position_last_bar+1) into v_fichier from dual;
v_file := UTL_FILE.FOPEN (v_path,v_fichier,'r',20000);
loop
UTL_FILE.GET_LINE(v_file,v_buff);
p_affect(v_buff);
end loop;
exception
when others then
utl_file.fclose(v_file);
end;
create public synonym importer_remise_transac for appli_backdb.importer_remise_transac
grant execute on importer_remise_transac to public
create or replace procedure lance_job_remise_galana
is
v_date varchar2(10);
v_path varchar2(100);
begin
select to_char(sysdate,'DD_MM_RRRR') into v_date from dual;
select 'E:\Remise_galana\'||v_date||'_Remise.txt' into v_path from dual;
importer_remise_transac(v_path);
end;
create public synonym lance_job_remise_galana for appli_backdb.lance_job_remise_galana
grant execute on lance_job_remise_galana to public
SQL>var x number
SQL>execute dbms_job.submit(:x,'lance_job_remise_galana;',sysdate,'sysdate+1/288')
SQL>commit;
The content of the file text 01_08_2003_Remise.txt is :
DT;000000193215500001;110703;002;1000033;10;000727;14:42;0000000000200000;1000000
DT;000000193215500004;110703;002;1000274;50;000000;15:26;0000000000232400;1000000
DT;000000193215500006;110703;002;1000039;12;394580;15:49;0000000000025000;1000000
DT;000000193215500008;110703;002;1000368;11;009252;15:54;0000000000150000;1000000
DT;000000193215500010;110703;002;0000015;14;000000;16:57;0000000000225000;1000000
DT;000000193215500012;110703;002;1000042;12;570649;17:13;0000000001020000;1000000
DT;000000193215500014;110703;002;1000113;12;005803;19:01;0000000000103800;1000000
DT;000000193215500018;110703;002;1000113;12;003556;19:03;0000000000269880;1000000
DT;000000193215500021;110703;002;1000115;10;132475;19:20;0000000000035000;1000000
DT;000000193215500023;110703;002;1000037;12;108930;19:24;0000000000050000;1000000
DT;000000193215500025;110703;002;1000113;12;007016;20:02;0000000001342480;1000000
The problem is that it seams that the job does not do its work : after 6 minutes , I select the table transaction and there is no row in it.
What is the solution ?
Thank you very much.

Answer 1

What is the status of the job in ALL_JOBS?
Does this program run if you call it from SQL*Plus. It has no exception handling, so if anything goes wrong it will crash and burn and you'll never know why.
If the program does run as a one off then you need to look at the JOB side of things, but on the face of it there is nothing amiss there.
Cheers, APC