HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- 2nd SQL Log on SIM server fills up
Server Management - Systems Insight Manager
1833594
Members
3893
Online
110061
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
10-31-2005 11:55 AM
10-31-2005 11:55 AM
2nd SQL Log on SIM server fills up
So I've got this SIM 4.2sp2 server with a SQL log file on the server that keeps filling up... None of the typical responses like setting the DB to simple, daily backups and autoshrinking enabled seems to be making any changes. This is not the typical SQL log on the remote SQL server, This seems to be more like a transaction log..but on the SIM server. when I delete it, the system recreates the log and starts fill it up again...
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2005 09:16 PM
10-31-2005 09:16 PM
Re: 2nd SQL Log on SIM server fills up
Ralph, what exactly name and full path of the file? Maybe name is not SQL.log as you wrote in http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=965481 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2005 09:25 PM
10-31-2005 09:25 PM
Re: 2nd SQL Log on SIM server fills up
Maybe you mean MX.log file - audit log of HPSIM?
If yes: see
"HP Systems Insight Manager 4.2 May Record Repeated Error Messages in MX.LOG if Custom Commands Run with the Run Now Button Then Deleted"
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080430635
You can also configure max size of this file
http://docs.hp.com/en/5991-0710/ch14s03.html
If yes: see
"HP Systems Insight Manager 4.2 May Record Repeated Error Messages in MX.LOG if Custom Commands Run with the Run Now Button Then Deleted"
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080430635
You can also configure max size of this file
http://docs.hp.com/en/5991-0710/ch14s03.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2005 07:39 AM
11-01-2005 07:39 AM
Re: 2nd SQL Log on SIM server fills up
SQL.Log ...This is why it's been so confusing to reponses... our SQL DB says there seems to be two files named SQL.log..one on the remote sql server that is doing exactly as predicted (grows, shrinks, etc).. but this SQL.log file on the SIM server doesn't correspond to any named transaction log in the SIM documentation. it just keeps growing....it's on a seperate drive name logs (we'll call it "L"). So this file is at the root of L.. another problem.. I don't know were it orginated or where it would have gone by default..
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