06-10-2008 05:34 PM
Since we ran out of disk space HUM isn't working.
Disk was freed, but things wren't running right so did a net stop crmdmgtd which never completed.
In the end had to do a reboot. Have tried stop/start crmdmgtd but the UPM processes won't start.
Can't seem to find a log that gives any clues. pdshow attached
Is there a lock somewhere that needs to be cleaned?
Solved! Go to Solution.
06-10-2008 06:41 PM
The best you can hope for is that the database transaction log has become corrupt. To check this, shutdown dmgtd, then look at NMSROOT\databases\upm. If you see a upm.log in there, delete it (del /f/q upm.log). Then, run:
NMSROOT\objects\db\win32\dbsrv9 -f NMSROOT\databases\upm\upm.db
Then restart dmgtd, and the UPM database engine and monitor should start. If not, then the upm database is most likely corrupt, and will have to be restored from a known good backup, or reinitialized. To reinit, run:
NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl dsn=upm dmprefix=UPM
06-10-2008 06:41 PM
The best you can hope for is that the database transaction log has become corrupt. To check this, shutdown dmgtd, then look at NMSROOT\databases\upm. If you see a upm.log in there, delete it (del /f/q upm.log). Then, run:
NMSROOT\objects\db\win32\dbsrv9 -f NMSROOT\databases\upm\upm.db
Then restart dmgtd, and the UPM database engine and monitor should start. If not, then the upm database is most likely corrupt, and will have to be restored from a known good backup, or reinitialized. To reinit, run:
NMSROOT\bin\perl NMSROOT\bin\dbRestoreOrig.pl dsn=upm dmprefix=UPM
06-10-2008 07:46 PM
thanks, I'll give it a try. We're running in eval so data loss not too much of a problem
06-12-2008 03:36 AM
Success. After shutting down, removing upm.log then running dbsrv9 -f as suggested, all seems good again. Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide