Memory Error?

[fevacoder]

Has anyone see this error and what could possibly be the solution? I am getting this when I run the report in the reports wizard, after I select a layout, fields, template etc.
REP-0065: Virtual Memory System error.
REP-0200: Cannot allocate enough memory.
cavaa22
Another window...
REP-0619: You can not run without a layout.

 

[nagornyi]

Using Ref cursor already?
Here is whar Oracle says about the causes of these errors:
Scenario 1
**********
Your open cursor statement does not have the same datatype "order" as defined
in the record type definition.

Scenario 2
**********
Your record type definition does not match the datatype of the column in the
database that you are selecting.

 

[fevacoder]

OK, well I have the below package in my Oracle Report...
PACKAGE pkg_test IS
type rec_test
is record
( client_name client.client_name%type
, last_name client.last_name%type
, date_of_birth client.date_of_birth%type );

type rc_test is REF CURSOR return rec_test;
END;

next I'm calling it from a function...
function QR_1 return pkg_test.rc_test is
outCursor pkg_test.rc_test;
begin
edmdata.pkg_reports.get_oip_59_half_and_over('OOD', '2004,2009',outCursor);
return outCursor;
end;

My proc begins...
PROCEDURE get_oip_59_half_and_over
(p_foreign_oip_id IN OIP.foreign_oip_id%TYPE,
p_reg_dsi_list IN VARCHAR2,
p_out_cursor OUT RETURNCURSOR)
IS
v_sql_string VARCHAR2(4000) :=
' SELECT DISTINCT CLIE

Is my record type definition wrong? I'm a little illiterate when it comes to this are of PL/SQL...
Thanks.

 

[fevacoder]

See I think I have scenrio 1 and 2 of your reply covered...
I do think I should mention that Perhaps that the open cursor is using a weakly typed ref cursor and that the report is using a strongly typed ref cursor. I'm not sure how or if I can get around this.
Thanks, Brian

 

[nagornyi]

It is possible the difference in type definitions causing the problem. Using Ref cursor is a pretty tricky part of Oracle Reports. I would recommend to make some simple report that works with some simplest ref cursor returning single-field record. Once that works, I would upgrade the report in steps to make it what you need.