What' wrong???

Question

hi everybody,
I've a problem which need a genius to solve.
I've written some code into the when-button pressed trigger:
DECLARE
clob_help clob;
clob_rec clob;
video_h number(38);
clip_h number(38);
tt_h varchar2(4000);
help number(38):=0;
cursor c1 is select gt.video,gt.clip,gt.text_data from get_tt_view gt;
amt binary_integer;
pos integer:=1;
begin
for rec in c1 loop
tt_h:=rec.text_data;
amt:=length(tt_h);
dbms_lob.write(clob_rec,amt,pos,'asd');
dbms_lob.append(clob_help,clob_rec);
if help != rec.clip AND help!=0 then
insert into save_result_tt values(rec.video,rec.clip,clob_help);
commit;
end if;
help:=rec.clip;
end loop;
end;
when i start this code an error occurs(frm-40735; ora-06502).
this error says that a datatype is not correct.
I've tried to delete the dbms_lob.write line it works.
what's wrong?????
thanks in advance
tommyO
PS:
the database fields have the same length as the parameters in the script.

Answer 1

Hey Thomas,
Just go thru the below rules and limitations and see whether you're doing any one of that, may find a solution by yourselves.
So, you'll be a genius by yourself if you solve it. Sorry it's not a direct answer for ya, but may help to ya, here you go
-- RULES AND LIMITATIONS
-- The following rules apply in the specification of functions and
-- procedures in this package.
-- LENGTH and OFFSET parameters for routines operating on BLOBs and
-- BFILEs are to be specified in terms of bytes.
-- LENGTH and OFFSET parameters for routines operating on CLOBs
-- are to be specified in terms of characters.
-- A function/procedure will raise an INVALID_ARGVAL exception if the
-- the following restrictions are not followed in specifying values
-- for parameters (unless otherwise specified):
-- 1. Only positive, absolute OFFSETs from the beginning of LOB data
-- are allowed. Negative offsets from the tail of the LOB are not
-- allowed.
-- 2. Only positive, non-zero values are allowed for the parameters
-- that represent size and positional quantities such as AMOUNT,
-- OFFSET, NEWLEN, NTH etc.
-- 3. The value of OFFSET, AMOUNT, NEWLEN, NTH must not exceed the
-- value lobmaxsize (which is (4GB-1) in Oracle 8.0) in any DBMS_LOB
-- procedure or function.
-- 4. For CLOBs consisting of fixed-width multi-byte characters, the
-- maximum value for these parameters must not exceed
-- (lobmaxsize/character_width_in_bytes) characters
-- For example, if the CLOB consists of 2-byte characters such as
-- JA16SJISFIXED, then the maximum amount value should not exceed
-- 4294967295/2 = 2147483647 characters
-- PL/SQL language specifications stipulate an upper limit of 32767
-- bytes (not characters) for RAW and VARCHAR2 parameters used in
-- DBMS_LOB routines.
-- If the value of AMOUNT+OFFSET exceeds 4GB (i.e. lobmaxsize+1) for
-- BLOBs and BFILEs, and (lobmaxsize/character_width_in_bytes)+1 for
-- CLOBs in calls to update routines - i.e. APPEND, COPY, TRIM, and
-- WRITE routines, access exceptions will be raised. Under these input
-- conditions, read routines such as READ, COMPARE, INSTR, SUBSTR, will
-- read till End of Lob/File is reached.
-- For example, for a READ operation on a BLOB or BFILE, if the user
-- specifies offset value of 3GB, and an amount value of 2 GB, READ
-- will read only ((4GB-1) - 3GB) bytes.
-- Functions with NULL or invalid input values for parameters will
-- return a NULL. Procedures with NULL values for destination LOB
-- parameters will raise exceptions.
-- Operations involving patterns as parameters, such as COMPARE, INSTR,
-- and SUBSTR do not support regular expressions or special matching
-- characters (such as % in the LIKE operator in SQL) in the PATTERN
-- parameter or substrings.
-- The End Of LOB condition is indicated by the READ procedure using
-- a NO_DATA_FOUND exception. This exception is raised only upon an
-- attempt by the user to read beyond the end of the LOB/FILE. The
-- READ buffer for the last read will contain 0 bytes.
-- For consistent LOB updates, the user is responsible for locking
-- the row containing the destination LOB before making a call to
-- any of the procedures (mutators) that modify LOB data.
-- For BFILEs, the routines COMPARE, INSTR, READ, SUBSTR, will raise
-- exceptions if the file is not already opened using FILEOPEN.
null