Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

CMDB DB Move and Then Prompt to Upgrade DB?

Created: 11 Jul 2013 • Updated: 23 Jul 2013 | 6 comments
HighTower's picture
This issue has been solved. See solution.

We attempted to move our Symantec_CMDB from one SQL server to another today and ran into a snag.  Here are the steps we followed:

  1. Stop Altiris services on SMP
  2. Backup up Symantec_CMDB and restored into new server
  3. Started Altiris services on SMP
  4. Inside app under Notification Server > Database Settings I changed the old servername\instance to the new location, selected Use Existing Database, and selected my Symantec_CMDB

When I clicked Save Changes I was greeted with this dialog box that I cannot find information on:

DatabaseUpgradeWTF.PNG

Can anyone shed some light on what's going on here? 

Thanks!

Operating Systems:

Comments 6 CommentsJump to latest comment

HighTower's picture

I'm adding the text of the dialog box to make it searchable:

Upgrade Progress:
The selected database needs to be upgrade, click OK to upgrade the database.  After the upgrade the database size is expected to be doubled.

Please Note:  The system will be left in a paused state after the upgrade to allow for the subsequent installation of any required solutions/products.  Once ready, please unpause the NS using the toggle switch under 'Setting -> Notification Server -> Notification Server Settings'.

md investigate's picture

Hi,

I had this screen like you in more than one movement. If you say OK it will upgrade the database and that can take a long time (depends on database size).

Like described in this thread (http://www.symantec.com/connect/forums/moving-database-71) you can change to new database location with other settings than the ones in console.

The thread is based on http://www.symantec.com/docs/HOWTO10098

I did the movement like described there and was working like a charm without any issue and database upgrade waiting times.

Regards

SOLUTION
HighTower's picture

Thanks!  We're making another attempt next week and I'll try those instructions. 

I'll report back :)

HighTower's picture

Yes, we had extra work to do with SSAS and SSRS but it's all working.