We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE: [sap-basis] Table UVERS shows S - Kernel Switch Executed after Upgrade Completion.

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from Andy Murzyn on Oct 4 at 9:54 PM
Please close this issue. Modifying the UVERS table did the trick. Since the upgrade completed successfully, per the SUM final report, I decided to give it a shot. It worked, I was able to release the transport out of SE01. No ST22/SM21 errors/warnings. SICK came back green. So far so good.

Andy Murzyn

---------------Original Message---------------
From: Andy Murzyn
Sent: Saturday, October 04, 2014 9:07 AM
Subject: Table UVERS shows S - Kernel Switch Executed after Upgrade Completion.

Hello,
I have just completed a NW 7.31 upgrade and installation of EWM on a DEV system. Installs completed, however when I try to release transports, I receive the following:
Requests cannot be released during the upgrade.
Additionally:
Requests cannot be released during the upgrade
Message no. TR811

Diagnosis
An upgrade to a new version is currently running in your SAP ystem. No change requests or transports are released in the current upgrade phase.

System Response
Request DWMK900008 is not released.

Procedure
Wait for the upgrade to finish. You can then release request DWMK900008.

Further information can be found in the upgrade guide.
Note in particular the section about adjusting the ABAP Dictionary objects.

Looking at Table UVERS it shows for PUTSTATUS S - Kernel Switch Executed.

The system appears to be fine, no ST22 entries, no SM21 entries, and no failed standard SAP jobs.

I guess my question is: CAn I simply update the status of the packages to + Upgrade or add-on update ended successfully.

At this point I don't see too many options:
1. Revert to a lower patch level, restart the system, then see what happens.
2. Manually modify UVERS table PUTSTATUS to +
3. Begin upgrade process all over again.

I'll try 1. and see what happens. 2 may cause even more issues going foward. And as painful as 3 is, may be the only answer.

If anyone has come across this before I'd sure like to know what solution they implemented.

THank you,

Andy

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
Andy Murzyn  

achievement
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language