Consultor Eletrônico



Kbase 15465: SE: bkmod: block <number> without EXCLUSIVE lock. (3639)
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   5/10/1998
SE: bkmod: block <number> without EXCLUSIVE lock. (3639)

DRAFT COPY - Currently under review and edit.

INTRODUCTION:
=============

This Technical Support Knowledgebase entry describes what PROGRESS
message 3639 means and possible ways to correct it.


PROGRESS ERROR MESSAGE:
=======================

SYSTEM ERROR: bkmod: block <number> without EXCLUSIVE lock. (3639)


WHAT DOES THE ERROR MEAN?:
==========================

This message is written when a database buffer has been marked dirty
and is not exclusively locked. A dirty buffer is shared memory that
has been modified. This should not happen because a user cannot
update shared memory or write to the database without first getting an
exclusive lock.


POSSIBLE CAUSE OF ERROR:
========================

The occurrance of this message indicates that the buffer was corrupted
either by a hardware problem or a software bug.


DOES ERROR INDICATE CORRUPTION: IF SO, WHAT TYPE
======================================== =========================

Sometimes Data corruption


CORRECTIVE MEASURES:
====================

1 - If the database is not accessible, you need to do one of the
following.
Restore a backup.
Force in and dump and reload.
Run dbrpr to scan for corruption.

2 - Check the database .lg file for additional messages.

3 - Check the hardware error log.

4 - Run full diagnostics on the disk, memory, and controller.

5 - Disable write cache.

6 - Make a checklist of any new hardware that has recently been added
to the system or any configuration change that has been made.
Also note any recent system crashes.

7 - Contact your hardware vendor.

If these steps do not point exclusively to a hardware failure, contact
Progress Technical Support to review the corrective measures that you
have taken.


RELATED PROGRESS MESSAGES:
==========================

SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2>
(1124)
SYSTEM ERROR: wrong BI blk, read <dbkey> from <dbkey> (1119)


ONLINE PROCEDURES OR UTILITIES:
===============================

prorest <dbname>
proutil <dbname> -C dbrpr
PROGRESS Data Dictionary Dump and Reload Utilities


REFERENCES TO WRITTEN DOCUMENTATION:
====================================

PROGRESS Version 6 System Administration II, Chapter 4
PROGRESS Version 7 System Administration Guide, Chapters 11, 14

Progress Software Technical Support Note # 15465