Ansicht
Dokumentation
00684 - SAP "logical system name" change in SCC4 w hen refreshing a system
CPI1466 during Backup Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
SAP "logical system name" change in SCC4 w hen refreshing a system
Our remote client copies work great now. We just run it in test mode firstto check for any possible database errors. After that, I just use parallel
processes (usually 8 to 10) and it takes off. The last one I did from our
DEV to TST system took just over 4 hours. The Client on DEV was 35 Gb..
You just have to be sure the RFC user (SM59) is set up on both systems with
the same password also. And as usual, this group gave me lots of great tips
and tricks.
-----Original Message-----
From: Thierry [mailto:mrsevenZm...]
Sent: Wednesday, February 07, 2001 2:24 PM
To: sap400Zm...
Subject: Re: SAP "logical system name" change in SCC4
when refreshing a system
> I know, remote client copies churn and bubble, moan and groan and take
forever,
> but basically when they are done there is little to worry about.
>
Apart from being slow, are they finally reliable in 4.6 ? I remember a note
in 3.1i which basically said "just forget it" 🙂 Was not much better in
4.0B (for large clients with transaction data).
Thierry.
To unsubscribe from this group, send an email to:
SAP on System i-unsubscribeZegroups.com
Durban Tours - Südafrika Safari
BAL_S_LOG - Application Log: Log header data General Material Data
This documentation is copyright by SAP AG.
Length: 2066 Date: 20231205 Time: 091050 sap01-206 ( 3 ms )
