Fetch from cursor variable

Hello,
I have a procedure, which specification is something like that:
procedure proc1 (pcursor OUT SYS_REFCURSOR, parg1 IN NUMBER, parg2 IN NUMBER, ...);Inside the body of proc1 I have
OPEN pcursor FOR
SELECT column1,
 column2,
 CURSOR (SELECT column1, column2
 FROM table2
 WHERE <some clauses come here>) icursor1
 FROM table1
 WHERE <some clauses come here>;In a PL/SQL block I would like to execute proc1 and then to fetch from pcursor. This is what I am doing so far:
DECLARE
ldata SYS_REFCURSOR;
larg1 NUMBER := 123;
larg2 NUMBER := 456;
outcolumn1 dbms_sql.Number_Table;
outcolumn2 dbms_sql.Number_Table;
BEGIN
some_package_name.proc1 (ldata, larg1, larg2, ...);
FETCH ldata BULK COLLECT INTO
 outcolumn1, outcolumn2,..., *and here is my problem*;
END;
/How can I rewrite this in order to get the content of icursor1 ?
Thanks a lot!

Verdi wrote:
How can I rewrite this in order to get the content of icursor1 ?
Firstly ref cursors contain no data they are not result sets but pointers to compiled SQL statements.
Re: OPEN cursor for large query
PL/SQL 101 : Understanding Ref Cursors
Ref cursors are not supposed to be used within PL/SQL or SQL for that matter, though people keep on insisting on doing this for some reason.
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10472/static.htm#CIHCJBJJ
Purpose of Cursor Variables
You use cursor variables to pass query result sets between PL/SQL stored subprograms and their clients. This is possible because PL/SQL and its clients share a pointer to the work area where the result set is stored.A ref cursor is supposed to be passed back to a procedural client language, such as Java or .Net.
If you want to re-use a SQL statement in multiple other PL/SQL or SQL statements you would use a view.

Similar Messages

How to fetch from cursor into plsql collection

Dear Friends,
I am trying to understand PLSQL collections. I am trying with the following example.
CREATE OR REPLACE TYPE emp_obj AS OBJECT
( empname VARCHAR2(100), empjob VARCHAR2(50), empsal NUMBER);
CREATE OR REPLACE TYPE emp_tbl IS TABLE OF emp_obj;
CREATE OR REPLACE PACKAGE eg_collection AS
-- Delcare ref cursor
TYPE rc IS REF CURSOR;
-- Procedure
PROCEDURE eg_collection_proc (out_result OUT rc);
END;
CREATE OR REPLACE PACKAGE BODY eg_collection AS
PROCEDURE eg_collection_proc( out_result OUT rc) AS
emp_tdt emp_tbl := emp_tbl(emp_obj('oracle','DBA',100));
CURSOR c2 IS SELECT ename,job,sal FROM emp WHERE sal > 2000;
-- Declare a record type to hold the records from cursor and then pass to the collection
emp_rec emp_obj;
BEGIN
 OPEN c2;
 LOOP FETCH c1 INTO emp_rec;
 EXIT WHEN c1%NOTFOUND;
 emp_tdt.extend;
emp_tdt(emp_tdt.count) := emp_rec;
 END LOOP;
 CLOSE c2;
OPEN out_result FOR SELECT * FROM TABLE(CAST(emp_tdt AS emp_tbl));
END eg_collection_proc;
END eg_collection;
Executing the proc
variable r refcursor;
exec eg_collection.eg_collection_proc(:r);
print r;
But I am getting compilation error type mismatch found at emp_rec between fetch cursor into variable

