Calling a procedure with a CLOB input parameter

Question

All,
I trying to execute a simple stored procedure that can accept the text of another stored procedure as an input argument. The text of the stored procedure could exceed size allowable under plsql varachar2, so I typed this as a clob..
Problem is the system hangs when I call this stored procedure. I am able to use varchar2 for the input code.. and this works, but using clob just causes the client (sqlplus, sqlDeveloper) to hang..
Database version 10.2.0.4
Any assistance would be greatly appreciated.. I suspect an Oracle bug but I could use some guidance before I hit up support..
thanks Badri..
DECLARE
PROC_NAME VARCHAR2(200);
INPUT_CODE CLOB;
RESULT VARCHAR2(200);
BEGIN
PROC_NAME := 'TESTHANG';
INPUT_CODE := '(input IN VARCHAR2)' || CHR(9) || ' AS BEGIN NULL;' || CHR(9) || 'END;'
FWK_CREATE_PROCEDURE(
PROC_NAME => PROC_NAME,
INPUT_CODE => INPUT_CODE,
RESULT => RESULT
DBMS_OUTPUT.PUT_LINE('RESULT = ' || RESULT);
END;
create or replace PROCEDURE FWK_CREATE_PROCEDURE
(proc_name IN VARCHAR2,
input_code IN CLOB,
result OUT NOCOPY VARCHAR2)

Answer 1

Hi, Badri,
badrinathg wrote:
All,
I trying to execute a simple stored procedure that can accept the text of another stored procedure as an input argument. The text of the stored procedure could exceed size allowable under plsql varachar2, so I typed this as a clob..
Problem is the system hangs when I call this stored procedure. I am able to use varchar2 for the input code.. and this works, but using clob just causes the client (sqlplus, sqlDeveloper) to hang..Are you sure the code you posted is what you're running? It's missing a semicolon, which would cause a compile error, regardless of whether input_code was a CLOB or a VARCHAR2.
Database version 10.2.0.4
Any assistance would be greatly appreciated.. I suspect an Oracle bug but I could use some guidance before I hit up support..
thanks Badri..
DECLARE
PROC_NAME VARCHAR2(200);
INPUT_CODE CLOB;
RESULT VARCHAR2(200);
BEGIN
PROC_NAME := 'TESTHANG';
INPUT_CODE := '(input IN VARCHAR2)' || CHR(9) || ' AS BEGIN NULL;' || CHR(9) || 'END;'
FWK_CREATE_PROCEDURE(
PROC_NAME => PROC_NAME,
INPUT_CODE => INPUT_CODE,
RESULT => RESULT
DBMS_OUTPUT.PUT_LINE('RESULT = ' || RESULT);
END;Please format any code that you post, and type these 6 characters:
\(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing on this site.
Compile the procedure first.  The procedure has to exist before the anonymous block will compile.
create or replace PROCEDURE FWK_CREATE_PROCEDURE
(proc_name IN VARCHAR2,
input_code IN CLOB,
result OUT NOCOPY VARCHAR2)It looks like the rest of the procedure got cut off.
The following works fine for me:create or replace PROCEDURE FWK_CREATE_PROCEDURE
( proc_name     IN     VARCHAR2,
input_code     IN     CLOB,
result     OUT NOCOPY VARCHAR2
IS
BEGIN
     result := 'Hello, world!';
END     fwk_create_procedure;
SHOW ERRORS
DECLARE
     PROC_NAME     VARCHAR2(200);
     INPUT_CODE     CLOB;
     RESULT          VARCHAR2(200);
BEGIN
     PROC_NAME := 'TESTHANG';
     INPUT_CODE := '(input IN VARCHAR2)' || CHR(9)
                         || ' AS BEGIN NULL;'
                         || CHR(9)
                         || 'END;';          -- Need ; at end
     FWK_CREATE_PROCEDURE (
               PROC_NAME     => PROC_NAME,
               INPUT_CODE     => INPUT_CODE,
               RESULT          => RESULT
     DBMS_OUTPUT.PUT_LINE ('RESULT = ' || RESULT);
END;
Edited by: Frank Kulash on Sep 23, 2010 4:20 PM
I see you posted some more code.
Whenever you write a loop, include a call to dbme_output.put line inside the loop, so see how it's progressing.
If it's an infinite loop, the calls to put_line will eventually cause the buffer to overflow, and the output may help you solve the problem.
I added a call to put_line at the end of the loop:...     LOOP
          next_delim := INSTR (input_code, delim, pos);
          source_code := source_code || SUBSTR(input_code, pos, next_delim - pos) || CHR(13) || CHR(10);
          pos := next_delim + 1;
          EXIT WHEN pos >= str_length;
          dbms_output.put_line (pos || ' = pos inside loop in FWK_CREATE_PROCEDURE');     -- NEW
     END LOOP;
and got this output:21 = pos inside loop in FWK_CREATE_PROCEDURE
37 = pos inside loop in FWK_CREATE_PROCEDURE
1 = pos inside loop in FWK_CREATE_PROCEDURE
21 = pos inside loop in FWK_CREATE_PROCEDURE
37 = pos inside loop in FWK_CREATE_PROCEDURE
1 = pos inside loop in FWK_CREATE_PROCEDURE
21 = pos inside loop in FWK_CREATE_PROCEDURE
37 = pos inside loop in FWK_CREATE_PROCEDURE
1 = pos inside loop in FWK_CREATE_PROCEDURE
Maybe the condition for ending the loop should be:...          EXIT WHEN pos >= str_length
          OR pos = 1;
Remember to comment out (or delete) the call to put_line before moving the code to Production.