Re: dbimport - 512MB RAM not enough?

In article <Pine.SOL.3.94.1.980310025817.8269A-100000@jfku.edu>, Don Miller <dmiller@jfku.edu> writes > >Hi - thanks for the help so far - but I'm still stuck. Here's some >further info. based on the suggestions I've received: > >On Sun, 8 Mar 1998, MARTIN wrote: > >> Just a question . Are you usings dbimport command with the "-d" option >> and telling informix the dbspace in which you want your db , if you >> don't say one ( with -d option ) all go to rootdbs and perhaps in >> rootdbs you don't have enought space. > >I'm using the -d toggle, and specifying a brand-new dbspace - I can >confirm that it is actually writing there, until it crashes. > That sounds correct. >On Sun, 8 Mar 1998, David Williams wrote: > >> Why do you think all of memory is used. >> >> Could it be you are running out of temp space? >> >> Try setting DBTEMP to point to a directory on a filesystem with >> lots of free space. > >I'm not sure - AIX monitor (running while the dbimport attempt is in >progress) shows gradually increasing use of memory, predominantly by >processes, but also to some extent by files. I don't see any activity >writing to any filesystem at all, but I DO see major amounts of data 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. >written to the physical disk where the (small) root dbspace resides. > That would be the reseved pages and getting updated. >Although the 5.0 manuals don't talk much about the DBTEMP environment >variable, it appears to be used to determine where temporary filesystem >writes go (which otherwise would go to /tmp) - but I'm not sure of that - >please correct me if I'm wrong. I tried this dbimport again with DBTEMP That is correct. DBTEMP under 5.x DBSPACETEMP under 7.x >set to a filesystem with a couple of GB's of space - nothing was written >there, or in /tmp, and it crashed as before (this time returning the error >"Segmentation Fault" and dumping a small core file. > >And on Sun, 8 Mar 1998, Wes Loftis wrote: > >> All my experience is with 7.xx, but I think you need more temp dbspace >> for the import to be successful > >That is what I think I need to do, too - but in 5.0, I don't see any >mention of the DBSPACETEMP configuration parameter, and the Dbspace Temp >box you see in 7's onconfig / Initialization screen does not appear in the >similar place in 5's tbconfig. So, how can I specify a temp dbspace in 5 >- can I manually add the DBSPACETEMP entry to tbconf, or will it be >ignored? And does that temporary dbspace need to be otherwise set up or >initialized? I'd prefer to use a unix ("cooked") file for this temporary >purpose, but I can't find a clue on how to set it up... > DBSPACETEMP and temporary dbspaces ONLY EXIST under 7.x NOT under 5.x. 5.x uses DBTEMP. >All further thoughts and suggestions gratefully accepted! > Run df -k before starting the dbimport. After a few minutes run another df -k. What changes. Same with onstat -d. what changes? Run ps -ef | grep dbimport what is the size of the dbimport process? Run swap -l, how much swap is free? >Regards, > >Don Miller >Network Operations >JFK University > > -- David Williams Maintainer of the Informix FAQ Primary site (Beta Version) http://www.smooth1.demon.co.uk Official site http://www.iiug.org/techinfo/faq/faq_top.html I see you standin', Standin' on your own, It's such a lonely place for you, For you to be If you need a shoulder, Or if you need a friend, I'll be here standing, Until the bitter end... So don't chastise me Or think I, I mean you harm... All I ever wanted Was for you To know that I care