| Re: OTM 5.5 performance problems? Check STATISTICS_LEVEL in database. Nick:
Yes, we are behind a fire wall, and we have a fully configured DMZ, so we've got firewall rules in place that allow connectivity between the servers.
Another thing that often gets overlooked is data communication between servers. I believe that some NIC cards default to half duplex, instad of full duplex, so check that as well.
Hmm, other things. The recompile invalid objects script doesn't always work, especially on a few VPD_LOGON objects (I think they're triggers, if I remember correctly). Recompile them manually, that should help some as well.
And, then you probably need to increase your JVM memory settings on your app server and web server. I've seen thrashing garbage collection bring a server to it's knees for having too little memory allocated for the JVM (It was only 256M). I've seen plenty of references to this here, so I'm sure you've got that covered.
And, obviously, check the last time database statistics were collected, and the STATISTICS_LEVEL parameter that was the main reason for this thread.
And, finally, don't forget to create a startup database trigger to pin certain packages in memory, especially large packages that are executed frequently. This is very easy to do, let me know if you need a code example.
Thanks...Steve Hughes |