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 NOTE:
You must have SQL Server sysadmin authorization to execute this procedure.
  1. Stop any console sessions.
  2. Shut down the Windows Management Instrumentation (WMI) service, which stops all management server components.
  3. 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.
  4. Before you detach the openview database you must ensure that there are no more processes active in this database.
  5. 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.

  6. 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

  7. Edit the attached script myattach.sql, replacing the lines containing NEW_LOCATION with the actual physical location of the file.
    Note NOTE:
    You must specify all physical database files, even those that did not move.
  8. Attach the database files. Run the command:

    osql -S<database_instance> -E -i myattach.sql

    You should see the message "Successfully attached database openview."

  9. Start the OVEpStatusEngine service, which starts all management server components.

Related Topics:

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.