Skip to Main Content
Forums

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

What is the equivalent of (ENABLE=BROKEN) in GoldenGate?

Bobby DurrettAug 25 2022

I realize this is a long shot but here goes. For Oracle databases you can add (ENABLE=BROKEN) in your connect string to work in coordination with OS TCP Keepalive settings. We have used this with AWS Gateway Load Balancer which has a 350 second unchangeable idle timeout. By setting tcp_keepalive_time to less than 350 in Linux and using (ENABLE=BROKEN) an Oracle connection from an AWS EC2 to an on premises Oracle database through the GWLB will not timeout. Without (ENABLE=BROKEN) the Linux tcp_keepalive_time setting does not seem to do much if anything.
Anyway, we have GoldenGate between AWS and on premises and I would like to find the equivalent of (ENABLE=BROKEN) to cause GoldenGate to use the TCP keepalive functionality. We have set tcp_keepalive_time to 60 seconds in the EC2s that have GoldenGate but that by itself did nothing. We have weird unexplainable issues with all our GoldenGate connections between AWS and on premises and Oracle support has not been able to find anything so I thought it would be worth trying to get the keep alive features working for GGS. Our on premises GGS works like a charm so it is just the ground to cloud that is messed up.
Anyone out there have any ideas?
Thanks!
Bobby
This post has been answered by Bobby Durrett on Aug 31 2022
Jump to Answer

Comments

Aman....
does existing user and new connection affect when we rebuild a index?

What kind of efect you are mentioning?
Aman....
Anand...
Hii..

let me try to answer your query, it might not be 100% correct.
When you rebuild the index using ONLINE clause then, the copy of the index is maintained which is modified and then replaces the old index and by the time the new one is rebuilt the older one is used by the users.Whereas, when you simply do , alter index indexname rebuild; the index goes into unusable state and will not be available to the users.If the index which is going to be rebuilt is already being used by someone then you will get ORA error sayin RESOURCE BUSY WAIT...

Anand
26741
1. A REBUILD locks the table (the table can still be queried). A REBUILD ONLINE allows operations to run concurrently against the table.

2. You run the risk of ORA-01410 errors. For a good explanation see http://jonathanlewis.wordpress.com/2007/09/16/index-rebuild/

3. In 10g and above a REBUILD implicitly updates statistics on the Index. This can change execution plans as Oracle parses SQL statements that execute after the REBUILD.

But, generically, existing user connections and user queries are NOT affected by a rebuild.


Hemant K Chitale
http://hemantoracledba.blogspot.com
1 - 3

Post Details

Added on Aug 25 2022
#general-database-discussions, #goldengate
2 comments
1,785 views