Ansicht
Dokumentation
12274 - Recommendations for patchlevels of binary patches on iseries/Windows-Appl.
ROGBILLS - Synchronize billing plans RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Recommendations for patchlevels of binary patches on iseries/Windows-Appl.
Hi,I don't know of any "official" thing.
But, it is clear, that both patches need to be "as similar" as
possible. There it is not of any interest if the iSeries patch is
higher or the windows patch. Just take that what you can find on the
SMP - mostly this is not exact in sync.
The simple reason:
In general it would be not of any interest at all when no changes
were done in special structures, that go from appl-server to appl-
server or are stored in the DB.
But, unfortunately this happens sometimes with special patches. (I
think with about 1498 we changed the dynpro version) This had a
pretty bad result for customers with NT below this and iSeries above
or vice versa, because it always started regenerating with the
performance and SQL0913 problems, that are a result of this.
Here you can see, that it does make no difference what system would
have been higher.
As soon as the patch number is not the same, there is ALWAYS a slight
risk, that you run into such an issue ...
Regards
Volker
--- In DoNotReply@consolut.eu, "niko_schmitz" <nschmitzZg...>
wrote:
> Hello group,
>
> does anybody know about official SAP recommendations regarding the
> patchlevels of binary patches on an iSeries central instance
compared
> to the patchlevels on the associated Windows application servers?
> I only know about the inofficial statement that the patchlevels on
> the Windows application servers should not be higher than the
> patchlevels on the central instance.
>
> Thank you for your help,
>
> Kind regards,
>
> Niko Schmitz
> gib mbH
Durban Tours - Südafrika Safari
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 2310 Date: 20240419 Time: 230519 sap01-206 ( 2 ms )
