COMPUTE_BCD_OVERFLOW in st22

Hi guys, my 4.6C system in st22 show u201CCOMPUTE_BCD_OVERFLOWu201D
The dump detail show:
ABAP runtime errors    COMPUTE_BCD_OVERFLOW
Occurred on 12.05.2010 at 17:15:07
Overflow for arithmetical operation (type P) in program "SAPLSTUW "            
What happened?
The current ABAP/4 program "SAPLSTUW " had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
A value does not fit in a calculation field.
If you require an interim solution to this error, you can look in the SAP note system. If you have access to
the SAP notes system yourself, enter the following search strings:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
point)
"SAPLSTUW " or "LSTUWF01 "
"CONVERT_PFDIAREC"
Appreciate anyone have any ideal what is going on?
Thanks

Hi,
Please search for SAP Notes for your system and patch level.
This sort of error usually occurs when the amounts involved are too big for the program to handle. The ABAP will be trying to write to a table or structure which does not have enough space.
Get an ABAPer to work with you and analyse the short dump (ST22 will take you there). Then run the proposal in debug mode and see where it drops out. Once you have identified the table or structure get your basis people to allocate more space to it, re-index it or generally kick it into shape.
Regards,
Shitij

Similar Messages

  • COMPUTE_BCD_OVERFLOW ST22 dump

    Dear All,
    When I run the ECC_PRD_BITX_D_FDM_INVOICE, which is a standard SAP(program FDM_INVOICE_MEMORY).
    I get COMPUTE_BCD_OVERFLOW ST22 dump.
    This short dump occured due to CX_SY_ARITHMETIC_OVERFLOW i.e. Target field size was not able to store the value of source field at the folowing code location while assigning value to l_days_of_delay.
       90       ENDIF.
       91
       92 *     set actual discount and delay in payment
    >>>>>       l_days_of_delay = sy-datlo
       94                       - <open_item>-zfbdt
       95                       - <open_item>-zbd1t.
    Are there SAP Notes that can solve this problem?
    My system details
    S/w Component : SAP_APPL
    Release : 604
    Highest Support : SAPKH60405
    sapnote_0000620532, sapnote_0001239612 , sapnote_0001323002 do not work in my system
    Regards,
    Jack Silverz

    hi jack,
    just check these avalilabe notes for your dump.
    620532
    1323002
    1239612
    hope this will help u.
    thanks

  • ABAP DUMP in ST03N : COMPUTE_BCD_OVERFLOW

    HI Guys,
         When I go to ST03N, Expert Mode, Select the Daily workload, I double clicked on 15.03.2010, the system will hit the abap dump : COMPUTE_BCD_OVERFLOW. However, when I try for other dates, it is fine. Which meant it is only the 15.03.2010 causing the dump.
        following is the system's details:
         SAP R/3 Kernel :              640_REL
         Kernel Patch  :                304
         SAP BASIS  : SAPKB62041
        I have raised a OSS message to SAP, and the consultant had replied me with two sapnotes:
         881968
         840763.
        I've implemented the 881968 but there is some error after implement, the ST03N cannot be executed. ( ABAP DUMP syntax error). Hence, I revoked the sapnote 881968. For the 840763, I did not implement since it advised to upgrade the support package for SAP BASIS and I am not sure what is affected after I upgrade the support package.
        The system I mentioned above is not a BW system and I doubt this is why I get the SYNTAX ERROR dump after implement the sapnote.
        Did you guys encountered similar problem? Any solution for this?
        The following is ABAP DUMP: COMPUTE_BCD_OVERFLOW:
    Runtime Errors         COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
           Occurred on     29.03.2010 at 09:37:45
    Overflow for arithmetical operation (type P) in program "SAPWL_ST03N"
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPWL_ST03N" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    A value does not fit in a calculation field.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
    was neither
    caught nor passed along using a RAISING clause, in the procedure
    "CALCULATE_PROFILE" "(METHOD)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    An overflow has been determined in the current arithmetical operation
    containing operands of type P. Possible causes include:
    1.  The results field of type P is to small and the result does not fit
        into it.
        places.
    2.  The result or partial result has more than 31 decimal places.
    Edited by: Wei Jian Kwan on Mar 30, 2010 3:57 AM

    Hi Amber,
        The following sapnote is not implementable in my system:
         0001384846 ST03N: BCD_OVERFLOW in SAPWL_LCL_03N_HITLNRESPTI
         This is due to the current Support Pack : SAP BASIS in my system is : SAPKB62041 and the corrections in the sapnote are only available for 700 until 720.
    Best Regards,
    Ken

  • COMPUTE_BCD_OVERFLOW MIRO Incoming Invoice

    Hi, Gurus,
    I have extended most of my domains successfully and everything seems fine until in MM when the MM consultant tries to simulate or save in trans MIRO, a short dump appears saying the above. I have look at the position specified in the dump and BETRAG and PX_DRSEG-WRBTR reference the same domain which has the same number of characters so, it seems here things are OK. But there is that dump as follows:
    Runtime Errors         COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          05.06.2008 09:49:32
    Short text
         Overflow during the arithmetical operation (type P) in program "SAPLMRMP".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLMRMP" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
          caught in
         procedure "SPERRGRUND_T" "(FORM)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
       The reason for the exception is:
       An overflow was discovered in an ongoing arithmetical operation with
       operands of type P. Possible causes are:
       1. The result field of type P is too small for the result.
       2. The result or a intermediate result has more than 31 decimal places.
    ow to correct the error
       The result field must be enlarged, if this is still possible. It may
       also be possible to break up the current process into subprocesses so
       that only smaller values occur.
       There may already be a solution to the error in the SAP notes system.
       If you have access to the SAP notes system first try searching with the
       following keywords:
        "COMPUTE_BCD_OVERFLOW"
        "BCD_FIELD_OVERFLOW" (Until release 4.0a, this runtime error occurred at this
        position)
        "SAPLMRMP" or "LMRMPF1K"
        "SPERRGRUND_T"
       If you cannot solve the problem yourself and want to send an error
       notification to SAP, include the following information:
       1. The description of the current problem (short dump)
          To save the description, choose "System->List->Save->Local File
       (Unconverted)".
       2. Corresponding system log
        Display the system log by calling transaction SM21.
        Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
        In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SPERRGRUND_T" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    tem environment
    SAP-Release 700
    Application server... "dev"
    Network address...... "10.0.0.81"
    Operating system..... "SunOS"
    Release.............. "5.9"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "tetradev"
    Database type..... "ORACLE"
      Database name..... "DEV"
      Database user ID.. "SAPSR3"
      Char.set.... "C"
      SAP kernel....... 700
      created (date)... "Aug 31 2006 20:59:23"
      create on........ "SunOS 5.9 Generic_117171-13 sun4u"
      Database version. "OCI_102 (10.2.0.2.0) "
      Patch level. 75
      Patch text.. " "
      Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
      SAP database version. 700
      Operating system..... "SunOS 5.9, SunOS 5.10"
      Memory consumption
      Roll.... 16192
      EM...... 16759392
      Heap.... 0
      Page.... 188416
      MM Used. 9422712
      MM Free. 3143832
    er and Transaction
      Client.............. 300
      User................ "USER01"
      Language key........ "E"
      Transaction......... "MIRO "
      Program............. "SAPLMRMP"
      Screen.............. "SAPLMR1M 6000"
      Screen line......... 34
    Information on where terminated
        Termination occurred in the ABAP program "SAPLMRMP" - in "SPERRGRUND_T".
        The main program was "SAPLMR1M ".
        In the source code you have the termination point in line 39
        of the (Include) program "LMRMPF1K".
        The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"
         occurred in
        procedure "SPERRGRUND_T" "(FORM)", but it was neither handled locally nor
         declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLMRMP "; its source code begins in line
        12 of the (Include program "LMRMPF1K ".
    Source Code Extract
    Line  SourceCde
        9 * --> PI_XNULLPOS: Liegt eine Nullpos. vor?  (wenn ja: keine Verarb.)  *
       10 * <-> PX_DRSEG: Struktur mit den aktuell zu bearbeitenden Pos.daten    *
       11 ----
       12 FORM SPERRGRUND_T USING    PI_RBKPV TYPE MRM_RBKPV
       13                            PI_XNULLPOS LIKE BOOLE-BOOLE
       14                   CHANGING PX_DRSEG TYPE MMCR_DRSEG.
       15
       16   CHECK PI_XNULLPOS = SPACE.           "keine Nullpos.
       17
       18   DATA s_t169g TYPE t169g.
       19   SELECT SINGLE * FROM t169g INTO s_t169g
      20                   WHERE   bukrs = px_drseg-bukrs
      21                     AND    tolsl = 'ST'.
      22   check sy-subrc = 0.
      23   IF NOT s_t169g-xw2ne IS INITIAL.
      24     EXIT.
      25   ENDIF.
      26   DATA: datum1 LIKE sy-datum,
      27         DATUM2 LIKE SY-DATUM.
      28   DATA: DT_DIFF(8) TYPE C.
      29
      30   CHECK: PI_RBKPV-XRECH NE SPACE,
      31          PX_DRSEG-RETPO = SPACE,  "keine Sperre durch eine Retoure-Pos.
      32          PX_DRSEG-EINDT NE '00000000',
      33          PX_DRSEG-PSTYP NE C_PSTYP_1,  " keine Blanket PO
      34          PX_DRSEG-FPLNR IS INITIAL.    " kein Rechnungsplan
      35
      36   DATUM1 = SY-DATLO.
      37   DATUM2 = PX_DRSEG-EINDT.
      38   CHECK DATUM2 > DATUM1.
    >>>>   BETRAG = PX_DRSEG-WRBTR * ( DATUM2 - DATUM1 ).
      40   DT_DIFF = ( DATUM2 - DATUM1 ).
      41
      42   SY-SUBRC = 0.
      43   CALL CUSTOMER-FUNCTION '001'
      44        EXPORTING I_RBKPV  = PI_RBKPV
      45                  I_YDRSEG  = PX_DRSEG
      46        EXCEPTIONS CALL_FAILURE = 001.
      47   CASE SY-SUBRC.
      48     WHEN 001.
      49       MESSAGE E271 RAISING PARAMETER_ERROR.
      50   ENDCASE.
      51
      52   RC = 0.
      53   CALL FUNCTION 'MRM_TOLERANCE_CHECK'
      54        EXPORTING
      55             I_AKT_WERT       = BETRAG
      56             I_BUKRS          = PX_DRSEG-BUKRS
      57             I_TOLSL          = 'ST'
      58             I_VERGLEICHSWERT = '0.00'
    Please assist as urgently as possible. Assistance will be rewarded.
    Thanx in advance.
    Edited by: Darlington Chiyamha on Jun 5, 2008 11:06 AM

    Hi Darlington,
    You usually get that, if a number you calculate i getting bigger than the field it is stored in allows.
    Check the data declaration of the variable which holds this value. If the resultant value is too large then the ABAP throws this exception.
    You may handle this using CATCH ENDCATCH statement.
    Check this e.g.:
    PARAMETERS fact TYPE i.
    DATA: fact_save TYPE i,
    res(16) TYPE p.
    ARITHMETIC_ERRORS contains COMPUTE_BCD_OVERFLOW ***
    CATCH SYSTEM-EXCEPTIONS ARITHMETIC_ERRORS = 5.
    res = fact_save = fact.
    SUBTRACT 1 FROM fact.
    DO fact TIMES.
    MULTIPLY res BY fact. "<- COMPUTE_BCD_OVERFLOW
    SUBTRACT 1 FROM fact.
    ENDDO.
    ENDCATCH.
    IF sy-subrc = 5.
    WRITE: / 'Overflow! Factorial of', fact_save,
    'can not be calculated.'.
    ELSE.
    WRITE: / 'Factorial of', fact_save, 'gives', res.
    ENDIF.
    Edited by: Raj on Jun 5, 2008 2:43 PM

  • COMPUTE_BCD_OVERFLOW -  CX_SY_ARITHMETIC_OVERFLOW

    Hello all,
    I'm getting the ABAP Dump in CJ13 tcode please find below dump error & my system release info:
    Component version    SAP ECC 6.0
    SAP_ABA      700     0010     SAPKA70010
    SAP_BASIS     700     0010     SAPKB70010
    SAP_APPL     600     0006     SAPKH60006
    Kernel release    700 (Sup.Pkg lvl.      52)
    Begin of Dump -
    Runtime Errors         COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          07.04.2008 11:53:18
    Short text
         Overflow during the arithmetical operation (type P) in program "SAPLKBPR".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLKBPR" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also keep them for a long time.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
         caught in procedure "READ_COSA" "(FORM)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is:
         An overflow was discovered in an ongoing arithmetical operation with
        operands of type P. Possible causes are:
        1. The result field of type P is too small for the result.
        2. The result or a intermediate result has more than 31 decimal places.
    Regards,

    HI,
    My patch level is below but even i got a dump of "COMPUTE_BCD_OVERFLOW".
    Component       Lvl    
    SAP_ABA     0019
    SAP_BASIS     0019
    Pls. suggest.
    Thanks in advance.

  • Getting dump everyday COMPUTE_BCD_OVERFLOW

    Hello Everybody,
    Everyday at particular time we are getting COMPUTE_BCD_OVERFLOW runtime error.
    At same there is no failed jobs..........
    =========================
    Runtime Error          COMPUTE_BCD_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
           Occurred on     17.05.2010 at   09:15:41
    Overflow for arithmetical operation (type P) in program "SAPLXM06"
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLXM06" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    A value does not fit in a calculation field.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    User, transaction...
    Client.............. 600
    User................ "INTE"
    Language key........ "E"
    Transaction......... "ME22 "
    Program............. "SAPLXM06"
    Screen.............. "SAPMM06E 0120"
    Screen line......... 88
    Information on where terminated
    The termination occurred in the ABAP program "SAPLXM06" in "WRITE_LIST".
    The main program was "SAPMM06E ".
    The termination occurred in line 124 of the source code of the (Include)
    program "ZXM06F01"
    of the source code of program "ZXM06F01" (when calling the editor 1240).
    The program "SAPLXM06" was started as a background job.
    Error occurred during batch input processing
    Processing was terminated because the exception "CX_SY_ARITHMETIC_OVERFLOW"
    occurred in the
    procedure "WRITE_LIST" "(FORM)" but was not handled locally, not declared in
    theRAISING clause of the procedure.
    The procedure is in the program "SAPLXM06 ". Its source code starts in line 69
    of the (Include) program "ZXM06F01 ".
    =====================================
    Please advice us on this.
    Thanks in advance.
    Regards,
    Pratyusha

    Hi,
    What is your SAP release ?
    I am not sure if it applicable for your problem..
    Have a look at the below note
    [Note 869851 - Field overflow with large purchase order quantities|https://service.sap.com/sap/support/notes/869851]
    Regards.
    Rajesh Narkhede

  • St22 show u201CCOMPUTE_BCD_OVERFLOWu201D and st03 stop at running

    Hi guys, my 4.6C system in st22 show u201CCOMPUTE_BCD_OVERFLOWu201D and st03 stop at running at 08.05.2010.
    The dump detail show:
    ABAP runtime errors COMPUTE_BCD_OVERFLOW
    Occurred on 12.05.2010 at 17:15:07
    Overflow for arithmetical operation (type P) in program "SAPLSTUW "
    What happened?
    The current ABAP/4 program "SAPLSTUW " had to be terminated because one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    A value does not fit in a calculation field.
    If you require an interim solution to this error, you can look in the SAP note system. If you have access to
    the SAP notes system yourself, enter the following search strings:
    "COMPUTE_BCD_OVERFLOW"
    "BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
    point)
    "SAPLSTUW " or "LSTUWF01 "
    "CONVERT_PFDIAREC"
    Appreciate anyone can help and have any ideal what is going on?
    Thanks

    Try this note: SAP Note 1384846 - ST03N: BCD_OVERFLOW in
    SAPWL_LCL_03N_HITLNRESPTI
    and also check SAP note 881124
    It is a good idea if you give all the system information at the beginning so assistance can be more relevant.
    Maybe you should start pushing SAP for an update.

  • Dunning - ST22- Exception in GET_DUNNING_CUSTOMIZING FM.

    Hi Experts,
    Issue is,
    When the user ran the Dunning report on July 16th, (selection criteria is--> July 16th & From customer 1 TO customer 999999999), bcoz of some thing, at CUST_444, the Exception was raised (say, for customers CUST_111, CUST_222, CUST_333, its successful), saying that...ABAP/4 processor: RAISE_EXCEPTION and it stopped there/job cancelled!
    So, now, again when the user wants to(subsequent running of dunning report) run the report for customer 1 to 999999999, SAP is blocking CUST_111, CUST_222, CUST_333 reports and saying already printed on July 16th!
    ST22- Exception in GET_DUNNING_CUSTOMIZING FM.
    So, How to fix it? I guess, we hv to delete the July 16th history report, If so, How to delete it?
    thanq.
    Message was edited by:
            Srikhar

    Hi Sheshu,
    If u get chance, pls. culd u respond to my other thread, title is,
    <i><b>SM 30 -
    AUTHORITY-CHECK OBJECT 'XXX' ??</b></i>
    search criteria: authority-check object
    area: abap general-abap development
    time: 7 days.
    Pls. clarify my doubts, sent to Roman!
    I copied and paste the same code to my requiremetn, after declaring necessory data part, but not working!
    if u did not find the thread , pls. let me know!
    thanq.

  • ST22 short dump with error DFIF_REPO_SQL_ERROR

    HI, All
    SAP ERP 2004s on windows 2003x64 with SQLserver database.
    Here is ST22 and dev_w0
    20.03.2014                                      Dynamic List Display                                              1
    Runtime Error
    |Date      |Time    |Host      |User  |Client|Keep|Name of runtime error|Exception|Appl. component|Report|No. Sess|
    |20.03.2014|08:48:44|clusterx64|SAPSYS|000  |C  |DBIF_REPO_SQL_ERROR  |        |              |      |1      |
    |20.03.2014|08:18:44|clusterx64|SAPSYS|000  |C  |DBIF_REPO_SQL_ERROR  |        |              |      |1      |
    D:\usr\sap\PRD\DVEBMGS00\work\dev_w0
    trc file: "dev_w0", trc level: 1, release: "640"
    *  ACTIVE TRACE LEVEL          1
    *  ACTIVE TRACE COMPONENTS      all, M
    B
    B Mon Mar 17 13:26:13 2014
    B  create_con (con_name=R/3)
    B  Loading DB library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' ...
    B  Library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' loaded
    B  Version of 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.405)
    B  New connection 0 created
    M sysno      00
    M sid        PRD
    M systemid  562 (PC with Windows NT)
    M relno      6400
    M patchlevel 0
    M patchno    414
    M intno      20020600
    M make:      multithreaded, Unicode, 64 bit
    M pid        4544
    M
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4544) [dpxxdisp.c  1227]
    I  MtxInit: -2 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpShMCreate: sizeof(wp_adm) 58560 (1464)
    M  DpShMCreate: sizeof(tm_adm) 38387184 (19184)
    M  DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
    M  DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
    M  DpShMCreate: sizeof(comm_adm) 1248000 (624)
    M  DpShMCreate: sizeof(vmc_adm) 0 (512)
    M  DpShMCreate: sizeof(wall_adm) (400056/346328/64/192)
    M  DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000B9B0050, size: 40479544)
    M  DpShMCreate: allocated sys_adm at 000000000B9B0050
    M  DpShMCreate: allocated wp_adm at 000000000B9B1C30
    M  DpShMCreate: allocated tm_adm_list at 000000000B9C00F0
    M  DpShMCreate: allocated tm_adm at 000000000B9C0118
    M  DpShMCreate: allocated wp_ca_adm at 000000000DE5BF08
    M  DpShMCreate: allocated appc_ca_adm at 000000000DE61CC8
    M  DpShMCreate: allocated comm_adm_list at 000000000DE63C08
    M  DpShMCreate: allocated comm_adm at 000000000DE63C20
    M  DpShMCreate: allocated vmc_adm_list at 000000000DF94720
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 000000000DF94748
    M  DpShMCreate: allocated wall_adm at 000000000DF947B8
    M  DpRqQInit: Parameter rdisp/queue_lock_level = 2
    M  ThTaskStatus: rdisp/reset_online_during_debug 0
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M  tskhstart: taskhandler started
    M  tskh_init: initializing DIA work process W0
    M  tskh_init: rdisp/cleanup_after_crash = 1
    M
    M Mon Mar 17 13:26:15 2014
    M  calling db_connect ...
    C  Thread ID:3128
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  CopyLocalParameters: dbuser is 'prd'
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.
    C
    C Mon Mar 17 13:26:16 2014
    C  Provider Release:9.00.4035.00
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.
    C
    C Mon Mar 17 13:26:22 2014
    C  Cache sizes: header 104 bytes, 20000 names (32960000 bytes), 1000 dynamic statements (5752000 bytes), total 38712104 bytes
    C  Using shared procedure name cache SAPPRDX64_PRDPRD_PRD_MEM initialized by another process.
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: prd
    C  pn_id:SAPPRDX64_PRDPRD_PRD
    C  Using MARS (on sql 9.0)
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    M  db_connect o.k.
    M  ICT: exclude compression: *.zip,*.cs,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.js,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png
    I
    I Mon Mar 17 13:26:26 2014
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF (addr: 0000000016320050, size: 41613000)
    M  SHM_ROLL_AREA (addr: 000007FFC4050050, size: 268435456)
    M  SHM_PAGING_AREA (addr: 0000000018AD0050, size: 134217728)
    M  SHM_ROLL_ADM (addr: 0000000020AE0050, size: 2678942)
    M  SHM_PAGING_ADM (addr: 0000000020D70050, size: 787488)
    M  ThCreateNoBuffer allocated 544152 bytes for 1000 entries at 0000000020E40050
    M  ThCreateNoBuffer index size: 3000 elems
    M  ThCreateNoBuffer: correct_btc_behaviour = 1
    M  ThCreateVBAdm allocated 12176 bytes (50 server) at 0000000020ED0050
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    X  ES initialized.
    B  dbntab: NTAB buffers attached
    B  dbntab: Buffer FTAB(hash header)  (addr: 0000000020F700D8, size: 584)
    B  dbntab: Buffer FTAB(anchor array) (addr: 0000000020F70320, size: 6240232)
    B  dbntab: Buffer FTAB(item array)  (addr: 0000000021563B08, size: 24960000)
    B  dbntab: Buffer FTAB(data area)    (addr: 0000000022D31708, size: 128000000)
    B  dbntab: Buffer IREC(hash header)  (addr: 000000002A7500D8, size: 584)
    B  dbntab: Buffer IREC(anchor array) (addr: 000000002A750320, size: 6240232)
    B  dbntab: Buffer IREC(item array)  (addr: 000000002AD43B08, size: 6240000)
    B  dbntab: Buffer IREC(data area)    (addr: 000000002B337208, size: 13312000)
    B  dbntab: Buffer STAB(hash header)  (addr: 000000002BFF00D8, size: 584)
    B  dbntab: Buffer STAB(anchor array) (addr: 000000002BFF0320, size: 6240232)
    B  dbntab: Buffer STAB(item array)  (addr: 000000002C5E3B08, size: 6240000)
    B  dbntab: Buffer STAB(data area)    (addr: 000000002CBD7208, size: 3072000)
    B  dbntab: Buffer TTAB(hash header)  (addr: 00000000350400D8, size: 4744)
    B  dbntab: Buffer TTAB(anchor array) (addr: 0000000035041360, size: 6240232)
    B  dbntab: Buffer TTAB(item array)  (addr: 0000000035634B48, size: 15600000)
    B  dbntab: Buffer TTAB(data area)    (addr: 00000000365154C8, size: 113880000)
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 40, CON_ID = -1
    B  dbstat: TABSTAT buffer attached (addr: 000000002CEEEA58)
    B  dbtbxbuf: Buffer TABL  (addr: 000000003D1C0150, size: 263640000, end: 000000004CD2D510)
    B  dbtbxbuf: Buffer TABLP (addr: 000000002E780150, size: 61440000, end: 0000000032218150)
    B  dbexpbuf: Buffer EIBUF (addr: 000000004CD30158, size: 122880000, end: 0000000054260158)
    B  dbexpbuf: Buffer ESM  (addr: 0000000032230158, size: 4194304, end: 0000000032630158)
    B  dbexpbuf: Buffer CUA  (addr: 0000000054270158, size: 30720000, end: 0000000055FBC158)
    B  dbexpbuf: Buffer OTR  (addr: 0000000032640158, size: 4194304, end: 0000000032A40158)
    B  dbcalbuf: Buffer CALE  (addr: 0000000032A50050, size: 500000, end: 0000000032ACA170)
    M  rdisp/reinitialize_code_page -> 0
    M  icm/accept_remote_trace_level -> 0
    M  rdisp/no_hooks_for_sqlbreak -> 0
    M  rdisp/hold_keeps_time_slice -> 0
    M  CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    G  RelWritePermissionForShm( pLocation = 120, pEnforce = 0 )
    G  GetWritePermissionForShm( pLocation =  99, pEnforce = 1 )
    G  RelWritePermissionForShm( pLocation = 100, pEnforce = 1 )
    S  *** init spool environment
    S  TSPEVJOB updates outside critical section: event_update_nocsec = 1
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 0000000010E29190
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  3 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)  = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 00000000331C00C0
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 00000000331C0C58
    S    using messages for server info
    S  size of spec char cache entry: 297032 bytes (timeout 100 sec)
    S  size of open spool request entry: 2512 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A
    A  ---PXA-------------------------------------------
    A  PXA INITIALIZATION
    A  System page size: 4kb, total admin_size: 50852kb, dir_size: 25348kb.
    A  Attached to PXA (address 000007FFD4080050, size 720000K, 2 fragments of 334576K )
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  ---PXA-------------------------------------------
    A
    A  ABAP ShmAdm attached (addr=000007FF26F71000 leng=20955136 end=000007FF2836D000)
    A  >> Shm MMADM area (addr=000007FF2741D070 leng=246976 end=000007FF27459530)
    A  >> Shm MMDAT area (addr=000007FF2745A000 leng=15806464 end=000007FF2836D000)
    A  RFC Destination> destination clusterx64_PRD_00 host clusterx64 system PRD systnr 0 (clusterx64_PRD_00)
    A  RFC Options> H=clusterx64,S=00,d=2
    A  RFC FRFC> fallback activ but this is not a central instance.
    A  
    A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 2
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC abap/SIGCHILD_default not set, use default value: 0
    A  RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    M  ThrCreateShObjects allocated 83148 bytes at 0000000033330050
    Y  dyWpInit
    Y    ztta/dynpro_ara 800000
    Y    ztta/cua_ara    360000
    Y    ztta/diag_ara  250000
    N  SsfSapSecin: putenv(SECUDIR=D:\usr\sap\PRD\DVEBMGS00\sec): ok
    N
    N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is D:\usr\sap\PRD\SYS\exe\run\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...sucessfully completed.
    N  =================================================
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    W  =================================================
    W  === ipl_Init() called
    B    dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
    B    max_blocking_factor =  50,  max_in_blocking_factor      = 255,
    B    min_blocking_factor =  5,  min_in_blocking_factor      =  10,
    B    prefer_union_all    =  1,  prefer_union_for_select_all =  0,
    B    prefer_fix_blocking =  0,  prefer_in_itab_opt          =  0,
    B    convert AVG        =  1,  alias table FUPD            =  0,
    B    escape_as_literal  =  0,  opt GE LE to BETWEEN        =  0,
    B    select *            =0x00,  character encoding          = STD / []:X,
    B    use_hints          = abap->1, dbif->0x1, upto->0, rule_in->0,
    B                          rule_fae->0, concat_fae->0, concat_fae_or->0,
    B    join_conforms_iso  =  1
    W    ITS Plugin: Path dw_gui
    W    ITS Plugin: Description ITS Plugin - ITS rendering DLL
    W    ITS Plugin: sizeof(SAP_UC) 2
    W    ITS Plugin: Release: 640, [6400.0.414.20020600]
    W    ITS Plugin: Int.version, [32]
    W    ITS Plugin: Feature set: [29]
    W    ===... Calling itsp_Init in external dll ===>
    W  === ipl_Init() returns 0, ITSPE_OK: OK
    W  =================================================
    E  Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume clusterx64_PRD_00
    E  Profile-Parameter: enque/sync_dequeall = 0
    E  Replication is disabled
    E  EnqCcInitialize: local lock table initialization o.k.
    E  EnqId_SuppressIpc: local EnqId initialization o.k.
    E  EnqCcInitialize: local enqueue client init o.k.
    S
    S Mon Mar 17 13:26:31 2014
    S  server @>SSRV:clusterx64_PRD_00@< appears or changes (state 1)
    S  server @>SSRV:clusterx64_PRD_00@< appears or changes (state 1)
    B
    B Mon Mar 17 13:26:34 2014
    B  table logging switched off for all clients
    N
    N Mon Mar 17 13:26:44 2014
    N  login/password_change_for_SSO : 1 -> 1
    M  SecAudit(RsauShmInit): WP attached to existing shared memory.
    M  SecAudit(RsauShmInit): addr of SCSA........... = 0000000005990050
    M  SecAudit(RsauShmInit): addr of RSAUSHM........ = 00000000059907B8
    M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 00000000059907F0
    M  SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 00000000059907FC
    M  SecAudit(check_daily_file): audit file opened D:\usr\sap\PRD\DVEBMGS00\log\20140317000001.AUD
    D
    D Mon Mar 17 13:26:51 2014
    D  GuiStatus: table test
    D  GuiStatus set generate inline  >20140317132651<
    D  GuiStatus clear generate inline  >20140317132651<
    B
    B Mon Mar 17 13:27:00 2014
    B  dbmyclu : info : my major identification is 3232240218, minor one 0.
    B  dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
    B  dbmyclu : info : my uuid is C8157D392BFA064AAC992593949203BE.
    B  dbmyclu : info : current optimistic cluster level: 3
    B  dbmyclu : info : pessimistic reads set to 2.
    G
    G Mon Mar 17 13:27:03 2014
    G  GetWritePermissionForShm( pLocation = 283, pEnforce = 0 )
    G
    G Mon Mar 17 13:27:04 2014
    G  RelWritePermissionForShm( pLocation = 277, pEnforce = 0 )
    G  GetWritePermissionForShm( pLocation = 281, pEnforce = 0 )
    G  RelWritePermissionForShm( pLocation = 277, pEnforce = 0 )
    M  ThEMsgArrived: sysmsg_for_rfc = 0
    G
    G Mon Mar 17 13:27:18 2014
    G  GetWritePermissionForShm( pLocation = 281, pEnforce = 0 )
    G  RelWritePermissionForShm( pLocation = 277, pEnforce = 0 )
    A
    A Mon Mar 17 13:31:19 2014
    A  ***ATRA: session closed by other process
    D
    D Mon Mar 17 13:35:06 2014
    D  GuiStatus generation SAPLSUU5 is not running
    Y  go to separate LUW generation ===> 20140317133506
    Y    GuiStatus generate texts: SAPLSUU5 M
    Y  return from separate LUW <=== WP: 1 th_rc=0 OK
    G
    G Mon Mar 17 13:35:16 2014
    G  GetWritePermissionForShm( pLocation = 281, pEnforce = 0 )
    G  RelWritePermissionForShm( pLocation = 277, pEnforce = 0 )
    M
    M Mon Mar 17 13:40:02 2014
    M  ThIUsrDel: th_rollback_usrdelentry = 1
    A
    A Mon Mar 17 13:44:07 2014
    A  ***ATRA: session closed by other process
    B
    B Mon Mar 17 13:46:35 2014
    B  create_con (con_name=++DBO++0020)
    B  New connection 1 created
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 1 opened (DBSL handle 1)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000001 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    S
    S Mon Mar 17 13:51:33 2014
    S  found spool memory service RSPO-ACTIONS at 00000000331C9090
    D
    D Mon Mar 17 14:05:56 2014
    D  GuiStatus generation RSSTAT26 is not running
    Y  go to separate LUW generation ===> 20140317140556
    Y    GuiStatus generate: RSSTAT26 SELECT            
    Y
    Y Mon Mar 17 14:05:57 2014
    Y  return from separate LUW <=== WP: 2 th_rc=0 OK
    Y  go to separate LUW generation ===> 20140317140557
    Y    GuiStatus generate texts: RSSTAT26 E
    Y  return from separate LUW <=== WP: 1 th_rc=0 OK
    D
    D Mon Mar 17 14:06:11 2014
    D  GuiStatus generation RSSTAT50 is not running
    Y  go to separate LUW generation ===> 20140317140611
    Y    GuiStatus generate: RSSTAT50 0010              
    Y
    Y Mon Mar 17 14:06:12 2014
    Y  return from separate LUW <=== WP: 1 th_rc=0 OK
    Y  go to separate LUW generation ===> 20140317140612
    Y    GuiStatus generate texts: RSSTAT50 E
    Y  return from separate LUW <=== WP: 1 th_rc=0 OK
    Y
    Y Mon Mar 17 14:07:10 2014
    Y
    Y  ===> running separate LUW generation: 20140317140710
    Y    ===> requesting WP: 1
    Y    GuiStatus generate: SAPMSRD0 MAIN_NEW          
    D  GuiStatus generate status prog >SAPMSRD0< status >MAIN_NEW<  >20140317140710<
    D  GuiStatus set generate inline  >20140317140710<
    D  GuiStatus clear generate inline  >20140317140710<
    Y
    Y  ===> running separate LUW generation: 20140317140710
    Y    ===> requesting WP: 1
    Y    GuiStatus generate texts: SAPMSRD0 E
    D  GuiStatus generate texts prog >SAPMSRD0<  >20140317140710<
    D  GuiStatus set generate inline  >20140317140710<
    D  GuiStatus clear generate inline  >20140317140710<
    Y
    Y Mon Mar 17 14:23:12 2014
    Y
    Y  ===> running separate LUW generation: 20140317142312
    Y    ===> requesting WP: 1
    Y    GuiStatus generate: RSMSSDBPAHI 0100              
    D  GuiStatus generate status prog >RSMSSDBPAHI< status >0100<  >20140317142312<
    D  GuiStatus set generate inline  >20140317142312<
    D  GuiStatus clear generate inline  >20140317142312<
    B
    B Mon Mar 17 14:31:34 2014
    B  create_con (con_name=++DBO++0020)
    B  New connection 2 created
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      YES NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000016 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000017 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 143134 SAPPRDX64                  
    B
    B Mon Mar 17 14:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,17,2}
    B
    B Mon Mar 17 15:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000030 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000031 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 153136 SAPPRDX64                  
    B
    B Mon Mar 17 15:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,31,2}
    B
    B Mon Mar 17 16:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C
    C Mon Mar 17 16:31:37 2014
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000044 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000045 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 163136 SAPPRDX64                  
    B
    B Mon Mar 17 16:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,45,2}
    B
    B Mon Mar 17 17:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000058 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000059 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 173136 SAPPRDX64                  
    B
    B Mon Mar 17 17:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,59,2}
    B
    B Mon Mar 17 18:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000072 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000073 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 183136 SAPPRDX64                  
    B
    B Mon Mar 17 18:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,73,2}
    B
    B Mon Mar 17 19:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000086 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000087 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 193136 SAPPRDX64                  
    B
    B Mon Mar 17 19:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,87,2}
    B
    B Mon Mar 17 20:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000100 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000101 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 203136 SAPPRDX64                  
    B
    B Mon Mar 17 20:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,101,2}
    B
    B Mon Mar 17 21:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000116 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000117 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 213136 SAPPRDX64                  
    B
    B Mon Mar 17 21:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,117,2}
    B
    B Mon Mar 17 22:31:37 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000130 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000131 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 223137 SAPPRDX64                  
    B
    B Mon Mar 17 22:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,131,2}
    B
    B Mon Mar 17 23:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000144 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000145 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140317 233136 SAPPRDX64                  
    B
    B Mon Mar 17 23:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,145,2}
    M
    M Tue Mar 18 00:01:33 2014
    M  SecAudit(check_daily_file): audit file closed D:\usr\sap\PRD\DVEBMGS00\log\20140317000001.AUD
    M  SecAudit(check_daily_file): audit file opened D:\usr\sap\PRD\DVEBMGS00\log\20140318000001.AUD
    B
    B Tue Mar 18 00:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000158 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000159 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 003136 SAPPRDX64                  
    B
    B Tue Mar 18 00:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,159,2}
    B
    B Tue Mar 18 01:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000172 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000173 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 013136 SAPPRDX64                  
    B
    B Tue Mar 18 01:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,173,2}
    B
    B Tue Mar 18 02:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000186 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000187 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 023136 SAPPRDX64                  
    B
    B Tue Mar 18 02:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,187,2}
    B
    B Tue Mar 18 03:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000200 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000201 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 033136 SAPPRDX64                  
    B
    B Tue Mar 18 03:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,201,2}
    B
    B Tue Mar 18 04:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000214 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000215 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 043136 SAPPRDX64                  
    B
    B Tue Mar 18 04:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,215,2}
    B
    B Tue Mar 18 05:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000230 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000231 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 053136 SAPPRDX64                  
    B
    B Tue Mar 18 05:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,231,2}
    B
    B Tue Mar 18 06:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000244 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000245 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 063136 SAPPRDX64                  
    B
    B Tue Mar 18 06:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,245,2}
    B
    B Tue Mar 18 07:31:36 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000258 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000259 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 073136 SAPPRDX64                  
    B
    B Tue Mar 18 07:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,259,2}
    B
    B Tue Mar 18 08:31:41 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140317 132615 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000272 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000273 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 083141 SAPPRDX64                  
    B
    B Tue Mar 18 08:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,273,2}
    C  RpcExec: line 12553. hr: 0x80004005 Communication link failure
    C  sloledb.cpp [RpcExec,line 12553]: Error/Message: (err 10054, sev 0), Communication link failure
    C  Procname: [Y3R40000001F9FG0332RSEUMODut01i1o211ns]
    C  sloledb.cpp [RpcExec,line 12553]: Error/Message: (err 10054, sev 0), TCP Provider: An existing connection was forcibly closed by the remote host.
    C  Procname: [Y3R40000001F9FG0332RSEUMODut01i1o211ns]
    C  RpcExec failed.  HR 80004005 DBSL retcode 99. proc: [Y3R40000001F9FG0332RSEUMODut01i1o211ns]
    C  Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:1128862
    C  DbSlRead - Error 99 (dbcode 10054) on open
    C  DbSlRead - <Y3R40000001F9FG0332RSEUMODut01i1o211ns>
    C  DbSlRead - Error 99 (dbcode 10054) on fetch
    C  DbSlRead - <Y3R40000001F9FG0332RSEUMODut01i1o211ns>
    C  SET_EC p->msgno 10054 p->severity 0
    C  dbca_p->errclass set to DBSL_EC_RESTART
    B  ***LOG BYM=> severe DB error 10054    ; work process in reconnect status [dbsh#4 @ 1127] [dbsh    1127 ]
    B  ***LOG BY4=> sql error 10054  performing SEL on table RSEUMOD    [dbtrtab#5 @ 3988] [dbtrtab 3988 ]
    B  ***LOG BY0=> [10054] TCP Provider: An existing connection was forcibly closed by the remote host.
    [10054] Communication link failure [dbtrtab#5 @ 3988] [dbtrtab 3988 ]
    B  *** ERROR => missing return code handler
    abdebug#?[17989] does not handle return code 1 from dbcrtab#6[1596]
    ==> calling sap_dext to abort transaction
    [dbeh.c      84]
    C  RpcExec: line 12553. hr: 0x80004005 Communication link failure
    C  sloledb.cpp [RpcExec,line 12553]: Error/Message: (err 10054, sev 0), Communication link failure
    C  Procname: [Y3R40000001F1CN2138T100ut01i3o4ns]
    C  sloledb.cpp [RpcExec,line 12553]: Error/Message: (err 10054, sev 0), TCP Provider: An existing connection was forcibly closed by the remote host.
    C  Procname: [Y3R40000001F1CN2138T100ut01i3o4ns]
    C  RpcExec failed.  HR 80004005 DBSL retcode 99. proc: [Y3R40000001F1CN2138T100ut01i3o4ns]
    C  Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:1112522
    C  DbSlRead - Error 99 (dbcode 10054) on open
    C  DbSlRead - <Y3R40000001F1CN2138T100ut01i3o4ns>
    C  DbSlRead - Error 99 (dbcode 10054) on fetch
    C  DbSlRead - <Y3R40000001F1CN2138T100ut01i3o4ns>
    C  SET_EC p->msgno 10054 p->severity 0
    C  dbca_p->errclass set to DBSL_EC_RESTART
    B  ***LOG BYM=> severe DB error 10054    ; work process in reconnect status [dbsh#4 @ 1127] [dbsh    1127 ]
    B  ***LOG BY4=> sql error 10054  performing SEL on table T100      [dbtrtab#5 @ 3988] [dbtrtab 3988 ]
    B  ***LOG BY0=> [10054] TCP Provider: An existing connection was forcibly closed by the remote host.
    [10054] Communication link failure [dbtrtab#5 @ 3988] [dbtrtab 3988 ]
    C  RpcExec: line 12553. hr: 0x80004005 Communication link failure
    C  sloledb.cpp [RpcExec,line 12553]: Error/Message: (err 10054, sev 0), Communication link failure
    C  Procname: [Y3R40000001F1CN2138T100ut01i3o4ns]
    C  sloledb.cpp [RpcExec,line 12553]: Error/Message: (err 10054, sev 0), TCP Provider: An existing connection was forcibly closed by the remote host.
    C  Procname: [Y3R40000001F1CN2138T100ut01i3o4ns]
    C  RpcExec failed.  HR 80004005 DBSL retcode 99. proc: [Y3R40000001F1CN2138T100ut01i3o4ns]
    C  Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:1112522
    C  DbSlRead - Error 99 (dbcode 10054) on open
    C  DbSlRead - <Y3R40000001F1CN2138T100ut01i3o4ns>
    C  DbSlRead - Error 99 (dbcode 10054) on fetch
    C  DbSlRead - <Y3R40000001F1CN2138T100ut01i3o4ns>
    C  SET_EC p->msgno 10054 p->severity 0
    C  dbca_p->errclass set to DBSL_EC_RESTART
    B  ***LOG BYM=> severe DB error 10054    ; work process in reconnect status [dbsh#4 @ 1127] [dbsh    1127 ]
    B  ***LOG BY4=> sql error 10054  performing SEL on table T100      [dbtrtab#5 @ 3988] [dbtrtab 3988 ]
    B  ***LOG BY0=> [10054] TCP Provider: An existing connection was forcibly closed by the remote host.
    [10054] Communication link failure [dbtrtab#5 @ 3988] [dbtrtab 3988 ]
    C  TestConnection: line 7344. hr: 0x80004005 Unable to open a logical session
    C  sloledb.cpp [TestConnection,line 7344]: Error/Message: (err 10054, sev 0), Unable to open a logical session
    C  Procname: [TestConnection - no proc]
    C  sloledb.cpp [TestConnection,line 7344]: Error/Message: (err 10054, sev 0), TCP Provider: An existing connection was forcibly closed by the remote host.
    C  Procname: [TestConnection - no proc]
    C  Rollback: TestConnection(0) failed with dbcode 10054
    C  TestConnection: line 7344. hr: 0x80004005 Unable to open a logical session
    C  sloledb.cpp [TestConnection,line 7344]: Error/Message: (err 10054, sev 0), Unable to open a logical session
    C  Procname: [TestConnection - no proc]
    C  sloledb.cpp [TestConnection,line 7344]: Error/Message: (err 10054, sev 0), TCP Provider: An existing connection was forcibly closed by the remote host.
    C  Procname: [TestConnection - no proc]
    C  Rollback: TestConnection(1) failed with dbcode 10054
    C  SET_EC p->msgno 10054 p->severity 0
    C  dbca_p->errclass set to DBSL_EC_RESTART
    B  ***LOG BYM=> severe DB error 10054    ; work process in reconnect status [dbsh#4 @ 1127] [dbsh    1127 ]
    B  Reconnect state is entered by connection:
    B  000: name = R/3, con_id = 000000000, state = ACTIVE      , tx = NO , hc = NO , perm = YES,
    B      reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    B  hdl_error_on_commit_rollback: DB-ROLLBACK detected RECONNECT state
    M  ThShortCommit: db unusable
    B  RECONNECT: rsdb/reco_trials: 3
    B  RECONNECT: rsdb/reco_sleep_time: 5
    B  RECONNECT: rsdb/reco_sync_all_server: OFF
    B  db_con_reconnect: reconnecting to connection 0:
    B  000: name = R/3, con_id = 000000000, state = INACTIVE    , tx = NO , hc = NO , perm = YES,
    B      reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    B  disconnecting from connection 0 ...
    B  disconnected from connection 0
    B  opening connection 0 ...
    C  Thread ID:3128
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  CopyLocalParameters: dbuser is 'prd'
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.
    C  Provider Release:9.00.4035.00
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.
    C  Cache sizes: header 104 bytes, 20000 names (32960000 bytes), 1000 dynamic statements (5752000 bytes), total 38712104 bytes
    C  Using shared procedure name cache SAPPRDX64_PRDPRD_PRD_MEM initialized by another process.
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: prd
    C  pn_id:SAPPRDX64_PRDPRD_PRD
    C  Using MARS (on sql 9.0)
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140318 085133 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000279 INACTIVE    NO  NO  NO  NO  NO  003 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000273 DISCONNECTED NO  NO  NO  NO  NO  000 255 255 20140318 085133 SAPPRDX64                  
    B  successfully reconnected to connection 0
    B  ***LOG BYY=> work process left reconnect status [dblink#6 @ 732] [dblink  0732 ]
    B
    B Tue Mar 18 09:31:35 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C
    C Tue Mar 18 09:31:36 2014
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140318 085133 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000286 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000287 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 093135 SAPPRDX64                  
    B
    B Tue Mar 18 09:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,287,2}
    B
    B Tue Mar 18 10:31:35 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO  NO  000 255 255 20140318 085133 SAPPRDX64                  
    B  000 001 ++DBO++0020                    000000300 ACTIVE      YES NO  NO  NO  NO  004 255 255 20140317 134635 SAPPRDX64                  
    B  000 002 ++DBO++0020                    000000301 ACTIVE      NO  NO  NO  NO  NO  004 255 255 20140318 103135 SAPPRDX64                  
    B
    B Tue Mar 18 10:51:33 2014
    B  Disconnected from connection con_da={++DBO++0020,301,2}
    B
    B Tue Mar 18 11:31:35 2014
    B  Connect to ++DBO++0020 as  with MSSQL_SERVER=SAPPRDX64 MSSQL_DBNAME=PRD OBJECT_SOURCE=prd
    C  Thread ID:3128
    C  dbmssslib.dll patch info
    C    patchlevel  0
    C    patchno      405
    C    patchcomment Poor performance with isolation level read committed (1721164)
    C  Network connection used from SAPPRD2X64 to SAPPRDX64 using tcp:SAPPRDX64
    C  Connected to db server : [SAPPRDX64] server_used : [tcp:SAPPRDX64], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDX64_PRD_PRD
    B  Connection 2 opened (DBSL handle 2)
    B  Wp  Hdl ConName                        ConId    ConState    TX  HC  PRM RCT FRC TIM MAX OPT Date    Time  DBHost                      
    B  000 000 R/3                            000000000 ACTIVE      NO  NO  YES NO 

    Hi All,
    We need to activate 0SR_DEFCUR currency object. I have activated the object and transported. Issue is resolved.
    Thanks to all for your kind replied.
    Regards,
    Don

  • T-code or Table to find total errors in SAP APO like ST22 in ABAP

    hi all,
    Could please tell me the T-code or Table to find total errors in SAP APO like ST22 t-code in SAP ABAP.
    Thanks.
    Suryam S

    Hello Venu,
    Do you mean other functional errors?
    You can check SLG1, /SAPAPO/C3, STAD
    Best Regards,
    R.Brahmankar

  • ST22 , Need to  get the Transaction and Pgm name using a FUNCTION MODULE ?

    Hi All,
    I need to create a Report for monitoring Dumps which is seen in ST22 every day.
    The function module RS_ST22_GET_DUMPS gives the dump information . But i need to fetch the Program name and the transaction where the dump has happened for my report.(Like when we double click the alv output in ST22 and the next list gives us the complete information , Transaction , Main program name ...etc)
    Kindly suggest me and help me on this .
    Regards,
    Richard A

    Hi
    Funcion module RS_ST22_GET_DUMPS will return the program names where the dump has taken place.
    Pass this program name to function module RPY_TRANSACTION_READ to get the trascation code of the program.
    Regards
    Srilaxmi

  • SAP ST22 dump SAPSQL_ARRAY_INSERT_DUPREC

    Hi All,
    We are getting dump SAPSQL_ARRAY_INSERT_DUPREC in testing system. SAP basis: 701 and Oracle 10.2.0.2
    We are getting this dump from yesterday only and the details of the dump are as mentioned below:
    ============================================================================================
    Short text
        The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it
         has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
         in
        procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", nor was it propagated
         by a RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        If you use an ABAP/4 Open SQL array insert to insert a record in
        the database and that record already exists with the same key,
        this results in a termination.
        (With an ABAP/4 Open SQL single record insert in the same error
        situation, processing does not terminate, but SY-SUBRC is set to 4.)
    Information on where terminated
        Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
         "BAL_DB_INTERNAL_NO_UPDATE_TASK".
        The main program was "SWNCCOLL ".
        In the source code you have the termination point in line 64
        of the (Include) program "LSBAL_DB_INTERNALU02".
        The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
        Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
        Job Initiator.. "BASIS"
        Job Number..... 08893100
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
         handled locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins
         line
        1 of the (Include program "LSBAL_DB_INTERNALU02 ".
    System environment
        SAP-Release 701
        Application server... "appl543"
        Network address...... "122.99.01.88"
        Operating system..... "AIX"
        Release.............. "5.3"
        Hardware type........ "099DER88BN90000"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 27
        Shortdump setting.... "full"
        Database server... "appl543"
        Database type..... "ORACLE"
        Database name..... "Q22"
        Database user ID.. "SAPSR3"
    =====================================================================================================
    Also some jobs are cancelled and they are forming the above dump. the detials are:
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 00:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 02:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 03:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 04:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 05:43:31
    SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 06:43:31
    **The cancelled job SAP_COLLECTOR_FOR_NONE_R3_STAT generating the above dump at ST22.**
    Please suggest us a solution. Thanks in advance!!!
    Regards
    Veera
    Edited by: Veerab on Dec 17, 2010 11:33 AM

    >     1 of the (Include program "LSBAL_DB_INTERNALU02 ".
    Try the following:
    open http://service.sap.com/notes
    Search for "LSBAL_DB_INTERNALU02"
    Markus

  • Reading Short Dump in ST22

    Hi , Is there any Function Module or a way  to read the Short Dump generated in ST22 for a particular program.?
    I have a Z program running in Background on daily basis.For error Handling , when the program generates a short dump , i want to read the short dump. I tried the FM  /SDF/GET_DUMP_LOG .with this i am able to read the  runtime error , exception , error short text  but i am unable to read the entire log description.
    like what happened , what can u do etc  which can be viewed in st22.Any Inputs Appreciated.
    Thanks & Regards,
    John.

    Hi,
    Try FM
    "STRUCTURE_DUMP"     -- Current contents of internal tables will be printed
    RS_SNAP_DUMP_DISPLAY
    Best regards,
    Prashant

  • TIME_OUT in ST22 while loading data

    Hello all!
    While I load data from ODS-object to an InfoCube, after around 18 minutes I have the first TIME_OUT in ST22. Some seconds later I have the next and then again after 18 minutes and so on. All the time while loading. The loading doesn´t stop.
    I found the following statement in ST22:
    The program "GP2GCXJX3UPKBEN0B528IGJFPA3 " has exceeded the maximum permitted runtime and has therefore been terminated.
    But loading is still running.
    This programm is the programm which is generated from the update rules which can be found in the update rules under ->Extras ->Display Activated Programm in the menu there.
    I found also the information in ST22 that "rdisp/max_wprun_time" is 1000 seconds (16.66 minutes) which is the max. runtime. I think there is a second chance so the max. runtime should be 2000 seconds.
    But I think "rdisp/max_wprun_time" is a parameter for dialog processes and loading over InfoPackage isn´t one as far as I know.
    I load as a backround process. I´m loading from ODS and reading in update rules from 2 other ODS-objects. I read around 2 million records. Another IC which is very similar but doesn´t read from the 2nd ODS needs around 1 and a half hour to load.
    Can someone please help me?
    Thank you,
    Peter

    Peter,
    Update rules are processed in foreground and the time out setting applies to all dialog processes. The processing is done one data packet at a time.
    If the load is from ODS to InfoCube and is timing out then there is no option but to tune the update rules. Bring down the records that are being read. If your select statement is reading based on the contents of the data packet, then bring down the size of the data packet. THis can be done in the InfoPack in Scheduler --> DataS. Default Data Transfer. In the Max size field try 10000 or even 5000. Number of data pakckets will increase but processing time per packet should be lower.
    Another option is to find the ODS PSA request in the PSA Tree. ODS PSA Request number is the request number right before the REQU number in the ODS requests tab. They begin with ODSR.... Find this in the PSA and update to data target from there. This processing is then done in the background and the time out setting does not apply.
    If you do not see the request then turn on display generated object from the menu of the admin workbench Settings --> Display Generated Objects
    Cheers
    Aneesh

  • How to delete the short dump list in st22

    Hi all,
              i want to clear the runtime error list in ST22.
    How to clear the list of short dump in ST22.
    is there any T.code kindly suggest
    thanks in advance
    Sundar.c

    Dear Sundar,
    By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
    Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
    The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
    1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
    ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
    2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
    3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
    4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
    Hope this information resolves your error and also more useful in the feature.
    Thanks
    Kishore

Maybe you are looking for

  • Why are web pages smaller on new pc (Windows 8.1) in Firefox 36.0 and how can I fix it?

    I have just moved from an old pc running Vista to a new one running Windows 8.1. When I set it up the first thing I did was download the latest version of Firefox. Not sure what version I had on the Vista machine, but this is FF 36.0. Then I synced m

  • I'm having trouble with a Text Field and a Time Format

    I have created a form. There are many text fields for clients to fill out. One Field have been formatted to enter a time. Ex. 6:00pm. This works great unless it's a 12:00am time then the field reads 00:00am I would rather it read 12:00 am. How can I

  • Windows server 2003 cannot find the media player plug in

    i have searched for hours now and cant find the needed plug in for the recent update on fire fox for windows server 2003

  • I phone 4 network signal issue after updating 4.0.1

    hello friends please help me on this issue urgently i purchased iPhone 4 working absolutely fine then i update ios from 4.0 to 4.01 now i got network issues signal not showing full... what i do please help me urgently on this issue pleasr Rgds Mohit

  • Expdp over network fails.

    I have a test1 and test2 db's on two different servers. I want to run expdp from test2 db and get the export of a table from test1. I have created a db link and used network_link in expdp command. Granted read,write on directory to user with which i