HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Cleaning HP SIM database for a fresh start?
Server Management - Systems Insight Manager
1833785
Members
2306
Online
110063
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
Forums
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
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
01-03-2006 08:53 PM
01-03-2006 08:53 PM
Cleaning HP SIM database for a fresh start?
I've been having strange problems with HP SIM ever since the temp db completely filled the C: disk on our server, I described those problems in a different thread a while ago.
Even after I moved the tempdb to a disk with more than plenty of diskspace, this problem persisted.
So I'm kind of pondering what to do now, would it be best to start fresh again? And if so, how would I do that?
I couldn't find any information about this so far.
Or is it possible to purge all information about, let's say all the Windows servers?
Any help would be appreciated.
Even after I moved the tempdb to a disk with more than plenty of diskspace, this problem persisted.
So I'm kind of pondering what to do now, would it be best to start fresh again? And if so, how would I do that?
I couldn't find any information about this so far.
Or is it possible to purge all information about, let's say all the Windows servers?
Any help would be appreciated.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2006 10:25 PM
01-03-2006 10:25 PM
Re: Cleaning HP SIM database for a fresh start?
To start fresh you can just uninstall HPSIM and install it as new installation, it will create fresh DB.
But before doing it: Did you try to set "tempdb" Recovery mode to simple ?
http://support.microsoft.com/kb/873235/en-us
Even if you reinstall HPSIM your "tempdb" will be filled if you use "Full" recovery mode and don't do regular transaction log backup.
But before doing it: Did you try to set "tempdb" Recovery mode to simple ?
http://support.microsoft.com/kb/873235/en-us
Even if you reinstall HPSIM your "tempdb" will be filled if you use "Full" recovery mode and don't do regular transaction log backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2006 10:45 PM
01-03-2006 10:45 PM
Re: Cleaning HP SIM database for a fresh start?
Thank you for the reply.
The database has indeed been set to simple recovery mode, but the problem with the orphaned entries still exists.
Even after I deleted those servers (I even manually removed all remaining references to these servers from the database) and added them again, they became orphans the next day.
I think that the database somehow got (partially) corrupted when the tempdb logfile filled the entire harddisk. Nothing could be written to the database anymore.
The database has indeed been set to simple recovery mode, but the problem with the orphaned entries still exists.
Even after I deleted those servers (I even manually removed all remaining references to these servers from the database) and added them again, they became orphans the next day.
I think that the database somehow got (partially) corrupted when the tempdb logfile filled the entire harddisk. Nothing could be written to the database anymore.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP