- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ora_smon
Operating System - HP-UX
1752808
Members
6178
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
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
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
тАО06-09-2005 08:50 PM
тАО06-09-2005 08:50 PM
ora_smon
Hi
When I tried to startup the db crash due ora_smon takes 100% cpu, what happened? the error is ora-00600
Thanks
Bye
Diego
When I tried to startup the db crash due ora_smon takes 100% cpu, what happened? the error is ora-00600
Thanks
Bye
Diego
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 09:44 PM
тАО06-09-2005 09:44 PM
Re: ora_smon
... You're probably facing a bug. ORA-00600 and ORA-07445 is usually a way Oracle tells you it doesn't know what happens.
You should have a look at your alert.log file to get more info. This can be found in the background_dump_dest directory (specified in init/spfile configuration file, available in $ORACLE_HOME/dbs). It may point you to log files in user_dump_dest.
What is your Oracle version ? It may be a good choice to go to a better patche version.
If traces are not explicit enough and you are in latest patchset version, you'll have to log a TAR in Oracle's Metalink.
Regards,
Fred
You should have a look at your alert.log file to get more info. This can be found in the background_dump_dest directory (specified in init/spfile configuration file, available in $ORACLE_HOME/dbs). It may point you to log files in user_dump_dest.
What is your Oracle version ? It may be a good choice to go to a better patche version.
If traces are not explicit enough and you are in latest patchset version, you'll have to log a TAR in Oracle's Metalink.
Regards,
Fred
--
"Reality is just a point of view." (P. K. D.)
"Reality is just a point of view." (P. K. D.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2005 11:09 PM
тАО06-09-2005 11:09 PM
Re: ora_smon
hi diego,
can you post more details about:
a. Version
b. Error message as indicated in the alert_.log
thanks
yogeeraj
can you post more details about:
a. Version
b. Error message as indicated in the alert_
thanks
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2005 05:03 AM
тАО06-10-2005 05:03 AM
Re: ora_smon
Some more things to consider:
1. after a restart on some oracle versions, the first thing SMON does is clean up the temp segments. If you TEMP tablespace(s) are improperly configured (i.e. extents are too small) then this can take a while.
2. Slow disks. We've had situations here before where the redo logs and control file were on slow disks and everything in the database was slow, including the TEMP rewrite as above.
I had that situation before, and it caused SMON to take 100%, but the database here just got slow, it didn't crash. May not apply here, but with what you've said, it sounds familiar.
1. after a restart on some oracle versions, the first thing SMON does is clean up the temp segments. If you TEMP tablespace(s) are improperly configured (i.e. extents are too small) then this can take a while.
2. Slow disks. We've had situations here before where the redo logs and control file were on slow disks and everything in the database was slow, including the TEMP rewrite as above.
I had that situation before, and it caused SMON to take 100%, but the database here just got slow, it didn't crash. May not apply here, but with what you've said, it sounds familiar.
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