| Author |
Message |
Kerrie
Guest
|
 Posted:
Thu Jan 13, 2005 5:03 am Post subject:
Alert on Transaction Log space for OnePoint database |
|
|
I continue to get an alert for the Transaction Log space for OnePoint, that
it is less than the Warning threshold of 150 MB of free space. (It has
82.29MB of space)
This alert is as created by Script SQL Server 2000 Space Analysis.
I have gone to the SQL Management Pack, found the rule (Microsoft SQL
Server\SQL Server 2000\State Monitoring and Service Discovery\Event
Rules\SQL Server Space Analysis), and edited it to change the All other
transaction logs warning threshold value to 70., and the All other
transaction logs error threshold to 50.
I saved my changes, committed the configuration change, and yet even after
the 5 minute recycling period, I continued to get the alert (which reoccurs
every 15 minutes per the timing in the rule).
I then disabled the rule, and commited the configuration change. ... and I
still get the alert.
I have looked all through the management pack and I don't see another rule
that would seem to be generating these results.
I have created some custom rules in other management groups, and they do
behave as expected, so I don't think its a matter of configuration /
installation of the Management Server.
Your thoughts would be greatly appreciated! |
|
| Back to top |
|
 |
Murugesan Vivekananthan [
Guest
|
| Posted:
Thu Jan 13, 2005 11:08 pm Post subject:
Re: Alert on Transaction Log space for OnePoint database |
|
|
For reproduce the issue:
Can you give the details of the alert? [You can copy and paste the alert
from the details pane]
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------
"Kerrie" <kerrieL@comcast.net> wrote in message
news:%23XZFhrP%23EHA.3376@TK2MSFTNGP12.phx.gbl...
| Quote: | I continue to get an alert for the Transaction Log space for OnePoint, that
it is less than the Warning threshold of 150 MB of free space. (It has
82.29MB of space)
This alert is as created by Script SQL Server 2000 Space Analysis.
I have gone to the SQL Management Pack, found the rule (Microsoft SQL
Server\SQL Server 2000\State Monitoring and Service Discovery\Event
Rules\SQL Server Space Analysis), and edited it to change the All other
transaction logs warning threshold value to 70., and the All other
transaction logs error threshold to 50.
I saved my changes, committed the configuration change, and yet even after
the 5 minute recycling period, I continued to get the alert (which
reoccurs every 15 minutes per the timing in the rule).
I then disabled the rule, and commited the configuration change. ... and I
still get the alert.
I have looked all through the management pack and I don't see another rule
that would seem to be generating these results.
I have created some custom rules in other management groups, and they do
behave as expected, so I don't think its a matter of configuration /
installation of the Management Server.
Your thoughts would be greatly appreciated!
|
|
|
| Back to top |
|
|
Kerrie
Guest
|
| Posted:
Fri Jan 14, 2005 2:01 am Post subject:
Re: Alert on Transaction Log space for OnePoint database |
|
|
Description:
Transaction Log space for "OnePoint" in instance "MSSQLSERVER" has less than
the Warning threshold of 150MB free space. The transaction log currently has
82.29MB free space. It is recommended database files for a transaction log
have more than 150MB of free space, taking into account growth potential.
Name: SQL Server Log Space
Severity: Warning
Resolution State: New
Domain: DEMO
Computer: MONARCH
Time of First Event: 1/12/2005 4:12:16 PM
Time of Last Event: 1/13/2005 1:57:00 PM
Alert latency: 0 sec
Problem State: Active
Repeat Count: 68
Age:
Source: SQL Server 2000 Space Analysis:MSSQLSERVER:Log(OnePoint)
Alert Id: 6976f522-17b6-407c-97f7-696bb4d595e4
Rule (disabled): Microsoft SQL Server\SQL Server 2000\State Monitoring and
Service Discovery\SQL Server Space Analysis
Note that the rule is disagled (!) but the alert still fires.
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:u7XzPKZ%23EHA.1076@TK2MSFTNGP10.phx.gbl...
| Quote: | For reproduce the issue:
Can you give the details of the alert? [You can copy and paste the alert
from the details pane]
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Kerrie" <kerrieL@comcast.net> wrote in message
news:%23XZFhrP%23EHA.3376@TK2MSFTNGP12.phx.gbl...
I continue to get an alert for the Transaction Log space for OnePoint,
that it is less than the Warning threshold of 150 MB of free space. (It
has 82.29MB of space)
This alert is as created by Script SQL Server 2000 Space Analysis.
I have gone to the SQL Management Pack, found the rule (Microsoft SQL
Server\SQL Server 2000\State Monitoring and Service Discovery\Event
Rules\SQL Server Space Analysis), and edited it to change the All other
transaction logs warning threshold value to 70., and the All other
transaction logs error threshold to 50.
I saved my changes, committed the configuration change, and yet even
after the 5 minute recycling period, I continued to get the alert (which
reoccurs every 15 minutes per the timing in the rule).
I then disabled the rule, and commited the configuration change. ... and
I still get the alert.
I have looked all through the management pack and I don't see another
rule that would seem to be generating these results.
I have created some custom rules in other management groups, and they do
behave as expected, so I don't think its a matter of configuration /
installation of the Management Server.
Your thoughts would be greatly appreciated!
|
|
|
| Back to top |
|
|
burnsy
Guest
|
| Posted:
Tue Jan 18, 2005 2:09 am Post subject:
Re: Alert on Transaction Log space for OnePoint database |
|
|
I am experiencing the exact same issue - reduced my threshold and still
receive the alert.....though this is not for the onepoint DB, but for a
Blackberry DB....have you made any headway with this issue?
"Kerrie" wrote:
| Quote: | Description:
Transaction Log space for "OnePoint" in instance "MSSQLSERVER" has less than
the Warning threshold of 150MB free space. The transaction log currently has
82.29MB free space. It is recommended database files for a transaction log
have more than 150MB of free space, taking into account growth potential.
Name: SQL Server Log Space
Severity: Warning
Resolution State: New
Domain: DEMO
Computer: MONARCH
Time of First Event: 1/12/2005 4:12:16 PM
Time of Last Event: 1/13/2005 1:57:00 PM
Alert latency: 0 sec
Problem State: Active
Repeat Count: 68
Age:
Source: SQL Server 2000 Space Analysis:MSSQLSERVER:Log(OnePoint)
Alert Id: 6976f522-17b6-407c-97f7-696bb4d595e4
Rule (disabled): Microsoft SQL Server\SQL Server 2000\State Monitoring and
Service Discovery\SQL Server Space Analysis
Note that the rule is disagled (!) but the alert still fires.
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:u7XzPKZ%23EHA.1076@TK2MSFTNGP10.phx.gbl...
For reproduce the issue:
Can you give the details of the alert? [You can copy and paste the alert
from the details pane]
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Kerrie" <kerrieL@comcast.net> wrote in message
news:%23XZFhrP%23EHA.3376@TK2MSFTNGP12.phx.gbl...
I continue to get an alert for the Transaction Log space for OnePoint,
that it is less than the Warning threshold of 150 MB of free space. (It
has 82.29MB of space)
This alert is as created by Script SQL Server 2000 Space Analysis.
I have gone to the SQL Management Pack, found the rule (Microsoft SQL
Server\SQL Server 2000\State Monitoring and Service Discovery\Event
Rules\SQL Server Space Analysis), and edited it to change the All other
transaction logs warning threshold value to 70., and the All other
transaction logs error threshold to 50.
I saved my changes, committed the configuration change, and yet even
after the 5 minute recycling period, I continued to get the alert (which
reoccurs every 15 minutes per the timing in the rule).
I then disabled the rule, and commited the configuration change. ... and
I still get the alert.
I have looked all through the management pack and I don't see another
rule that would seem to be generating these results.
I have created some custom rules in other management groups, and they do
behave as expected, so I don't think its a matter of configuration /
installation of the Management Server.
Your thoughts would be greatly appreciated!
|
|
|
| Back to top |
|
|
Kerrie
Guest
|
| Posted:
Wed Jan 19, 2005 6:48 am Post subject:
Re: Alert on Transaction Log space for OnePoint database |
|
|
No updates - was hoping to hear something back from the MSFT Test team, but
nothing yet.
"burnsy" <burnsy@discussions.microsoft.com> wrote in message
news:F12B7EA1-5589-40BD-BC72-70B163ACD06E@microsoft.com...
| Quote: | I am experiencing the exact same issue - reduced my threshold and still
receive the alert.....though this is not for the onepoint DB, but for a
Blackberry DB....have you made any headway with this issue?
"Kerrie" wrote:
Description:
Transaction Log space for "OnePoint" in instance "MSSQLSERVER" has less
than
the Warning threshold of 150MB free space. The transaction log currently
has
82.29MB free space. It is recommended database files for a transaction
log
have more than 150MB of free space, taking into account growth potential.
Name: SQL Server Log Space
Severity: Warning
Resolution State: New
Domain: DEMO
Computer: MONARCH
Time of First Event: 1/12/2005 4:12:16 PM
Time of Last Event: 1/13/2005 1:57:00 PM
Alert latency: 0 sec
Problem State: Active
Repeat Count: 68
Age:
Source: SQL Server 2000 Space Analysis:MSSQLSERVER:Log(OnePoint)
Alert Id: 6976f522-17b6-407c-97f7-696bb4d595e4
Rule (disabled): Microsoft SQL Server\SQL Server 2000\State Monitoring
and
Service Discovery\SQL Server Space Analysis
Note that the rule is disagled (!) but the alert still fires.
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:u7XzPKZ%23EHA.1076@TK2MSFTNGP10.phx.gbl...
For reproduce the issue:
Can you give the details of the alert? [You can copy and paste the
alert
from the details pane]
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Kerrie" <kerrieL@comcast.net> wrote in message
news:%23XZFhrP%23EHA.3376@TK2MSFTNGP12.phx.gbl...
I continue to get an alert for the Transaction Log space for OnePoint,
that it is less than the Warning threshold of 150 MB of free space. (It
has 82.29MB of space)
This alert is as created by Script SQL Server 2000 Space Analysis.
I have gone to the SQL Management Pack, found the rule (Microsoft SQL
Server\SQL Server 2000\State Monitoring and Service Discovery\Event
Rules\SQL Server Space Analysis), and edited it to change the All
other
transaction logs warning threshold value to 70., and the All other
transaction logs error threshold to 50.
I saved my changes, committed the configuration change, and yet even
after the 5 minute recycling period, I continued to get the alert
(which
reoccurs every 15 minutes per the timing in the rule).
I then disabled the rule, and commited the configuration change. ...
and
I still get the alert.
I have looked all through the management pack and I don't see another
rule that would seem to be generating these results.
I have created some custom rules in other management groups, and they
do
behave as expected, so I don't think its a matter of configuration /
installation of the Management Server.
Your thoughts would be greatly appreciated!
|
|
|
| Back to top |
|
|
Murugesan Vivekananthan [
Guest
|
| Posted:
Wed Jan 19, 2005 11:41 pm Post subject:
Re: Alert on Transaction Log space for OnePoint database |
|
|
I'm working on the isssue and I'll update the newsgroups once I have the
answer.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------
"Kerrie" <kerrieL@comcast.net> wrote in message
news:eIh8eKe$EHA.1408@TK2MSFTNGP10.phx.gbl...
| Quote: | No updates - was hoping to hear something back from the MSFT Test team,
but nothing yet.
"burnsy" <burnsy@discussions.microsoft.com> wrote in message
news:F12B7EA1-5589-40BD-BC72-70B163ACD06E@microsoft.com...
I am experiencing the exact same issue - reduced my threshold and still
receive the alert.....though this is not for the onepoint DB, but for a
Blackberry DB....have you made any headway with this issue?
"Kerrie" wrote:
Description:
Transaction Log space for "OnePoint" in instance "MSSQLSERVER" has less
than
the Warning threshold of 150MB free space. The transaction log currently
has
82.29MB free space. It is recommended database files for a transaction
log
have more than 150MB of free space, taking into account growth
potential.
Name: SQL Server Log Space
Severity: Warning
Resolution State: New
Domain: DEMO
Computer: MONARCH
Time of First Event: 1/12/2005 4:12:16 PM
Time of Last Event: 1/13/2005 1:57:00 PM
Alert latency: 0 sec
Problem State: Active
Repeat Count: 68
Age:
Source: SQL Server 2000 Space Analysis:MSSQLSERVER:Log(OnePoint)
Alert Id: 6976f522-17b6-407c-97f7-696bb4d595e4
Rule (disabled): Microsoft SQL Server\SQL Server 2000\State Monitoring
and
Service Discovery\SQL Server Space Analysis
Note that the rule is disagled (!) but the alert still fires.
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:u7XzPKZ%23EHA.1076@TK2MSFTNGP10.phx.gbl...
For reproduce the issue:
Can you give the details of the alert? [You can copy and paste the
alert
from the details pane]
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Kerrie" <kerrieL@comcast.net> wrote in message
news:%23XZFhrP%23EHA.3376@TK2MSFTNGP12.phx.gbl...
I continue to get an alert for the Transaction Log space for OnePoint,
that it is less than the Warning threshold of 150 MB of free space.
(It
has 82.29MB of space)
This alert is as created by Script SQL Server 2000 Space Analysis.
I have gone to the SQL Management Pack, found the rule (Microsoft SQL
Server\SQL Server 2000\State Monitoring and Service Discovery\Event
Rules\SQL Server Space Analysis), and edited it to change the All
other
transaction logs warning threshold value to 70., and the All other
transaction logs error threshold to 50.
I saved my changes, committed the configuration change, and yet even
after the 5 minute recycling period, I continued to get the alert
(which
reoccurs every 15 minutes per the timing in the rule).
I then disabled the rule, and commited the configuration change. ...
and
I still get the alert.
I have looked all through the management pack and I don't see another
rule that would seem to be generating these results.
I have created some custom rules in other management groups, and they
do
behave as expected, so I don't think its a matter of configuration /
installation of the Management Server.
Your thoughts would be greatly appreciated!
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in