[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dec_data_distributor

Title:	The Replication Option for Rdb
Notice:	Product renamed to Replication Option for Rdb
Moderator:	BROKE::PROTEAU

Created:	Wed Mar 02 1994
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	287
Total number of notes:	1231

226.0. "DDD transfer RDB --> ORACLE fails with %RDB-F-SYS-REQUEST ....." by ORAREP::LEMAN::NAUFFRAY () Tue Jul 02 1996 13:31

Hi,

   A customer is trying to execute a transfer from RDB 6.0 to ORACLE (NT) via
 DDD, DBI and DBI Gateway for Oracle . Everything is going well for the small
 relations, but when trying to transfer a 600.000 records table, the transfer
 is failing with the following message :

 %RDB-F-SYS-REQUEST, error from system servics request
 NONAME-NOMSG, The exception util_e_insufficient_memory caught by SDI_execute.


   It's clearly a lack of memory resources, but in order to save some time, do
 you know exactly what are the account/system parameters in cause for this kind
 of error. The account sending the transfer seems to have already quite fair    
 parameter values :

           Pgflquota : 260000
           wsdef     : 2048
           wsquota   : 16384
           wsextent  : 64000
           Bytlm     : 200000
           fillm     : 600
           Enqlm     : 32767


   I'll also have a look to the SYSGEN PQL/parameters and make some tests with
 bigger parameters.

   
   Any shortcut will be appreciated.
   

   Thanks a lot in advance for the hand.
   Cheers,

   James

T.R Title User Personal
Name Date Lines

226.1 The answer is "lots" BROKE::BROWN Wed Jul 03 1996 18:28 26

T.R	Title	User	Personal Name	Date	Lines
226.1	The answer is "lots"	BROKE::BROWN		`Wed Jul 03 1996 18:28`	26
	There is a problem with the shipping version of the Oracle gateway with respect to memory usage under certain circumstances. I believe this problem is discussed in the DBINTEGRATOR_PUBLIC notes file, but I did not find the reference. To make a long story short, when transfering data to an Oracle database, if you are using version 3.1a of the gateway (or earlier) the amount of memory you will need is a function of the amount of data you plan to move in a single transfer. Clearly this is not acceptable for transfers of any size. A better alternative is to get your customer to field test FT2 of the V7 gateway. In the meantime, you might try bumping wsextent up by the the size of the data you plan to transfer. I am ashamed to show my VMS ignorance, but assuming that you are running on a VAX, and assuming that wsextent is given in pages, if you estimate that your transfer consists of N records, each of approximately M bytes, then I guess I would try to bump wsextent up by N * M / 512. If you are running on an Alpha, I think the page size is 1024, so bump wsextent by half of the above. Oh, when I say "bump" I mean add in addition to what you already are using. Sorry I don't have a better answer. -chipper

There is a problem with the shipping version of the Oracle gateway with 
respect to memory usage under certain circumstances.  I believe this
problem is discussed in the DBINTEGRATOR_PUBLIC notes file, but I did
not find the reference.

To make a long story short, when transfering data to an Oracle database,
if you are using version 3.1a of the gateway (or earlier) the amount of
memory you will need is a function of the amount of data you plan to move in
a single transfer.  Clearly this is not acceptable for transfers of any size.
A better alternative is to get your customer to field test FT2 of the
V7 gateway.

In the meantime, you might try bumping wsextent up by the the size of the
data you plan to transfer.  I am ashamed to show my VMS ignorance, but
assuming that you are running on a VAX, and assuming that wsextent is given
in pages,  if you estimate that your transfer consists of N records, each of
approximately M bytes, then I guess I would try to bump wsextent up by
	N * M / 512.
If you are running on an Alpha, I think the page size is 1024, so bump wsextent
by half of the above.

Oh, when I say "bump" I mean add in addition to what you already are using.

Sorry I don't have a better answer.

-chipper