SYSTEM_SHM_READ_LOCK_ACTIVE is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: I - Internal Kernel Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Shared lock points to a released shared object area.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
In the current internal session, there is a shared lock on an instance
of a shared object area that has since been released.
The release could be due to the release method being called using an
application program, or could have been carried out by the system
administrator (in this case there will usually be an entry in the
system log).
As the instance has been released, it is not possible to continue with
the current transaction.
The area to be accessed was in shared object area <runtime parameter> and was locked
using handle object <runtime parameter>.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
SYSTEM_SHM_READ_LOCK_ACTIVE - system shm read lock active SYSTEM_SHM_OPEN_CHANGE_LOCK - system shm open change lock SYSTEM_SHM_NO_ROLL - system shm no roll SYSTEM_SHM_DETACH_IN_CONSTR - system shm detach in constr SYSTEM_SHM_CHANGE_LOCK_ACTIVE - system shm change lock active SYSTEM_SHM_AREA_READONLY - system shm area readonly