HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Client delay using MC/SG RAC
Operating System - HP-UX
1833451
Members
2989
Online
110052
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
Forums
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
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
03-02-2005 03:14 AM
03-02-2005 03:14 AM
Client delay using MC/SG RAC
Running HP/SG A.11.16 on HP-UX 11.11 (pa-risc) with RAC using Oracle DB 9.2.0 on a two
node (rp4440's) cluster. We are not using the Oracle Failsafe product or Oracle TAF. We
are unsatisfied with a delay (consistantly 22 seconds) that incurs during a client
connection to the Oracle database under a certain condition. The condition exists when we shutdown the package that runs on the first server defined within the tnsnames.ora file and make an attempt to connect to the oracle database. The connection succeeds to the secondary node after 22 seconds. I believe everything is working as defined but I want to know how to cut the 22 seconds down to a much lower number.
What I believe is occurring is that the communication between the client and the network (?) just takes 22 seconds to determine that the ip is not available and for the client to use the second defined location (ip) within the tnsnames.ora.
The package controls both the startup of the database instance and the listener. We used
HPs purchased SG toolkit to help define the package. The ip assigned to the package does
not move to a surviving node since this is a RAC cluster and the package does not move to
a surviving node.
I modified tcp_ip_abort_cinterval (from 75000 to 1000), tcp_rexmit_interval_initial (from
3000 to 200) and tcp_rexmit_interval_max (from 60000 to 5000) on the server that has the package shutdown. The 22 second delay still existed.
When I add the ip of the package that is down to the second node defined within tnsnames.ora the 22 second delay is gone and we are within our acceptable range.
I am thinking about modifying the serviceguard package to make the ip float between the hosts only for the first defined server within the tnsnames.ora.
Do you have any suggestions on how to reduce the delay other than modifying the existing
serviceguard packages?
node (rp4440's) cluster. We are not using the Oracle Failsafe product or Oracle TAF. We
are unsatisfied with a delay (consistantly 22 seconds) that incurs during a client
connection to the Oracle database under a certain condition. The condition exists when we shutdown the package that runs on the first server defined within the tnsnames.ora file and make an attempt to connect to the oracle database. The connection succeeds to the secondary node after 22 seconds. I believe everything is working as defined but I want to know how to cut the 22 seconds down to a much lower number.
What I believe is occurring is that the communication between the client and the network (?) just takes 22 seconds to determine that the ip is not available and for the client to use the second defined location (ip) within the tnsnames.ora.
The package controls both the startup of the database instance and the listener. We used
HPs purchased SG toolkit to help define the package. The ip assigned to the package does
not move to a surviving node since this is a RAC cluster and the package does not move to
a surviving node.
I modified tcp_ip_abort_cinterval (from 75000 to 1000), tcp_rexmit_interval_initial (from
3000 to 200) and tcp_rexmit_interval_max (from 60000 to 5000) on the server that has the package shutdown. The 22 second delay still existed.
When I add the ip of the package that is down to the second node defined within tnsnames.ora the 22 second delay is gone and we are within our acceptable range.
I am thinking about modifying the serviceguard package to make the ip float between the hosts only for the first defined server within the tnsnames.ora.
Do you have any suggestions on how to reduce the delay other than modifying the existing
serviceguard packages?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2005 10:49 PM
03-02-2005 10:49 PM
Re: Client delay using MC/SG RAC
Hi,
It seems that you have a problem in configuring your client.
Can you send your client's tnsnames.ora?
It seems that you have a problem in configuring your client.
Can you send your client's tnsnames.ora?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2005 12:20 AM
03-03-2005 12:20 AM
Re: Client delay using MC/SG RAC
Here is the tnsnames.ora:
################
LISTENER_IPSHR.DC2=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=IPSHR1.dc2.companyx.com)(PORT=1532))
(ADDRESS=(PROTOCOL=TCP)(HOST=IPSHR2.dc2.companyx.com)(PORT=1542))
)
)
################
IPSHR.DC2.companyx.COM=
(DESCRIPTION=
(LOAD_BALANCE=ON)
(FAILOVER=ON)
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
)
(CONNECT_DATA=
(SERVICE_NAME=IPSHR.DC2.companyx.COM)
)
)
################
IPSHR1.DC2.companyx.COM=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
(CONNECT_DATA=
(SERVICE_NAME=IPSHR.DC2.companyx.COM)
(INSTANCE_NAME=IPSHR1)
)
)
################
IPSHR2.DC2.companyx.COM=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
(CONNECT_DATA=
(SERVICE_NAME=IPSHR.DC2.companyx.COM)
(INSTANCE_NAME=IPSHR2)
)
)
################
LISTENER_IPSHR1.DC2.companyx.COM =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
)
################
LISTENER_IPSHR2.DC2.companyx.COM =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
)
################
LISTENER_IPSHR1.DC2 =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
)
################
LISTENER_IPSHR2.DC2 =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
)
################
LISTENER_IPSHR.DC2=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=IPSHR1.dc2.companyx.com)(PORT=1532))
(ADDRESS=(PROTOCOL=TCP)(HOST=IPSHR2.dc2.companyx.com)(PORT=1542))
)
)
################
IPSHR.DC2.companyx.COM=
(DESCRIPTION=
(LOAD_BALANCE=ON)
(FAILOVER=ON)
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
)
(CONNECT_DATA=
(SERVICE_NAME=IPSHR.DC2.companyx.COM)
)
)
################
IPSHR1.DC2.companyx.COM=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
(CONNECT_DATA=
(SERVICE_NAME=IPSHR.DC2.companyx.COM)
(INSTANCE_NAME=IPSHR1)
)
)
################
IPSHR2.DC2.companyx.COM=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
(CONNECT_DATA=
(SERVICE_NAME=IPSHR.DC2.companyx.COM)
(INSTANCE_NAME=IPSHR2)
)
)
################
LISTENER_IPSHR1.DC2.companyx.COM =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
)
################
LISTENER_IPSHR2.DC2.companyx.COM =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
)
################
LISTENER_IPSHR1.DC2 =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR1.dc2.companyx.com)
(PORT=1532)
)
)
################
LISTENER_IPSHR2.DC2 =
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=IPSHR2.dc2.companyx.com)
(PORT=1542)
)
)
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP