Warning 167

• 
  It appears that the RedGate backups are actually working. However, they are being reported as failed. My suspicion is that the RedGate backup history is the culprit. Is it possible to clear the RedGate backup history for a single database?

  eilandd October 12, 2007 15:32

  - 0 +
• 
  SQL Backup uses the following query to retrieve the dabase size:
  
  SELECT SUM(size) size FROM [<database name>]..sysfiles
  
  Does running this command in Query Analyzer/SSMS raise any errors?
  
  Thanks.

  petey October 13, 2007 09:26

  - 0 +
• 
  Sorry for the delayed response.
  
  The query returns the appropriate results, no errors.

  eilandd October 22, 2007 06:41

  - 0 +
• 
  Could you pls run a test backup together with SQL Profiler and trace the sequence of commands leading up to the error? You can filter on the ApplicationName column with the value 'SQBCoreService.exe'. Try running the last few SELECT commands manually and check if the same error turns up.
  
  With regards to your earlier question, SQL Backup does not retrieve any data from its backup history database during a backup. If you want to clear this database, you can use the 'sqbdata' extended stored procedure e.g.
  

  EXEC master..sqbdata 'DELETE FROM backuplog WHERE backup_id IN (SELECT id FROM backuphistory WHERE dbname = ''pubs'')'
  
  EXEC master..sqbdata 'DELETE FROM backupfiles WHERE backup_id IN (SELECT id FROM backuphistory WHERE dbname = ''pubs'')'
  
  EXEC master..sqbdata 'DELETE FROM backuphistory WHERE dbname = ''pubs'''
  

  petey October 23, 2007 21:14

  - 0 +
• 
  Peter;
  
  Thanks for your reply. It seems that time has healed this issue. We are no longer receiving the 913 error.

  eilandd October 24, 2007 07:37

  - 0 +
• 
  I too am getting this error.
  
  11/12/2008 5:00:05 PM: Warning 167: Failed to get database size from server.
  11/12/2008 5:00:05 PM: SQL error 913: Could not find database ID 38. Database may not be activated yet or may be in transition.
  
  The backups are fine, but the warning is anoying. This started happening when the database was deleted and a new database with the same name was created. The database in question now has an ID of 35 not 38. So how do I fix this?
  
  BTW, I did run the script posted earlier to clear out the history, but the problem remains.
  
  EXEC master..sqbdata 'DELETE FROM backuplog WHERE backup_id IN (SELECT id FROM backuphistory WHERE dbname = ''MyDBName'')'
  
  EXEC master..sqbdata 'DELETE FROM backupfiles WHERE backup_id IN (SELECT id FROM backuphistory WHERE dbname = ''MyDBName'')'
  
  EXEC master..sqbdata 'DELETE FROM backuphistory WHERE dbname = ''MyDBName'''

  DonFerguson November 12, 2008 20:46

  - 0 +
• 
  Update:
  
  I just recycled the SQL Server service and now I no longer get the warning.
  
  For future reference, is there a better way?

  DonFerguson November 12, 2008 20:56

  - 0 +

Add comment

Please sign in to leave a comment.