Kbase 17212: Memory Violation 49 when doing dbanalys
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Memory Violation 49 when doing dbanalys
This kbase is being generated to document an issue which has appeared
several times over the past year. The issue is one of a user getting
a Memory Violation (49) error when doing a dbanalys against thier db.
Steps to troubleshoot this issue, normally result in trying the
following:
1. Scanning the db to see if any record or block level corruption
2. Rebuilding the RM and Free Chain
3. A full index rebuild to rule out any index corruption.
4. Some customers have even done a test indices to see if there was
possible leaf note corruption which could be causing the problem.
Usually an ixanalys or tabanalys against this same db will be
successful.
The cause of this issue is usually the result of schema corruption.
The exact cause of that schema corruption is not known. It could have
been left over from a force against this db or an earlier prostrct
unlock. The solution is to dump and load the db. Then you should
be able to do a dbanalys against the new db without any problems.
Progress Software Technical Support Note # 17212