✅ CONTENT MIGRATED TO GURU ON FEBRUARY 22, 2024

Model Base checking is a process that cleans up any problems that may have occurred due to lost network connections, software crashes or other problems.

checkMB is a server side process should be run nightly as a cron job. It produces a report called MBchecker.rpt.

However, sometime it is necessary to run the checker before the nightly job. Below are some typical cases and how to run it for these.

• Log on as samm to your server
• Make VERY sure everyone is out of samm and check with the command

 psamm 

• Then run:

 MBchecker -v /whatif/samm/<name_MB> 

• Log on as samm to your server
• Make VERY sure everyone is out of samm and check with the command

 psamm 

• if there are still some samm servers running kill those processes with SIGHUP:

kill -signal HUP <pid>

This alone might fix the problem. If not, do a check like any of the other topics here and/or mark the #users in the framework to 0.

• Log on as samm to your server
• Make VERY sure everyone is out of the Model base because it can become corrupted if this is run while someone is in it. Check with the command

 psamm 

• Then run:

 checkMB /whatif/samm/<name_MB> 

• Log on as samm to your server
• Make VERY sure everyone is out of the Model base because it can become corrupted if this is run while someone is in it. Check with the command

 psamm 

• Then run:

 checkMB /whatif/samm/<name_MB> 

• If that fails try:

 MBchecker -v -dirty /whatif/samm/Models_MB 

Using the -dirty option, MBchecker only checks model families with numUsers != 0 and may get the Model base functional again but the real problem is not yet fixed. At least other mf's will be useable though.

• Log on as samm to your server
• Make VERY sure everyone is out of the Model base because it can become corrupted if this is run while someone is in it. Check with the command

 psamm 

• Then run:

 MBchecker -v /whatif/samm/Models_MB