Distribute database files and log files to different disk drives
After initial installation all components of the management server
database are stored in the same directory, for example, as:
%OvDataDir%\datafiles\<database_instance>
The database consists of several physical files, as shown in the
table:
File Name
Purpose
openview.mdf
Primary partition for system tables
store.ndf
Store tables and indexes
pmad.ndf
Policy Management and Deployment tables and
indexes
msgaction_dat.ndf
Message Action Server tables
msgaction_idx.ndf
Message Action Server indexes
role.ndf
Security Server Role tables and indexes
In large production environments with many managed nodes, a
considerable amount of data could be collected and stored into the
database. In such environments it is advisable to distribute the
database files and log files to dedicated disk drives with
sufficient capacity to prevent data overflow.
To achieve better performance by utilizing parallel disk I/Os,
you should distribute database files and log files to separate disk
drives.
To move the database files to another disk location
You can change the location of any database file (data file or log
file) using this procedure.
NOTE:
You must have SQL Server sysadmin authorization to execute
this procedure.
Stop any console sessions.
Shut down the Windows Management Instrumentation (WMI) service,
which stops all management server components.
Use the scripts for attaching and detaching the physical files
with the HPOM database that were provided with the product,
attachdb.sql and detachdb.sql. Scripts are located in
the
%OvInstallDir%\lbin\OvOW\ServerConsoleInstall\dbscripts
directory.
Before you detach the openview database you must ensure that
there are no more processes active in this database.
Detach the openview database by running the detach script:
osql -S<database_instance> -E -i detachdb.sql
The operation is successful if there is no error
message.
Copy the physical database files that you want to move to their
new location.
Make a copy of the attachdb.sql script, as
shown:
copy attachdb.sql myattach.sql
Edit the attached script myattach.sql, replacing
the lines containing NEW_LOCATION with the actual physical location
of the file.
NOTE:
You must specify all physical database files, even those that did
not move.
Attach the database files. Run the command:
osql -S<database_instance> -E -i myattach.sql
You should see the message "Successfully attached database
openview."
Start the OVEpStatusEngine service, which starts all management
server components.
NOTE: