|
We're running Domino v 6.5.4 on a combination of W2K servers and one iSeries. Some of our databases have documents that are basically copies of iSeries data files. We've been using LEI to keep those documents in sync with the iSeries, but my boss wants to get away from that, so I've been setting up an agent in each one that a) deletes all the documents in question and then b) creates new documents using ODBC and SQL to pull the information from the iSeries. This has worked very well so far, but now I've got a problem: I've got a Domino database on the iSeries whose agent is throwing an "LS:DO- Out of memory" error at some point during the document creation process. Actually, it seems to create the new documents fine, but at the end it's supposed create a log entry telling how many it created, and instead it throws the error. The thing is, this database is a copy of one that runs on a W2K server, and the one on the W2K server works fine. I even made another copy of the one on the W2K server onto the iSeries, and it throws the same error. But other databases on the iSeries run fine, including one whose total number of records x record size is about twice as big. The ones that fail are trying to copy about 1300 records that are about 550 characters each. One that works fine copies 12,000 records of 79 characters each. Does anyone have any ideas about what might be causing this, or where I might look to troubleshoot the problem? Worst case scenario, I figure I could set up a replica on the W2K server and run the agent from there, but I'd really prefer not to do that. . . . Thanks very much, Mike Naughton Senior Programmer/Analyst Judd Wire, Inc. 124 Turnpike Road Turners Falls, MA 01376 413-863-4357 x444 mnaughton@xxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.