Skip to Content
author's profile photo Former Member
Former Member

oradebug setospid ?

Hello

Does anyone has experience with oradebug.

Namely I can not stop DB and I guess the reason is an Oracle process running at 100 % CPU.

I think I should issue something like "oradebug setospid 11287" where 11287 is PID at OS level.

I guess (based on note 613872) then I would get detailed trace log in working directory.

However I do not find "oradebug" anywhere on machine.

Has anyone some idea where to find "oradebug" and is the command I would issue correct

Thx in advance

Jan

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Feb 10, 2014 at 01:59 PM

    Hi Jan,

    > Does anyone has experience with oradebug

    For sure 😊

    > However I do not find "oradebug" anywhere on machine.

    Oradebug is a utility within SQL*Plus, so you can not find it anywhere on your server. You have to login via SQL*Plus and then you can use oradebug. This can be tricky sometimes (especially in hanging situations), but there is a prelim option for such situations as well.

    > I think I should issue something like "oradebug setospid 11287" where 11287 is PID at OS level.

    Depends on what you want to trace / debug. For example system state dumps can be created with any attached process, but stack traces are OS process dependent.

    I have written several blog posts about several scenarios:

    > Namely I can not stop DB and I guess the reason is an Oracle process running at 100 % CPU.

    How do you try to shutdown the database? Is it the SMON process, that is running on CPU by chance?

    Regards

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Jan,

      > When trying restart an R3 system yesterday, the database did not get down.

      Yes, i understand this, but there could be several reasons for that. At first we need to know how you exactly tried to shutdown the database (shutdown, shutdown immediate, shutdown abort).

      > This process was hanging when trying to shutdown

      The process seems to run fully on CPU. Was this PID related to SMON by chance? This is a well known root cause and possibly works as it designed. You also could verify this in the alert log file, if you have a large time gap with "SMON: disabling tx recovery" for example.

      > Could you let me know if I can in that situation kill that process without threaten consistancy

      No, as i don't know which process it is (and what it is doing).

      > What should be done in such an situation

      You are far away from using oradebug with your described scenario. At first you need to know which kind of process is running fully on CPU, then you need to determine what it is doing / waiting for and only after that you may need to use oradebug for further troubleshooting.

      Regards

      Stefan

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.