04788 - Upgrading to V4R5M0 of OS/400

04788 - Upgrading to V4R5M0 of OS/400

BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Upgrading to V4R5M0 of OS/400

Curious as to why you would want to move to V4R5 now, when IBM is dropping
support for it in July?

We are a productive 3tier V4R5 account; but we're not current on CUME, ptf's as
our system maintenance is "locked down" from Nov thru April each year.
We are running CUME C01198 with DB fixpack #9

Our next move will be to V5R1 (by July)

Doreen Anderson
Ball Horticultural Company
(630) 231-3600 x3214

-----Original Message-----
From: Gary_DavisZp... [mailto:Gary_DavisZp...]
Sent: Friday, January 25, 2002 8:50 AM
To: 'sap400Zm...'
Cc: Wendy_SimmondsZp...
Subject: Upgrading to V4R5M0 of OS/400

We are currently on OS/400 V4R4 running SAP R/3 4.0B on the AS/400 in a 3 tier
and would like to upgrade to OS/400 V4R5. We have all the latest PTFs and kernel
to enable us to do so but do not want the following nightmare to occur on our
production machine
supporting 500 active users world-wide who are producing mega money orders for
our world-wide
customers! Is there any permanent fixes to the problem or does anyone suggest
not upgrading?
Has anybody else had the following problem with V4R5 and fix pack 11?
I do not want our SAP support to say load the current PTFs, latest hot packages
and kernel fixes
should the problem occur and they can't resolve it.

Gary Davis. Basis Administrator. Pall Europe Ltd.


Thanks, all, who responded to my message. But my customer now has a huge

It seems there is a problem in V4R5, DB Fix Pack #11 with extremely large
SQL statements. We originally thought that the was a problem with the ABAP
SELECT...INNER JOIN statement and the SQL Optimizer, but we found out (from
IBM) that extremely large SQL statements are exceeding the size of their
internal table at the DB level. They constructed a PTF for us which broke
this SQL statement into pieces, then reconstructed before executing it in
the DB. Unfortunately, they are able to do this on a case-by-case level,
and each subsequent problem has to be addressed by IBM individually.

This, of course, is a dangerous situation, as we cannot know what statement
will halt at the DB level next.

Durban Tours - Südafrika Safari

General Data in Customer Master   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3342 Date: 20240620 Time: 021350     sap01-206 ( 3 ms )