- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Oracle trace
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО10-13-2006 06:12 AM
тАО10-13-2006 06:12 AM
Oracle trace
I have two database processes [ LOCAL=NO ] on the production database server. lsof shows they are from the apps server. But the apps does not know what that is :( same reply from the DBAs. These processes are consuming 20 % of CPU each. They are running for last 3 days !!.
There is also a file in "bdump" directory called , ${ORACLE_SID}_ora_
Can I kill this processes ?.
Regards,
Kaps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 07:10 AM
тАО10-13-2006 07:10 AM
Re: Oracle trace
To see the underlying SQL statements for these processes, substitute your PIDs in the following statement:
SELECT sql_text
FROM v$sqlarea sa, v$session s, v$process p
WHERE sa.address = s.sql_address
AND s.paddr = p.addr
AND p.spid = '
"[LOCAL=NO]" means a process is not one of Oracle's background processes. Therefore, it should be safe to kill them. Just realize that this may cause unexpected results on your application server.
The preferred order for killing an Oracle process:
1) Close the session from the application server.
2) SQL> alter system kill session 'sid,serial#';
3) SQL> alter system kill session 'sid,serial#' immediate;
4) # kill
5) Usual kill switch progression (-1, -2, -3, -11, -9).
Trace files in bdump are commonplace, and may not be related to the issue at hand. These files are ASCII data.
PCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 07:29 AM
тАО10-13-2006 07:29 AM
Re: Oracle trace
Regards,
Kaps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 07:35 AM
тАО10-13-2006 07:35 AM
Re: Oracle trace
select s.process from v$session s, v$process p
where s.paddr = p.addr and p.spid =
you should get something like 1180:1023.
The first number in that pair should be the process ID on the app server. Go to that server and see what that process is. If it is a windows box use taskman or the following command:
tasklist -FI "PID eq 1180" (or whatever your pid is)
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 07:48 AM
тАО10-13-2006 07:48 AM
Re: Oracle trace
In general, trace files just happen. As long as their number is small and you review them regularly, you should be fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 07:51 AM
тАО10-13-2006 07:51 AM
Re: Oracle trace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2006 09:08 PM
тАО10-13-2006 09:08 PM
Re: Oracle trace
Allow me to add that in case, this happens too often you may wish to log a Service Request with Oracle.
The trace file will also allow you to identify the culprit user. If you query your alert.log, you can also get the exact Oralce error message.
hope this helps too!
kind regards
yogeeraj