11-15-2006 11:16 AM
11-15-2006 12:12 PM
hi
good
go through this
Before doing a client copy, you need to prepare the following :-
1. Find the source client space with the client size custom program which can be implemented using the rel. note:
Find the space of the client - '0118823'. This will give you the size of the source client.
2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV
client based on space requirements also.
3. You can do the client copy by remote or export/import client.
Remote method is not preferred if you are doing a large client copy.
Do a client export/import.
4. To speed up the export/import, use R3trans export/import for the clustered tables.
Please find the rel. notes related to performance improvements for cluster tables in OSS.
5. Do import and post processing.
Note: Export may take 10 to 20 hr. for 50gb of data
import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on
your system performance.
Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process.
Note :-
If it is a fresh installation, do this --
1. SCC4 --> Create client no. and fill other details.
2. Logon to the newly created client with SAP* and PASS as password.
3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client <as created just now>.
4. Preferably do a test run initially to check if it can go well.
5. As a care check space in databases.
thanks
mrutyun^
11-15-2006 11:22 AM
Hi,
Procedure
1. Choose Administration --> System administration --> Administration --> Client admin. --> Client Copy --> Remote Copy. Select a copy profile.
3. Enter the RFC destination.
4. Make an RFC system comparison if necessary.
5. Setup the parallel process parameters.
6. Start the Copy.
<b>Note</b>
When you copy a client from one system to another, the data is transferred directly via the RFC interface - there is no intermediate storage on hard disk.
Check this link for copy profile.
http://help.sap.com/saphelp_47x200/helpdata/en/99/0a2a887e2511d2a6250000e82deaaa/content.htm
--Ragu
11-15-2006 11:36 AM
Hi John,
This is basis job and required authorization to do so .. following are the steps
1. TRANSACTION - SCC9
2. Select the profile to be copied..
3. Select the source system
4. Check the test box, if you wish to test the
copy...recommended to go for this...
5. Either you can schedule the copy or execute
immediately..Option for both is provided on
the application tool bar..
Thats all...
Hope this helps..
11-15-2006 12:12 PM
hi
good
go through this
Before doing a client copy, you need to prepare the following :-
1. Find the source client space with the client size custom program which can be implemented using the rel. note:
Find the space of the client - '0118823'. This will give you the size of the source client.
2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV
client based on space requirements also.
3. You can do the client copy by remote or export/import client.
Remote method is not preferred if you are doing a large client copy.
Do a client export/import.
4. To speed up the export/import, use R3trans export/import for the clustered tables.
Please find the rel. notes related to performance improvements for cluster tables in OSS.
5. Do import and post processing.
Note: Export may take 10 to 20 hr. for 50gb of data
import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on
your system performance.
Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process.
Note :-
If it is a fresh installation, do this --
1. SCC4 --> Create client no. and fill other details.
2. Logon to the newly created client with SAP* and PASS as password.
3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client <as created just now>.
4. Preferably do a test run initially to check if it can go well.
5. As a care check space in databases.
thanks
mrutyun^