Expert Oracle Exadata - Parent Directory

CHAPTER 13 MIGRATING TO EXADATANote that these settings are not persistent, they will be lost after a reboot. If you want to persist thesesettings, you should add a startup script into rc3.d (or some rc.local equivalent), which would re-run theprevious commands. Another option would be to put these values to /etc/system, but starting fromSolaris 10 the use of the global /etc/system settings is not encouraged. Yet another approach would be toput the values into a Solaris Service Management Framework (SMF) manifest file, but that is out of thescope of this book.If the source server is still going to be actively in use (in production) during the data transfer, thenthink twice before increasing the default buffer sizes globally. While you could potentially make the bulkdata transfer much faster for everybody with larger buffer sizes, your server memory usage would alsogrow (TCP buffers live in kernel memory) and you could run into memory shortage issues.This is where a more sophisticated way for changing buffer sizes becomes very useful. Solaris allowsyou to set the default send and receive buffer sizes at route level. So, assuming that the target server is ina different subnet from most other production servers, you can configure the buffer sizes for a specificroute only.Let’s check the current routes first:# netstat -rnRouting Table: IPv4Destination Gateway Flags Ref Use Interface-------------------- -------------------- ----- ----- ---------- ---------default 192.168.77.2 UG 1 0 e1000g0default 172.16.191.1 UG 1 1172.16.0.0 172.16.191.51 U 1 2 e1000g1192.168.77.0 192.168.77.128 U 1 3 e1000g0224.0.0.0 192.168.77.128 U 1 0 e1000g0127.0.0.1 127.0.0.1 UH 1 82 lo0Let’s assume that that the target Exadata server uses subnet 192.168.77.0, and one of the servers hasIP 192.168.77.123. You can use the route get command in the Solaris machine to see if there are anyexisting route-specific settings:# route get 192.168.77.123route to: 192.168.77.123destination: 192.168.77.0mask: 255.255.255.0interface: e1000g0flags: recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire0 0 0 0 0 0 1500 0The recvpipe and sendpipe values are zero; they use whatever are the O/S system-wide defaults.Let’s change the route settings now and check the settings with route get again:# route change -net 192.168.77.0 -recvpipe 4194304 -sendpipe 4194304change net 192.168.77.0# route get 192.168.77.123route to: 192.168.77.123destination: 192.168.77.0mask: 255.255.255.0interface: e1000g0flags: recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire4194304 4194304 0 0 0 0 1500 0433