The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

We have a version 12 DB on solaris that is now showing a higher than normal CPU. As in 60% versus the normal 5-10%. What can I do to diagnose this? I have looked at some of the system procedures and none of them seem to provide what I need. I want to see if there is a connection that is pinning the CPU or connection that has been open and executing a query or update for a long time. This is in a production environment so I don't want to bring down the DB.

asked 23 Jul '13, 14:20

Codecranker's gravatar image

Codecranker
391192228
accept rate: 0%


Try the SQL Anywhere Monitor (which comes in the box), or Foxhound...

alt text

permanent link

answered 23 Jul '13, 16:40

Breck%20Carter's gravatar image

Breck Carter
26.6k418575824
accept rate: 21%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×238

question asked: 23 Jul '13, 14:20

question was seen: 610 times

last updated: 23 Jul '13, 16:40