I am trying to understand PLSQL collections. I dont why the code is not working
SQL> CREATE OR REPLACE TYPE emp_obj AS OBJECT
2 (
3 empname VARCHAR2(100),
4 empjob VARCHAR2(50),
5 empsal NUMBER
6 )
7 /
Type created.
SQL> CREATE OR REPLACE TYPE emp_tbl IS TABLE OF emp_obj
2 /
Type created.
SQL> DECLARE
2 emp_tdt emp_tbl := emp_tbl ();
3 BEGIN
4
5 emp_tdt.extend;
6 SELECT emp_obj(ename, job, sal) BULK COLLECT INTO emp_tdt
7 FROM emp WHERE sal < 4000;
8
9 DBMS_OUTPUT.PUT_LINE ('The total count is ' || emp_tdt.count);
10
11 emp_tdt.extend;
12 SELECT ename, job, sal INTO emp_tdt(1).empname, emp_tdt(1).empjob, emp_tdt(1).empsal
13 FROM emp WHERE empno = 7900;
14
15 DBMS_OUTPUT.PUT_LINE ('The total count is ' || emp_tdt.count);
16
17 END;
18 /
The total count is 13
The total count is 14
PL/SQL procedure successfully completed.
SQL> DECLARE
2 emp_tdt emp_tbl := emp_tbl ();
3 BEGIN
4
5 emp_tdt.extend;
6 SELECT ename, job, sal INTO emp_tdt(1).empname, emp_tdt(1).empjob, emp_tdt(1).empsal
7 FROM emp WHERE empno = 7900;
8
9 DBMS_OUTPUT.PUT_LINE ('The total count is ' || emp_tdt.count);
10
11 emp_tdt.extend;
12 SELECT emp_obj(ename, job, sal) BULK COLLECT INTO emp_tdt
13 FROM emp WHERE sal < 4000;
14
15 DBMS_OUTPUT.PUT_LINE ('The total count is ' || emp_tdt.count);
16 END;
17 /
DECLARE
ERROR at line 1:
ORA-06530: Reference to uninitialized composite
ORA-06512: at line 6

Fetch from cursor when no records returned

Hi,
I've got the following question / problem?
When I do a fetch from a cursor in my for loop and the cursor returns no record my variable 'r_item' keeps the value of the previous fetched record. Shouldn't it contain null if no record is found and I do a fetch after I closed and opend the cursor? Is there a way the clear the variable before each fetch?
Below you find an example code
CURSOR c_item (itm_id NUMBER) IS
SELECT DISTINCT col1 from table1
WHERE id = itm_id;
r_item c_item%ROWTYPE;
FOR r_get_items IN c_get_items LOOP
IF r_get_items.ENABLE = 'N' THEN
      open c_item(r_get_items.ITMID);
      fetch c_item into r_item;
      close c_item;
      IF r_item.ACCES = 'E' then
           action1
      ELSE
           action2
      END IF;
END IF;
END LOOP; Thanx

DECLARE
    CURSOR c_dept IS
      SELECT d.deptno
      ,      d.dname
      ,      d.loc
      ,      CURSOR (SELECT empno
                     ,      ename
                     ,      job
                     ,      hiredate
                     FROM   emp e
                     WHERE e.deptno = d.deptno)
      FROM   dept d;
    TYPE refcursor IS REF CURSOR;
    emps refcursor;
    deptno dept.deptno%TYPE;
    dname dept.dname%TYPE;
    empno emp.empno%TYPE;
    ename emp.ename%TYPE;
    job emp.job%TYPE;
    hiredate emp.hiredate%TYPE;
    loc dept.loc%TYPE;
BEGIN
   OPEN c_dept;
   LOOP
     FETCH c_dept INTO deptno, dname, loc, emps;
     EXIT WHEN c_dept%NOTFOUND;
     DBMS_OUTPUT.put_line ('Department : ' || dname);
     LOOP
       FETCH emps INTO empno, ename, job, hiredate;
       EXIT WHEN emps%NOTFOUND;
       DBMS_OUTPUT.put_line ('-- Employee : ' || ename);
     END LOOP;
END LOOP;
CLOSE c_dept;
END;
/like this...

Help!!! slow fetch from cursor

I have a problem fetching records from a ref cursor returned by a procedure.
Basically I play both a PL/SQL developer and DBA roles for a development and production Oracle 9.2.0.6 databases hosted on separate Sun Solaris 5.8 servers. The problem PL/SQL signature is shown below, and it basiccally dynamically constructs a large querry (I will call global querry) which is a UNION ALL of 16 smaller querries and opens the cursor parameter for this dynamically constructed querry. The entire querry is assigned to a VARCHAR2(20000) variable, and is normally a little over 15,000 bytes in size. The returned cursor is used to publish the querry result records in Crystal reports. The problem is that the entire process of executing and fetching the result records from the procedure is taking as much as 25 minutes to complete. On investigation of the problem by executing the procedure with a PL/sql block in sqlplus, and adding timing constructs in the execution of the procedure and fetches from the returned cursor, I discovered to my shock that the procedure executes consistently in 1 second (second is the granularity of the timer), but each record fetch is done in a minimum of 16 seconds. All efforts to tune the database memory structures to improve the fetches have yielded very small improvements bringing down the fetch times to about 11 seconds. This is still unacceptable. Is there anybody out there who can suggest a solution to this problem?
Procedure signature:
sp_production_report ( p_result_set IN OUT meap_report.t_reportRefCur,
p_date_from IN VARCHAR2,
p_date_to IN VARCHAR2,
p_agency_code IN INTEGER DEFAULT NULL,
p_county_code IN INTEGER DEFAULT NULL,
p_selection IN INTEGER DEFAULT 0);
Test block in sqlplus:
declare
-- Local variables here
i integer;
v_start INTEGER;
v_end INTEGER;
v_end_fetch INTEGER;
v_cnt INTEGER := 0;
v_end_loop INTEGER;
v_elapsed INTEGER;
v_cur meap_report.t_reportRefCur;
v_desc VARCHAR2(300);
v_hh VARCHAR2(300);
v_meap INTEGER;
v_bp INTEGER;
v_ara INTEGER;
v_tot INTEGER;
BEGIN
-- Test statements here
DBMS_OUTPUT.ENABLE(100000);
SELECT TO_NUMBER ( TO_CHAR(SYSDATE, 'SSSSS')) INTO v_start FROM DUAL;
sp_production_report ( p_result_set => v_cur,
p_date_from => '07/01/2008',
p_date_to => '07/31/2008',
p_selection => 0);
SELECT TO_NUMBER ( TO_CHAR(SYSDATE, 'SSSSS') ) INTO v_end FROM DUAL;
FETCH v_cur INTO v_desc, v_hh, v_meap, v_bp, v_ara, v_tot;
SELECT TO_NUMBER ( TO_CHAR(SYSDATE, 'SSSSS') ) INTO v_end_fetch FROM DUAL;
WHILE v_cur%FOUND LOOP
v_cnt := v_cnt + 1;
FETCH v_cur INTO v_desc, v_hh, v_meap, v_bp, v_ara, v_tot;
END LOOP;
SELECT TO_NUMBER ( TO_CHAR(SYSDATE, 'SSSSS') ) INTO v_end_loop FROM DUAL;
v_elapsed := v_end_loop - v_end;
DBMS_OUTPUT.PUT_LINE ( 'Procedure (p_selection 0) executed in ' || TO_CHAR ( (v_end - v_start) ) || ' seconds.' );
DBMS_OUTPUT.PUT_LINE ( 'Fetched 1st record in ' || TO_CHAR ( (v_end_fetch - v_end) ) || ' seconds.' );
DBMS_OUTPUT.PUT_LINE ( 'Procedure (p_selection 0) :' || TO_CHAR (v_cnt) ||
' records fetched in ' || TO_CHAR ( v_elapsed ) || ' seconds.' );
CLOSE v_cur;
END;

And why not use timestamps instead of dates? They get subsecond resolution:
declare
        t1 timestamp;
        t2 timestamp;
        d1 INTERVAL DAY(3) TO SECOND(3);
begin
        t1 := systimestamp;
        dbms_lock.sleep(1.45);
        t2 := systimestamp;
        d1 := t2 - t1;
        dbms_output.put_line('Start:    '||t1);
        dbms_output.put_line('End:      '||t2);
        dbms_output.put_line('Duration: '||d1);
end;
/As for how to speed up your fetch, that depends on how the SQL the cursor is based on is constructed. Without that you need to refer to Rob's post.

Fetch From Cursor

