Can someone explain the following error in more detail?
Error in synchronize(1:length(search())): No room in database table
This is happening to us with Splus3.4 on Solaris2.6.
>From within a for-loop we call a function that---among other
things---executes the synchronize command mentioned above. The loop
bombs out after 2 or 3 iterations. In this particular case we might
be able fix things by being more selective in what we synchronize and
when, but in general what are the rules governing this "database
table?" It seems to me that calling synchronize should just update
Splus's notion of which objects are available, it shouldn't cause
Splus to use up more room somehow.
Thanks, and I will summarize any responses to the list.
--
Ed Kademan 508.651.3700
PHZ Capital Partners 508.653.1745 (fax)
321 Commonwealth Road <kademan@phz.com>
Wayland, MA 01778
-----------------------------------------------------------------------
This message was distributed by s-news@wubios.wustl.edu. To unsubscribe
send e-mail to s-news-request@wubios.wustl.edu with the BODY of the
message: unsubscribe s-news
|