Size of PL\SQL Cursor block

I want to know the internal working of the PL\SQL Cursor. Lets start with a scenario.
     1) I have 3 table with 20 million records each.
     2) I am making a join out of them on a certain condition which gives me 60 million records, now I am putting them in a cursor.
Questions :
     i) Can the Oracle PL\SQL Cursor is capable of holding that much records or there is any limit for it ?
     ii) If there is a limit for such block, then where can I find it and how can I set it ?
     3) If there is no such limit, then running such a query and holding all the data in the Cursor Block would degrade the performance. How Oracle handles such situations, It might be possible that Oracle only have the indexes of those records in the Cursor, but still it would be to time consuming to index 3 different table
Kindly Inform me about this issue ....
Thanks & regards
- Nabil Shams

1. Oracle PL/SQL cursor is just a handle to shared SQL area in Oracle SGA and as such does not consume an awful lot of memory (I would dare to say it consumes peanuts). What is more important it does not depend on number of rows you are going to fetch via cursor
2. Therefore the answer to question 2 is NO
3. Running the query could and would affect you in most unpleasnat ways if you tried to store results of the query in your process memory (PGA/UGA), or more specifically if you created PL/SQL indexed by table and tried to pack all 60000000 rows into it.
If you fetch rows one by one, process the row, throw it away - then no problem... but what do you need to do it for?

Similar Messages

HTML Form in a "PL/SQL (anonymour Block)"

Hello
I need a little ugent guidance
I have create a "form" within a "PL/SQL (anonymour Block)". The requirement is to show what a HTML form looks like as you build the code
The problem is I am "Up Setting" the APEX processing i.e. wwv_flow.accept ... I have added an example below .....
All help very welcome
Thanks
Pete
htp.prn('<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">');
htp.prn( '<style type="text/css">');
htp.prn('#form{font-family: "Trebuchet MS", Verdana, sans-serif; width:25em;}');
htp.prn('h2{margin: 0 0 0 0; padding: 0;}');
htp.prn('p{margin: 0 0 1em 0; padding: 0; font-size:90%}');
htp.prn('fieldset{background:#C361D2; border:none; margin-bottom:1em; width:24em; padding-top:1.5em}');
htp.prn('p.legend{background:#DED983;
color:black;
padding: .2em .3em;
width:750px;
font-size:18px;
border:6px outset #DED980;
position:relative;
margin: -2em 0 1em 1em;
width: 20em;}');
htp.prn('fieldset{margin-bottom:1em; width:66em; padding-top:1.5em;}');
htp.prn('#company {background:#F3B4F5; border:outset #F3B4F5; width="700";}');
htp.prn('#company label{position:absolute;
font-family:arial;
font-size:16px;
padding:.2em;}');
htp.prn('input{margin-left:9em;margin-bottom:.2em; line-height:1.4em;}');
htp.prn('#message1 {background:#a3B4F5; border:outset #a3B4F5; width="700";}');
htp.prn('#message2 {background:#c3B4F5; border:outset #c3B4F5; width="700";}');
htp.prn('button1 {font:48px "Trebuchet MS", "Verdana", sans-serif;
background:#F0888A;
border:outset #6EC6F1}');
htp.prn('#buttons1 input {background:#DED983;
font:1.2em "Trebuchet MS", Verdana, sans-serif}');
htp.prn('p#buttons1 {white-space:nowrap}');
htp.prn('</style>');
htp.prn('<table width="760"><tr bgcolor="#D5EAE9">');
htp.prn('<BR><BR>');
htp.prn ('<form method="" action="">');
htp.prn ('<fieldset id="company"><p class="legend" >Company</p>');
htp.prn ('<label>Comapany Name: </label> <input name="company" type="Text" size="30"/>');
htp.prn ('<br><br>');
htp.prn ('</fieldset>');
htp.prn ('<br><br><br>');
htp.prn ('<fieldset id="message1"><p class="legend">Message One</p>');
htp.prn ('</fieldset>');
htp.prn ('<br><br><br>');
htp.prn ('<fieldset id="message2"><p class="legend">Message Two</p>');
htp.prn ('</fieldset>');
htp.prn ('<br><br>');
htp.prn ('</form>');
htp.prn('</tr></table>');
End;
______________________________________________________________________________________________________

Pete:
Remove the name attributes from all input elements defined by the pl/sql process. For example
<input name="company" type="Text" size="30"/> should be replaced by <input type="Text" size="30"/> or <input name="f01" type="Text" size="30"/>
The APEX accept process recognises a predefined set of HTML form input names. Any input with a name not from this set will cause the accept process to fail. f01 through f50 are valid names for the accept procedure.
varad

Understanding SQL cursor attributes

I was trying to understand the use of SQL cursor attributes.So i chose sql%notfound attribute to be used with an exception in the below example.
create or replace procedure checkExcp
is
v_empName varchar2(30);
exp_no_row_found exception;
errorMessage varchar2(500);
begin
select ename into v_empName from emp where empno = '8000';
if sql%notfound then
     raise exp_no_row_found ;
end if;
exception
when exp_no_row_found
then
errorMessage := 'Error occured while executing updateInventoryTotalsInDB function: ';
end;When i debugged this proc i realized that the
if sql%notfound then
     raise exp_no_row_found ;bit of the code(and the custom exception exp_no_row_found) is useless. Because when no rows are returned by the query
select ename into v_empName from emp where empno = '8000';it straightaway goes to the exception block bypassing the 'if sql%notfound....' bit. So when is a SQL cursor attribute like sql%notfound useful?

But i want to add specific error messages to each
SELECT...INTO statements. So a single,common
NO_DATA_FOUND exception would mask these specific
errors.Then don't make it a single, common exception block. Have specific execution blocks with their own exception block for each different way you want to handle the exception e.g.
BEGIN
BEGIN
    SELECT mydata INTO myvar FROM mytable;
EXCEPTION
    WHEN NO_DATA_FOUND THEN
      myvar := 'No data for myvar';
END;
BEGIN
    SELECT myotherdata INTO myvar2 FROM mytable;
EXCEPTION
    WHEN NO_DATA_FOUND THEN
      myvar2 := 'No data for myvar2';
END;
END;Nested execution blocks are your friend when you want to handle exceptions for specific areas.

Building report from PL/SQL cursor

Hello,
is there any way to build APEX report using just PL/SQL cursor?
I don't have grant to SELECT from views or tables, but I can use some functions returning row types and cursors. I know I can use them to build table from scratch with htp.p etc., but it’s not very nice. I want to do it using APEX reporting with filtering and pagination functionality.
Is it possible?
Regards,
Przemek

Apologies for the delay, I was out of the office.
Below is a package serving as the basis for creating a view based on a pipelined function. The package is just a skeleton and will not compile in its current form, you will need to go through it filling in the blanks as described by the comments.
If you want some control over what rows are returned by the view from a larger result set, use the set_parameters function in the WHERE clause, E.G.:
select * from really_big_complicated_slow_view where 1 = view_pkg.set_parameters(something_that_reduces_the_view_result_set_size);
Or, a more concrete example:
select result_text from view_to_convert_to_csv where 1 = view_pkg.set_parameters(pi_table => 'my_table', pi_where = 'whatever');
In the spirit of full disclosure, I got the idea for using the "set_parameters" function in the view WHERE clause from a post or blog somewhere a couple of years ago but have lost track of who actually deserves the credit for the good idea.
-Tom
create or replace package demo_vw as
-- Package to serve as the basis for a view based on a function
-- Customize this record so that it represents a row from this view...
type row_type is record (
-- record fields here
type table_type is table of row_type;
-- This function is used in the DDL to define the view, for example:
-- create or replace view my_view (col1, col2, ..., colN) as
-- select * from table(my_view_vw.get_view);
function get_view
return table_type
pipelined;
-- Customize this function header to accept the parameters for this view, if
-- any. If this view does not require any parameters, the set_parameters
-- function may be deleted.
-- This function should always return 1 and is called as follows
-- select <whatever>
-- from my_view
-- where 1 = my_view_vw.set_parameters(p1, p2, p3, ..., pN);
function set_parameters (pi_whatever1 in whatever,
pi_whateverN in whatever)
return number;
end demo_vw;
show error package demo_vw
create or replace package body demo_vw as
-- Customize this list of private global variables to match the parameters
-- required by the view. These variables are set, reset, and validated by
-- set_parameters, reset_parameters, and valid_parameters respectively...
g_var1 whatever;
g_varN whatever;
function set_parameters (pi_whatever1 in whatever,
pi_whateverN in whatever)
return number
is
-- Customize this function header to accept the parameters for this view, if
-- any. If this view does not require any parameters, the set_parameters
-- function may be deleted.
-- This function should always return 1 and is called as follows
-- select col1, col2, ..., colN
-- from my_view
-- where 1 = my_view_vw.set_parameters(p1, p2, p3, ..., pN);
begin
g_var1 := pi_whatever1;
g_varN := pi_whateverN;
return 1;
end set_parameters;
function valid_parameters
return boolean
is
-- Customize...
-- Assumes that set_parameters has been called to set the value of the view
-- parameters.
l_valid boolean := true;
begin
return l_valid;
end valid_parameters;
procedure reset_parameters
is
-- Customize...
-- This is called at the end of the get_view function to reset the view
-- parameters for the next caller.
begin
g_var1 := null;
g_varN := null;
end reset_parameters;
function get_view
return table_type
pipelined
is
-- build and return each row for the view...
l_row row_type;
begin
if valid_parameters then
-- do your process to populate the l_row variable here...
pipe row (l_row);
end if;
reset_parameters;
exception
when others then
reset_parameters;
raise;
end get_view;
end demo_vw;
show error package body demo_vw
create or replace view demo
as
select * from table(demo_vw.get_view);

Reference value of an SQLPLUS variable in a PL/SQL anonymous block

All,
Is there a way of referencing an SQLPLUS variable within a PL/SQL anonymous block. See my example below........
sqlplus -s /@${L_DB_SID} <<-ENDOFSQL >> ${L_LOGFILE}
SET FEEDBACK OFF
SET PAGES 0
SET SERVEROUTPUT ON
WHENEVER SQLERROR EXIT SQL.SQLCODE
WHENEVER OSERROR EXIT 2
VARIABLE l_ret_sts NUMBER;
VARIABLE l_ret_msg VARCHAR2(300);
exec sh_plsql_owner.sh\$secure_batch.p\$set_role(p_ret_sts => :l_ret_sts);
begin
if :l_ret_sts > 0 then
dbms_output.put_line('l_ret_sts:'||:l_ret_sts||':SECURITY');
else
${L_PLSQL_PROG}(p_ret_type => 0, p_ret_sts => :l_ret_sts, p_ret_msg => :l_ret_msg);
dbms_output.put_line('l_ret_sts:'||NVL(:l_ret_sts,0));
dbms_output.put_line('l_ret_msg:'||:l_ret_msg);
end if;
end;
exit
ENDOFSQL
I need to be able to reference :l_ret_sts in the begin block using the if statement "if :l_ret_sts > 0 then"
:l_ret_sts is populated in a procedure call beforehand.
However it seems as though the begin block cannot reference the value returned to :l_ret_sts.
Any ideas.
Ian.

Managed to solve this. I put my call to the package that the role enables via dynamic sql....
sqlplus -s /@${L_DB_SID} <<-ENDOFSQL >> ${L_LOGFILE}
SET FEEDBACK OFF
SET PAGES 0
SET SERVEROUTPUT ON
WHENEVER SQLERROR EXIT SQL.SQLCODE
WHENEVER OSERROR EXIT 2
VARIABLE l_ret_sts NUMBER;
VARIABLE l_ret_msg VARCHAR2(300);
exec dbms_application_info.set_client_info('CONTROL-M');
exec sh_plsql_owner.sh\$secure_batch.p\$set_role(p_ret_sts => :l_ret_sts);
declare
v_text varchar2(500);
begin
if :l_ret_sts > 0 then
dbms_output.put_line('l_ret_sts:'||:l_ret_sts||':SECURITY');
else
v_text := 'begin ${L_PLSQL_PROG}(p_ret_type => 0, p_ret_sts => :1, p_ret_msg => :2);end;';
execute immediate v_text using in out :l_ret_sts, in out :l_ret_msg;
dbms_output.put_line('l_ret_sts:'||NVL(:l_ret_sts,0));
dbms_output.put_line('l_ret_msg:'||:l_ret_msg);
end if;
end;
exit
ENDOFSQL
Cheers
Ian.

Implicit PL/SQL cursors remain open, causing ORA-01000 (Client 9.2.0.1)

Hello,
since migrating our system from Oracle Client 9.0.X to 9.2.0.1 (Windows XP), i am encountering troubles when calling a stored procedure from a Cobol-Program:
after a while i run into a 'Maximum open cursors exceeded'-message (ORA-01000)
The stored procedure returns a cursor (ref_cursor)
When Executing the stored procedure, there are actually 2 cursors involved, in fact the stored PL/SQL procedure implicitely opens a child-cursor when doing a select within the PL/SQL.
After fetching the result and closing the cursor in my cobol-program, it correctly closes the cursor associated with the stored-procedure, but it does not close the cursor that was implicitely opened by oracle.
After a while i am running into a Maximum open cursors message, because those cursors have not properly been closed.
Here's a simple PL/SQL package that illustrates the problem:
create or replace package scott.SCOTTS_PACKAGE is
type ref_cursor IS REF CURSOR;
function GET_EMP(EMP_IN CHAR) return ref_cursor;
end SCOTTS_PACKAGE;
create or replace package body scott.SCOTTS_PACKAGE is
-- Function and procedure implementations
function GET_EMP(EMP_IN CHAR) return ref_cursor is
MyCurs ref_cursor;
begin
OPEN MyCurs FOR
SELECT EMPNO ,
ENAME ,
JOB
FROM SCOTT.EMP
WHERE ENAME = EMP_IN;
return(MyCurs);
end;
end SCOTTS_PACKAGE;
Here are some exerpts from my cobol program:
(The program iterates 100x through the section that executes the PL/SQL. After each iteration an additional open cursor remains in the database)
003800 EXEC SQL BEGIN DECLARE SECTION END-EXEC.
003900*
004000 01 SQL-USERNAME PIC X(16) VARYING.
004100 01 SQL-PASSWD PIC X(16) VARYING.
004200 01 SQL-DBNAME PIC X(64) VARYING.
004300 01 ORACLE.
004700 02 ORA-CUR-EMP SQL-CURSOR.
01 EMPREC.
02 EMPREC-EMPNO PIC X(4).
02 EMPREC-ENAME PIC X(10).
02 EMPREC-JOB PIC X(9).
005400 EXEC SQL END DECLARE SECTION END-EXEC.
018400 PROCEDURE DIVISION.
CONTINUE.
018700 EXEC SQL
018800 WHENEVER SQLERROR DO PERFORM SQL-ERROR
018900 END-EXEC.
019000*
CONTINUE.
019100 EXEC SQL
019200 WHENEVER NOT FOUND DO PERFORM SQL-NOT-FOUND
019300 END-EXEC.
022400 EXEC SQL
022500 ALLOCATE :ORA-CUR-EMP
022600 END-EXEC
PERFORM VARYING I FROM 1 BY 1 UNTIL I > 100
ACCEPT DUMMY FROM TER
IF DUMMY = "E"
MOVE 100 TO I
END-IF
PERFORM GET-EMP
ADD 1 TO I
END-PERFORM
119300 GET-EMP SECTION.
119400************************
119500 GAM0.
MOVE SPACES TO EMPREC-EMPNO EMPREC-JOB
MOVE "SMITH" TO EMPREC-ENAME
120200 EXEC SQL AT SSSI EXECUTE
120300 BEGIN
120400 :ORA-CUR-EMP:=
120500 SCOTT.SCOTTS_PACKAGE.GET_EMP(:EMPREC-ENAME );
120900
END;
121000 END-EXEC
121200 IF DB-ERR-CODE NOT = HIGH-VALUE
121300 DISPLAY "CCSIFSO:GET-AUTRE-MATR:APPEL PERS... OK"
121400 EXEC SQL
121500 FETCH :ORA-CUR-EMP
121600 INTO
121700 :EMPREC-EMPNO,
121800 :EMPREC-ENAME,
121900 :EMPREC-JOB
122400 END-EXEC
122500 END-IF
122600*
122700 IF DB-ERR-CODE NOT = HIGH-VALUE
122800 DISPLAY "CCSIFSO:GET-AUTRE-MATR:APPEL FETCH.. OK"
123000 ELSE
123100 MOVE LOW-VALUE TO DB-ERR-CODE
123200 END-IF
123300 EXEC SQL
123400 CLOSE :ORA-CUR-EMP
123500 END-EXEC
123600 GA-EX.
123700 EXIT.
124000 SQL-NOT-FOUND SECTION.
124100*----------------------
124200 NF0.
124300 DISPLAY "CCSIFSO:SQL-NOT-FOUND SECTION."
124400 MOVE HIGH-VALUE TO DB-ERR-CODE.
124500 NF-EX.
124600 EXIT.
124700*
124800 SQL-ERROR SECTION.
124900*-----------------
125000 ER0.
125200 EXEC SQL
125300 WHENEVER SQLERROR CONTINUE
125400 END-EXEC
125700 MOVE HIGH-VALUE TO DB-ERR-CODE
125800*
126100 DISPLAY "ORACLE ERROR DETECTED: " SQLCODE UPON TER
126200 DISPLAY SQLERRMC UPON TER
126300*
126400 EXEC SQL AT SSSI
126500 ROLLBACK WORK
126600 RELEASE
126700 END-EXEC
126800 DISPLAY "----------------------------" UPON TER
126900 DISPLAY " ! ROLLBACK ET DISCONNECT ! " UPON TER
127000 DISPLAY "----------------------------" UPON TER
127200 CALL "PPTERMJ".
127400 ER-EX.
127500 EXIT.
Finally here's an exerpt from V$OPEN_CURSOR, after a few iterations:
1 begin :b1 := SCOTT . SCOTTS_PACKAGE . GET_EMP (:b2 ) ; END ;
2 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
3 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
4 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
5 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
6 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
7 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
8 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
9 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
10 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
11 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
As you see, there is only 1 cursor starting with 'begin ... '
but there are 10 implicit cursors 'SELECT EMPNO, ... ' that have not been properly closed, nor reused by ORACLE.
In our old configuration (ORACLE CLient 9.0.X), you would only see:
1 begin :b1 := SCOTT . SCOTTS_PACKAGE . GET_EMP (:b2 ) ; END ;
2 SELECT EMPNO , ENAME , JOB FROM EMP WHERE ENAME = :B1
meaning all the other cursors have properly been closed.
As a conclusion: the program correctly closes the implicit cursors when using a 9.0 Client, wheras the implicit cursors remain open on Client 9.2.0.1 (Windows XP)
The underlying database can be either 8.i or 9, the problem remains the same.
Finally here's a small Delphi code, using ODAC-components, that somewhat illustrates the same problem:
procedure TForm1.ExecProcClick(Sender: TObject);
var I: INTEGER ;
begin
FOR I := 1 TO 5 DO
BEGIN
SP1.StoredProcName:='SCOTT.SCOTTS_PACKAGE.GET_EMP';
SP1.Prepare;
SP1.ParamByName('EMP_IN').AsString := 'SMITH';
SP1.ExecProc;
SP1.Next;
SP1.Close;
SP1.UnPrepare;
END;
end;
After each call to 'PREPARE', an additional implicit cursor remains open on the database. (using Oracle Client 9.2.0.1)
On our old system (Oracle Client 9.0 or 8.X), the same program would not generate accumulating open cursors on the database
Any suggestions would be welcome,
Claude

Cobol.. been many years since I last even saw some Cobol source code. Invokes all kinds of memories. :-)
Since you found the patch, the advice is superfluous, but works. Close the cursor at the PL/SQL side, e.g.
create or replace procedure CloseRefCursor( cRefCursor TYPELIB.TRefCursor ) is
begin
close cRefCursor;
exception when OTHERS then
-- if the cursor is already gone, not a problem
NULL;
end;In Delphi for example, one can subclass the class used for ref cursor calls and add a call to the above PL/SQL proc in the destructor. Or add create a standard Cobol close ref cursor section that does similar.

Error while executing Procedure - ORA-06511: PL/SQL: cursor already open

I have successfully compiled the following procedure but when I execute it, following error occurs, please adv.
Thanks and Regards,
Luqman
create or replace
procedure TESTKIBOR
(contno in varchar)
AS
BEGIN
DECLARE cursor c1 is
SELECT * FROM KIBOR_SCHEDULE
WHERE CN=contno;
begin
OPEN C1;
FOR line IN c1 LOOP
update kibor_schedule
set lincome=line.Lincome,
expo=line.eXPO,
pport=line.pPORT
where cn=line.cn
and rno=line.rno;
END LOOP;
COMMIT;
close c1;
END;
END TESTKIBOR;
ERROR at line 1:
ORA-06511: PL/SQL: cursor already open
ORA-06512: at "MKTG.TESTKIBOR", line 6
ORA-06512: at "MKTG.TESTKIBOR", line 10
ORA-06512: at line 1

Hi,
CREATE OR REPLACE PROCEDURE Testkibor
     (contno IN VARCHAR)
AS
BEGIN
DECLARE
    CURSOR c1 IS
      SELECT *
      FROM   kibor_schedule
      WHERE cn = contno;
BEGIN
--//    OPEN c1; --no need to open if using for loop
    FOR line IN c1 LOOP
      UPDATE kibor_schedule
      SET    lincome = line.lincome,
             expo = line.expo,
             pport = line.pport
      WHERE cn = line.cn
             AND rno = line.rno;
    END LOOP;
    COMMIT;
--//     CLOSE c1; -- no need for loop does it for you
END;
END testkibor;SS

Need help on Dynamic SQL Cursor in Forms

Hi All,
I am trying to execute Dynamic SQL Cursor in forms using EXEC_SQL built in.
I have a cursor for example:
'select * from supplier where supplier = '||p_supplier||' and processing_order = '||p_order
My code is
cur_num := Exec_SQL.Open_cursor;
sql_order := 'select * from supplier where supplier = '||p_supplier||' and processing_order = '||p_order;
EXEC_SQL.PARSE(cursor_number, sql_order);
EXEC_SQL.DEFINE_COLUMN(cur_num ,1,ln_Supp_Id);
EXEC_SQL.DEFINE_COLUMN(cur_num ,2,ls_Suppl_Name,30);
EXEC_SQL.DEFINE_COLUMN(cur_num ,24,ls_exchange,20);
sql_count := EXEC_SQL.EXECUTE(cur_num );
While EXEC_SQL.FETCH_ROWS(cur_num ) > 0 Loop
        EXEC_SQL.COLUMN_VALUE(cur_num ,1,ln_Supp_Id);
        EXEC_SQL.COLUMN_VALUE(cur_num ,2,ls_Suppl_Name);
        EXEC_SQL.COLUMN_VALUE(cur_num ,24,ls_exchange);
End Loop;
EXEC_SQL.CLOSE_CURSOR(cur_num );
In this case I have to write 24 Define Columns and 24 Column value. Is there any way to assign them to %rowtype at one time as I need all coulmn of the table.
I had similar case on multiple tables.
Please help me
Thanks,
Maddy

I need this dynamic sql because p_supplier and p_order values changes at run time
I do not understand. Is this a simplified sample or the real thing? You do know that you can pass variables to cursors:
cursor test is
select * from supplier where supplier = p_supplier and processing_order = p_order;
or does e.g. p_supplier hold other parts of the query?
cheers

Data type of preprend array size in Flatten To String block

Hi
The data type of the preprend array size in Flatten To String block is given as I32. Is it somehow possible to reduce the data type to I8, since the width and height of my array won't exceed 255 ?. I also need to do the same in Unflatten To String as well.
Best regards
Oesen

Oesen wrote:
Hi
The data type of the preprend array size in Flatten To String block is given as I32. Is it somehow possible to reduce the data type to I8, since the width and height of my array won't exceed 255 ?. I also need to do the same in Unflatten To String as well.
The short answer is no. This is because the index is an I32. NI likes to keep integers as an I32 whenever possible for reasons like this.
Since you are dealing with a 2D array (width and height), it will actually use 2 I32s before the actual data.
As Ravens stated, you could put in your own array sizes before the array in the string. But it is worth saving 6 bytes? Not likely.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Maximum size of an SQL statement

Hello,
we get a short dump with runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB.
The dump occurs at the following select statement:
        select * from /rtc/tm_inuse
          appending table gt_zrtc4inuse
          where obj_name in lv_sel_copy
            and trkorr ne p_trkorr.
We think the problem is the number of entries in the range table lv_sel_copy so that the maximum size of the SQL statement is reached.
But how likely is the maximum size ?
Depends the size on the data base ? We are using MaxDB 7.6, MaxDB 7.7.
How can we determine the maximum size so that we can calculate the nubmer of entries in the range tabel.
Any other idea or solution ?
Thanks
Arnfried

Hi,
You are getting this dump because maybe your entries are huge and it might have exceeded the buffer space of the table. You have to ask your basis team to increase the size of the buffer space.
or,
You can segregate the range values into smaller ranges and fetch from the database accordingly..
You can see the size of the table space in DB02.
or please refer this thread:
Need help regarding short dumps in BW
Edited by: sneha singhania on Jun 12, 2009 4:01 PM

The maximum size of an SQL statement has been exceeded.

In ST22, abap dump shows that one of the possible reason was "The maximum size of an SQL statement has been exceeded."
How can I know what's the maximum size and how to compute that size had been reached?
Is this shown anywhere in the log?

1. decalre temp_key as a table.
2. use this package size option ....this gets the data in bite-sized chunks
SELECT MATKL MATNR MEINS
INTO corresponding fields of table TEMP_KEY package size 1000
FROM MARA
WHERE MATNR IN SO_MATNR.
loop at temp_key.
MOVE-CORRESPONDING TEMP_KEY TO ITAB_KEY1.
IF WS_PCHR SPACE.
CLEAR ITAB_CHAR.
CLEAR ITAB_KEY1-CHARACTER. REFRESH ITAB_KEY1-CHARACTER.
PERFORM GET_CHAR TABLES ITAB_CHAR ITAB_KEY1-CHARACTER
USING ITAB_KEY1-MATNR.
ENDIF.
APPEND ITAB_KEY1. CLEAR ITAB_KEY1.
endloop.
ENDSELECT.

DBIF_RSQL_INVALID_RSQL The maximum size of an SQL statement was exceeded

Dear,
I would appreciate a helping hand
I have a problem with a dump I could not find any note that I can help solve the problem.
A dump is appearing at various consultants which indicates the following.
>>> SELECT * FROM KNA1                     "client specified
559                  APPENDING TABLE IKNA1
560                  UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER
ST22
What happened?
    Error in the ABAP Application Program
    The current ABAP program "/1BCDWB/DBKNA1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    The SQL statement generated from the SAP Open SQL statement violates a
    restriction imposed by the underlying database system of the ABAP
    system.
    Possible error causes:
     o The maximum size of an SQL statement was exceeded.
     o The statement contains too many input variables.
     o The input data requires more space than is available.
     o ...
    You can generally find details in the system log (SM21) and in the
    developer trace of the relevant work process (ST11).
    In the case of an error, current restrictions are frequently displayed
    in the developer trace.
SQL sentence
550     if not %_l_lines is initial.
551       %_TAB2[] = %_tab2_field[].
552     endif.
553   endif.
554 ENDIF.
555 CASE ACTION.
556   WHEN 'ANZE'.
557 try.
>>> SELECT * FROM KNA1                     "client specified
559                  APPENDING TABLE IKNA1
560                  UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER
561    WHERE KUNNR IN I1
562    AND   NAME1 IN I2
563    AND   ANRED IN I3
564    AND   ERDAT IN I4
565    AND   ERNAM IN I5
566    AND   KTOKD IN I6
567    AND   STCD1 IN I7
568    AND   VBUND IN I8
569    AND   J_3GETYP IN I9
570    AND   J_3GAGDUMI IN I10
571    AND   KOKRS IN I11.
572
573   CATCH CX_SY_DYNAMIC_OSQL_SEMANTICS INTO xref.
574     IF xref->kernel_errid = 'SAPSQL_ESCAPE_WITH_POOLTABLE'.
575       message i412(mo).
576       exit.
577     ELSE.
wp trace:
D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found [dypbdatab.c 510]
D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1 Reference= >TEXT-SYS< [dypbdatab.c 430]
D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1 Reference=>TEXT-SYS< [dypbdatab.c 137]
Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1 [dypropbag.c 641]
Y *** ERROR => ... Dynpro-Field= >DISPLAY_SY_SUBRC_TEXT< [dypropbag.c 642]
Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]
D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found [dypbdatab.c 510]
D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1 Reference= >TEXT-SYS< [dypbdatab.c 430]
D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1 Reference=>TEXT-SYS< [dypbdatab.c 137]
Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1 [dypropbag.c 641]
Y *** ERROR => ... Dynpro-Field= >DISPLAY_FREE_VAR_TEXT< [dypropbag.c 642]
Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]
I thank you in advance
If you require other information please request

