Kbase 16646: Error (37) - Have you forced into your database?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Error (37) - Have you forced into your database?
DRAFT COPY - Currently under review and edit.
INTRODUCTION:
=============
There are users who note in their log file that they are receiving an
error (37), indicating that their database is damaged, everytime they
start up their database, yet scans of their database come out clean.
WHY YOU NEED TO KNOW THIS:
===========================
One reason that can cause this behavior is if the database has been
forced into. By "forced" I mean that the broker or a single user
session or a proutil command was invoked using the -F option. A
"forced" database constitutes a damaged database and will cause the
error (37) flag to be set until the database has been dumped and
loaded.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
For information regarding how to dump and load your database, please
refer to PROGRESS System Administration Guide, Chapter 14
Progress Software Technical Support Note # 16646