Skip to Content

After the FailOver , the lock table Empty

Dear All,

happy day ,

we have installed SAP SCM Server 7.0 in the red hat cluster environment under Red Hat Enterprise Linux 5.8 with Oracle DataBase 11.2,we install 4 services

Service 1 : ASCS ==> which is Enqueu Server with NR 12

Service 2 : CI ==> which is Central instance S1C with NR 11

Service 3 : ERS ==> which is Replication Server with NR 10

Service 2 : DB ==> which is DB instance S1C

running under 2 nodes

Node NO 1 : scmapp

Node No 2: scmdb

with the following Sequence (ERS - ASCS - DB - CI)

After the FailOver , the lock table Empty with some failover scenarios (not with all scenarios)

and

During the failover, the trace file of the standalone enqueue server dev_enqrepl contains the following error message:

[Thr 1094582240] Sun Sep 22 16:49:46 2013

[Thr 1094582240] A newly started replication server has connected

[Thr 1094582240] ***LOG GEZ=> repl. activ [encllog.cpp 501]

[Thr 1094582240] Sun Sep 22 16:49:58 2013

[Thr 1094582240] *** ERROR => ReplicationThread::Loop(): fatal error (read) on connection 1aa61b60 (hdl 89) [eniothread.c 2453]

[Thr 1094582240] ***LOG GEZ=> repl. closed [encllog.cpp 501]

Best Regards ,

Ahmed

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • Posted on Sep 24, 2013 at 01:07 PM

    HI,

    You are checkign the enqueue replication server trace.

    After the move of ASCS instnace to the second cluster note you should check the trace dev_enqsrv if the standalone enqueue was able to allocate to the ERS shared memory without error.

    If you receive errors like:

    ShadowTable:attach: ShmCreate - pool doesn't exist

    *** ERROR => EnqRepAttachOldTable: failed to get information on

    old replication table: rc=-1

    this means that the standalone enqueue was not able to connect to the ERS shared memory and, therefore, you should check the reason in the old traces of the ERS that was running in this host.

    If the standalone enqueue was able to attach to the ERS shared memory without errors, you should find a log with " shared key attached"

    Regards

    Clebio

    Add a comment
    10|10000 characters needed characters exceeded

    • HiClebio

      I post the Error in dev_enqrepl filel in the Original Post

      --------------------------------------------------------------------------

      ---------------------------------------------------

      trc file: "dev_enqrepl", trc level: 1, release: "720"

      ---------------------------------------------------

      sysno 12

      sid S1C

      systemid 390 (AMD/Intel x86_64 with Linux)

      relno 7200

      patchlevel 0

      patchno 94

      intno 20020600

      make multithreaded, Unicode, 64 bit, optimized

      pid 3220

      [Thr 1083785184] Tue Sep 24 13:42:21 2013

      [Thr 1083785184] profile /usr/sap/S1C/SYS/profile/S1C_ASCS12_scascs

      [Thr 1083785184] hostname scmapp

      [Thr 1083785184] IOListener::Listen: listen on port 51216 (addr 0.0.0.0)

      [Thr 1083785184] will sleep maximal 333 ms while waiting for response

      [Thr 1083785184] will sleep max 5000 ms when idle

      [Thr 1083785184] will wait maximal 1000 ms for input

      [Thr 1083785184] Tue Sep 24 13:42:22 2013

      [Thr 1083785184] A newly started replication server has connected

      [Thr 1083785184] ***LOG GEZ=> repl. activ [encllog.cpp 501]

      [Thr 1083785184] Tue Sep 24 13:43:03 2013

      [Thr 1083785184] *** ERROR => ReplicationThread::Loop(): fatal error (read) on connection 1f77c450 (hdl 65) [eniothread.c 2453]

      [Thr 1083785184] ***LOG GEZ=> repl. closed [encllog.cpp 501]

      [Thr 1083785184] Tue Sep 24 13:44:12 2013

      [Thr 1083785184] A newly started replication server has connected

      [Thr 1083785184] ***LOG GEZ=> repl. activ [encllog.cpp 501]

      [Thr 1083785184] Tue Sep 24 13:45:22 2013

      [Thr 1083785184] *** ERROR => ReplicationThread::Loop(): fatal error (read) on connection 1f781f50 (hdl 104) [eniothread.c 2453]

      [Thr 1083785184] ***LOG GEZ=> repl. closed [encllog.cpp 501]

      -------------------------------------------------------------

      the content of dev_enqsrv

      ------------------------------------------------------------

      ---------------------------------------------------

      trc file: "dev_enqsrv", trc level: 1, release: "720"

      ---------------------------------------------------

      sysno 12

      sid S1C

      systemid 390 (AMD/Intel x86_64 with Linux)

      relno 7200

      patchlevel 0

      patchno 94

      intno 20020600

      make multithreaded, Unicode, 64 bit, optimized

      pid 29637

      [Thr 47815365664608] Tue Sep 24 14:46:56 2013

      [Thr 47815365664608] profile /usr/sap/S1C/SYS/profile/S1C_ASCS12_scascs

      [Thr 47815365664608] hostname scmdb

      [Thr 47815365664608] Listen successful on port/service sapdp12

      [Thr 47815365664608] Tue Sep 24 14:46:57 2013

      [Thr 47815365664608] EnqInitCleanupServer: Shm of enqueue table (rc = 3) does not exist, nothing to clean up

      [Thr 47815365664608] ShadowTable:attach: ShmCreate - pool doesn't exist

      [Thr 47815365664608] initialize_global: Enqueue server started with replication functionality

      [Thr 47815365664608] Enqueue: EnqMemStartupAction Utc=1380023217

      [Thr 47815365664608] Enqueue Info: enque/use_pfclock2 = FALSE

      [Thr 47815365664608] Tue Sep 24 14:46:58 2013

      [Thr 47815365664608] ShadowTable:attach: ShmCreate - pool doesn't exist

      [Thr 47815365664608] EnqRepRestoreFromReplica: failed to attach to old replication table: rc=-1

      [Thr 47815365664608] enque/backup_file disabled in enserver environment

      [Thr 47815365664608] Tue Sep 24 14:46:59 2013

      [Thr 47815365664608] ***LOG GEZ=> Server start [encllog.cpp 501]

      [Thr 47815365664608] Enqueue server start with instance number 12

      ------------------------------------------------

      Best Regards

      Ahmed

  • author's profile photo Former Member
    Former Member
    Posted on Sep 23, 2013 at 08:35 AM

    Hi,

    Have you checked the below note.

    1249256 - Locks are lost during failover

    Thanks

    Rishi Abrol

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Ahmed Ibrahim

      When you reallocate CI service to other node the ASCS instance (and enqueue server) remains on the same node with its lock table. No failover occur. The tests you performed are necessary to monitor enqueue server failover to check enqueue ID and number of locks copied.

  • Posted on Sep 23, 2013 at 08:42 AM

    Hello,

    Possible error that I can see is ERS instance number if different on node 1 and node 2. Please make sure that the replication server must create the replicate with the same instance number that is used by the standalone enqueue server.

    Thanks

    Sunny

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Sunny Pahuja

      All you have quoted is valid for polling concept. Please read this link to the end:

      • Some HA software solutions do not offer the concept that a software package obeys another package on this packageā€™s host. For this reason SAP has introduced the polling concept: Here, a replication server runs on every possible failover host, and does not have to be controlled by the HA software. Whether you need this or not depends on your HA software. For more information, contact your HA software partner.

      Red Hat Clustering contains Follow Service Dependency which allows you to setup ERS as a cluster resource.

  • author's profile photo Former Member
    Former Member
    Posted on Sep 24, 2013 at 02:22 PM

    Hello Ahmed,

    This might be helpful,

    http://scn.sap.com/thread/1666119

    Regards,

    Naga

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 26, 2013 at 08:17 AM

    Dear All

    I notes the following error in the trace file DEV_ENQSRV after lock table content lost

    ---------------------------------------------------

    trc file: "dev_enqsrv", trc level: 1, release: "720"

    ---------------------------------------------------

    sysno 12

    sid S1C

    systemid 390 (AMD/Intel x86_64 with Linux)

    relno 7200

    patchlevel 0

    patchno 430

    intno 20020600

    make multithreaded, Unicode, 64 bit, optimized

    pid 25066

    [Thr 47930438192992] Thu Sep 26 10:15:25 2013

    [Thr 47930438192992] profile /usr/sap/S1C/SYS/profile/S1C_ASCS12_scascs

    [Thr 47930438192992] hostname scmdb

    [Thr 47930438192992] Listen successful on port/service sapdp12

    [Thr 47930438192992] Thu Sep 26 10:15:26 2013

    [Thr 47930438192992] EnqInitCleanupServer: Shm of enqueue table (rc = 3) does not exist, nothing to clean up

    [Thr 47930438192992] ShadowTable:attach: ShmCreate(,SHM_ATTACH,) -> 2aab3e200000

    [Thr 47930438192992] EnRepClass::getReplicaData: found old replication table with the following data:

    [Thr 47930438192992] Line size:744, Line count: 89144, Failover Count: 0

    [Thr 47930438192992] EnqId: 1380112831/8767, last stamp: 1/380179531/3000

    [Thr 47930438192992] Byte order tags: int:1159934994 char:Z

    [Thr 47930438192992] initialize_global: Enqueue server started with replication functionality

    [Thr 47930438192992] Enqueue: EnqMemStartupAction Utc=1380179726

    [Thr 47930438192992] EnqLockTableCreate: create lock table (size = 102400000)

    [Thr 47930438192992] EnqLockTableMapToLocalContext: enque/use_pfclock2 = FALSE

    [Thr 47930438192992] Thu Sep 26 10:15:28 2013

    [Thr 47930438192992] Enqueue checkpointing: start restoring entries. Utc=1380179728

    [Thr 47930438192992] Delete replication table which was attached by the enqueue server

    [Thr 47930438192992] ShadowTable:destroy: ShmCleanup( SHM_ENQ_REP_SHADOW_TBL)

    [Thr 47930438192992] *** ERROR => ShadowTable:destroy: failed to delete SHM (rc=2) [enreptbl.cpp 723]

    [Thr 47930438192992] enque/backup_file disabled in enserver environment

    [Thr 47930438192992] Thu Sep 26 10:15:29 2013

    [Thr 47930438192992] ***LOG GEZ=> Server start [encllog.cpp 501]

    [Thr 47930438192992] Enqueue server start with instance number 12

    -----------

    kindly check the error

    thanks

    Ahmed

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 26, 2013 at 10:06 AM

    Dear All ,

    for your information only , i am not losing content of the lock table in case adding the content by the following command

    > enqt pf=/usr/sap/SID/SYS/profile/SID_ERS10_scers 11 20

    only in case if i modifying DataBase records for example modifying User Master record

    Best Regards

    Ahmed

    Add a comment
    10|10000 characters needed characters exceeded

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.