Hi,
Under certain conditions, an Open SQL statement with range tables can be reformulated into a FOR ALL ENTRIES statement:
    DESCRIBE TABLE range_tab LINES lines.
    IF lines EQ 0.
      [SELECT for blank range_tab]
    ELSE.
      SELECT .. FOR ALL ENTRIES IN range_tab ..
      WHERE .. f EQ range_tab-LOW ...
      ENDSELECT.
    ENDF.
Since FOR ALL ENTRIES statements are automatically converted in accordance with the database restrictions, this solution is always met by means of a choice if the following requirements are fulfilled:
1. The statement operates on transparent tables, on database views or on a projection view on a transparent table.
2. The requirement on the range table is not negated. Moreover, the range table only contains entries with range_tab-SIGN = 'I'
and only one value ever occurs in the field range_tab OPTION.
This value is then used as an operator with operand range_tab-LOW or range_tab-HIGH.In the above example, case 'EQ range_tab-LOW' was the typical case.
3. Duplicates are removed from the result by FOR ALL ENTRIES.This must not falsify the desired result, that is, the previous Open SQL statement can be written as SELECT DISTINCT.
For the reformulation, if the range table is empty it must be handled in a different way:with FOR ALL ENTRIES, all the records would be selected here while this applies for the original query only if the WHERE clause consisted of the 'f IN range_tab' condition.
FOR ALL ENTRIES should also be used if the Open SQL statement contains several range tables.Then (probably) the most extensive of the range tables which fill the second condition is chosen as a FOR ALL ENTRIES table.
OR
What you could do in your code is,
prior to querying;
since your select options parameter is ultimately an internal range table,
1. split the select-option values into a group of say 3000 based on your limit,
2. run your query against each chunck of 3000 parameters,
3. then put together the results of each chunk.
For further reading, you might want to have a look at the Note# 13607 as the first suggestion is what I read from the note.

