Insert into with problems

Question

Hy,
i have a little question. Try this:
create table strangetab (
id varchar2(20),
textfield varchar2(200)
CREATE OR REPLACE PROCEDURE writestrangetab
id VARCHAR2,
textfield varchar2 default null)
IS
pragma autonomous_transaction;
BEGIN
INSERT INTO strangetab
(id, textfield
) VALUES
(id, textfield
COMMIT;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line(sqlerrm);
rollback;
END;
After table and procedure creation, try to run this script (simple insert into in autonompus_transaction):
set serveroutput on
declare
vstr varchar2(10000);
begin
for i in 1..2000
loop
vstr := vstr||'r';
end loop;
dbms_output.put_line('write a');
writestrangetab( 'idx' , 'a');
dbms_output.put_line('write big string');
writestrangetab( 'idx' , vstr);
dbms_output.put_line('write b');
writestrangetab('idx' , 'b');
end;
The script generate this output:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
write a
write big string
ORA-12899: value too large for column "STRANGETAB"."TEXTFIELD" (actual:
2000, maximum: 200)
write b
As i expect, the second write goes wrong but first and third no and it put string a and b into srangetable.
Now try to run this:
set serveroutput on
declare
vstr varchar2(10000);
begin
for i in 1..5000
loop
vstr := vstr||'r';
end loop;
dbms_output.put_line('write a');
writestrangetab( 'idx' , 'a');
dbms_output.put_line('write big string');
writestrangetab( 'idx' , vstr);
dbms_output.put_line('write b');
writestrangetab('idx' , 'b');
end;
The only difference from the previous is the vstr dimension: first 2000 now 5000.
In my db (10.2.0.4 on linux) the output of this, is:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
write a
write big string
ORA-01461: can bind a LONG value only for insert into a LONG column
write b
ORA-01001: invalid cursor
If i query the strangetable i am non able to find string b (Only string a was registered)!
As if that were not enough, If you try to insert others writestrangetab, anything after wath that produce the error will be stored!
It is normal?
By
Stefano

Answer 1

Tanks for your reply Jhon, but:
1) "The second run you are trying to pass 5000 characters to a varchar, which caused your error when trying to call your procedure"
Why you say "which caused". When i call a procedure can't pass more than 4000 Chars? I know that pl/sql varchar2 is up to 32000 Chars even in procedure calls!
2) "That is why your cursor because invalid"
Witch cursor? The strange thing is that there isn't any cursor in the autonomous procedure! The anly statement is an insert into!
The problem of the second miss in the second run is ok: that wont register the string. The main problem is the miss of the third in the seconf run.
Why it not register the third writestrangetab? In that case i pass only a 'b' char. Writestarngetab Is an autonomous transaction so i expect a miss if it fail, but the next, if ok, will be registerd. why not?
By
Stefano