cancel
Showing results for 
Search instead for 
Did you mean: 

Shadow instance not starting during the phase START_SHDI_PREPUT

Former Member
0 Kudos


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

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

If possible stop the primary system

Clean the shared memory segments

Start the primary system and then try to start the shadow system manually.

Regards

RB

Former Member
0 Kudos

hi Reagan,

Thanks for the reply.

Is there any command that could help us in cleaning the shared memory segments.

Best regards SP

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello SP

su - sidadm

cleanipc 00 remove

Replace 00 with the right system number.

If possible restart the server and that would do the work.

Regards

RB

Former Member
0 Kudos

Hi Reagan,

Thanks for the recommendations, when i execute cleanipc for sap system it shows as below,

Show/Cleanup SAP-IPC-Objects V2.3, 94/01/20
===========================================

+-------------------------------------------------+
| To inhibit destruction of valid SAP-IPC-Objects |
| during shutdown, this program requires now      |
| special options for removing IPC-Objects.       |
+-------------------------------------------------+

Running SAP-Systems (Nr)...:

----------------------------------------------------------
---- Show IPC-Objects of Sap-System  0 -------------------
----------------------------------------------------------

Number of IPC-Objects...........:    0
Summary of all Shared Memory....:        0.3 MB (may be incomplete when not in superuser mode)


Number of SAP_ES files found:.............:    0
Number of SAP_ES files removed:...........:    0

seems like, there is no such file types.

And is it that my  shared memory is low, do you have any recommendations on that.

Best Regards, SP

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

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

Former Member
0 Kudos

Hi Reagan,

Yes, Manually starting the shadow instance from the upgrade directory helped. And the upgrade is in progress.

Answers (1)

Answers (1)

Former Member
0 Kudos

The environments are  Solaris 10 and Oracle 11g.