Same thing here. Anyone have any ideas?
The solution is found in the same article you were looking at:
The vCenter 5.1 script for creating this job (job_schedule1_mssql.sql) is supposed to create a job with only one step. Looks like they decided to remove the purge step and the stored procedure for it, but for some reason the job doesn't always get updated and the step calling the (now missing) procedure stays.
You can fix it by running the job_schedule1_mssql.sql script per the instructions in the article.
That did the trick for me. Thanks!
It works for me.
Hi there, Josh from the VC support team here. I'm not able to reproduce this issue at all. I'm curious what might be causing it in your guys environments.
What exact version of SQL are you using? 10.50.xxxx?
Is it on the same system as VC or seperated?
Did you upgrade to 5.1 GA or 5.1 A?
At the time of the upgrade, you are sure the DB user had DBO rights on MSDB?
How did you do the VC upgrade - simple install or each component by hand?
If not simple, were all the components installed on this same machine?
Do you still have the VCDatabaseUpgrade.log file in %temp% ?
It's work for me
Im not able to run job_schedule1_mssql.sql to remedy the problem. I still have two steps in "Past Day stats rollupDB".
I still have the VCDatabaseUpgrade.log file intakt.
I upgrade to 5.1 A
SQL 10.50.2500 (during the upgrade i december) but just recently upgraded to SQL 10.50.4000.0 (where running job_schedule1_mssql.sql manually fails).