Hi all,

I am using "SAS/Access to RDB", allowing the SAS System to access to
RDB data.
We have a %COSI-F-EXQUOTA error message about quota exceeded, which is
generated by RDB, not by SAS.

Here is my configuration :
VMS : OpenVMS V7.3-1 on node FRLI08
RDB : Oracle Rdb V7.0-7
Rdb/Dispatch V7.0-7 (OpenVMS AXP)

I access to RDB with the SAS System, but I have a RDB error message
that do not stop my program :

430 +proc sql;
431 + create table work.PRPDTAIL as
432 + select a.*,b.reconacc
433 + from work.PRPDTAIL a, XXX.VSOLDTO b
434 + where a.soldto=b.soldto and a.salorg=b.salorg and
a.channel=b.channel;
ERROR: Finish failed. Error due to commit, end transaction or detach
failure.
The Rdb/VMS error message is %COSI-F-EXQUOTA,
+ERROR: Finish failed. Error due to commit, end transaction or detach
failure.
The Rdb/VMS error message is %COSI-F-EXQUOTA,
+ERROR: Finish failed. Error due to commit, end transaction or detach
failure.
The Rdb/VMS error message is %COSI-F-EXQUOTA,
exceeded quota -SYSTEM-F-EXQUOTA, process quota exceeded.
+ exceeded quota -SYSTEM-F-EXQUOTA, process quota exceeded.
+ exceeded quota -SYSTEM-F-EXQUOTA, process quota exceeded.
NOTE: Table WORK.PRPDTAIL created, with 35208 rows and 15 columns.


We have found an interesting documentation about Rdb7 Release 7.0.1.3.
It says that this is a bug, fixed on Release 7.0.1.3, but we are using
7.0.7.
Here is the documentation; "Oracle Rdb7™forOpenVMS, Release Notes,
Release 7.0.1.5", January 1999, page 61 :
************************************************** *******************
4.1.26 Query Using a Table with Many Indexes Ran Out of Memory Quota
Bug 658882.
When a table had many indexes defined on it, a simple SELECT query
with an
equality selection ran out of memory with the following error:
%COSI-F-EXQUOTA, exceeded quota
-SYSTEM-F-EXQUOTA, process quota exceeded
The following example shows this problem where the optimizer
repeatedly created
redundant ordering data structures for the order "FIRST_NAME,
LAST_NAME"
and finally ran out of memory if the number of indexes increases.
SQL> CREATE INDEX EMP_F_L ON EMPLOYEES (FIRST_NAME, LAST_NAME);
SQL> CREATE INDEX EMP_F_M ON EMPLOYEES (FIRST_NAME, MIDDLE_INITIAL);
SQL> CREATE INDEX EMP_F_C ON EMPLOYEES (FIRST_NAME, CITY);
SQL> CREATE INDEX EMP_F_S ON EMPLOYEES (FIRST_NAME, STATE);
SQL> CREATE INDEX EMP_F_C_S ON EMPLOYEES (FIRST_NAME, CITY, STATE);
SQL>
SQL> SELECT EMPLOYEE_ID FROM EMPLOYEES
cont> WHERE FIRST_NAME = 'Foo' AND LAST_NAME = 'Bar'
cont> ORDER BY FIRST_NAME, LAST_NAME;
%COSI-F-EXQUOTA, exceeded quota
-SYSTEM-F-EXQUOTA, process quota exceeded
As a workaround drop enough indexes to run the query.
This problem has been corrected in Oracle Rdb7 Release 7.0.1.3.
************************************************** *******************

Can someone help me ?
Regards

certainly Oracle Rdb support can assist. Why not simply
get in touch directly with them? This news group is not an official
support channel.

As far as the error - I'd start by doubling all the account
quotas and trying again. VMS isn't all that great at articulating
what is the actual quota being exceeded in some cases.

G?raldine Deschamps wrote:
--
- - - - -
opinions expressed here are mine and mine alone
and certainly are not intended in any way to
express or represent any opinions or commitment
of oracle corporation.

norman lastovica / oracle rdb engineering