September 22, 2013 at 7:17 pm
Hi all,
A new database was created on our existing single instance Sql Server 2012 Enterprise .
Our over night maintenance job to backup the database failed with the following error from this new database:
Msg 8152, Level 16, State 13, Line 1
String or binary data would be truncated.
Msg 3009, Level 16, State 1, Line 1
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
-I have verified that MSDB is not corrupted via dbcc checkdb with 0 errors
-Space is not an issue on any database as all files are set to auto grow and this is a new server with plenty of disk.
-Since the db was created the maint job has failed on this specific db, but I have not tried to drop/recreate this new database. (trying to avoid drop/create)
-I've tried restoring msdb from an older backup from before the db create, but backup still errors out. (never had a successful backup since new db created)
(One thing I've noticed since this is a sharepoint database, the name is 97 chars long, however as a test I created another test db with a longer name than this one and backup worked fine)
I've searched online and the forums here with old entries and no luck.
Am I missing any other possible solutions?
Thanks in advance!
September 23, 2013 at 12:20 am
check for names containing this large db-name
which might be too long for columns in
msdb.dbo.backup... tables.
i.e.: logical_name, physical_drive, physical_name etc.
September 23, 2013 at 12:56 am
Hi,
Cheers for your reply,
I found that it was not the full path of the "physical_name" column of msdb.dbo.backupfile because that had used only 181 of max 260 chars,
but rather it was the "NAME" portion of the backup statement which exceeded 128 chars.
Once I edited it within 128, then the backup statement worked.
Thank you for pointing me in the right direction.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply