- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- tcp parameters tuning for JDB access to Oracle
Operating System - HP-UX
1753880
Members
7154
Online
108809
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2002 11:00 PM
10-15-2002 11:00 PM
tcp parameters tuning for JDB access to Oracle
Hi All,
We have a Oracle 8.1.7 database in HP-UX 11.0 and trying to access this database using JDBC over the network. It seems the queries take unusually long time. Keeping the network delays and traffic congestion issues aside, is there something I can do to tune up the tcp/ip related params in HP-UX using ndd ?
Which parameters should be tuned to which values ?
Following are some params with their respective values (they are actually deafult values) at the moment.
tcp_conn_request_max 20
tcp_syn_rcvd_max 500
tcp_time_wait_interval 60,000
tcp_xmt_hiwater_def 32768
tcp_recv_hiwater_def 32768.
All comments and suggestions are very much appreciated.
We have a Oracle 8.1.7 database in HP-UX 11.0 and trying to access this database using JDBC over the network. It seems the queries take unusually long time. Keeping the network delays and traffic congestion issues aside, is there something I can do to tune up the tcp/ip related params in HP-UX using ndd ?
Which parameters should be tuned to which values ?
Following are some params with their respective values (they are actually deafult values) at the moment.
tcp_conn_request_max 20
tcp_syn_rcvd_max 500
tcp_time_wait_interval 60,000
tcp_xmt_hiwater_def 32768
tcp_recv_hiwater_def 32768.
All comments and suggestions are very much appreciated.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2002 08:53 AM
10-17-2002 08:53 AM
Re: tcp parameters tuning for JDB access to Oracle
It is unlikely that you would need t change any of them. The one most likely to require changes would be tcp_conn_request_max - but that only if you see an increasing number of connections dropped due to full queue in the output of netstat -p tcp.
Changing the TIME_WAIT interval is generally not advised.
The tcp_syn_rcvd_max is only to deal with DOS situations, and the hiwaters would only need to be changed if your queries ever tried to dump more than 32KB (actually 64KB given how the stack works) at a time into the connection.
It might be interesting to take a tcpdump (www.tcpdump.org) trace of one or more transactions against the database and see what it looks like.
Changing the TIME_WAIT interval is generally not advised.
The tcp_syn_rcvd_max is only to deal with DOS situations, and the hiwaters would only need to be changed if your queries ever tried to dump more than 32KB (actually 64KB given how the stack works) at a time into the connection.
It might be interesting to take a tcpdump (www.tcpdump.org) trace of one or more transactions against the database and see what it looks like.
there is no rest for the wicked yet the virtuous have no pillows
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP