Scribd Logo
Upload

Welcome to Scribd!

  • SAP Issues 4 June 2015

    Uploaded by

    Garry360
    7 views1 page
    All SAP servers shut down due to a UPS failure. To resolve, the steps taken were to manually start all SAP servers by stopping and starting services, ensure the SAP router was up before servers, and address a Sybase transaction log space issue that was preventing users from logging on to the development system.

    Original Description:

    SAP Issues 4 June 2015

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    All SAP servers shut down due to a UPS failure. To resolve, the steps taken were to manually start all SAP servers by stopping and starting services, ensure the SAP router was up before servers, and address a Sybase transaction log space issue that was preventing users from logging on to the development system.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    7 views1 page

    SAP Issues 4 June 2015

    Uploaded by

    Garry360
    All SAP servers shut down due to a UPS failure. To resolve, the steps taken were to manually start all SAP servers by stopping and starting services, ensure the SAP router was up before servers, and address a Sybase transaction log space issue that was preventing users from logging on to the development system.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Issue- All SAP Servers shut down.

    RCA- UPS failure


    Resolution:
    1. Manually Start all the SAP servers
    a. MSTSC
    b. ASF-DATA\sap.operator OR AFSInfrastructure >> SIDADM
    c. Services. MSc > stop all services (e.g. 3+2 Sybase)
    d. MMC (all SAP DEV, QA, PRD servers, except MSCS. Cluster Server)
    e. Start SAP (CI+DB)
    2. SAPROUTER system should be UP and running before all. (for ABAP
    connection over internet)
    a. CMD
    b. Saprouter -r
    3. CLUSTER :
    4. Sybase (Users unable to logon to DEV system. MMC shows Green> DPMON
    > killed dispatchers > DEV_DISP / W* points SYBASE issue: DB
    connection >> Copy Sybase log to Desktop > Analyse >
    TRANSACTION LOG SPACE issue >> ):
    a. Mstsc
    b. Logon as : sybSID
    c. CMD > isql uspsa PAsf@2014 SECD X
    d. dump transaction ECD <i.e. SID> using config = ECDLOG

    You might also like