- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- High CPU and PRI
Operating System - HP-UX
1752716
Members
5861
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 12:18 AM
04-15-2003 12:18 AM
High CPU and PRI
I'm running Oracle 8.1.7.3 on HP-UX 11.0 and I has a situation each day where an oracle process 'runs away' and uses 99.5% of the CPU and has a PRI (from top) of 233. This process locks the entire instance but still allows me to login to the second instance on the server. How can I find out what this process is doing in terms of SQL statement, when in essence it has the oracle instance locked?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2003 01:34 AM
04-15-2003 01:34 AM
Re: High CPU and PRI
hi,
Below are the steps for one of the ways:
Step 1: Identify the OS PID
========
Using Glance or ps identify the OS PID of the process.
E.g.
=============================
B3692A GlancePlus
--------------------------------------------------------------------------------
CPU Util SSU U | 17% 49% 100%
Disk Util F F | 10% 46% 100%
Mem Util S SU UB B | 68% 68% 71%
Swap Util U UR R | 18% 18% 19%
--------------------------------------------------------------------------------
PROCESS LIST Users= 1
User CPU Util Cum Disk Thd
Process Name PID PPID Pri Name ( 100% max) CPU IO Rate RSS Cnt
--------------------------------------------------------------------------------
oracleyddb 5513 1 154 ora817 5.9/ 0.3 1.7 22.3/ 0.4 4.8mb 1
=============================
Here =>> 5513
Step 2: Identify the Oracle Process (SID, Serial#)
=======
select b.sid SID,b.serial# "Serial#", c.spid "srvPID", b.osuser, b.username, b.status, b.client_info
from v$session b, v$process c
where b.paddr = c.addr
and c.sPID = '5513';
Here: (212,6156)
Step 3: Trace the process
=======
exec sys.dbms_system.set_sql_trace_in_session(212,6156,TRUE);
Step 4: Identify the log being generated.
========
../app/oracle/admin/pfs/udump
e.g. ora_29291_yddb.trc
Step 5: After some time
=======
exec sys.dbms_system.set_sql_trace_in_session(212,6156,FALSE);
[this will stop the trace of the session]
Step 6: Convert the trace file into a more readable form
=======
tkprof ora_29291_yddb.trc yddb.txt
Step 7: Analyse the yddb.txt
=======
This will allow you to identify the process.
Good luck!
If you need any further clarification, please let us know.
Regards
Yogeeraj
Below are the steps for one of the ways:
Step 1: Identify the OS PID
========
Using Glance or ps identify the OS PID of the process.
E.g.
=============================
B3692A GlancePlus
--------------------------------------------------------------------------------
CPU Util SSU U | 17% 49% 100%
Disk Util F F | 10% 46% 100%
Mem Util S SU UB B | 68% 68% 71%
Swap Util U UR R | 18% 18% 19%
--------------------------------------------------------------------------------
PROCESS LIST Users= 1
User CPU Util Cum Disk Thd
Process Name PID PPID Pri Name ( 100% max) CPU IO Rate RSS Cnt
--------------------------------------------------------------------------------
oracleyddb 5513 1 154 ora817 5.9/ 0.3 1.7 22.3/ 0.4 4.8mb 1
=============================
Here =>> 5513
Step 2: Identify the Oracle Process (SID, Serial#)
=======
select b.sid SID,b.serial# "Serial#", c.spid "srvPID", b.osuser, b.username, b.status, b.client_info
from v$session b, v$process c
where b.paddr = c.addr
and c.sPID = '5513';
Here: (212,6156)
Step 3: Trace the process
=======
exec sys.dbms_system.set_sql_trace_in_session(212,6156,TRUE);
Step 4: Identify the log being generated.
========
../app/oracle/admin/pfs/udump
e.g. ora_29291_yddb.trc
Step 5: After some time
=======
exec sys.dbms_system.set_sql_trace_in_session(212,6156,FALSE);
[this will stop the trace of the session]
Step 6: Convert the trace file into a more readable form
=======
tkprof ora_29291_yddb.trc yddb.txt
Step 7: Analyse the yddb.txt
=======
This will allow you to identify the process.
Good luck!
If you need any further clarification, please let us know.
Regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP