cancel
Showing results for 
Search instead for 
Did you mean: 

Run time error READ_SWITCHSTATES_FAILED when starting ECC CI

Former Member
0 Kudos

Hi Friends,

We are running ECC 6.0 in clustor mode we have DB server and ECC CI server in clustor having HP-UX 11i v3 and Oracle 11g.

Now CI package is running on DB server, we are trying to move CI package from DB to CI server but CI package is showing status at OS level is running on CI server but when we are trying to login in SAS then it is giving the error dump READ_SWITCHSTATES_FAILED. Other than CI we have 3 DI application instances.

Please find the below dump detail.

Runtime Errors         READ_SWITCHSTATES_FAILED
Date and Time          12.04.2013 01:02:02

     For further help in handling the problem, contact your SAP administrator
     .

     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.


Error analysis
     The error when importing the current switch configuration into an
     internal switch status buffer can occur if the read enqueue lock, which
     is requested from the datatabase for consistent reading, is rejected due
      to a parallel change operation on this database.

     Furthermore, it could also be an internal problem preventing the request
      of the required enqueue lock.

     Specifically, the error situation in this case is described under 2 in
      the following:

     (1) A lock collision occurred when requesting the enqueue lock
      "E_ABAP_SWTSTATE".
         This enqueue lock is currently helb by user " " with enqueue owner
         ID " ".
     (2) The enqueue server rejects the enqueue request for the enqueue lock
         "E_ABAP_SWTSTATE" with the internal error code 8.
         Check any existing enqueue server entries in the developer trace.

Your valuable support is most awaited.

Regards

Ganesh Datt Tiwari

Accepted Solutions (1)

Accepted Solutions (1)

former_member188883
Active Contributor
0 Kudos

Hi Ganesh,

Refer SAP

Note 1392449 - Runtime error: READ_SWITCHSTATES_FAILED

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

Thanks for your valuable reply.

As we have SAP_BASIS 700 and patch is 25.

The given note is in patch 22.

Regards

Ganesh Datt Tiwari

former_member188883
Active Contributor
0 Kudos

Hi Ganesh,

It looks to me that, Enqueue services are not running correctly when you failover.

Could you confirm the following for your installation

1 ) Describe the instances installed on Node 1

2) Describe the instances installed on Node 2

3) Have you installed Enqueue replication server . If yes, which node ?

4) Please the full abap dump.

Regards,

Deepak Kori

former_member189546
Active Contributor
0 Kudos

Hello,

The user  " " locked a lot of objects objects and
that throws the current shortdumps during the usage of "E_ABAP_SWTSTATE"
object.

You can avoid the short dump by increasing the enque/table_size normally.

Please double enque/table_size to a maximun of 250,000

regards,

John Feely

former_member188883
Active Contributor
0 Kudos

Hi John,

Don't you feel enque/table_size to a maximun of 250,000 value is too high ?

Also has this problem been identified before ?

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

1. ECC CI Instance on Node1

2. ECC DB Instance on Node2.

3. There are 3 other ECC DI instacneces running on different server.

      a. ECCAPP1 on Node 1 (ECCCI)

      b. ECCAPP2 on Node 2 (ECCDB)

      c. ECC APP3 on Node3

3. No Enqueue server installed separately.

4.  Dump Detail

Runtime Errors         READ_SWITCHSTATES_FAILED
Date and Time          11.04.2013 23:49:54

Short text
     Error creating a switch status buffer

What happened?
     The import of the current switch configuration from the database into an
     internal switch status buffer has failed.

What can you do?
     Note which actions and input led to the error.

     For further help in handling the problem, contact your SAP administrator
     .

     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.


Error analysis
     The error when importing the current switch configuration into an
     internal switch status buffer can occur if the read enqueue lock, which
     is requested from the datatabase for consistent reading, is rejected due
      to a parallel change operation on this database.

Furthermore, it could also be an internal problem preventing the reques
of the required enqueue lock.

Specifically, the error situation in this case is described under 2 in
the following:

(1) A lock collision occurred when requesting the enqueue lock
"E_ABAP_SWTSTATE".
    This enqueue lock is currently helb by user " " with enqueue owner
    ID " ".
(2) The enqueue server rejects the enqueue request for the enqueue lock
    "E_ABAP_SWTSTATE" with the internal error code 8.
    Check any existing enqueue server entries in the developer trace.

Information on where terminated
    Termination occurred in the ABAP program "CL_ABAP_SWITCH================CP" -
     in "GET_SWITCH_STATE".
    The main program was "SAPLSMTR_NAVIGATION ".

    In the source code you have the termination point in line 2
    of the (Include) program "CL_ABAP_SWITCH================CM001".

Source Code Extract

Line  SourceCde

    1 method GET_SWITCH_STATE by kernel module ab_km_getSwitchState.
>>>>> endmethod.

Active Calls/Events

No.   Ty.          Program                             Include                             Line
      Name

   13 METHOD       CL_ABAP_SWITCH================CP    CL_ABAP_SWITCH================CM001     2
      CL_ABAP_SWITCH=>GET_SWITCH_STATE
   12 FUNCTION     SAPLSFW_COMMON                      LSFW_COMMONU02                         16
      SFW_GET_SW_STATUS
   11 FUNCTION     SAPLSHI25                           LSHI25U02                              60
      STREE_SFW_CHECK_NODES_ACTIVE
   10 FUNCTION     SAPLSHI2                            LSHI2U06                              264
      STREE_READ_SINGLE_LAYER_GENER
    9 FUNCTION     SAPLSHI2                            LSHI2U07                               96
      STREE_READ_MULTI_LAYER_GENER
    8 FUNCTION     SAPLSHI1                            LSHI1U01                              103
      STREE_STRUCTURE_READ_N_LEVEL
    7 FUNCTION     SAPLSHI1                            LSHI1U14                               74
      STREE_STRUCTURE_READ_N_TOP_LEV
    6 FUNCTION     SAPLSHI6                            LSHI6U08                               38
      STREE_HIERARCHY_READ
    5 FUNCTION     SAPLSMNU_NEW                        LSMNU_NEWU02                          130
      MENU_GET_MENU_TREE_PART
    4 FUNCTION     SAPLSMTR_NAVIGATION_MODULES         LSMTR_NAVIGATION_MODULESU01           128
      NAVIGATION_LOAD_MENU_DATA
    3 FORM         SAPLSMTR_NAVIGATION                 LSMTR_NAVIGATIONF11                    14
      HELP_FORM_LOAD_ALL

No.      13 Ty.          METHOD
Name  CL_ABAP_SWITCH=>GET_SWITCH_STATE

P_SWITCH_ID
    INS_FSCD
    000000000000000000000000000000
    000000000000000000000000000000
    445545442222222222222222222222
    9E3F63340000000000000000000000
P_CLIENT
    300
    000
    000
    333
    300
P_USERNAME

    000000000000
    000000000000
    222222222222
    000000000000
P_ONLY_ACTIVE_VERSION
    X
    0
    0
    5
    8
P_SWITCH_STATE

    0

%_SPACE

    0
    0
    2
    0
ABAP_TRUE
    X
    0
    0
    5
    8

No.      12 Ty.          FUNCTION
Name  SFW_GET_SW_STATUS

SWITCH
    INS_FSCD
    000000000000000000000000000000
    000000000000000000000000000000
    445545442222222222222222222222
    9E3F63340000000000000000000000
STATUS

    0
    0
    2
    0
SWITCHTAB[]
    Table IT_278[0x62]

Table IT_278[0x62]

\FUNCTION=STREE_SFW_CHECK_NODES_ACTIVE\DATA=SWITCHTAB

Table reference: 68

TABH+  0(20) = 0000000000000000C000000051A9822000000000

TABH+ 20(20) = 0000004400000116000000000000003EFFFFFFFF

TABH+ 40(16) = 040000A4000005600010249401800000

store        = 0x0000000000000000

ext1         = 0xC000000051A98220

shmId        = 0     (0x00000000)

id           = 68    (0x00000044)

label        = 278   (0x00000116)

fill         = 0     (0x00000000)

leng         = 62    (0x0000003E)

loop         = -1    (0xFFFFFFFF)

xtyp         = TYPE#000014

occu         = 16    (0x00000010)

access       = 1     (ItAccessStandard)

idxKind      = 0     (ItIndexNone)

uniKind      = 2     (ItUniqueNon)

keyKind      = 1     (default)

cmpMode      = 2     (cmpSingleMcmpR)

occu0        = 1

groupCntl    = 0

rfc          = 0

unShareable  = 0

mightBeShared = 0

sharedWithShmTab = 0

isShmLockId  = 0

gcKind       = 0

isUsed       = 1

    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC000000051A981B0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC000000051A86BF0
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
TEXT_LANGU

    000000000000000000000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000000000000000000000
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
SCREEN

SCREEN

    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY
    #######################################dž#########(###########################&#±###(###䵘 C#Ѐ>
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
    000000000000000000000000000000000000000C000000000200000000000000000000000000020B00020005240000
    00000100000000000000010A010001000000000600000000080000000000000000000000000006010008000803000C
%_DUMMY$$

    0000
    0000
    2222
    0000
SY-MANDT
    300
    000
    000
    333
    300
SWITCHTAB

    0000000000000000000000000000000
    0000000000000000000000000000000
    2222222222222222222222222222222
    0000000000000000000000000000000

Former Member
0 Kudos

Hi Friends,

Thanks to all of you for your kind support.

Issue has been resolved after setting the HP-UX 11iv3  kernel parameter shmmax. Command is given below

#kctune shmmax=0x40000000000

Regards

Ganesh Datt Tiwari

Answers (0)