update process is not working Properly in ECC 6.0

[Former Member]

Hi!!!!!!!!!!!!!!

We have upgraded our patch level in Ecc 6.0 ,after applying these patches our any update process has been stucked .Its not doing any type of updates in the system.Lots of database update requests are listed in SM13 (For update process) and all update processes are showing the status busy in SM50 .

Our Patch level details are given below.

SAP_BASIS 700 0021 SAPKB70021 SAP Basis Component

SAP_ABA 700 0021 SAPKA70021 Cross-Application Component

Please suggest some solution ASAP.

Thanks and regards

Anil

[Former Member]

Have you updated the kernel along with the support packages?

Kind regards,

Mark

[Former Member]

No my Boss tolde me that is not mandatory to do because the tp other necessary exe are alrady update before patching..

[Former Member]

Can you check the dev_ traces in the work directory?

Kind regards,

Mark

[Former Member]

You might have a problem at database level.. Is there anything full? archive logs, tablespace, maximum number of extents, filesystem?

Kind regards,

Mark

[Former Member]

i have checked mount point at os level,tablespace, every thing i checked related to space , even i login to the oracle database, and i create a table then insert the data properly that is ok...

[Former Member]

Can you check the dev_enq log and other dev_ traces.

Kind regards,

Mark

[Former Member]

Hi,

Please check the below things

1) Check if the update process is active or incative in SM14. If it is inactive then activate the same.

2) Check for the free space in Table space. If tablespace is filled then extend the same.

3) Check if there are any dead locks in DB01. If it is then check with whose login and what process the lock is there and ask the user to log off from the system.

4) Check in SM50 for update work process which job or program it is running and with whose login.

Regards,

Sharath

[Former Member]

HI Sharath

thanks for your immediate responce..

1) Check if the update process is active or incative in SM14. If it is inactive then activate the same.

Ans>> that is active

2) Check for the free space in Table space

Ans>> No problem of space in there.

3) Check if there are any dead locks in DB01. If it is then check with whose login and what process the lock is there and ask the user to log off from the system.

Ans> when i check i foun no any ded lock (only some locking information found on IND$ dictionary table dew to the index rebulding is goingon on the same time)

4) Check in SM50 for update work process which job or program it is running and with whose login.

Ans> every job or any user who is try update some records that stuck for update.

[JPReyes]

Can you post the errors in SM21?

Regards

Juan

[Former Member]

hi juan

this total sm21 message for today

16:08:03 DIA 002 109 DRFI GE O Lock entry deleted manually: EKKO S

16:08:08 DIA 002 109 DRFI GE O Lock entry deleted manually: EKPO E

16:08:11 DIA 002 109 DRFI GE O Lock entry deleted manually: EKKO S

16:14:36 DIA 001 109 JPBASIS R0 J Work process with PID 10640 is terminated manually

16:14:36 DIA 001 109 JPBASIS R0 J Work process with PID 10641 is terminated manually

16:14:36 UP1 016 109 DRFI Q0 2 Stop Workproc16, PID 10640

16:14:36 UP1 017 109 DRMM MIGO Q0 2 Stop Workproc17, PID 10641

16:14:36 UP1 016 Q0 1 Start Workproc16, 3 times since system startup. PID 12637

16:14:36 UP1 017 Q0 1 Start Workproc17, 3 times since system startup. PID 12638

16:30:13 DIA 000 109 DRSD AB 0 Run-time error "ROLLBACK_IN_POSTING" occurred

16:30:13 DIA 000 109 DRSD AB 1 > Short dump "100512 163013 JPECCPRD2_ECP_00 DRSD " created