Error while inserting data in Forms10G using TEXT_IO

Question

Dear all i am using 10g Forms.
I am using Text_io to read the text file and putting into table and again reading the tables and putting into another text file .
I was testing in 3 tables which is the same copy of the original table but only the name is different .
But after testing when i change the table name to Original table name , it is not inserting for 1 table .
What could be the reason ?
I already check the columns and all , everything is current .
Edited by: Sandy on Sep 14, 2010 5:39 PM

Answer 1

Please use tags when posting your code over here and format it proper so others can read it more easily.
e.g.
[code]
procedure my_proc is
  num_data number;
begin
  select 1
  into num_data
  from dual;
  if num_data = 2 then
end;
[/code]
Are you sure you are getting here:
[code]
INSERT INTO MU_PAY_OLB(RECORD_TYPE,LOAD_NO,TRAN_AMT,OLB_CODE,ACCT_NO,BEN_NAME,PAY_DTL,MACCS_IND)
VALUES(lval,l_val,DTL_AMT,lbank,DTL_BEN_AC_NO,DTL_BEN_NM,Null,'N');
[/code]
Also: only trap the exceptions you expect, and not ALL exceptions e.g.
[code]
begin
  INSERT INTO MU_PAY_OLB(RECORD_TYPE,LOAD_NO,TRAN_AMT,OLB_CODE,ACCT_NO,BEN_NAME,PAY_DTL,MACCS_IND)
  VALUES(lval,l_val,DTL_AMT,lbank,DTL_BEN_AC_NO,DTL_BEN_NM,Null,'N');
exception
  when dup_val_on_index then
    --do whatever you need to do in that case
end;
[/code]
Maybe your tablespace is full and thus your insert statement fails? You need to inform the user so he/she can inform the DBA.
and at last this one:
[code]
WHEN Others THEN
  Text_IO.Fclose(in_file);
END;
[/code]
You are hiding all possible exceptions; it might be a numeric or value error as the line you are reading is longer then your line buffer, or $add_any_possible_exception_here. You only close the file and behave like nothing ever happened. If you need to close your text file in any case it should look like this:
[code]
exception
  when others then
    if text_io.is_open(in_file) then
      text_io.fclose(in_file);
    end if;
    raise;
end;
[/code]
By that you are closing the file if necessary (the exception might occur after you closed the file and closing it again will cause another exception), and reraise your exception so it can be processed by the higher element in the call stack; maybe your calling procedure expects some exceptions in your procedure too and handles them respectively. If no one in the call stack expects the exception and traps it, it finds it's way to the end user (who is you in that case). If it throws an exception take a look where it happens and take actions.
So remove your when others exceptions and look if some other exceptions occur. By now there might occur an exceptions but as you are hiding them all we and you have no clue about if, when, why and where it happens. Remove / replace the exception handlers as shown and you should get a clue about if, when, why and where.
cheers