High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

MAX_CONNECTION Attribute in RAC and single instance Physical standby


Dear All,

I have two nodes RAC Primary Database and two single instance physical standby databases. The parameters are as

*.log_archive_dest_2='service="ostdbp"','LGWR ASYNC NOAFFIRM delay=0 optional compression=enable max_failure=0 max_connections=5 reopen=60 db_unique_name="ostdbp" net_timeout=30','valid_for=(all_logfiles,primary_role)'

*.log_archive_dest_3='service="ostdbdr"','LGWR ASYNC NOAFFIRM delay=0 optional compression =enable max_failure=0 max_connections=1 reopen=60 db_unique_name="ostdbdr" net_timeout=30','valid_for=(all_logfiles,primary_role)'

*.log_archive_dest_state_2='ENABLE'

*.log_archive_dest_state_3='ENABLE'

*.log_archive_max_processes=16

I have used max_connections=5 parameter for shipping redo log files for gap resolution for one of my physical standby database named ostdbp, but, in the alert log file of the standby DB I found that simultaneous shipment of the multiple archive log files are there which results in network congestion whereas max_connections was set for sending single archive log file with multiple archive processes. Is there any restriction for the RAC configuration to send archive log file with only one archive process? or something is missing the configuration.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center