Skip to Main Content

Database Software

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!

Data Guard Primary abnormally stall (and cannot log switch) while STB down but in Maximum Performance mode

user-68ej9Feb 6 2023

Hi All,

We found unusual behavior on Primary Database with Data Guard Broker (12.1) in Maximum Performance mode. When the connection between Pri & Stb down (or Stop STB instance), our Primary will stall and freeze! Also, when we tried to “Alter system switch logfile” on Primary, the screen will be hang and the common cursor not be returned. No any new archive file was created in dest1.

As far as I understand about the Maximum Performance mode, the Primary should never be endangered when the STB was crash or shutdown or loss of Network between them. Since the Transport mode is ASYNC, the Primary never wait ack from STB.

So we further checked any other possibly parameters that might force Pri to be stalled (e.g. net_timeout, Max_failure) but we found nothing suspicious.

the current parameter of both Instances are below:
Pri:
LogXptMode = 'ASYNC'
DelayMins = '0'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
TransportDisconnectedThreshold = '1800'

log_archive_dest_1 = LOCATION=/oracle/SRP/oraarch/S
RParch valid_for=(ONLINE_LOGFI
LE,ALL_ROLES)
log_archive_dest_2 string service="sby.world", ASYNC NOA
FFIRM delay=1 mandatory compre
ssion=disable max_failure=0 ma
x_connections=1 reopen=300 db_
unique_name="sby" net_timeout=
30, valid_for=(online_logfile,
all_roles)
log_archive_dest_3 string location="/oracle/SRP/12102/db
s/arch", valid_for=(STANDBY_L
OGFILE,STANDBY_ROLE)

Also, when we checked in Alert.log on Primary, we only found error related about redo log on Pri as below:
> ORACLE Instance SRP - Cannot allocate log, archival required
> Thread 1 cannot allocate new log, sequence 832340
All online logs need archiving
Error 1034 received logging on to the standby
krsd_check_stuck_arch: stuck archiver: inactive mandatory dest LOG_ARCHIVE_DEST_2
krsd_check_stuck_arch: stuck archiver condition declared
----------------------------

We really have no ideas and can't figure it out why this happens. Could you please help and guide me what to check further next?
Thank you so so much.

Best Regards,
RC.

Comments
Post Details
Added on Feb 6 2023
0 comments
437 views