on 2013 Apr 02 7:33 PM
When starting the cetnral instance the Dispatcher (/workprocesses) stops after 1 minute. Looking at the logs of the workprocesses the creation of the lock table is failing. Normally work-processes should attach to an existing lock table if already created and not trying to re-create it (in this case the lock table was created by the enq server)
How can we solve this?
Bart
---------------------------------------------------
trc file: "dev_w0", trc level: 1, release: "720"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS all, MJ
*
M sysno 22
M sid ND1
M systemid 562 (PC with Windows NT)
M relno 7200
M patchlevel 0
M patchno 401
M intno 20020600
M make multithreaded, Unicode, 64 bit, optimized
M profile \\SDSAPE01\sapmnt\ND1\SYS\profile\ND1_DVEBMGS22_SDSAPE01
M pid 9460....
W === ipl_Init() returns 0, ITSPE_OK: OK
W =================================================
N SignInit: successfully obtained handle for Security Context cache
N VSI: WP init in ABAP VM completed with rc=0
E Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume SDSAPE01_ND1_22
E Enqueue Info: enque/use_pfclock2 = FALSE
E Enqueue Info: row condense enabled
E EnqLockTableCreate: create lock table (size = 33554432)
E *** ERROR => EnqLockTableCreate: Lock table already exists! (size = 33554432) [enxxmini.h 461]
M ***LOG GEF=> [enxxmini.h 462]
M ***LOG GZZ=> Creation of lock table failed [enxxmini.h 463]
M ***LOG GZZ=> Lock table already exists! (size = 33554432) [enxxmini.h 464]
M in_ThErrHandle: 1
M *** ERROR => ThInit: create lock table (step 1, th_errno 2, action 3, level 1) [thxxhead.c 11318]
M
M Info for wp 0...
---------------------------------------------------
trc file: "dev_enqsrv", trc level: 1, release: "720"
---------------------------------------------------
sysno 22
sid ND1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 318
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
pid 13144[Thr 8884] Tue Apr 02 14:19:03 2013
[Thr 8884] profile \\SDSAPE01\sapmnt\ND1\SYS\profile\ND1_DVEBMGS22_SDSAPE01
[Thr 8884] hostname SDSAPE01
[Thr 8884] Listen successful on port/service sapdp22
[Thr 8884] EnqInitCleanupServer: Shm of enqueue table (rc = 3) does not exist, nothing to clean up
[Thr 8884] initialize_global: Enqueue server started WITHOUT replication functionality
[Thr 8884] Enqueue: EnqMemStartupAction Utc=1364905143
[Thr 8884] EnqLockTableCreate: create lock table (size = 33554432)
[Thr 8884] EnqLockTableMapToLocalContext: enque/use_pfclock2 = FALSE[Thr 8884] Tue Apr 02 14:19:04 2013
[Thr 8884] ***LOG GEZ=> Server start [encllog.cpp 501]
[Thr 8884] Enqueue server start with instance number 22
Hi Bart,
In my case, renaming the ENQBCK file under the /usr/sap/<SID>/DVEBMGS../log to something else solved this issue.
Regards,
Pat.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Bart,
Can you please reboot OS basically and start SAP again.
The following link has similar issue. Hope it solves your issue.
http://scn.sap.com/thread/3243859
Kind Regards,
Jacob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Most probably during a previous shutdown the enqueue service was not correct finished and the shared memory still present. Another reason could be that another SAP instance running with the number 00 on the same server. So, make sure that no other SAP instance exists there with number 00. If you do not find such a SAP instance with number 00 on it, you need to stop the installation and reboot the server to clean the shared memory which is responsible for the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please attach profile ND1_DVEBMGS22_SDSAPE01.
Normally work-processes should attach to an existing lock table if already created and not trying to re-create it (in this case the lock table was created by the enq server)
What installation option you use for enqueue server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you please clean the shared memory it seems that during the shutdown the enqueue services were not correct finished and the shared memory still present.
So please clean the shared memory and start it agin.
Please check and let me know the result.
Best Regards,
Atul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
73 | |
10 | |
8 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.