I finally got through updating the RMS (had an issue with the startup of services), and now I'm attempting to run the database queries against the SCOM and Datawarehouse databases. However, when updating the SCOM db, I get the following errors as part of the output. Has anyone else seen these errors, and if so, what do I do to correct them to get this query to run successfully? Msg 208, Level 16, State 6, Procedure p_MakeViewCreationText, Line 176 Invalid object name 'dbo.p_MakeViewCreationText'. Msg 208, Level 16, State 1, Line 8 Invalid object name 'ManagedType'. Msg 208, Level 16, State 1, Procedure fn_AlertViewNoContext, Line 64 Invalid object name 'dbo.Alert'. Msg 208, Level 16, State 1, Procedure fn_AlertViewChangesNoContext, Line 70 Invalid object name 'dbo.Alert'.

I also have about 3 dozen of these errors (for these two modules due to different missing objects): The module 'p_InstallTypesAndReltypes' depends on the missing object 'dbo.p_TypeDeletePermanent'. The module will still be created; however, it cannot run successfully until the object exists. The module 'p_DeleteObsoleteMPObjects' depends on the missing object 'dbo.p_DeleteFolder'. The module will still be created; however, it cannot run successfully until the object exists.

was this a new install from OpsMgr R2 RTM to CU3?Scott Moss MVP (Operations Manager) | President - System Center Virtual Users Group | Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you!

No. Actually, we had successfully applied the CU2 update a couple of months ago.

Hi, According to my search, this issue should be related to SQL server. I suggest posting to SQL forum to check if there is anything can be done from SQL side: http://social.technet.microsoft.com/Forums/en-us/category/sqlserverPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I finally got through updating the RMS (had an issue with the startup of services), and now I'm attempting to run the database queries against the SCOM and Datawarehouse databases. However, when updating the SCOM db, I get the following errors as part of the output. Has anyone else seen these errors, and if so, what do I do to correct them to get this query to run successfully? Msg 208, Level 16, State 6, Procedure p_MakeViewCreationText, Line 176 Invalid object name 'dbo.p_MakeViewCreationText'. Msg 208, Level 16, State 1, Line 8 Invalid object name 'ManagedType'. Msg 208, Level 16, State 1, Procedure fn_AlertViewNoContext, Line 64 Invalid object name 'dbo.Alert'. Msg 208, Level 16, State 1, Procedure fn_AlertViewChangesNoContext, Line 70 Invalid object name 'dbo.Alert'. This generally happens when you are running the query against the wrong database (need to select OperationsManager) or when you dont have SA rights against the instance hosting the OpsDB. Kevin Holman

This as stated above is where SQL does not implicitly know which DB the update script is supposed to run against. If this is an update for the OperationsManager DB then up at the top of the script add a "Use OperationsManager" without the quotes and if for the Operations Manager Data Warehouse then add "Use OperationsManagerDW" to the top of the SQL update script. Make sure which DB the update is supposed to run against though. I have run itno this before.