Optivity Tip -- When database's go bad... [Optivity NMS-Unix]

[jfk]

This tip covers ver 8.1.1 and lower:<br>
<br>
If a user should start getting "raima" errors of any sort, this is almost (99.9%) always a sign of database corruption. Optivity uses a raima object-oriented database for each user under the $LNMSHOME/db/&lt;username&gt;.db directory. When the database becomes corrupt, it will affect a variety of applications that query the database (many apps query the db for community name, for example). Use the previous tip to remove the users corrupt db and then revalidate from the NMS station. You'll be good to go.<br>
<br>
This is an opportunity to plug back-ups! Occasional backups will get a user's db back up and running more quickly. Delete the db as per the previous tip and restore the database...<br>
<br>
Bonus Tip:<br>
The command line for backup and restore is:<br>
<br>
$LNMSHOME/bin/output_db_contents &lt;filename&gt; --backup app<br>
<br>
$LNMSHOME/bin/input_db_contents &lt;filename&gt; --restore app<br>
<br>
The backup is a plain text version of the database... see next tip