Gateway service restart on AIX

Due to heavy load generated by TDMS_RFCs the gateway service on PRD CI hanged due to that there were many spool errors.
Solution
1. Logged on to CI
2. Found gateway service
ps -ef grep gw
found the process named gwrd (this is gateway service on AIX)
3. Killed the process with command
kill -2 PID of gateway service
4. ps -ef grep gw
again
it will show new gwrd process running.
(Actually dispatcher automatically restarts the gateway once it is killed)

BTCTRNS1 adn BTCTRNS2

We can use the following reports for de-scheduling and releasing the jobs before and after some activity. For more info follow the below link :
https://forums.sdn.sap.com/message.jspa?messageID=3999326

Microsoft Exchange Relaying feature

While configuring SAP Connect with Microsoft Exchange server, SAP could send the mails to internal email addresses but couldn't send to email addresses out of domain. This is because of Exchange relay feature (quoting)
http://technet.microsoft.com/en-us/library/dd277329.aspx
"To allow specified IP addresses—internal or external—to relay, check the "Hosts and clients with these IP addresses" checkbox, then use the Add, Edit, and Remove buttons to build the list of IP addresses from which you want to accept relay traffic. Remember that this checkbox controls relaying when you have selected the radio dial for "Reroute incoming SMTP ..." in the Routing tab. You should normally check this box; doing so will prevent relaying. If you leave it unchecked, your server is open for relay."

But the confusion remained from normal IP address 192.168.1.x we can send mail to outofdomain email addresses but why not from SAP servers (because they are on 192.168.213.x IP range ) :-)

If the administrator wants he may allow the same (192.168.213.x) as well to relay to outofdomain email addresses.

We were getting (Value is obsolete) in Operating System MTE in RZ20. We followed the below link :
http://help.sap.com/saphelp_nw04/helpdata/EN/28/58b3d95bcea54d81e76b2ec122c564/content.htm
You can also reset the method status by selecting the corresponding MTE, choosing Display Details (), and, on the following screen, choosing Edit ® Method Status ® Reset ® Select Data Collection Method and it resolved the same.

5 steps to configure HADR on db2

Here is all the setup required for HADR on one slide. Note the steps are quite simple.
Backup database on primary
Restore database on secondary
Set config parms (which are all pretty straight forward, hostname, port to listen on, remote instance name)
Start standby
Start primary
That’s it!

SAP may remain up during offline database backup

Within an SAP environment, the SAP system may remain up and running during an offline backup to preserve the buffers of the SAP application servers. All SAP work processes are disconnected from the database and remain in a reconnect state during the offline backup. After the backup has been finished, the work processes reconnect to the database using the reconnect feature of the SAP Database Support Layer (DBSL). - DB2 UDB for SAP Guide

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.