Skip to content
January 20, 2011 / doganay

TOO MANY COMMITS

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Hi,
If you have too many commits in a sessions and you should not kill it or change it (for example embedded in an ancient program 🙂 ), you may use these commit_write parameter varieties:

alter session set commit_write=batch,nowait;

If you have medium count of commits:
alter session set commit_write=immediate,nowait;

or

alter session set commit_write=batch,wait;

This can be used in a normal DB lifetime:

alter session set commit_write=immediate,wait;

You can try these, test and choose the best for your situation.

Of course, you must change these systemwide if you can not step-in the problematic session (e.g. an old program)

alter system set..

try and pray 🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: