SYSTEM_SHM_OPEN_CHANGE_LOCK 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: A - ABAP Programming 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 abap error for more details about the possible cause of this runtime error and how it could be avoided.
Active change lock on transactional area during COMMIT.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
An exclusive or change lock that was set on a transactional ABAP shared
objects area has not been removed yet.
As the content of sections like this should be synchronised with the
database, there must be no active exclusive or change locks on it
during a database COMMIT.
In this case, the lock is on:
Area <runtime parameter>,
Client <runtime parameter>,
Instance <runtime parameter>.
The lock was set at the following position:
Program <runtime parameter> (version <runtime parameter>),
code offset <runtime parameter>.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
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 SYSTEM_SHM_AREA_OBSOLETE - system shm area obsolete