Need a column based off a PL/SQL cursor, how to do this?

Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Real Application Testing option
JServer Release 9.2.0.8.0 - Production
Report Builder 10.1.2.2.0
ORACLE Server Release 10.1.0.5.0
Oracle Procedure Builder 10.1.2.2.0
Oracle ORACLE PL/SQL V10.1.0.5.0 - Production
Oracle CORE     10.1.0.5.0     Production
Hi,
I am trying to create a fairly basic report but in the initial data model query, I have one column that is built based off of a PL/SQL cursor. How do I add this into my report? I have tried to create a function under Program Units and reference the function in my select statement for the data model however it keeps saying it is an invalid identifier, and I assume its looking in our database and not the function I created inside the report.
This is what it looks like:
SELECT   a.id,
         b.name,
         F_GET_GENERIC_NAME(b.code) "Generic Name",
         c.strength...and the function i want it to use in my report:
FUNCTION F_GET_GENERIC_NAME (in_code varchar2) RETURN VARCHAR2 IS
BEGIN
DECLARE
generic_name table.column%TYPE;
CURSOR cs_get_generic_name IS
SELECT /*+ USE_HASH (AR) */ desc
FROM a_ref AR, ai_ic AC
WHERE AC.code = in_code
AND   AC.code = AR.code
ORDER BY sort_nbr;
BEGIN
       generic_name := '';
          FOR v_get_generic_name IN cs_get_generic_name
          LOOP
             generic_name := generic_name || RTRIM(v_get_generic_name.desc)
                                 || '/' || ' ';
          END LOOP;
          generic_name := SUBSTR(generic_name, 1,(NVL(LENGTH(generic_name), 0) - 2));
