- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: DB disk IO problems - deathstar query
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
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
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
04-15-2014 06:33 AM
04-15-2014 06:33 AM
DB disk IO problems - deathstar query
Hi Forum,
Why is this query at the top of the leaderboard over most resource consuming tasks in my DB-server?
SELECT trapItems.trap_id, RTRIM(trap_name), enabled_flag, trapItems.sev_vb FROM trapItems,trapItemsEx WHERE trapItems.trap_id = trapItemsEx.trap_id AND trap_generic_id = @P0
It is since this thursday continuously generating 60-80MB/s in disk access, why o why is this happening?
Any ideas of how to kill this deathstar?
Best Regards,
Johannes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2014 11:50 PM
04-15-2014 11:50 PM
Re: DB disk IO problems - deathstar query
Hi,
as far as i can see, database file I/O more then trippled since last thursday. We have not added the tripple amount of objects and actually done no additional configurations at all.
I can see that the query executes is as intended, but what is strange is the disk I/O. Is there any way to make this deathstar query happen less often? The SIM DB is now our top contender on this particular storage array which is odd since it more or less does nothing except for monitoring hardware alerts.
Best Regards,
Johannes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2014 04:28 AM
04-16-2014 04:28 AM
Re: DB disk IO problems - deathstar query
Aight,
restarting any and all SIM services did the trick and IO settled, as long as the services were turned off of course, as soon as SIM loaded its ray gun DB file I/O got aggressive again.
Actually restarting the SQL-service did the trick for definite. I have looked through at what could have got stuck but found absolutely nothing.
BR,
Johannes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2014 12:09 AM
06-24-2014 12:09 AM
Re: DB disk IO problems - deathstar query
This obnixious behaviour keeps coming back over and over again, this is really really bad for my SAN.
Any ideas?
BR,
johannes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2014 12:54 AM
06-24-2014 12:54 AM
Re: DB disk IO problems - deathstar query
Hello,
Did you set the Database logging to simple ? If it is set to Full the logfiles tend to explode. An other thing could be that you get a lot of events. The combination is lethal.
I've seen the SIM server using the full 100Mb link to the SQL server. You could also do a database check in the comamdnline on the SIM server type MXCONFIGREPO -c. for a database check. If you see corruption use the -f option to fix your database errors.
Kind regards,
Andrew
Andrew