Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

error 1105

Status
Not open for further replies.

ariking

MIS
Jul 9, 2003
4
US
Hi,

Below is the error I am getting...it recommend to dump the transaction log...we are running sql 6.5. not so familiar with 6.5, can you send step by step instruction. thanks.

-----------------------------------

Event Type: Error
Event Source: MSSQLServer
Event Category: (2)
Event ID: 17060
Date: 7/8/2003
Time: 4:25:31 AM
User: N/A
Computer: THUNDERBOLT
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Error : 1105, Severity: 17, State: 1, Can't allocate space for object 'sysbackuphistory' in database 'msdb' because the 'default' 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..
Data:
0000: 51 04 00 00 11 00 00 00 Q.......
0008: 0c 00 00 00 54 48 55 4e ....THUN
0010: 44 45 52 42 4f 4c 54 00 DERBOLT.
0018: 05 00 00 00 6d 73 64 62 ....msdb
0020: 00 .


 
This is from memory but as a start:- It may just be the backup history has grown large enough to fill the allocated space for the msdb. When I had this problem I found the easiest thing was just to delete the backup history. This procedure removes all history you could be more selective if needed.

With enterprise manger
Use server configure and change Allow Updates to 1

USE msdb
Delete from SysRestoreDetail
Delete from SysRestoreHistory
Delete from SysBackupDetail
Delete from SysBackupHistory

Change Allow Updates back to 0

 
OK, I was able to find section 1 which is "with entp mgr".
It is under Server\SQL Server\Configure\Configuration tab

I am confuse about section 2, which is "USE msdb".
Do I use Tool\SQL Query Tool to execute the 2nd section?

Thanks for the help.
 
Sorry Im doing this from memory (not always a good idea) - but yes use the sql query tool and type in the commands as listed and execute them.

The USE statement just sets the context to the required database, msdb in this case, where these tables reside (maybe check this first),

You could type DELETE FROM msdb..SysRestoreDetail
 
after executing the script, it give me the error below. ANy idea?

Thanks again.
===============================

Msg 1105, Level 17, State 2
Can't allocate space for object 'Syslogs' in database 'msdb' 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.
 
Just following up to see if anybody has a solution to the error I am getting above. How do I dump the transaction log? or can I issue the following command...

Delete from Syslogs

Thanks..
 
Use the BACKUP command:

USE mydatabase
BACKUP LOG mydatabase WITH TRUNCATE_ONLY

That will truncate your log without backing it up. Just replace mydatabase with your database name.

Do you use Enterprise Manager?

-SQLBill
 
I forgot to add....it appears to me that your log and maybe your database are not set to automatically increase in size. In Enterprise Manager you can right click on the database, select properties and then check the settings for the database and the transaction log files (at least in SQL Server 2000, not sure about 6.5).

Check out the Books OnLine for more information.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top