RETURN generic_name;
END;
END;
    Any suggestions? Should I just create the function in the database?

I am trying to do it through a formula column but am encountering the following problem.
I've created a formula column in my data model where I want the column to be (inside the group).
Inside the PL/SQL for the column I reference the function that I had previously created with the following:
function CF_Generic_nameFormula return Char is
begin
     F_GET_GENERIC_NAME(:code);
end;However it won't let me compile, giving the error that "F_GET_GENERIC_NAME is not a procedure or is undefined." Is there something else that I am missing?
EDIT: Nevermind, i missed something simple like putting a return in front of the function call.
Edited by: a small rabbit on Nov 3, 2009 10:43 AM
Edited by: a small rabbit on Nov 3, 2009 10:44 AM

How to see pl/sql cursor in v$sql

Hi All,
I am trying to find how many child cursor will be created for select * into employee_rec from employees where employee_id = i however I couldn't find anything?
Do I have to use execute immediate?
Can't I measure PL/SQL cursors?
set serveroutput on;
declare
     employee_rec employees%rowtype;
begin
     for i in 100..110
     loop
            select * into employee_rec from employees where employee_id = i;
            dbms_output.put_line(employee_rec.first_name);
     end loop;
end;
select sql_text, sql_ıd, versıon_count, hash_value from v$sqlarea where sql_text like 'select * into employee_rec from employees where employee_id%';
<<No row returns>>
select sql_text, sql_id, child_number, hash_value, plan_hash_value from v$sql where sql_text like 'select * into employee_rec from employees where employee_id%';
<<No row returns>>
Thanks in advance

