<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<META content="MSHTML 6.00.2900.3492" name=GENERATOR></HEAD>
<BODY class=hmmessage>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>Hi Mike,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>In relation to # 6 please apply note 1125717</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>* 1125717 - Enhanced analysis for DEQUEUE_ALL</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>With note 1125717 you must create the checkpoint group
WF_DEQUEUE_ALL via SAAB and then activate it. If there is an issue with the
DEQUEUE_ALL function a short dump is created and we can see where the issue
is.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>You need to goto transaction SAAB, enter WF_DEQUEUE_ALL and click
the Create button. Fill in the following:</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>Checkpoint Group
WF_DEQUEUE_ALL<BR>Description Assert
for
DEQUEUE_ALL<BR>Package
SWW</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>Now activate the assertion 'WF_DEQUEUE_ALL' via the Activate
button on the original screen.<BR>Goto the Server Button.<BR>Right mouse click
on the line 'Global settings' in the column 'Assert'.<BR>Select 'Abort'.
Confirm. Save this configuration.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>Once this is done a shortdump will be created wit the location for
the dequeue_all function. </FONT></SPAN></DIV>
<DIV><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=068372011-20012009><FONT face=Arial color=#0000ff>It is most
likely being called from application code and will have to be looked at by the
application area responsible in order to remove the call to
DEQUEUE_ALL.</FONT></SPAN></DIV>
<DIV><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=068372011-20012009><FONT face=Arial
color=#0000ff>Eddie</FONT></SPAN></DIV>
<DIV dir=ltr align=left><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Mike
Gambier<BR><B>Sent:</B> 20 January 20, 2009 11:07<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> RE: Upgrade to ECC 6 from 4.6c => the
aftermath...so far...<BR></FONT><BR></DIV>
<DIV></DIV>Hi,<BR> <BR>More creaks and groans to report from our ECC 6
upgrade I'm afraid. The current issues are:<BR> <BR>#1 Massive growth of
WF-BATCH enqueues in SM12 - briefly these hit 50k+ last night. With
the 'new' locking profile that came with ECC 6 as the 'Standard' option on
our WF definitions we expected a saw-tooth pattern to locks and hoped this would
be a bit more efficient than the lock/unlock frenzy we had in 4.6C. So a spike
in numbers was to be expected too, but this amount is just crazy. If we can't
cope with this we might have to switch back to the 'Background' locking
approach.<BR> <BR>#2 SWWERRE job is having seriously difficulty clearing
the backlog of temporary exceptions. Longest runtime so far has been 26,000
seconds before it was killed and restarted :(<BR> <BR>#3 Notable increase
in the number of events not being delivered first time, i.e. appearing on
'linkages with errors' tab in SWEQADM.<BR> <BR>#4 Unicode runtime errors
with standard SAP code have started to crawl out of the woodwork<BR> <BR>#5
SWWWIRET table growth is still causing a lot of concern. Total number of new
entries added since we upgraded = 5.4 million. Of these, the total number of
<STRONG>useless</STRONG> 'Success' messages = 3.1 million, a staggering
57%.<BR> <BR>#6 Thousands of H0 Messages (Lock Deletion failed) appearing
in SM21 - despite numerous OSS Notes applied to prevent them.<BR> <BR>Guess
we have work to do still...<BR> <BR>Regards,<BR> <BR>Mike GT<BR><BR>
<HR id=stopSpelling>
<BR>From: madgambler@hotmail.com<BR>To: sap-wug@mit.edu<BR>Subject: RE: Upgrade
to ECC 6 from 4.6c => the aftermath...so far...<BR>Date: Mon, 19 Jan 2009
15:50:42 +0000<BR><BR>
<STYLE>.ExternalClass .EC_hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
.ExternalClass BODY.EC_hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
Hi John,<BR> <BR>As a precaution I had already arranged for our
instance linkages to be backed up in a Transport and reapplied as part of our
Build process following the upgrade, as we spotted that exact same problem early
on. But thanks for reminding me :)<BR> <BR>We always use 'Do Not Change
Linkage' anyway because of our volumes and the risk of massive penalties if we
don't progress some Workflows immediately.<BR> <BR>Oh, and another thing,
I'm asking SAP to turn off are these blasted SWF_RUN 641 messages (Method
&1->&2 executed successfully) being posted in SWWWIRET every
time a step actually works. We've had nearly 1.5 million of these things already
and they serve no use whatsoever!<BR> <BR>Mike GT<BR><BR><BR>
<HR id=EC_stopSpelling>
<BR><BR>Subject: RE: Upgrade to ECC 6 from 4.6c => the aftermath...so
far...<BR>Date: Mon, 19 Jan 2009 09:37:03 -0600<BR>From:
Scheinoha.John@basco.com<BR>To: SAP-WUG@mit.edu<BR>CC:
coyle.pat@basco.com<BR><BR><BR><BR>
<STYLE>.ExternalClass .EC_hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
.ExternalClass BODY.EC_hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009>Mike,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009> When we upgraded from 4.6C to ECC
5.0, we noticed the upgrade changed our Receiver Err Feedback value from "3 Do
not Change Linkage" to "1 Deactivation of Linkage". We did not notice this
change until a workflow error occurred, and subsequent workflow instances
errored after that. It happened to our Purchase Requisition application
and plenty of workflow errors occurred in a very short period of time.
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009> You might want to review SWEQADM
> Basic Data tab > Receiver Error Feedback value.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009> The SAP Inbox feature of
"Double-clicking on an object in the same window is also fully functional in ECC
5.0 and I assume ECC 6. This checkbox needs to be checked in the Personal
workflow settings as a default value in order to view SAP workflow
objects.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009>Hope this helps and thanks for the ECC 6
update. We'll be upgrading to ECC 6 later this year.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009>Thanks,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=EC_EC_084212615-19012009>John Scheinoha</SPAN></FONT></DIV>
<DIV><SPAN class=EC_EC_084212615-19012009></SPAN><FONT face=Arial><FONT
color=#0000ff>Briggs & Stratton </FONT></FONT></DIV>
<DIV><SPAN class=EC_EC_084212615-19012009></SPAN><SPAN
class=EC_EC_084212615-19012009></SPAN><FONT face=Arial><FONT
color=#0000ff>(<SPAN class=EC_EC_084212615-19012009>414) 256 -
5136</SPAN></FONT></FONT><BR></DIV>
<DIV class=EC_EC_OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Mike
Gambier<BR><B>Sent:</B> Monday, January 19, 2009 4:39 AM<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> Upgrade to ECC 6 from 4.6c => the
aftermath...so far...<BR></FONT><BR></DIV>
<DIV></DIV>Hi,<BR> <BR>Well it happened...we upgraded over the
weekend...and things seem to be creaking a little, but so far so good.
:)<BR> <BR>We had a problem with SAP's XPRA for Event Linkages that needed
to be tackled on the day by Oracle DBAs. We couldn't use SAP's single-stream
version of the code because we had 8 million table entries to move from
SWEINSTCOU to SWFDEVINST so we converted their program to a mutli-stream job to
run in parallel. But on the day our Basis people decided to import table
statsitics from a Pre-Prod system which skewed the SQL to run with very poorly
optimised indexes. Once we spotted why the job was taking so long and producing
so little the stats were updated on both the old and the new tables again and
the app servers bounced and the job re-run again. It finished in 20 minutes
instead of the 6 hours it looked like it might take, yay! :)<BR> <BR>Then,
a few hours later with the system up, a quick scan of SWWWIDH entries with
a Status of '02' showed up some issues we weren't aware of. We had about 4k
deadlines that stubbornly refused to fire properly. They kept coming back even
after using the new Transaction SWF_ADM_SWWWIDH to reset
them.<BR> <BR>After a bit of sleuthing it turned out that they were related
to old instances of Workflows (mostly the same template which was
handy) that now were suffering from syntax errors because their container
definition had become invalid during the upgrade. ECC 6 has introduced a
new vulnerability here that we might have to have squished by an OSS Note.
<BR> <BR>In our case a few versions of a common Workflow had an element
that pointed to a SAP-defined structure that had been deleted as part of
the upgrade. Luckily it was obvious that the developer had simply wanted to
find a simple BOOLE-BOOLE flag but had unwisely chosen something else instead.
<BR> <BR>In this situation SAP's new code detects that it is dealing with
an old WF instance and switches to a 'Persistence' version of its Container ABAP
Class inside CL_SWF_CNT_FACTORY, namely CL_SWF_CNT_WF_PERSISTENCE. This Class
duly calls old FMs (SWD_GET_WF_CONTAINER_TABLE) to fetch the Container
Definition for the version of the instance in question which end up selecting
from old tables SWDSWFCONT and SWD_WFCONT. And it's here that the definition of
our element was suddenly found to be pointing to a bogus structure and field
when the element was instantiated at runtime.<BR> <BR>But the new code
can't cope with this syntax error very well and simply bombs out with an
Exception that is eventually caught in the stack:<BR> <BR> IF NOT
por-bus_key IS INITIAL.<BR> l_retcode = l_pmanager->load(
).
<== Return Code comes back here...<BR> CASE
l_retcode.<BR> WHEN
0.<BR><STRONG> WHEN
95.
</STRONG><== Exception bombs out
here...<BR> lr_cx_cnt =
instance->get_last_exception(
).<BR> RAISE EXCEPTION TYPE
cx_swf_utl_obj_create_failed<BR>
EXPORTING<BR>
t100_msg =
lr_cx_cnt->t100_msg<BR>
previous = lr_cx_cnt.<BR> <BR>The upshot of this was that we couldn't even
display these Deadline steps in SWI1, let alone reset their deadlines, because
of a nasty error crawling out. <BR> <BR>In the end I had to resort to
surgery and update the old 4.6c tables directly before we could move these
on :)<BR> <BR>We have some SAP guys here on site so I'll nag them to have
this situation looked at a bit more. I have a feeling though that they've missed
an XPRA or something here because I can imagine other clients suffering from
just this sort of thing were SAP have zapped their own DDIC structures and
Worklow defintions that were perfectly legitimate in 4.6c suddenly become
invalid in ECC 6 and behave erratically like
this.<BR> <BR>Regards,<BR> <BR>Mike GT<BR><BR>
<HR>
Are you a PC? <A href="http://clk.atdmt.com/UKM/go/122465942/direct/01/">Upload
your PC story and show the world</A><BR>
<HR>
Are you a PC? <A href="http://clk.atdmt.com/UKM/go/122465942/direct/01/">Upload
your PC story and show the world</A><BR>
<HR>
Choose the perfect PC or mobile phone for you. <A
href="http://clk.atdmt.com/UKM/go/130777504/direct/01/" target=_new>Click
here</A> </BODY></HTML>