Skip to Content
author's profile photo Former Member
Former Member

Enqueue Standalone vs Enqueue Work Process

Dear Gurus,

I'm currently have this landscape:

Node 1

-


CI

DB

ASCS

Node 2

-


Dialog Instance

System is configured that when Node 1 down, CI, DB, and ASCS move to Node 2, and run from there.

The question is, do you need to set the Enqueue Work Process when you have run ASCS, or just put 0 in Enqueue WP in RZ10?

Thanks for help.

Regards,

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Dec 09, 2011 at 12:49 AM

    Just looking at the profiles

    ASCS profile

    ###################################

    SAPSYSTEMNAME = SM1

    SAPSYSTEM = 01

    INSTANCE_NAME = ASCS01

    DIR_CT_RUN = $(DIR_EXE_ROOT)/run

    DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

    SAPLOCALHOST = up-ssm-cs

    DIR_PROFILE = $(DIR_INSTALL)/profile

    PF = $(DIRPROFILE)/SM1_ASCS01_up-ssm-cs

    SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)

    SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)

    SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)

    #----


    1. Copy SAP Executables

    #----


    CPARG0 = list:$(DIRCT_RUN)/scs.lst

    Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)

    #----


    1. Start SAP message server

    #----


    MS = ms.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

    Execute_01 = local rm -f $(_MS)

    Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)

    Start_Program_00 = local $(_MS) pf=$(_PF)

    #----


    1. Start SAP enqueue server

    #----


    EN = en.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

    Execute_03 = local rm -f $(_EN)

    Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN)

    Start_Program_01 = local $(_EN) pf=$(_PF)

    #######################################

    enque replication profile

    #######################################

    sm1adm> less START_ERS11_up-ssm-enrep

    SAPSYSTEMNAME = SM1

    SAPSYSTEM = 11

    INSTANCE_NAME = ERS11

    SCSID = 01

    DIR_CT_RUN = /usr/sap/SM1/SYS/exe/run

    DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

    DIR_PROFILE = /sapmnt/SM1/profile

    PF = $(DIRPROFILE)/SM1_ERS11_up-ssm-enrep

    SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)

    SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)

    SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)

    #----


    1. Copy SAP Executables

    #----


    CPARG0 = list:$(DIREXECUTABLE)/ers.lst

    Execute_00 = immediate $(DIR_EXECUTABLE)/sapcpe$(FT_EXE) $(_CPARG0) pf=$(_PF)

    #----


    1. start enqueue replication server

    #----


    ER = er.sap$(SAPSYSTEMNAME)$(INSTANCE_NAME)

    Execute_01 = immediate rm -f $(_ER)

    Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enrepserver $(_ER)

    Restart_Program_00 = local $(_ER) pf=$(_PF) NR=$(SCSID)

    ~

    now in the default profile we have

    ###################################

    enque/serverhost up-ssm-cs

    enque/serverinst 01

    if you read above, up-ssm-cs in this case is the host that will be always alive and pointing to current central instance.

    hope that helps

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      You are right. There will be small disconnect fron DI as well till the time DB and ASCS instance will not be started on node 2. But there are certain parameters which you can define to increase reconnect time. I have not tried this in Unix cluster but this works in MSCS cluster.

      Check SAP Note 24806 - Database Reconnect technical details and settings.

      Thanks

      Sunny

  • Posted on Dec 08, 2011 at 04:57 PM

    Hi,

    In case of HA systems, Enqueue server lies in ASCS. So, if node 1 down then ASCS moves to node 2 and it will provide Enqueue service there. So, you need to set it in instance profile in RZ10.

    Thanks

    Sunny

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Sunny Pahuja

      When DB switch to node 2, won't be there short time system down?

      This also means all user context currently logged in CI will be lost, user will be kicked out of the system.

      Dialog in node 2 can't find the DB until it is started on node 2, hence the user currently logged in to node 2 will be out of the system also.

      Regards,

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.