DMI 2.0 Installation and release notes

The DMI database

The DMI Service Provider creates its database in /etc/dmi/mifdb/sldb.dmi using /etc/dmi/mifs/backup/uxsp.mif in the process. When the DMI Service Provider runs, it creates a periodic backup (approximately every 5 minutes) of the database in /etc/dmi/mifs/backup/sldb.dmi.

If the /etc/dmi/mifdb/sldb.dmi database file becomes accidentally deleted, it can be restored manually from /etc/dmi/mifs/backup/sldb.dmi, but only when the DMI Service Provider has been stopped.

To create a new DMI Service Provider database, stop the DMI Service Provider, delete the file /etc/dmi/mifdb/sldb.dmi, and then restart the DMI Service Provider. This will cause the DMI Service Provider to create a new database containing only the component defined in the MIF file, /etc/dmi/mifs/backup/uxsp.mif, and any component MIF files found in /etc/dmi/mifs.

Management applications treat the Service Provider as a component with ComponentID set to 1. As such, the DMI-SP must support the standard ComponentID group.

When the DMI-SP is loaded, it looks for the database file, sldb.dmi. If this file does not exist, the Service Provider creates an empty database and installs the Service Provider MIF file, uxsp.mif.

Installing new MIF files into the MIF database

When the DMI-SP is invoked for the first time after being installed, it installs its own MIF file as ComponentID 1. You can install any other MIF files and instrumentation into the MIF database after this step has been completed. This can be achieved in one of two ways:

NOTE: When running the sample programs provided, the corresponding MIF files are installed automatically.

Next topic: Known problems and limitations
Previous topic: Troubleshooting

© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 27 April 2004