In my Procedure I want to explicitly open the cursor and fetch from the cursor and again close the cursor
I don’t want to use like this for some testingsomething:
Create procedure kk
Cur out sys_refcursor
As
Open cur for
Select * from table;
End
I need to use like this
Create procedure kk
Cursor c is select * from table; need to return this cursor.
As
How to return that cursor
Thanks

maybe something like:
create or replace procedure get_emp_name as
cursor c1 is
    select * from emp;
vEname emp.ename%type;
begin
open c1;
fetch c1 into vEname;
if c1%notfound then
     exit;
end if;
close c1;
end;
/or
Create procedure get_emp_name as
Cursor c1 is
   select *
     from emp;
begin
for c1_rec in c1 loop
     dbms_output.put_line('Emp Name: '||c1_rec.ename);
end loop;
end;
/

Fetching from cursor

Hello all.
How can i enforce the sql+ start fetching first cursor field by
one field intervals?
My sql+ starts fetch from the second item by 2 records intervals,
so the 4th record is the next one to fetched after the second.
best regards
yosi sarid.

Hi,
could you please show us the where clause of the cursor?
I think you are missing something.
Another fault in your Code is the x_commit_count.
You increment it every time, but you never set it to zero again. So after 100 inserts, it commits after each loopstep.
Is this what you want???
DECLARE
CURSOR c_cursor IS SELECT * FROM TABLE_A@REMOTE, TABLE_B@REMOTE WHERE...
x_commit_count NUMBER := 0;
BEGIN
FOR r_record IN c_cursor LOOP
INSERT INTO LOCAL_TABLE;
x_commit_count := x_commit_count + 1;
IF x_commit_count >= 100 THEN
COMMIT;
ELSE
NULL;
END IF;
END LOOP;
END;
HTH
Detlev

Dynamic Column Name while Fetching from Cursor?

Scenario:
I have a table having 5 Column C01,C02,C03,C04,C05....... now i have
a record type variable att_rec. One first fetch the first record
fetch into att_rec and i can access column like
att_rec.C01,att_rec.C02 and so on simply i wan access these columns
through following Loop but unable to do so. It Understand the
att_Rec.C01 as String .. Any Clue ???
IF NOT attdays_cnt%ISOPEN
THEN
OPEN attdays_cnt;
END IF;
/* Keep fetching until no more records are FOUND */
FETCH attdays_cnt INTO att_rec;
message('Cursor Opened');
WHILE attdays_cnt%FOUND
LOOP
a31_cnt:=1; -- reinitializtion of variables for other employees
p_days:=0;
w_days:=0;
WHILE a31_cnt<32 LOOP
IF concat('ATT_REC.C',to_char(a31_cnt,'00'))='L'='P' THEN
p_days:=p_days+1;
ELSE ATT_REC.C01='W' THEN
w_days:=w_days+1;
END IF;
END LOOP;
Message was edited by:
Fiz Dosani

Perhaps this is marginally simpler with nested table, YMMV ;-)
(based on Elic's example)
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> CRE ATE TABLE t (i, j, k)
2 AS
3 SELECT LEVEL, POWER (LEVEL, 2), POWER (LEVEL, 3)
4 FROM DUAL
5 CONNECT BY LEVEL <= 5;
Table created.
SQL> CREATE OR REPLACE type ntt_number AS TABLE OF NUMBER;
2 /
Type created.
SQL> SET SERVEROUTPUT ON;
SQL> DECLARE
2 TYPE t_tbl IS TABLE OF ntt_number;
3
4 var t_tbl;
5 BEGIN
6 SELECT ntt_number (i, j, k)
7 BULK COLLECT INTO var
8 FROM t;
9
10 FOR i IN 1 .. var.COUNT LOOP
11 FOR j IN 1 .. var (i).COUNT LOOP
12 DBMS_OUTPUT.PUT_LINE (
13 'var (' || i || ') (' || j || ') => ' || var (i) (j));
14 END LOOP;
15 END LOOP;
16 END;
17 /
var (1) (1) => 1
var (1) (2) => 1
var (1) (3) => 1
var (2) (1) => 2
var (2) (2) => 4
var (2) (3) => 8
var (3) (1) => 3
var (3) (2) => 9
var (3) (3) => 27
var (4) (1) => 4
var (4) (2) => 16
var (4) (3) => 64
var (5) (1) => 5
var (5) (2) => 25
var (5) (3) => 125
PL/SQL procedure successfully completed.
SQL>

NLS Error on Second Fetch from Cursor

Oracle 8i using PRO*C
We have a UNIX (HP) environment (operational account) in which the NLS_LANG was not set for the shell. One of our applications opened a cursor for update and performed its first fetch. After processing it went back to fetch an additional buffer. At this point, the application failed with the following error: "SQLCODE: ORA-01890: NLS error detected". When we set the NLS_LANG enviroment variable this error disappeared.
I need to know what the NLS_LANG enviroment variable is doing and why it is causing the second fetch to fail when it is not set so I can argue with the powers that be to have this paremeter always set for this accounts shell (i.e. globally). No-one really knows what this does here or why it would cause the cursor to fail, and so they are telling us to just set the variable in our own applications shell.
I know the real answer to this is to set it up for the operational (global) shell but...
Thanks in advance,
Bill Rosmus

it is difficult. The main problem is that you can't be sure that the function is called only once for each row.
Why don't you simply run the cursor and the function separatly in pl/sql.
CURSOR myCur IS SELECT myTable1.* FROM myTable1 ;
SUBTYPE myRecType IS myCur%ROWTYPE ;
funcResult varchar2(100); /* use the correct return datatype from your function here */
FOR myRec in myCur LOOP
 BEGIN
 funcResult := myPackage.myFunc(myRec.column1);
 EXCEPTION
 WHEN myPackage.myFunc_Exception THEN
 <... do anything when fetched but function myFunc raised this exception ...>
 END ;
 <...do anything with row currently fetched>
 END LOOP;You even have more control where to handle the exception. Also there is one pl/sql context switch less. Since the function itself is pl/sql it could even be faster to run it in pl/sql then to call it from sql (inside a select).

SAVE EXCEPTIONS when fetching from cursors by BULK COLLECT possible?

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
Hello,
I'm using an Cursor's FETCH by BULK COLLECT INTO mydata...
Is it possible to SAVE EXCEPTIONS like with FORALL? Or is there any other possibility to handle exceptions during bulk-fetches?
Regards,
Martin

The cursor's SELECT-statement uses TO_DATE(juldat,'J')-function (for converting an julian date value to DATE), but some rows contain an invalid juldat-value (leading to ORA-01854).
I want to handle this "rows' exceptions" like in FORALL.
But it could also be any other (non-Oracle/self-made) function within "any" BULK instruction raising (un)wanted exceptions... how can I handle these ones?
Martin

Different error messages from different env while fetching ref cursor

Hi 
I have a package where i need to call one of the procedure.I this 
procedure i am returning a refcursor as out parameter.Before returning refcursor i 
am doing i am checking a condition if it is satisfied then I am saying return or else 
it will proceed and refcursor is assigned for out parameter.So i am speakig about 
the condition where i am exiting from procedure before refcursor parameter is 
assigned .And later i am tring to fetch from that cursor .So i am getting different 
kinds of errors which i described as follows 
 
 
So If execute that procedure from sqlplus uing 
 
 
var m ref cursor 
DECLARE 
Y NUMBER; 
Z NUMBER; 
A NUMBER; 
BEGIN 
A:=campa.dtl_inq(2,100070875,'R',Y,Z,:M); 
END; 
 
Then if say 
Print m 
It gives 
 
ORA-24338: statement handle not executed 
 
And if i execute this using vb application 
 
I am getting following error 
 
ORA-01023: Cursor context not found (Invalid cursor number) 
 
So i am serching the reason for different errors 
 
Regards 
vamsi krishna 

The error depends on exactly what OCI calls the client software makes in accessing this invalid (null) ref cursor variable.
It would seem that SQL*Plus makes different calls than what your code and Visual Basic does - thus the different error messages returned by the two applications.

Difference of fetching data, into a cursor variable and into a record?

whats the difference of fetching data via cursor, into a cursor variable and into a record.
i feel infact fetching data into cursor variable is more better, and plus lesser lines to code??

Can you explain what you mean, preferably with an example? Generally, you fetch data from a cursor, not into one. I'm assuming by "fetching into a record" you mean inserting into a table?
Justin

Optimal number of records to fetch from Forte Cursor

Hello everybody:
I 'd like to ask a very important question.
I opened Forte cursor with approx 1.2 million records, and now I am trying
to figure out the number of records per fetch to obtain
the acceptable performance.
To my surprise, fetching 100 records at once gave me approx 15 percent
performance gain only in comparsion
with fetching records each by each.
I haven't found significant difference in performance fetching 100, 500 or
10.000 records at once.In the same time, fetching 20.000
records at once make a performance approx 20% worse( this fact I cannot
explain).
Does anybody have any experience in how to improve performance fetching from
Forte cursor with big number of rows ?
Thank you in advance
Genady Yoffe
Software Engineer
Descartes Systems Group Inc
Waterloo On
Canada

You can do it by writing code in start routine of your transformations.
1.If you have any specific criteria for filtering go with that and delete unwanted records.
2. If you want to load specific number of records based on count, then in start routine of the transformations loop through source package records by keeping a counter till you reach your desired count and copy those records into an internal table.
Delete records in the source package then assign the records stored in internal table to source package.

Cursor Variables in Pro*C/C++

I have very strange behaivour of the client application that uses cursor variable.
I have Oracle 8i enterprise 8.1.6 release for Sun/Solaris.
The follow SQL is installed on server:
create or replace package dummy is
type vemap_cur is ref cursor;
end;
create or replace procedure GET_CUR
( N IN number, cur IN OUT dummy.VEMAP_CUR ) as
begin
open cur for
select LS.ID, LS.SCALE
from LAYERS LS
where LS.ID = (select C.ID from CTM C where C.ORDERINDEX = N);
end;
This procedure (GET_CUR) i call from embedded SQL in follow manner:
EXEC SQL BEGIN DECLARE SECTION;
struct
int n1;
int n2;
} resrec;
sql_cursor c1;
int num;
EXEC SQL END DECLARE SECTION;
EXEC SQL ALLOCATE :c1;
EXEC SQL AT DB_VE EXECUTE
BEGIN
GET_VEC( :num, :c1 );
END;
END-EXEC;
Till now it is Ok. But when i run the follow line
EXEC SQL FETCH :c1 INTO :resrec;
i accept ORA-01012: not logged on
error !!!!
I checked the connection via using cursor in paralell and got the correct answer.
Therefore i think this error is not related to the actual problem and i have no idea what this problem is. I tried to open cursor via anonymous PL/SQL block inside my C program with same result.
Need help ASAP.
Leonid
null

