SansSQL: maintenance jobs

Thursday, November 8, 2012

Problem with SQL Server 2005 Maintenance Plan

Few days ago, one of my friend was facing an issue while creating Maintenance Plan in SQL Server 2005. When he was trying to create a Maintenance Plan, he was getting a message which says "Invalid column name 'from_msx'" and "Invalid column name 'has_targets'"


When we were trying to find out what might have caused this issues, we came to know that SP3 was recently applied to this instance.
This kind of errors usually pop up when the upgrades might have not completed properly.
Also in every service pack or hot fixes there will be a lot of changes like addition of tables and columns will be included for supporting the bug fixes or enhancements and if these are not applied properly to the database then you will get many similar errors.

To fix this particular issue, you have to execute the script "sysdbupg.sql" which will be present in the installation location  <Drive>:\Program Files\Microsoft SQL Server\<InstanceID>\MSSQL\Install
Example: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install

Once this has been executed successfully, you will now be able to work with Maintenance Plans.

Wednesday, October 31, 2012

Backup job failed - "file manipulation operations"


On some occasions when scheduling maintenance jobs like, Full database backup, Shrink database, Differential backups, index maintenance jobs we oversee the schedules and end up with jobs running into each other.

This will definitely lead to bigger errors and failures at any point in time. One such error we come across in such situations is the following.
 
"Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed."
Note: This is just the part of job history.
 
Fixes:
  • All we need to do is be alert and make sure we have the correct schedules for all the jobs without allowing any of the jobs running into each other.
  • If error or failures, make sure to change the job schedules and confirm if it works fine.
Hope this helps!

Ads