attachments/lrayl/media/windows-live-writer/how-to-correct-the-incorrect-file-names-_ae0f/clip_image001_thumb.png

How to correct the incorrect file names for the System Center 2012 SP1 Operations Manager OperationsManagerDW when installing on Windows 2012 with SQL 2012 SP1 also on Windows 2012

After the installation of Operations Manager 2012 SP1 on a SQL 2012 SP1 Database Server, with both the Database Server and the Operations Manager Server running on Windows 2012; the Operations Manager Data Warehouse DB files are now getting named DATA.mdf and DATA.ldf.

Cameron Fuller and JC Cowen has a similar experience where they found the name of the OperationManagerDW.mdf and OperationsManagerDW.ldf files were missing the name a file name, only the file name extension was available. This is another condition you may run into. I am also adding in how to create a Maintenance Plan to backup the databases. It’s probably a best practice to use Maintenance Plans plus its easier to backup all of your databases with a Maintenance Plan rather than trying to backup individually.

 

Cameron’s blog can be read here:

http://blogs.catapultsystems.com/cfuller/archive/2013/02/13/issue-when-installing-opsmgr-2012-sp1-all-in-one-scom-sysctr.aspx

 

Jonathan Cowen’s Blog can be read here:

http://blogs.catapultsystems.com/jcowan/archive/2013/04/18/opsmgr-2012-sp1-workaround-fresh-install-results-in-blank-operationsmanagerdw-data-and-log-file-names-mdf-and-ldf.aspx

 

On the Database Server, whether on an all-in-one installation or a remote SQL installation into a default instance of SQL, the database files are called Data.mdf and Data.ldf and are located one level up in the folder structure for your SQL database files and the log files.

clip_image001

To correct after installation or (when you notice the issue Smile), perform the following:

Shut down all OpsMgr services:

clip_image002

Open SQL Management Studio and create a new Maintenance Plan to back up all the databases:

clip_image003

 

clip_image004

 

clip_image005

 

clip_image006

 

clip_image007

 

clip_image008

 

clip_image009

 

clip_image010

 

Once the maintenance plan is created, run it.

image

 

clip_image012

 

Databases backed up…

 

clip_image013

 

Right Click on the OperationsManagerDW Database in the SQL Management Studio and select Detach. The Detach Database windows opens

clip_image014

 

Move the DATA.mdf and the DATA.ldf from the *\MSSQL11.MSSQLSERVER\MSSQL folder to *\MSSQL11.MSSQLSERVER\MSSQL\Data folder where all the other database and log files are located

 

clip_image015

 

clip_image016

 

Rename the Data.mdf and .ldf files to OperationsManagerDW.mdf and OperationsManagerDW.ldf.

 

clip_image017

Right Click on Databases again and select Attach…

 

image

 

Select Add then select the OperationsManagerDW.mdf, then select OK

 

clip_image019

 

Under the OperationsMangerDW database details, select the New File Path for the databases by clicking on the ellipse (…). The Not Found will go away once you select the renamed file.

image

 

 

clip_image021

 

Select OK then you’re done! Restart the OpsMgr services and continue configuring.

 

clip_image022

 

Restart OpsMgr Services again

.

That’s all there is too it. Happy monitoring everyone, see ya all again soon! Smile

 

Leave a Reply