[suse-oracle] SLES 10SP2 and Oracle 10.2.0.2

Werner Flamme <[email protected]>
Newsgroups gmane.linux.suse.oracle.general
Organization Helmholtz-Zentrum für Umweltforschung UFZ
Message-ID <[email protected]>
Hi all,

we have a SAP Solution Manager (on Oracle 10.2.0.2) running on a box
under SLES 10 x86_64 with kernel 2.6.16.60-0.30. Then, we updated to
kernel 2.6.16.60-0.33 - but this one obviously caused problems: the
machine ran for 7 days and then started swapping without mercy, every
process was kicked out of ram until the guilty one was killed, too.
System load about 40 (2 cores).

After the guilty process was dead, the load went back to 0. Then, most
of the time even "init 0" failed because of "no more processes to kill".
Every 7 days the same show :-(

Most of the time - as far as the logs show before the logging processes
were killed - the oracle backup was running. Since it runs every night
with the same task, wa can't blame Oracle for the over-full memory.
After going back to 2.6.16.60-0.30, this problem did not occur again.
And we never updated the RDBMS...

First question: are we the only people who had this problem?

Second question: now the next kernel is out, 2.6.16.60-0.34. Is there
someone out in the world running Oracle 10.2.0.2 on a x86_64 system with
that kernel, who can say that the memory consumption does not start to
get out of bounds?

I don't want a crashing SAP SolMan, otherways I'd just try it out...

Regards,
Werner
_______________________________________________
suse-oracle mailing list
[email protected]
http://listx.novell.com/mailman/listinfo/suse-oracle
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.