|
|
|
|
|
|
NADDR="sdp://IB_IP: 9003"
NLSADDR="sdp://IB_IP: 3050”
SITE2
NADDR="sdp://IB_IP: 9003"
NLSADDR="sdp://IB_IP: 3050"Using the IPoIB address as the network address.
Listing 4 shows a UBBCONFIG file IPoIB configuration example.Prefixed “sdp:” to the network address, and the network address must be an IPoIB address, as shown in Listing 5.Prefixed “sdp:” to the network address, and the network address must be an IPoIB address as shown in Listing 6.Prefixed “sdp:” to the network address, and the network address must be an IPoIB address as shown in Listing 9.Prefixed “sdp:” to network address for WSNADDR, and the network address must be an IPoIB address, for example:Using the IPoIB address as the network address for WSNADDR, for example:Prefixed “sdp:” to the network address, and the network address must be an IPoIB address as shown in Listing 11.It is the same as the GWTDOMAIN NWADDR configuration in the DMCONFIG file.
The receiving poll time before going to sleep waiting for data. You can improve the write performance by decreasing the recv_poll value. It is recommended to set it to zero.
The threshold for zero copy sending data. If the messages are longer than the sdp_zcopy_thresh value, it causes the user buffer to be pinned and the data sent directly from the original buffer. This results in decreased CPU use. The default value is 64K; it is recommended to set it to zero.For example, you can set the two parameters in “/etc/modprobe.conf” on the server node as follows:options ib_sdp sdp_zcopy_thresh=0 recv_poll=0The default name is /u01/common/patches/tuxtmpfile, you can also set your own directory using the EXALOGIC_SHARED_PATH environment variable. It is used for Oracle Tuxedo file transfer. When the EMSQ is full, or the message size exceeds the queue size, Oracle Tuxedo puts this message into a temporary file under the /u01/common/patches/tuxtmpfile directory, and sends notification directly to the remote process queue. The remote process can then get the file as long as it receives the notification.
1. tmlisten_start.sh on all the slave nodes.
2. tmboot.sh on the master node
For shutdown, you should run commands in the following sequence:
1. tmshut.sh on the master node
2. tmlisten_stop.sh on all the slave nodes.When Msgq_daemon starts, it allocates a shared memory. You can get the memory size by using tmloadcf -c ubb, as shown in Listing 14.Listing 14 UBBCONFIG File *MACHINES SectionListing 15 tmloadcf -c ubb Output ExampleAfter getting the RCDMSZ, you can adjust the actual size according to the following runtime factors:MAXSERVERS: A UBBCONFIG file attribute.RDMAQSIZE: A UBBCONFIG file attribute.If the EXALOGIC_MSGQ_CACHE_SIZE environment variable is set, at most 3* EXALOGIC_MSGQ_CACHE_SIZE* MAXSERVERS* RDMAQSIZE more bytes of shared memory should be allocated.For example, if MAXSERVERS is 100, RDMAQSIZE is 100000 and processes on machine ex04 start/stop frequently, you should configure the shared memory size with at most 1300M (340M+960M) instead of 340M.The number of machines in the UBBCONFIG file is considered in calculating RCDMSZ. If new machines are added using MIB, you should increase the size linearly.In some scenarios, Msgq_daemon needs to allocate more shared memory when increasing queue cache entry number using EXALOGIC_MSGQ_CACHE_SIZE. For example, if Oracle Tuxedo process start/stop or tpinit/tpterm frequently. Then you should consider adjusting the initial Msgq_daemon shared memory size, otherwise the message transfer may fail.The default value is 32 for each Oracle Tuxedo thread, and tmloadcf -c always assumes the value of 32. If you change the default value, adjust the Msgq_daemon shared memory size using the following method:MEMSZ: The current shared memory size calculated by above method.CACHENUM: The maximum entry queue cache number for each Oracle Tuxedo thread.