Hi Leonid, Andrea
When you use "CONNECT AT :db_handle" instead of default connection "CONNECT", you have to give the connect handle to the command you want to execute.
ie:
EXEC SQL AT :db_handle PREPARE SQL_stat FROM "select ...";
EXEC SQL AT :db_handle DECLARE cur_stat CURSOR for SQL_stat;
EXEC SQL AT :db_handle OPEN cur_stat ;
EXEC SQL AT :db_handle FETCH cur_stat INTO :resrec;
Leonid, the error you had is probably because you connected at "DB_VE", and tried to select from default connect (that you're not connected to ==> ORA-01012)
Try EXEC SQL AT :DB_VE FETCH :c1 INTO :resrec;
or, if you connect to only 1 database, use "EXEC SQL CONNECT;" instead of (EXEC SQL CONNECT :pConnectString AT "DB_VE";) so that you use default connect name and you don't have to add "AT :DB_VE" to your SQL commands.
I know this reply comes long after your request, but I hope it may still help anybody.

How to (in Pro*C) pass a cursor variable as a pointer between functions

I am opening a cursor in a called function that accepts as one argument a pointer to a cursor variable, and a second argument for the sql string defining the cursor select. That works fine, and in that same function can successfully fetch and access the records from the cursor. However, my objective is to fetch the records in another function that calls the first function. I want to pass back to the calling function the pointer to the cursor variable from the first function. In the second (calling) function, is where I want to fetch the records. What I am getting is SQLCODE = -1002 (fetch out of sequence).
Here is the relevent code in the first called function that calls a PL/SQL package procedure to open the cursor, followed by the code in the second calling procedure where I am attempting to fetch the records:
/******Called function code starts here ******/
EXEC SQL INCLUDE SQLCA;
long db_makeCursor(cursorID, SQLstr)
EXEC SQL BEGIN DECLARE SECTION;
sql_cursor cursorID; / a pointer to a cursor variable */
char *SQLstr;
EXEC SQL END DECLARE SECTION;
long SQLCODE;
EXEC SQL BEGIN DECLARE SECTION;
sql_cursor dbCursor; /* a cursor variable */
EXEC SQL END DECLARE SECTION;
EXEC SQL WHENEVER SQLERROR DO sql_error();
dbCursor = *cursorID;
EXEC SQL EXECUTE
BEGIN
db_util_ref_cursor_pkg.open_dbNameCursor( :dbCursor, :SQLstr );
END;
END-EXEC;
return;
/******Calling function code starts here ******/
EXEC SQL INCLUDE SQLCA;
EXEC SQL BEGIN DECLARE SECTION;
static PROCLOG PROC_Rec;
EXEC SQL END DECLARE SECTION;
long retrieveProcesses( _proclog, sqlForProcLog )
EXEC SQL BEGIN DECLARE SECTION;
PROCLOG _proclog;
char *sqlForProcLog
EXEC SQL END DECLARE SECTION;
long rc;
long SQLCODE;
EXEC SQL BEGIN DECLARE SECTION;
sql_cursor dbCursor; /* a cursor variable */
sql_cursor cursorID; / a pointer to a cursor variable */
PROCLOG proclog;
short end_ts_ind;
short proc_name_ind;
short comments_ind;
EXEC SQL END DECLARE SECTION;
cursorID = &dbCursorName; /* assign a value to the pointer */
EXEC SQL ALLOCATE :dbCursor;
rc = dbUtilities_makeCursor( cursorID, sqlForProcLog);
if (rc == TRUE)
while (SQLCODE == 0)
EXEC SQL FETCH :dbCursorName INTO
:proclog.PROC_ID,
:proclog.START_TS,
:proclog.END_TS:end_ts_ind,
:proclog.PROC_NAME:proc_name_ind,
:proclog.COMMENTS:comments_ind,
if (SQLCODE == 0)
printf("PROC_ID: %d; COMMENTS: %s\n",proclog.PROC_ID, proclog.COMMENTS);
} /* end retrieveProcesses */

