Oracle's network configuration parameters

Oracle databases are widely used in different geographies, so it is important for professional Oracle personnel to understand how network connectivity affects database performance. TNS provided by Oracle allows for allocation of traffic in each database. The TNS server is considered an insulator in Oracle's logical data request and a server between remote servers. Similarly, network administrators have the ability to control network performance tuning, but Oracle administrators do not have the right to control network settings that affect database performance.

You can use the important settings I have described below to change the performance of the distributed things. These include parameters in Sqlnet.ora, Tnsnames.ora, and Protocol.ora files that can be used to change settings and TCP packet sizes, and adjust these parameters to affect the underlying network transport layer in order to change the throughput of the Oracle thing Meta.

As noted earlier, Oracle networks do not allow Oracle professionals to adjust the underlying network transport layer, and most network traffic cannot be changed in Oracle environments. Remember, Oracle

The network is a network layer in the OSI model, the network layer exists on the network protocol stack.

However, the frequency and size of network packets can be controlled by Oracle DBAs. Oracle has a large number of tools to change the frequency and size of packets.

An Oracle network connection between servers can be tuned with several parameters. However, you must remember that the network tuning must be outside of Oracle and a qualified network administrator must be consulted before they can tune the network. The frequency and size of packets can be affected by the settings of the following parameter files.

Sqlnet.ora Server file--AUTOMATIC_IPC parameters

Sqlnet.ora Customer File-break_poll_skip parameters

Tnsnames.ora and Listener.ora file-sdu and TDU parameters

Protocol.ora File-tcp.nodelay parameters

These tuning parameters only affect the performance of the Oracle Network layer. Let's explain them in more detail and see how they are tuned to change Oracle network throughput.

Tcp.nodelay parameters in the Protocol.ora file

The Oracle network waits until the buffer is filled before the data is transmitted. As a result, demand cannot be sent immediately to their destinations. This is the most common when large amounts of data are sent from one place to another. The Oracle network cannot transmit packets until the buffer is full. Adding a Protocol.ora file and specifying a delay of a tcp.nodelay stop buffer can fix this flaw.

The Protocol.ora file can be specified to indicate no data buffering for all TCP/IP implementations. This parameter can be used on both the client and server side. The Protocol.ora statement is like this:

Tcp.nodelay = yes

Specifying this parameter allows the TCP buffer to be skipped so that each request can be sent quickly. Keep in mind, however, that the increased network traffic due to smaller and more frequent packet transfers can slow down the network.

Tcp.nodelay

The Tcp.nodelay parameter is only used when TCP encounters a timeout setting. Setting Tcp.nodelay when there is a large amount of traffic between the database servers can result in significant performance

Change.

Automatic_ip parameters in the Sqlnet.ora file

The AUTOMATIC_IPC parameter is circuitous to the network layer, so it can be used to speed local connections to the database. When Automatic_ipc=on, the Oracle network checks whether the local database is defined as the same, and if so, the network layer is circumvented when the connection is directly converted to a local ICP connection. This is useful on the database server, but it doesn't work for Oracle network users.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/

When an Oracle network connection must be treated as a local database, the AUTOMATIC_IPC parameter should only be used on the database server. If you do not need a local connection, set this parameter to OFF, and by taking advantage of this setting, all Oracle networks can improve their performance.

SDU and TDU in the Tnsnames.ora file

The SDU and TDU parameters are located in the Tnsnames.ora and Listener.ora files. SDU Specifies the size of packets to be sent to the network, theoretically, SDU should not exceed the maximum MTU size.

The MTU relies on a realistic network implementation, which is an invariant value. SDU the same position as the MTU in Oracle.

In Oracle's network, the size of the TDU packet is a default value. Ideally, the TDU parameter should be defined as one times the SDU parameter. The default value for SDU and TDU is 2048, and the maximum value is 32767 bytes.

Here are the guidelines for using SDU and TDU:

· SDU never set larger than TDU, because you will waste network resource space.

• If your users are using a modulation mediator to get to the Internet, you should set the value of SDU and TDU smaller, because frequent resend will often occur on the line of the modulating mediator.

• In a broadband connection, you should set the value of your network SDU and TDU to the same size as the MTU value. In a standard Ethernet network, the default MTU size is 1514 bytes, and in the standard Token Ring network, the MTU default size is 4202.

• If MTS is used, you must use the appropriate MTU,TDU settings to set the Mts_dispatchers.

Between hosts, the SDU and TDU settings are a direct function of the connection speed. For example T1, set SDU=TDU=MTU. For slow-speed modulation mediators, it is best to use SDU and TDU with smaller values.

Queuesize parameters in the Listener.ora file

When Oracle is establishing a connection, this connection is determined by the Queuesize parameter. This parameter is only used by a large database. People expect the connection to occur at the same time the big

The small must be equal to the size of the Queuesize parameter. Here is an example of the use of this parameter in a listener.org file:

LISTENER =

(Address_list =

(address =

(PROTOCOL = TCP)

(HOST = Marvin)

(PORT = 1521)

(Queuesize = 32)

)

)

One disadvantage of this argument is that it assigns parameters to the expected request, so more memory and resources are used. If you need to use a large capacity connection you should consider using MTS.

Also, note that some UNIX versions do not allow queues of more than 5, and there are limits on the size of MTS queues.

Performance

Although the flow of most packets is tuned, the correct Oracle network parameter settings will have a significant impact on the performance of the distributed system. For professionals using Oracle, they must fully understand their performance and optimize these important parameters.