SAP Knowledge Base Article - Preview

2808886 - enqt command is not working with Standalone Enqueue Server 2 (ENSA2) enabled

Symptom

enqt command is not working.

For example, "enqt pf=<ERS_instance_profile> 11 20" command is to fill the lock table of the enqueue server with 20 locks. when use enqt command (e.g. "enqt pf=<ERS_instance_profile> 20 1 1 9999" ) to check out the enqueue lock table entries,  it returns "Number of selected entries: 0" which means filling the lock table of the enqueue server with 20 locks with enqt command above got failed.

You can also see following error from dev_eq_trcXXXX(at the same directory where enqt command performed)
---------
*** ERROR => EnqLockTableAttach2: attach to lock table failed, rc = 3 [enxxmini.h 575]
***LOG GEF=> [enxxmini.h 576]
***LOG GZZ=> Attach to lock table failed [enxxmini.h 577]
***LOG GZZ=> Size = <XXXXXX>, rc = 3 [enxxmini.h 578]
No enqueue table available


Read more...

Environment

NW 7.5X with ENSA2 enabled.

You can find following parameters from DEFAULT.PFL if ENSA2 enabled.

enq/enable = TRUE
enq/serverhost = <enqueue server 2 host>
enq/serverinst = <instance number>

Keywords

KBA , BC-CST-EQ , Enqueue , Product Enhancement

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.