6.5 master database syslogs full

I inherited an application (or two) that run on SQL Server 6.5, which I
haven't used in years, and am having a problem. I get the error:
---
Can't allocate space for object 'Syslogs' in database 'master' because
the 'logsegment' segment is full. If you ran out of space in Syslogs,
dump the transaction log. Otherwise, use ALTER DATABASE or
sp_extendsegment to increase the size of the segment.
---
...when I... well... just about everything. If I try:
DUMP TRAN master WITH NO_LOG
...I get:
---
Can't allocate space for object 'Syslogs' in database 'master' because
the 'logsegment' segment is full. If you ran out of space in Syslogs,
dump the transaction log. Otherwise, use ALTER DATABASE or
sp_extendsegment to increase the size of the segment.
Unable to write CHECKPOINT record in database 1 because the log is out
of space.
Unable to continue logged version of DUMP TRANsaction. Please free up
some space in database 1 or use the NO_LOG option.
---
...If I try to expand the device or database, I get the "Can't allocate
space..." error. If I use "DBCC UPDATEUSAGE(0)" I get nothing, "DBCC
CHECKTABLE(syslogs)" tells me it's using one page and has 29 rows
(which is what I get if I "SELECT * FROM syslogs").
How can I expand the space available to the master database or
otherwise resolve this problem?
Thanks in advance for any help anyone can offer. I know there probably
aren't many of you still using 6.5.
Regards,
BrianHave you also tried:
DUMP TRAN master WITH TRUNCATE_ONLY
Also, consider just creating a new device and extend the log onto it.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
<brian.j.parker@.gmail.com> wrote in message
news:1156254945.725458.60220@.b28g2000cwb.googlegroups.com...
I inherited an application (or two) that run on SQL Server 6.5, which I
haven't used in years, and am having a problem. I get the error:
---
Can't allocate space for object 'Syslogs' in database 'master' because
the 'logsegment' segment is full. If you ran out of space in Syslogs,
dump the transaction log. Otherwise, use ALTER DATABASE or
sp_extendsegment to increase the size of the segment.
---
...when I... well... just about everything. If I try:
DUMP TRAN master WITH NO_LOG
...I get:
---
Can't allocate space for object 'Syslogs' in database 'master' because
the 'logsegment' segment is full. If you ran out of space in Syslogs,
dump the transaction log. Otherwise, use ALTER DATABASE or
sp_extendsegment to increase the size of the segment.
Unable to write CHECKPOINT record in database 1 because the log is out
of space.
Unable to continue logged version of DUMP TRANsaction. Please free up
some space in database 1 or use the NO_LOG option.
---
...If I try to expand the device or database, I get the "Can't allocate
space..." error. If I use "DBCC UPDATEUSAGE(0)" I get nothing, "DBCC
CHECKTABLE(syslogs)" tells me it's using one page and has 29 rows
(which is what I get if I "SELECT * FROM syslogs").
How can I expand the space available to the master database or
otherwise resolve this problem?
Thanks in advance for any help anyone can offer. I know there probably
aren't many of you still using 6.5.
Regards,
Brian|||Tom Moreau wrote:
> Have you also tried:
> DUMP TRAN master WITH TRUNCATE_ONLY
> Also, consider just creating a new device and extend the log onto it.
Thank you, Tom, for replying.
Using "DUMP TRAN master" with any combination of NO_LOG and/or TRUNCATE
ONLY gives me the error "Can't allocate space for object 'Syslogs' in
database 'master' because the 'logsegment' segment is full..."
Trying to create a new device in Enterprise Manager or by using "DISK
INIT" either hangs or returns the same error.
Very frustrating!... if I could just dump the log, it seems, I could
add plenty of space.|||Hmm. If possible, do a full backup of master. Also stop and start SQL
Server.
You may have to do a rebuild of master. I'd stop SQL Server, copy the
devices on which master resides to a safe place and then rebuild master.
Extend the master device. Start SQL Server in single-user mode and then
restore the backup.
Hopefully, I've got it right. It's been a very long time since I last used
6.5...
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
<brian.j.parker@.gmail.com> wrote in message
news:1156257305.897687.128200@.p79g2000cwp.googlegroups.com...
Tom Moreau wrote:
> Have you also tried:
> DUMP TRAN master WITH TRUNCATE_ONLY
> Also, consider just creating a new device and extend the log onto it.
Thank you, Tom, for replying.
Using "DUMP TRAN master" with any combination of NO_LOG and/or TRUNCATE
ONLY gives me the error "Can't allocate space for object 'Syslogs' in
database 'master' because the 'logsegment' segment is full..."
Trying to create a new device in Enterprise Manager or by using "DISK
INIT" either hangs or returns the same error.
Very frustrating!... if I could just dump the log, it seems, I could
add plenty of space.|||Thank you very much for your help and advice, Tom.
Tom Moreau wrote:
> Hmm. If possible, do a full backup of master. Also stop and start SQL
> Server.
I got the same error trying to do a full backup of master. With some
reluctance, I rebooted the server, and... the problem magically cleared
up. I could truncate the log, expand the devices and the database and
log, and go on from there (get a backup, etc).
Sorry to raise a ruckus about what turned out to be an easy problem,
but I'd wished not to reboot since it's an important (what isn't?)
application and I'd felt a little paranoid I wouldn't get the server
started again.
Of course it's now a renewed priority to see if we can move the
application on SQL Server 2000! That should be much easier to manage.
Cheers,
Brian|||Well, MS keeps support for n - 1 releases. Considering that this is n - 3,
it would be a good idea. Indeed, I don't believe there is now a direct
upgrade path from 6.5 to 2005. You'll likely have to upgrade via either of
the following paths:
1) 6.5 -> 7.0; 7.0 -> 2005
2) 6.5 -> 2000; 2000 -> 2005
If you have 2000 in house, you can upgrade that part now.
If it's an "important" app, it's also important to keep the RDBMS current.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
<brian.j.parker@.gmail.com> wrote in message
news:1156262141.064510.218430@.i42g2000cwa.googlegroups.com...
Thank you very much for your help and advice, Tom.
Tom Moreau wrote:
> Hmm. If possible, do a full backup of master. Also stop and start SQL
> Server.
I got the same error trying to do a full backup of master. With some
reluctance, I rebooted the server, and... the problem magically cleared
up. I could truncate the log, expand the devices and the database and
log, and go on from there (get a backup, etc).
Sorry to raise a ruckus about what turned out to be an easy problem,
but I'd wished not to reboot since it's an important (what isn't?)
application and I'd felt a little paranoid I wouldn't get the server
started again.
Of course it's now a renewed priority to see if we can move the
application on SQL Server 2000! That should be much easier to manage.
Cheers,
Brian|||(brian.j.parker@.gmail.com) writes:
> I got the same error trying to do a full backup of master. With some
> reluctance, I rebooted the server, and... the problem magically cleared
> up. I could truncate the log, expand the devices and the database and
> log, and go on from there (get a backup, etc).
Great to hear that it worked out.
BACKUP, DISK INIT etc must all fail in this situation. BACKUP will
always fail, since it wants to write to the log. DISK INIT could
work for a user database, but DISK INIT needs to write to a table
in guess which database.
I would expect NO_LOG to work, but may NO_LOG writes to master.
Oh, well, 6.5, itwasn't too bad in its days, but it is dated now.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx