ORA-22275 error when running a USER_DATASTORE index on CLOB column

Question

Running Oracle 9.2.0.8
Getting the following errors thrown for every row in the table when creating the index:
DRG-12604: execution of user datastore procedure has failed
DRG-50857: oracle error in drsinopen
ORA-06502: PL/SQL: numeric or value error: invalid LOB locator specified: ORA-22275
ORA-06512: at "SYS.DBMS_LOB", line 347
ORA-06512: at "CRT_DEV.MULTI_INDEX_EN_PRC", line 27
ORA-06512: at "CTXSYS.CTXSYS_MULTI_INDEX_EN_PRC", line 7
ORA-06512:
Index scripts:
ctx_ddl.create_preference( 'crt_user_datastore_en', 'user_datastore' );
ctx_ddl.set_attribute( 'crt_user_datastore_en', 'procedure', 'ctxsys_multi_index_en_prc' );
ctx_ddl.set_attribute('crt_user_datastore_en', 'output_type', 'CLOB');
CTX_DDL.create_preference('CRT_PREF_EN','BASIC_WORDLIST');
ctx_ddl.set_attribute('CRT_PREF_EN','FUZZY_MATCH','ENGLISH');
ctx_ddl.set_attribute('CRT_PREF_EN','STEMMER','ENGLISH');
ctx_ddl.set_attribute('CRT_PREF_EN','SUBSTRING_INDEX','TRUE');
CTX_DDL.create_section_group('CRT_HTML_SECTION','HTML_SECTION_GROUP');
CTX_DDL.add_zone_section('CRT_HTML_SECTION', 'title', 'TITLE');
ctx_ddl.create_preference('CRT_LEXER_EN', 'BASIC_LEXER');
ctx_ddl.set_attribute('CRT_LEXER_EN', 'skipjoins', '-');
ctx_ddl.set_attribute ( 'CRT_LEXER_EN', 'index_text', 'YES');
ctx_ddl.set_attribute ( 'CRT_LEXER_EN', 'base_letter', 'YES');
ctx_ddl.set_attribute ( 'CRT_LEXER_EN', 'index_stems', 'ENGLISH');
ctx_ddl.set_attribute ( 'CRT_LEXER_EN', 'index_themes', 'YES');
ctx_ddl.set_attribute ( 'CRT_LEXER_EN', 'theme_language', 'ENGLISH');
CREATE INDEX MULTI_CONTENT_EN_IDX ON CONTENTS
(top_content_html_en)
INDEXTYPE IS CTXSYS.CONTEXT
parameters ('filter ctxsys.null_filter DATASTORE crt_user_datastore_en LEXER CRT_LEXER_EN wordlist CRT_PREF_EN section group CRT_HTML_SECTION');I have issued the following grants:
grant execute on CTXSYS.ctxsys_multi_index_fr_prc to CRT;
grant execute on CTXSYS.ctxsys_multi_index_en_prc to CRT;
grant execute on CRT_DEV.multi_index_fr_prc to CTXSYS;
grant execute on CRT_DEV.multi_index_en_prc to CTXSYS;CRT is the index owner schema
CRT_DEV is the schema owning the user_datastore procedure. (Could this be the problem?) Should the procedure reside in the same schema as index owner?
Here are my procedures:
CTXSYS stub:
CREATE OR REPLACE PROCEDURE ctxsys_multi_index_en_prc (
   rid    IN       ROWID,
   tlob   IN OUT   CLOB
IS
BEGIN
   crt_dev.multi_index_en_prc (rid, tlob);
END;Actual procedure:
CREATE OR REPLACE PROCEDURE multi_index_en_prc (rid IN ROWID, tlob IN OUT CLOB)
IS
BEGIN
   FOR c1 IN (SELECT    '<TITLE>'
                     || cc.content_category_name_en
                     || '</TITLE>' content_title,
                     c.content_html_content_en, c.top_html_content_en
                FROM content_categories cc, CONTENTS c
               WHERE cc.content_category_id = c.content_category_id
                 AND c.ROWID = rid)
   LOOP
      DBMS_LOB.writeappend (tlob, LENGTH (c1.content_title),
                            c1.content_title);
      DBMS_LOB.append (dest_lob => tlob, src_lob => c1.top_html_content_en);
      DBMS_LOB.append (dest_lob      => tlob,
                       src_lob       => c1.content_html_content_en
   END LOOP;
END multi_index_en_prc;I can run the following test script, and get no errors:
   declare
rid rowid;
tlob clob;
   begin
   dbms_lob.CREATETEMPORARY(tlob,false);
   CRT_DEV.multi_index_en_prc('AAAC0UAAMAAAAMAAA2',tlob);
   dbms_output.put_line(dbms_lob.GETLENGTH(tlob));
   dbms_output.put_line(dbms_lob.substr(tlob,25));
   dbms_lob.FREETEMPORARY(tlob);
   end;Output:
25
<TITLE>References</TITLE>
I'm at a total loss on the cause of the error.
Any help/tips is appreciated!
Thanks
Edited by: pl_sequel on Feb 9, 2010 11:25 AM

Answer 1

Thanks Roger.
I did add those in... DBA insists that didn't matter, since explicit "select" privs were granted to CRT_DEV to select CRT tables. He did say that a length check was required on the CLOBS before appedning them to the destination lob (tlob) to prevent NULL lob locators being appended and raising the exception.
In any case, it works now... however, unsure if it's due to the schema prefix on the tables, or the lob length checks...