Re: dbimport - 512MB RAM not enough?

Don Miller (dmiller@jfku.edu) wrote: : More on this, based on data I gathered in tonight's attempt: : On Tue, 10 Mar 1998, David Williams wrote: : > Probably because AIX is caching writes, hence the buffer is : > dynamically growing as needed. As more memory is needed by : > applications the buffer cache will skrink again. This is what they : > mean by a unified cache. : If that's AIX caching it, I'd expect (hope?) that it'd also use swap space : - but it doesn't seem to here; the swap space is never fully exhausted : when it crashes. : (Regarding the write activity I see to the root dbspace device) : > That would be the reseved pages and getting updated. : Could it be more than that? Maybe also temporary tables, etc? Or maybe : (as Wes Loftis has proposed) logs (even though they are being continuously : written to tape - maybe the tape can't keep up? : However, tonight I even tried sending the logs to /dev/null - made no : difference. : > DBTEMP under 5.x : > DBSPACETEMP under 7.x : [] : > DBSPACETEMP and temporary dbspaces ONLY EXIST under 7.x NOT under : > 5.x. 5.x uses DBTEMP. : Does that mean that the functions which use the temp dbspace under 7 (as : distinct from the filesystem /tmp writes affected by DBTEMP) can't be : forced out of the root dbspace in 5.x? : Or should NPROC_DBTEMP affect this in 5.x - I have tried setting it to a : filesystem with plenty of space - no effect; nothing is ever written there : at all. : > Run df -k before starting the dbimport. After a few minutes run : > another df -k. What changes. : Essentially nothing - no significant change in any mounted filesystem; : /tmp and also the filesystem specified by DBTEMP seem to be completely : unused. : > Same with onstat -d. what changes? : Again, not much - the number of free pages in the target dbspace of the : import declines as the tables are loaded; the rootdbs and other dbspaces : show exactly the same numbers of free pages all throughout the attempt. : > Run : > : > ps -ef | grep dbimport : > : > what is the size of the dbimport process? : It fluctuates wildly - from an initial 1700 K to a max of over 40MB, up : and down while the import proceeds. This does NOT correlate with overall : memory use, which steadily increases until it crashes. Just random guess. My AIX has ulimit default to 32MB of memory per process. Is this causing your crash? But I just wonder why dbimport need so much memory and your import has so much activities on rootdbs. Because, at least on IDS 7, dbimport performs non-logging operation during imports.. Chris