For example, I changed the code like the following
I just would like the see the cursor (select * from employees where employee_id = emp_id;) you know what I mean?
set serveroutput on;
declare
cursor my_c(emp_id number) is
select * from employees where employee_id = emp_id;
begin
     for i in 100..110
     loop
            for rec in my_c(i)
            loop
              dbms_output.put_line(rec.first_name);
            end loop;
     end loop;
end;
Thanks

At what point is PL/SQL cursor data retrieved?

Hi
This may sound like a silly question but since I am not entirely sure, I thought I'd ask.
In Oracle PL/SQL, do you know at what stage the query in a cursor is actually executed?
Is it at the DECLARE stage or when you first OPEN / LOOP on it?
I suspect upon the OPEN or the LOOP.
I.e. if I had a cursor declared but did not loop (using FOR .. LOOP) through it for some hours, would the query results be as at the time of declare or as at the time of the OPEN / FOR...LOOP?
E.g.
CURSOR invoices
IS
    SELECT invoice_number
    FROM unpaid_invoices
    WHERE due_date < TRUNC (SYSDATE)
BEGIN
-- Some time consuming processing that will take an hour
-- Start Loop through cursor of invoices.
<<overdue_invoices>>
FOR inv IN invoices LOOP
-- Some processing on the invoice
END LOOP overdue_invoices;
END;Would the cursor details for invoices be as at the CURSOR declaration or when the FOR inv... is reached?
Thanks
Martin

When you use a for loop like that it implicitly opens the cursor at the start and closes it at the end of the loop.
But the SQL query in that cursor is actually "run" when the first implicit or explicit fetch is issued, and retrieves new rows for every subsequent fetch.
Of course, before rows can be retrieved there needs to be several other tasks.
There's a good description of the steps of SQL processing in this part of the documentation.
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10471/adfns_sqlproc.htm
PL/SQL implicitly declares a cursor for all SQL data manipulation statements, including queries that return only one row. For queries that return multiple rows, you can explicitly declare a cursor to process the rows individually.
A cursor is a handle to a specific private SQL area. In other words, a cursor can be thought of as a name for a specific private SQL area. A PL/SQL cursor variable enables the retrieval of multiple rows from a stored subprogram.Edited by: fsitja on Dec 15, 2009 1:03 AM

Size of PL\SQL Cursor block

Similar Messages

Maybe you are looking for