Upgrade kernel

[Former Member]

Hello,

Our version: OS400 V5R1 EBCDIC DB2 sap 4.6C

I am upgraded kernel 46D package 2341 to kernel 46D EXt 64bit EBCDIC ( from CD - patch 1674).

Upgrade was right and I continued and uploaded patch sapkernel 2559 and saptools.

But after applying patch sap did not started.

I restored database sapkernel and I decided to repeat the whole process, but after upgrade to kernel 46D EXt 64bit EBCDIC ( from CD - patch 1674) SAP did not start. Sapstart dispatcher shut down after few seconds.

I found in log /usr/sap//work/dev_disp:

-

-

---

trc file: "dev_disp", trc level: 1, release: "46D"

-

-

---

Wed Jan 12 16:51:15 2011

relno 4640

patchlevel 0

patchno 1674

intno 0

pid 454

***LOG Q00=> DpSapEnvInit, DPStart (07 454) ¢dpxxdisp.c 918!

MtxInit: -2 0 0

• ERROR => ShmOsCreate: shmget(19909,1044480,1023) errno 3021 (3021: The

• ERROR => SemInMgt: Sema Mgt Table not init'd ¢semo4.c 382!

• ERROR => DpSysACreate: SemInMgt ¢dpxxtool2.c 532!

• ERROR => DpIPCInit: DpSysACreate ¢dpxxtool2.c 326!

• DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit

• DISPATCHER EMERGENCY SHUTDOWN ***

• ERROR => EvtRmMgt: Event Mgt not initialized ¢evto4.c 644!

• ERROR => ShmOsCreate: shmget(19909,1044480,1023) errno 3021 (3021: The

.......

....

If anyone has any ideas please reply.Thanks in advance for your answers.

Gabriel M.

[Former Member · Accepted solution]

Gabriel: you are already working with some of the best iSeries folks out there, but Volker always taught me to make sure the simple things were addressed, too. This suggestion worked on an earlier issue: when you applied the kernel, did you delete the SQL packages as well?

Other suggestions that have helped in the past: display your own joblog for the job where the SAP system is started; WRKSBMJOB *JOB to see what was submitted as part of the startup; WRKSPLF for sidOFR or sidNN; look in the .../work folder for any logs updated since you entered the command (WRKLNKSAP in the kernel library is very helpful for that).

[Former Member · Accepted solution]

Hello Jim,

I deleted the SQL packages before I starded sap.

New information for all :

When I import the new 46D ext kernel (patch 1674) then I rebooted server and sap started without problem.

Then I tried stopsap and startsap command several times and everything goes smoothly. Then I checked via transaction rz10 in SAP parameters for memory, but they look all right. Then I import the new patch and Sap did not start.I tried restarted server again, but same problem.Thanks to everyone for the support.

I found in log /usr/sap/<sid>/DVEBMGS<instid>/work/sapsart :

.....

.....

Command: /usr/sap/SA7/SYS/exe/run/disp+work pf=/usr/sap/SA7/SYS/profile/SA7_DVEBMGS07_AT51MIC1

Job started: 939449/SA707/DISP

(93) Starting: local /usr/sap/SA7/SYS/exe/run/disp+work pf=/usr/sap/SA7/SYS/profile/SA7_DVEBMGS07_AT51MIC1

(91) Starting local Command:

Command: /usr/sap/SA7/SYS/exe/run/SAPOSCOL

Job started: 939450/SA707/SAPOSCOL

(94) Starting: local /usr/sap/SA7/SYS/exe/run/SAPOSCOL

**(91) Waiting for Child Processes to terminate.**

***(91) **** 2011/01/14 09:50:36 Child 93 died due to Signal -1 . *******

***(91) **** 2011/01/14 09:50:36 Child 92 died due to Signal -1 . *******

***(91) **** 2011/01/14 09:52:07 Child 94 terminated with Status 0 . *******

**(91) No more Child Processes to wait for.**

**(91) Parent Shutdown at 2011/01/14 09:52:07**

AND in log usr/sap/<sid>/DVEBMGS<instid>/work/instatt :

***********Beginning of data*************

START_TIME 2011/01/14 09:50:32

START_PROF /usr/sap/SA7/SYS/profile/START_DVEBMGS07_AT51MIC1

SYSTEMNAME SA7

INST_NAME DVEBMGS07

CMD_LINE pf=/usr/sap/SA7/SYS/profile/START_DVEBMGS07_AT51MIC1

SHUTDWN_BY NO_MORE_CHILD_PROCESSES

SHUTDWN_AT 2011/01/14 09:52:07

EXIT_TIME 2011/01/14 09:52:10

EXIT_WITH 3 No more child processes

***********End of Data*******************

Gabriel M.

[Former Member]

SAPSTART is a good log to check in. If you look in the WORK folder/directory, are there any other logs for about that time? (I like to use WRKLNKSAP and sort by date/time) If you use WRKSPLF sidNN, or WRKSPLF sidOFR, are there any joblogs that may help? Doesn't seem like a failure of SAPOSCOL job would keep your SAP system from starting, but anything in that joblog? There is a note 175852 that refers to some SAPOSCOL authority problems, but again, it doesn't seem like an OSCOL problem would keep your system from starting.

[Former Member]

Hi Gabriel,

I would not ask why 16xx doesn't work ...

I STRONLGY recommend to upgrade to the LATEST 4.6D kernel and fix that - everything else is not supported anyway ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

[Former Member]

Hi Volker,

I don know why 46d ext kernel (patch 1674) first time worked and when I loaded a second time does not

work.

I have to upload the new ext kernel, because if I want to upload a new package hr SAPKE46CH0 I have to apply SAP note 1510174 and then note 1497003. In this note the condition is an upgrade to 46d ext minimum kernel patch 2551.

I need hr package SAPKE46CH0 so that I have uploaded a new lcp ce D3.

Gabriel Marcin

[Former Member]

Hi Gabriel,

ok, but as I said: you NEED the latest kernel and therefore, you shoudl ONLY fix the issue with the latest kernel.

In case of ermergency, we could help you ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

[Former Member]

After recording a new 46d ext kernel (patch 1674) even if there was a problem and shut down dispatcher I uploaded the last patch for this kernel 2559 but the error was the same dispatcher shut down after few seconds.

But I can not fix the problem. Thaks for your answer.

Gabriel

[thomas_obermeier]

Hi Gabriel,

Just a try: shut down the SID explicitly with STOPSAP. After that check if shared memory is cleared: Run

CLEANIPC INST(<nn>) OP(show)

where <nn> is your instance number. You should see

Number of IPC-Objects...........:    0

If not, run

CLEANIPC INST(<nn>) OP(remove)

If objects cannot be removed, run CLEANIPC with SECOFR authority.

After that try to start your system again.

Regards,

Thomas

[Former Member]

Hi Thomas,

I tried it, but I restored the old kernel and new kernel I deleted 1 hour ago. Now there are no objects for deletion. I will try again to record new 46D ext kernel.

Thanks

Gabriel

I used command CLEANIPC but there are no objects for deletion.

Gabriel

Edited by: GAMA05 on Jan 14, 2011 11:50 AM