Search my Blog

Follow me on Twitter

Like a cat on Hot tin roof changing sdu size

Introduction

On one of the projects there is a performance dip between Midnight and 05:00 and I have been asked to investigate the environment. The Oracle database I am working with is a 920.6 32 bit version on HP UNIX. I have used Stats pack as tool to do analyses. These stats packs are running in 15 minutes intervals in the database. During the intervals at night the top wait events are very often:

The application connecting to the database comes in via an application server with EAI Tibco software via Java.

Since we suspect that there might be an issue on the network level, and after searching the web following approach is chosen for now:

According to the information found on the Web (still grateful of people sharing their experiences in blogs) this wait event might tend to network latency and there is an interesting option to tweak the package size in the communication between Listener and Client by tweaking the SDU size. As a default in the communication this package size is 2K by and it can be tweaked up to 32K.

In a Database – Client environment this could be implemented in the following way if BOTH database environment and the client will set the SDU size. Hmm let me say that one more time. It needs 2 b done on BOTH sides. Heard about nasty things that could happen if the setting is not in sync between the two.

On the Client side you will either set the tnsnames.ora or set/chance your Java configuration or you alter your sqlnet.ora.