NOAGE Parameter set to 1 Under Baan Instance
Posted in 1999
Topics: Installation, Setup & Upgrades, Platform-Specific Issues
Hi All , Can anyone shed any light on this for. The scenario is as follows:- HP-UX 10.20 1 CPU Small D330 Baan Installed on machine Informix recommend you set NOAGE to 1 if platform supports it. As in release notes it does. So I set NOAGE to 1 I then proceeded to load using baan a company using a baan session , load company from sequential dump .( for none baan users a file in a baan format which baan program can read and creates relevant tables and indexes ). About 300 tables had been created and loaded and the load average of the machine shot up to 21.00 which was not good for the machine as you may know. I interrupted process running on PC. It stops and machine starts running as normal. Question : Why ??????? Thanks Pankaj Patel P.S I then set NOAGE to 0 and loaded using Baan Session and it loaded all Information. P.P.S I hope I have not been stupid and missed the obvious.
pankaj wrote: > > Hi All , > Can anyone shed any light on this for. The scenario is as follows:- > > HP-UX 10.20 > 1 CPU > Small D330 > Baan Installed on machine > > Informix recommend you set NOAGE to 1 if platform supports it. As in release > notes it does. > > So I set NOAGE to 1 > > I then proceeded to load using baan a company using a baan session , load > company from sequential dump .( for none baan users a file in a baan format > which baan program can read and creates relevant tables and indexes ). > > About 300 tables had been created and loaded and the load average of the > machine shot up to 21.00 which was not good for the machine as you may know. > I interrupted process running on PC. It stops and machine starts running as > normal. > > Question : Why ??????? > > Thanks > > Pankaj Patel > > P.S I then set NOAGE to 0 and loaded using Baan Session and it loaded all > Information. > > P.P.S I hope I have not been stupid and missed the obvious. I experienced the same behavior on an HP-UX 10.X platform -- it was the strangest thing. We did research the problem with Informix and found that Informix had a bug in their IDS version that caused the behavior (Informix sets the priority of its processes to realtime). You didn't mention what version of IDS you have .... but it might be the same problem.