How to reduce the HP-UX CPU loading when running Oracle SQL Update statement


I have executed a number of UPDATE statements in Oracle SQLplus and I noticed that the CPU loading (I'm using "sar" in HP-UX) reaches above 95%.    After the UPDATE statements were processed completely, the CPU load goes back to normal of about 5-10% only , Is there a way to reduce/limit the CPU loading to a maximum of 50% when using UPDATE statement?  

Processor:  4-CPU
Oracle:   11g

BTW, when I use SELECT statements, it does not reach 95%.
Norman Manzo NoraAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slightwv (䄆 Netminder) Commented:
What makes you think 95% CPU usage is a bad thing?  Are other apps suffering by this?

You "can" use resource management to limit OS resources:

I placed "can" in quotes because you might not want to do this.

95% CPU utilization is only a problem if other processes are degraded.  If normal CPU is 5-10%, what other apps slow down when your update statement uses 95%?  If none, then let Oracle use the available resources.  It isn't impacting anything.
what is the update doing?  Are there triggers?

if it's consuming cpu, with what is the cpu busy during that time?
Norman Manzo NoraAuthor Commented:
Hi Slightwv, unfortunately, it is affecting other some critical application processes when the update statement is ran.

To sdstuber, I've attached the sar command output.  

I'm using a simple update statement command and somehow, the SQL statement is consuming so much CPU resource.
according to your sar output,  you're NOT consumping cpu,  you're waiting on IO.  Which makes sense because an UPDATE must do io both to find the rows and then to write the new values.  If you have triggers or audits that write to other tables, then that's even more io.  Plus the redo and undo records also require io.

So, doesn't look to me like you have a problem at all.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
why the penalty grade?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.