Shadow instance not starting during the phase START_SHDI_PREPUT

    Hi ,

    We are in the process of performing a EHP6 upgrade, And it is in the preprocessing phase and it is executing the step START_SHDI_PREPUT.
    The SUM tools is trying to start the shadow instance, but the instance in no comming up. And we are getting the below errors in DEVTRACE.LOG

    *** ERROR => e=28 semget(20165,1,2016) (28: No space left on device) [semux.c      499]
    *** ERROR => SemRq: Implicit SemInit failed. Key=65 [semux.c      1183]
    *** ERROR => Es2Cleanup: SemRq SEM_ES2_ADM (rc=1) [es2xx.c      1086]

    *** ERROR => e=28 semget(20127,1,2016) (28: No space left on device) [semux.c      499]
    SemKeyPermission( 28 ) = 0740 (octal)

    *** ERROR => ShmCleanup(62) failed 3 [mpixx.c      4451]
    MpiCleanup() -> MPI_ERROR: General error
    DpCleanupSharedResources: removing Semaphore-Management
    DpCleanupSharedResources: removing request queue

    And we have followed the snote 724713 and we have set the parameter pg_contig_disable=1 and created the project for users <sid>adm, ora<sid> as per the same note.

    Also, we have a RAM of about 64GB and swap space of 39GB

    Please can you help me know, what is lacking in this scenario.

    Best regards, SP

    Hi , We are in the process of performing a EHP6 upgrade, And it is in the preprocessing phase and it is executing the step START_SHDI_PREPUT. The SUM tools is trying to start the shadow instance, but the instance in no comming up. And we are getting the below errors in DEVTRACE.LOG*** ERROR => e=28 semget(20165,1,2016) (28: No space left on device) [semux.c      499] *** ERROR => SemRq: Implicit SemInit failed. Key=65 [semux.c      1183] *** ERROR => Es2Cleanup: SemRq SEM_ES2_ADM (rc=1) [es2xx.c      1086]*** ERROR => e=28 semget(20127,1,2016) (28: No space left on device) [semux.c      499] SemKeyPermission( 28 ) = 0740…

    Shadow instance not starting during the phase START_SHDI_PREPUT

    Very Helpfull

    User Rating: Be the first one !
    Default Asked on November 2, 2016 in enhancement packages.
    Add Comment
    1 Answer(s)

      Make sure the SAP system is stopped completely (primary and shadow) before you execute the cleanipc command.

      If you have stopped the SAP system before running this command then start the main system.

      Once the main system has been started then start the shadow system as follows.

      su – sidadm

      cd <Upgrade_directory>/abap/bin

      ./SAPup startshd

       

      Regards

      RB

      Add Comment

        Make sure the SAP system is stopped completely (primary and shadow) before you execute the cleanipc command.

        If you have stopped the SAP system before running this command then start the main system.

        Once the main system has been started then start the shadow system as follows.

        su – sidadm

        cd <Upgrade_directory>/abap/bin

        ./SAPup startshd

         

        Regards

        RB

        Add Comment

        Your Answer

        By posting your answer, you agree to the privacy policy and terms of service.