Cannot open dbspace 'CIM1' from file ' mgmtdb1.db

  • 10075966N
  • NOVL83256
  • 24-Oct-2002
  • 11-Mar-2005

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Fact

Novell ZENworks for Servers 3.0

Novell ZENworks for Desktops 4.01

Novell ZENworks for Servers 2.0

Novell ZENworks for Desktops 3.2

Novell ZENworks Workstation Inventory

Novell ZENworks Server Inventory

Symptom

Sybase database will not load

Error: "<volume>:\ZENWORKS\mms\db\mw.db is not a valid database file "

Error: "<volume>:\zenworks\pds\db\zfslog.db is not a valid database file "

Error: "<volume>:\Zenworks\Database\nal.db is not a valid database file"

Error: "<volume>:ZENWORK/INV/DB/MGMTDM.DB is not a valid database file"

Error: "<volume>:ZENWORK/INV/DB/NAL.DB is not a valid database file"

Error: "Cannot open dbspace 'CIM1' from file ' mgmtdb1.db"

Note

Errors on Sybase screen for ZENworks for Desktops

Using a Maximum page size of 2048 bytes
Starting database "mgmtdb" (<volume>:\ZENWORKS\Inv\db\mgmtdb.bd) at <day><date><time>
Cannot open dbspace 'CIM1' from file 'mgmtdb1.db'
Cannot open dbspace 'CIM2' from file 'mgmtdb2.db'
Cannot open dbspace 'CIM3' from file 'mgmtdb3.db'
Cannot open dbspace 'CIM4' from file 'mgmtdb4.db'
Cannot open dbspace 'CIM5' from file 'mgmtdb5.db'
Cannot open dbspace 'CIM6' from file 'mgmtdb6.db'
Cannot open dbspace 'CIM7' from file 'mgmtdb7.db'
Cannot open dbspace 'CIM8' from file 'mgmtdb8.db'
Cannot open dbspace 'CIM9' from file 'mgmtdb9.db'
Transaction log: mgmtdb.log
Starting checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Finished checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Database "mgmtdb" (mgmtdb.db) started at <day><date><time>
<volume>\zenworks\database\nal.db is not a valid database file
Starting checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Finished checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Database server stopped at <day><date><time>

<Press any key to close screen>

Errors on Sybase screen for ZENworks for Servers

Using a Maximum page size of 2048 bytes
Starting database "mgmtdb" (<volume>:\ZENWORKS\Inv\db\mgmtdb.bd) at <day><date><time>
Cannot open dbspace 'CIM1' from file 'mgmtdb1.db'
Cannot open dbspace 'CIM2' from file 'mgmtdb2.db'
Cannot open dbspace 'CIM3' from file 'mgmtdb3.db'
Cannot open dbspace 'CIM4' from file 'mgmtdb4.db'
Cannot open dbspace 'CIM5' from file 'mgmtdb5.db'
Cannot open dbspace 'CIM6' from file 'mgmtdb6.db'
Cannot open dbspace 'CIM7' from file 'mgmtdb7.db'
Cannot open dbspace 'CIM8' from file 'mgmtdb8.db'
Cannot open dbspace 'CIM9' from file 'mgmtdb9.db'
Cannot open dbspace 'CIM10' from file 'mgmtdb10.db'
Cannot open dbspace 'CIM11' from file 'mgmtdb11.db'
Transaction log: mgmtdb.log
Starting checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Finished checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Database "mgmtdb" (mgmtdb.db) started at <day><date><time>
<volume>:\ZENWORKS\mms\db\mw.db is not a valid databse file
<volume>:\zenworks\pds\db\zfslog.db is not a valid database file
Starting checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Finished checkpoint of "mgmtdb" (mgmtdb.db) at <day><date><time>
Database server stopped at <day><date><time>

<Press any key to close screen>

Cause

This would occur only if mgmtdb.db is unable to find other mgmtdb(1..9) files

Note

Possible Causes:
1.  mgmtdb(1..9) are not present in the same directory as mgmtdb.db
2.  The administrator tried to run AlterDBSpace utility without configuring AlterDB.prop file correctly and then restarted the database. This has changed the reference of mgmtdb(1..9).db files in mgmtdb to the default location which may be different from the actual installed db location.
3.  The mgmtdb.log file has got some unfinished transactiions on mgmtdb(1..9).db and the server either abended or got restarted without shutting down the database normally.  This might have corrupted the mgmtdb.db in the sense removed/changed the references to mgmtdb(1..9).db in it.
4.  The user has manually moved mgmtdb1...mgmtdb11 files and has not run AlterDBSpace utility.
5.  Database is corrupted.
6. Compression on a NSS volume

Fix

Submitted to Engineering

Workaround (s):

Cut & paste the directory that contains the database to another server or workstation and Copy it back to the inventory server.   This is the ZENworks directory and subdirectories

Alternative methods to resolve this:
1. Rename every MGMTDBX.DB into *.ORG and back to *.DB (if necessary even the NAL.DB).
2. Switch off the file attribute "Compress" for the database files 
3. In case of a Windows NT client, change any attribute for the database files.

1. Change the settings in explorer to show compressed files  in a different color (Tools | Folder Options | View | enable Display compressed files and folders with alternate color),
2. Browse to the database directory
3. Touch every database file that shows up in a different color. 
4. Restart Sybase

1. Move the ZENworks directory and sub directories to another location.
2. Delete and recreate the volume with Compression disabled.
3. Move the ZENworks directory and sub directories back to the new volume.

The best prevention to avoid the SYBASE DB files from being compressed and resulting in this symptom, is to always maintain more than 10% Free blocks on the volume (to calculate true Free blocks:  load Monitor, select Volumes, highlight the volume, press the TAB key, find the Free blocks value and divide by the Total blocks value, and then move the decimal two places to the right to convert to %).  The 'Free blocks in the salvage system' are the blocks that can be moved to the Free blocks value with a purge of the volume.  The minimum percent of Free blocks is 20% for SYS if the database files are on it.  Once the DB files get compressed after a volume has gone below 10%, they will get compressed again more easily.  Making regular backups of the uncompressed DB files is recommended.  This continues to be investigated, but is a long term process.  Check this TID for any change in the status.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.