Learnings from Remote Client Copy

1. Take offline backup just before the activity and switch off the archive logs otherwise, they will pile up and fill up the filesystem.
2. Execute the Test run before actual activity but it may not give practical results, in our scenario test run gave 2 hours but actually it took 12 hours for the copy to complete.
3. Lock users both in Target System and Source System, otherwise inconsistencies specially in number ranges may occur.
4. Take offline backup after Copy and don't forget to switch on archive logs before releasing the sytem for use.

SAPCPIC user don't lock only change the password

SAPCPIC has the default password as (ADMIN), if you don't change the same your Early Watch Alert report will show red under User Authorizations. Follow SAP note 29276 to change the password only, don't lock the same.
Run report RSUSR003 to know what users are with standard passwords.

SAP Note 19574 Regarding Number Range in Client Copy

Amazing SAP Note clears concept of Number ranges during client copy:

St02 Call Statistics Hit Ratio

Yesterday we did a test run of client copy from PRD to DEV client. It took 2 hours during peak load. Today I checked the buffer it is showing hit ration 51% in call statistics the
"Select" is showing only 4-5% hit ration in both PRD and DEV instance.

The above is more or less in both PRD and DEV servers, then I read one blog and it said :
"Transport activity triggers flushing of SAP buffer. Hence it is always advisable to do transport in the least loaded segment of a day." -

http://soumen.wordpress.com/performance-tuning-of-sap-another-experiance/5-st02-another-magic-transaction-for-sap-tuners-ii/

After above scenario, we should take care even test run should be scheduled after peak hours. Any other suggestions on tuning are welcome.

SAP MC utility allows you to start / stop sap from browser

From Netweaver Release 7.0 onwards, you may start and stop SAP intance from browser itself using the port http://hostname:5$$13 where $$ is the instance number. Amazing utility, even for UNIX also you can do the same. For more information, follow the below link:
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/217444c3a34e6fe10000000a42189c/content.htm

Spool Request deleted immediately after printing

In the given scenario when we need to preserve the spool request even after printing, (in our scenario the spool is to be converted to pdf using zsmart program), we need to make sure that the "Delete after output " option in User profile (SU01) -> Defaults tab is unchecked, other wise it may delete the request immediately.
Follow below links for further information :
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/spool-request-gets-deleted-automatically-2065750

How to check process and memory status in AIX

During monitoring we check the processes in SAP SM50 but if the SAP system is running for a long time, ST06 may show the RAM is reducing even though the system load is less. This results in less availability of RAM for other processes.

We need to trace the process that is consuming considerable amount of RAM. In AIX us the following command :
ps aux more
General view can be optained by command :
topas
Vitual memory state can be known by :
vmstat 01
For more information follow the below threads:
http://www.unix.com/aix/91057-process-consuming-most-memory.html
http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/command-to-find-top-5-memory-consuming-process-2742917