Tutorials to .com

Tutorials to .com » Database » Oracle » Optimizing Oracle network configuration

Optimizing Oracle network configuration

Print View , by: iSee ,Total views: 19 ,Word Count: 1346 ,Date: Tue, 25 Aug 2009 Time: 3:59 AM

oracle database in a different geographic been widely used, so we must have professional staff know how to network connections, Oracle how the kind of impact database performance. Oracle provides TNS allows distributed communications in each database.

TNS server is seen as Oracle's logical data request and the remote server in an insulator between the servers. Similarly, the network administrator is able to control tuning of network performance, but the impact of Oracle database administrator has no control over the performance of the network settings right.

I said you can use the following important settings to change the things yuan distributed performance. Including sqlnet.ora, tnsnames.ora, and protocol.ora file parameters that can be used to change the settings, and TCP packet size, and adjust these parameters can affect the underlying network transport layer in order to change things yuan Oracle throughput.

As mentioned earlier, Oracle Net does not allow Oracle professionals to adjust basic network transport layer, and the majority of network traffic can not be changed in the Oracle environment. Remember, Oracle network is a network layer OSI model, the network layer exists in the network protocol stack.

However, the network information packet frequency and size of the Oracle DBA can be controlled. Oracle has a number of tools to change packet frequency and size.

In the server network connection between the Oracle can use several parameters to tune. However, you must remember that the network tuning must be outside of the Oracle, and a qualified network administrator must have the discussion before they can be tuned network. The frequency and size of the packets may be subject to the following set of parameter files.

• sqlnet.ora server file - automatic_ipc parameters

• sqlnet.ora client file-break_poll_skip parameter

• tnsnames.ora and listener.ora file-SDU and TDU parameters

• protocol.ora file-tcp.nodelay parameter

These tuning parameters affects only the Oracle network layer performance. Let us explain them in detail and see how they used to be adjusted to change the Oracle network throughput.

Oracle network before the data during transmission to wait until the buffer is filled by default. Therefore, the demand can not be immediately taken to their destination. When the large amount of data sent from one place another place when this is the most common of the. Oracle networks can not transmit the packet until the buffer is full. Add a protocol.ora file and specify a tcp.nodelay stop buffer delay can repair the defect.

protocol.ora file can be designated to account for all TCP / IP to achieve no data buffering. This parameter can be used in client and server side. protocol.ora statement is as follows:

tcp.nodelay = yes

This parameter can specify the TCP buffers are skipped so that each request can be sent quickly. However, please keep in mind that due to smaller and more frequent packet transmission led to an increase in network traffic, this will reduce the network speed.


tcp.nodelay parameter only in the TCP timeout encountered when being used. When the database server a large number of flow between the settings tcp.nodelay can cause a huge change in performance.

sqlnet.ora file parameters automatic_ip

automatic_ipc roundabout at the network layer parameters, so it can connect to the database to the local acceleration. When automatic_ipc = on time, Oracle will check the local database if the network is defined as the same do not, if so, when the connection is connected directly into the cost of land ICP was avoided when the network layer. The database server is very useful, but for Oracle Internet users who are not used to this point.

When the Oracle network connection must be regarded as a local database, automatic_ipc parameters should be used only in the database on the server. If you do not need a local connection when this parameter is set off, through the use of this setting, all of the Oracle network can improve its performance.

tnsnames.ora file in the SDU and TDU

SDU and TDU parameters in the tnsnames.ora and listener.ora files. SDU specifies the information packet sent to the network size, in theory, SDU should not exceed the maximum MTU size. MTU rely on a real network implementation, it is a constant value. SDU in Oracle's position and the same MTU.

In the Oracle network, TDU information packet size is a default value. Ideally, TDU parameter should be defined as twice the SDU parameter. SDU and TDU size of the default value of 2048, and the maximum is 32767 bytes.

The following is the policy of the use of SDU and TDU:

• SDU should never set great than TDU because you network resources will be wasted space.

• If your users access to the Internet via modem, you should set SDU and TDU to smaller values because of frequent re-send will often occur in the line modem.

• In the broadband connection, you should be your network SDU and TDU's value and set the value of MTU was the same size. In a standard Ethernet networks, the default MTU size is 1514 bytes, in the standard token ring network, MTU default size is 4202.

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

In between the hosts, SDU and TDU settings are a direct function of connection speed. For example, T1, set SDU = TDU = MTU. For the slow modem, the best to use the value of smaller SDU and TDU.

listener.ora file Queuesize parameters

When Oracle is setting up the connection when the connection is made by queuesize parameter to determine. This parameter is only used by large-capacity database. It is expected that the size of simultaneous connections queuesize parameters must be the same size. Here is a listener.org file on the use of this parameter example:





(HOST = marvin)

(PORT = 1521)




A drawback of this parameter is that it is expected to request for the allocation of parameters, therefore, will use more memory and resources. If you need to use large-capacity connections you have to consider the use of MTS. At the same time, pay attention to a number of versions of Unix do not allow the use of the queue more than 5, and there are restrictions on the MTS queue size.


While most of the flow of information packets have been tuned well, but the right will have a distributed Oracle network parameters to set a significant impact on system performance. The use of Oracle professionals, they must fully understand its performance and optimize these important parameters.

(Editor: Ming Ming mingming_ky@126.com TEL: (010) 68476606)

Oracle Tutorial Articles

Can't Find What You're Looking For?

Rating: Not yet rated


No comments posted.