dbcc errorlog fails

I have ran the sp_cycle_errorlog and dbcc errorlog command on a SQL 200
Datacenter cluster. The logs for .2 through .6 change. However, the
origional errorlog does not. I do not get a new error log started. I do not
want to stop and start the sql server as this would shutdown production. Has
anyone seen this and how should I go about fixing this?
Thanks for you support.
--
Rick SchantzHow are you determining that the log hasn't changed? If you
are viewing the logs in Enterprise Manager, did you refresh
the view? Are you viewing the files in Explorer and
expecting a new file? The logs are cycled rather than new
files being created.
What happens if you execute sp_cycle_errorlog a few times?
If you are sure data from errorlog isn't moving to
errorlog.1, you could check for locking on the log files by
some other process.
-Sue
On Mon, 4 Oct 2004 12:13:03 -0700, Rick Schantz
<RickSchantz@.discussions.microsoft.com> wrote:
>I have ran the sp_cycle_errorlog and dbcc errorlog command on a SQL 200
>Datacenter cluster. The logs for .2 through .6 change. However, the
>origional errorlog does not. I do not get a new error log started. I do not
>want to stop and start the sql server as this would shutdown production. Has
>anyone seen this and how should I go about fixing this?
>Thanks for you support.|||I tested the command on another server. The log size for errorlog. went to
errorlog.1 and so on while a new errorlog. was created. Errorlog.6 was
deleted. I executed sp_cycle_error a few times and .2 and .3 are missing. .4
and .5 still exist. .6 never existed. All of this was viewed by Enterpise
Manager and I was refreshing it several times. I did not look for locking on
the errorlog. file. What process would be locking the errorlog file? Our
goal is to cycle the logs on a weekly basis and archive the oldest one. Any
suggestions? Thanks for your fast response.
"Sue Hoegemeier" wrote:
> How are you determining that the log hasn't changed? If you
> are viewing the logs in Enterprise Manager, did you refresh
> the view? Are you viewing the files in Explorer and
> expecting a new file? The logs are cycled rather than new
> files being created.
> What happens if you execute sp_cycle_errorlog a few times?
> If you are sure data from errorlog isn't moving to
> errorlog.1, you could check for locking on the log files by
> some other process.
> -Sue
> On Mon, 4 Oct 2004 12:13:03 -0700, Rick Schantz
> <RickSchantz@.discussions.microsoft.com> wrote:
> >I have ran the sp_cycle_errorlog and dbcc errorlog command on a SQL 200
> >Datacenter cluster. The logs for .2 through .6 change. However, the
> >origional errorlog does not. I do not get a new error log started. I do not
> >want to stop and start the sql server as this would shutdown production. Has
> >anyone seen this and how should I go about fixing this?
> >
> >Thanks for you support.
>|||Backup or antivirus software would be a couple of programs that could
lock a file. You can check for this using filemon from sysinternals:
http://www.sysinternals.com/
Once you figure out whatever the problem is with cycling the logs, it
should be pretty easy to set up a job to archive. You can just save .6
file off somewhere using an ActiveX script and FSO or DOS commands and
a CmdExec step and then run sp_cycle_errorlog.
-Sue
On Tue, 5 Oct 2004 07:03:06 -0700, Rick Schantz
<RickSchantz@.discussions.microsoft.com> wrote:
>I tested the command on another server. The log size for errorlog. went to
>errorlog.1 and so on while a new errorlog. was created. Errorlog.6 was
>deleted. I executed sp_cycle_error a few times and .2 and .3 are missing. .4
>and .5 still exist. .6 never existed. All of this was viewed by Enterpise
>Manager and I was refreshing it several times. I did not look for locking on
>the errorlog. file. What process would be locking the errorlog file? Our
>goal is to cycle the logs on a weekly basis and archive the oldest one. Any
>suggestions? Thanks for your fast response.
>"Sue Hoegemeier" wrote:
>> How are you determining that the log hasn't changed? If you
>> are viewing the logs in Enterprise Manager, did you refresh
>> the view? Are you viewing the files in Explorer and
>> expecting a new file? The logs are cycled rather than new
>> files being created.
>> What happens if you execute sp_cycle_errorlog a few times?
>> If you are sure data from errorlog isn't moving to
>> errorlog.1, you could check for locking on the log files by
>> some other process.
>> -Sue
>> On Mon, 4 Oct 2004 12:13:03 -0700, Rick Schantz
>> <RickSchantz@.discussions.microsoft.com> wrote:
>> >I have ran the sp_cycle_errorlog and dbcc errorlog command on a SQL 200
>> >Datacenter cluster. The logs for .2 through .6 change. However, the
>> >origional errorlog does not. I do not get a new error log started. I do not
>> >want to stop and start the sql server as this would shutdown production. Has
>> >anyone seen this and how should I go about fixing this?
>> >
>> >Thanks for you support.
>>|||I renamed the file errorlog.6 and then ran the EXEC sp_cycle_errorlog
command. The errorlog.5 went to errorlog.6 and errorlog. when to errorlog.1.
A new errorlog. was created. Not sure what was going on but I'll monitor it
from here. I also used the filemon tool. Great tool.
Thanks
"Sue Hoegemeier" wrote:
> Backup or antivirus software would be a couple of programs that could
> lock a file. You can check for this using filemon from sysinternals:
> http://www.sysinternals.com/
> Once you figure out whatever the problem is with cycling the logs, it
> should be pretty easy to set up a job to archive. You can just save .6
> file off somewhere using an ActiveX script and FSO or DOS commands and
> a CmdExec step and then run sp_cycle_errorlog.
> -Sue
> On Tue, 5 Oct 2004 07:03:06 -0700, Rick Schantz
> <RickSchantz@.discussions.microsoft.com> wrote:
> >I tested the command on another server. The log size for errorlog. went to
> >errorlog.1 and so on while a new errorlog. was created. Errorlog.6 was
> >deleted. I executed sp_cycle_error a few times and .2 and .3 are missing. .4
> >and .5 still exist. .6 never existed. All of this was viewed by Enterpise
> >Manager and I was refreshing it several times. I did not look for locking on
> >the errorlog. file. What process would be locking the errorlog file? Our
> >goal is to cycle the logs on a weekly basis and archive the oldest one. Any
> >suggestions? Thanks for your fast response.
> >
> >"Sue Hoegemeier" wrote:
> >
> >> How are you determining that the log hasn't changed? If you
> >> are viewing the logs in Enterprise Manager, did you refresh
> >> the view? Are you viewing the files in Explorer and
> >> expecting a new file? The logs are cycled rather than new
> >> files being created.
> >> What happens if you execute sp_cycle_errorlog a few times?
> >> If you are sure data from errorlog isn't moving to
> >> errorlog.1, you could check for locking on the log files by
> >> some other process.
> >>
> >> -Sue
> >>
> >> On Mon, 4 Oct 2004 12:13:03 -0700, Rick Schantz
> >> <RickSchantz@.discussions.microsoft.com> wrote:
> >>
> >> >I have ran the sp_cycle_errorlog and dbcc errorlog command on a SQL 200
> >> >Datacenter cluster. The logs for .2 through .6 change. However, the
> >> >origional errorlog does not. I do not get a new error log started. I do not
> >> >want to stop and start the sql server as this would shutdown production. Has
> >> >anyone seen this and how should I go about fixing this?
> >> >
> >> >Thanks for you support.
> >>
> >>
>