Home » RDBMS Server » Server Administration » Killing a process
Killing a process [message #265873] Fri, 07 September 2007 13:11 Go to next message
babble
Messages: 25
Registered: July 2007
Location: new york
Junior Member
Hi Guru's

I saw 2 processes using 48% and 50% of CPU and idle % was about 0% looking on top command output.

Whole of the portal was slow . Hence I did kill -9 pid .
Everything was under control after killing that process.
Now I want to know what was that process doing.
I have the PID of that process,but nothing is coming out of v$process from that process Id.
Can it cause any problems due to killing any unknown oracle process
Is there any way to find out what was that process doing.

Regards


Re: Killing a process [message #265878 is a reply to message #265873] Fri, 07 September 2007 13:34 Go to previous messageGo to next message
BlackSwan
Messages: 25035
Registered: January 2009
Location: SoCal
Senior Member
An identical question was asked & answered on this board within the last month.
Re: Killing a process [message #265880 is a reply to message #265878] Fri, 07 September 2007 13:44 Go to previous messageGo to next message
babble
Messages: 25
Registered: July 2007
Location: new york
Junior Member
Can you forward me the link to that identical issue.

Thanks

[Updated on: Fri, 07 September 2007 14:27] by Moderator

Report message to a moderator

Re: Killing a process [message #265883 is a reply to message #265873] Fri, 07 September 2007 13:47 Go to previous messageGo to next message
BlackSwan
Messages: 25035
Registered: January 2009
Location: SoCal
Senior Member
You should have searched this board BEFORE posting the question.

If you are incapable or unwilling to perform the search yourself,
then You're On Your Own (YOYO)!

Re: Killing a process [message #266004 is a reply to message #265873] Sat, 08 September 2007 21:08 Go to previous messageGo to next message
galan_josel
Messages: 7
Registered: September 2007
Junior Member
Better to killing a process.
Use ORADEBUG parameter suspend
Sometimes just killing the process will create more work, If is the case of DML statemt.
Just think about what have to heppend if you kill an "INSERT"
well have to ROLLBACK. More work.

JLG


Galan.
Re: Killing a process [message #266022 is a reply to message #266004] Sun, 09 September 2007 00:59 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
SUSPEND does not release locks.
What if you updated millions rows. Do you want to see them indefinitely locked?

Regards
Michel
Re: Killing a process [message #266439 is a reply to message #266022] Mon, 10 September 2007 22:38 Go to previous messageGo to next message
galan_josel
Messages: 7
Registered: September 2007
Junior Member
Is true. It will not release the locks. But provide you with room to see what was the problem if your server was very busy.
You can continue the even during the day working and release the process after hours. Cool

Personally I don't like to kill the process from the OS.
I get the PSID, SID and check what is the problem. If I have to kill a process, I do it first in the DB, if is need it them I kill the OS. After knowing what it is. Mad

Usually when DML statements are in use and we are modifying a big numbers of rows I will like to commit frecuently. I like to use for this a cursor.
Laughing
Re: Killing a process [message #266441 is a reply to message #266439] Mon, 10 September 2007 23:03 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Usually when DML statements are in use and we are modifying a big numbers of rows I will like to commit frecuently. I like to use for this a cursor.

Wrong approach.
This:
  • can lead to ORA-01555
  • means you have to plan for an application implementation in case of failure
  • generates more waits on log components and/or DBWR
  • consumes more CPU

In summray, if you can do it in one SQL, then do it in one SQL. Just allocate space enough for your undo (that you have to (almost always) allocate with frequent commits if you don't want to get an ORA-01555 error).

Regards
Michel
Re: Killing a process [message #266456 is a reply to message #266441] Mon, 10 September 2007 23:33 Go to previous message
galan_josel
Messages: 7
Registered: September 2007
Junior Member
Thank you for your input.
I have not problems with ORA-01555.
But I'm testing diferent scenarios with big tables now doing updates. Cool

The original question was related to killing a process.
and my point was.
1)- Check what you are killing.
2)- Don't kill if you don't have to.
3)- Killing DML will increase the load.
4)- Kill from the DATABASE and them OS if is necesary.


Best Regards.
Jose.
Razz
Previous Topic: 64 bit oracle
Next Topic: ORA-04031 shared memory errors are occuring
Goto Forum:
  


Current Time: Sat Dec 03 20:37:56 CST 2016

Total time taken to generate the page: 0.04269 seconds