You need to include a loop...
for i=0;i<sqlca.sqlerrd[2];i++)
printf("name %s\n", struct.name)
This allows you to step through your cursor records!!!

Cursor variable and for update

hi
can anyone explain me why can't we use "for update " with a Cursor Variable.
Thanks in advance.

user10314274 wrote:
exmple : I read it in one book(Oracle press)And how difficult is it to test this?
declare
    v_cur sys_refcursor;
    v_ename varchar2(20);
begin
    open v_cur for select ename from emp for update;
    loop
      fetch v_cur into v_ename;
      exit when v_cur%notfound;
      dbms_output.put_line(v_ename);
    end loop;
    close v_cur;
    dbms_output.put_line('----------------------');
    open v_cur for 'select ename from emp for update';
    loop
      fetch v_cur into v_ename;
      exit when v_cur%notfound;
      dbms_output.put_line(v_ename);
    end loop;
    close v_cur;
end;
SMITH
ALLEN
WARD
JONES
MARTIN
BLAKE
CLARK
SCOTT
KING
TURNER
ADAMS
JAMES
FORD
MILLER
SMITH
ALLEN
WARD
JONES
MARTIN
BLAKE
CLARK
SCOTT
KING
TURNER
ADAMS
JAMES
FORD
MILLER
PL/SQL procedure successfully completed.
SQL> SY.

Fetch from cursor variable

Similar Messages

Maybe you are looking for