 |
> Support > Fixing Common DB8 PO Errors | 8.4.x |
 |
Fixing Common DB8 PO Errors |
By Ron Herardian
©1998, Global System Services Corporation (GSS)
Date: 2/10/98 8:02 PM
The most common problem with DB8 is a corruption of CCPOMI, the most heavily accessed file. Having this procedure handy and understanding its details can get you through 90% of common DB8 problems with no need to call Tech Support.
CCREGMOD: Remember to run or make available to cc:Mail R8 applications CCREGMOD on all Win32 systems that touch the cc:Mail database. If you have any doubt that CCREGMOD has been applied, place it in in startup
group(s).
ANALYZE: Always run ANALYZE to find out what is wrong before attempting any repair procedure. Also remember to back up your entire PO before attempting any repair procedure.
TROUBLESHOOTING: If you have any doubt about what the problem is, consult a cc:Mail database repair expert. When you seek help with a database problem, make sure that (1) you have any error messages recorded, (2) you have an ANALYZE log file handy, and (3) remember to describe any observed symptoms in Routers, gateways, or e-mail client applications, i.e., MCBR errors.
Once you have established that you have a corrupted CCPOMI file, follow these steps and you won't need to call Lotus or pay a 3rd party for Technical Support:
- Shut down the PO
- Back up the entire PO
- Delete CCPOMI.*
NOTE: This assumes you know that there is a corruption of the CCPOMI file because you ran ANALYZE before beginning this procedure.- Run CCRSTR with the /M parameter (remember to also use /IC when the POP is down). Remember to use the /LOG parameter.
NOTE: On some versions of NT you must close the CCRSTR window before RECLAIM will run.
Run RECLAIM with standard parameters (/DI and /LOG)- If RECLAIM succeeds (9 times out of 10 it will), backup the fixed PO
- Open the PO and resume normal operations
Ron
--
 |
©1995-2005 by Global System Services Corporation (GSS). Portions
of this material are copyright ©1995-1999 by Ron Herardian