> My understanding is that
> 1) D3 "takes" all of the memory that has been allocated to it at
> 2) TOP doesn't work real well with INDIVIDUAL D3 process threads ...
> seems to show "crazy" memory figures at times
> 3) What are your files sizes like in D3 ... poorly sized files in this
> environment can have a dramatic impact ... transaction files growing
> during the week ?
> 4) If all else fails, can you roll back to the "supported" RH7.1
> platform (or call your local distributor :-)
> > Hi Group
> > 100 User site with dual CPU's 512 MB Ram. D3 7.2.1 , RH 7.2. Twice or
> > more a week we have to reboot the system as performance dies. I am
> > wondering if anyone else out there has had similar issues with a similar
> > configuration. Has RH7.2 got severe memory leaks. A top shows that out
> > of 512 mb ram there is on 40+mb available. Any ideas / comments most
> > welcome.
> > Cheers
Unfortunalty, RDBMS D3 (NT or Linux/PROPlus) has not a mechanism of
service log file (as record in TCL-STACK, POINTER-FILE and others)
You have to do yourself manual or using PICK/BASIC Program which It
will be clear these files. Why RD doesn't undestand it? The OVF
Cleaner or OVF reconfig inside D3, and which works in an work hours
Why not ?
And I add follow I MUST refragmentation D3 ovf space, very easy way
file-save and D3 /restore, variant hot-back-up works but It has
several OF problems and e.t.c, but You can try in the first
AND YOU REMEMBER 15-20% free RDMS disk space is a VERY HARD SIGNAL of
reconfiguration your system.
I add, install D3 RDBMS as separate disk partion (signature d8), this
way helps increase performance your system, usually
1 Unix native xxx GB.
2 Unix swap xxx GB.
3 D3 RDBMS xxx GB.
4 Unix extended-
5 /usr xxx
6 /var/log/ xxx
7 /home xxx
other disk space I cut 1950 Mb. (Future devices for D3)
And again check module all often using D3 file
PICK/BASIC's shareware progs
I use a same Linux disk structure more 3+ years and say It works good.