Invalid hex number

Question

Greetings PL/SQL Greats!
Can someone please tell me why I am getting "ORA-0464-Invalid hext number" error?
What is weird is after I executed my stored proc with one file, I get the file copied successfully from db to folder.
A second try succeeded as well.
After that, any other attempts to copy from db to folder resulted to error above.
I am having difficulty wrapping my head around this error.
Any help is greatly appreciated.
<pre><code>create or replace PROCEDURE Getblob(pfname VARCHAR2, display_name IN VARCHAR2)
IS
vblob BLOB;
vstart NUMBER := 1;
bytelen NUMBER := 32000;
len NUMBER;
my_vr RAW(32000);
x NUMBER;
v_name VARCHAR2(100);
lv_str_len NUMBER;
l_output utl_file.file_type;
BEGIN
-- define output directory
--lv_str_len := Length(pfname);
--v_name := display_name||upper(substr(pfname,lv_str_len-3,lv_str_len));
v_name := display_name;
l_output := utl_file.Fopen('/m705/gfile', v_name, 'w', 32760);
-- get length of blob
SELECT dbms_lob.Getlength(GFILE_BLOB_VALUE)
INTO len
FROM GFILE
WHERE file_name = pfname;
-- dbms_output.put_line('Length: '||len);
-- save blob length
x := len;
-- select blob into variable
SELECT GFILE_BLOB_VALUE
INTO vblob
FROM GBFILE
WHERE file_name = pfname;
-- if small enough for a single write
IF len < 32760 THEN
-- dbms_output.put_line('Single write ');
utl_file.Put_raw(l_output, vblob);
utl_file.Fflush(l_output);
ELSE -- write in pieces
-- dbms_output.put_line('multi write '||vstart);
vstart := 1;
WHILE vstart < len LOOP
dbms_lob.READ(vblob, bytelen, vstart, my_vr);
utl_file.Put_raw(l_output, my_vr);
utl_file.Fflush(l_output);
-- set the start position for the next cut
vstart := vstart + bytelen;
-- set the end position if less than 32000 bytes
x := x - bytelen;
IF x < 32000 THEN
bytelen := x;
END IF;
END LOOP;
END IF;
dbms_output.Put_line('End');
utl_file.Fclose(l_output);
EXCEPTION
WHEN OTHERS THEN
dbms_output.Put_line('ERROR');
END getblob;</code></pre>
Edited by: sonny on Nov 11, 2011 8:59 AM

Answer 1

I don't know what to tell you.
Other than to ask you to please tell me what you saw in the code that convinced you otherwise.
The one thing I would like to add was that after I executed the code twice, as indicated above, the users asked me if it was possible to grab all the files instead of grabbing the one file at a time as the code shows, I created a different stored proc that has rowid in the WHERE clause.
I ran the code and it got pretty much every file from the db.
Problem was that for some reason, it was changing the files to .txt file.
I decided to go back to using the code I posted above and that's when I started getting the invalid hex number error.
Does this make more sense?
Somehow, it seems to me, the code with the ROWID is still somewhere is interferring with this stored proc.
This purely a guess.