Skip to Main Content

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!

Standby Db not transporting archivelogs.

Beauty_and_dBestNov 15 2018 — edited Nov 17 2018

11gR2

OL6

Hi ALL,

I have setup a Standby DB, and it was working for months now.

But today it stopped transporting archivelogs, I do not know why, but maybe some parameter in init.ora was changed? 

So today, I just manually copy or upload  all accumulated  archivelogs from Primary  to target Standby server.

Then do manual recovery using commands below:

$ rman target /

rman> startup mount;

rman> catalog start with '/u02/ARCH';

rman> recover database;

Then after the manual recovery, I will try to startup auto recovery again, using the following commands:

A. Shutdown the database.

sqlplus / as sysdba

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

shutdown immediate;

B. Then start auto recovery.

sqlplus / as sysdba

startup mount;

ALTER DATABASE OPEN READ ONLY;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

exit

The above commands have no error, but when I check the standby alert logs, it just stays stagnant, and no more heartbeat processes pinging added or logged.

Below is the last alert log message for the above commands, which stays same for long time.

==========================

ALTER DATABASE   MOUNT

ARCH: STARTING ARCH PROCESSES

Thu Nov 15 20:51:40 2018

ARC0 started with pid=18, OS id=14306

ARC0: Archival started

ARCH: STARTING ARCH PROCESSES COMPLETE

ARC0: STARTING ARCH PROCESSES

Successful mount of redo thread 1, with mount id 404159192

Physical Standby Database mounted.

Lost write protection disabled

Thu Nov 15 20:51:41 2018

ARC1 started with pid=19, OS id=14308

Thu Nov 15 20:51:41 2018

ARC2 started with pid=20, OS id=14310

Thu Nov 15 20:51:41 2018

ARC3 started with pid=21, OS id=14312

ARC1: Archival started

ARC2: Archival started

ARC1: Becoming the 'no FAL' ARCH

ARC2: Becoming the heartbeat ARCH

ARC2: Becoming the active heartbeat ARCH

Completed: ALTER DATABASE   MOUNT

Thu Nov 15 20:51:41 2018

ALTER DATABASE OPEN READ ONLY

SMON: enabling cache recovery

Dictionary check beginning

Dictionary check complete

Database Characterset is AL32UTF8

No Resource Manager plan active

replication_dependency_tracking turned off (no async multimaster replication found)

Physical standby database opened for read only access.

Completed: ALTER DATABASE OPEN READ ONLY

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION

Attempt to start background Managed Standby Recovery process (PROD)

Thu Nov 15 20:51:42 2018

MRP0 started with pid=22, OS id=14317

MRP0: Background Managed Standby Recovery process started (PROD)

Thu Nov 15 20:51:42 2018

db_recovery_file_dest_size of 184320 MB is 25.79% used. This is a

user-specified limit on the amount of space that will be used by this

database for recovery-related files, and does not reflect the amount of

space available in the underlying filesystem or ASM diskgroup.

ARC3: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

started logmerger process

Thu Nov 15 20:51:47 2018

Managed Standby Recovery starting Real Time Apply

Parallel Media Recovery started with 8 slaves

Waiting for all non-current ORLs to be archived...

All non-current ORLs have been archived.

Media Recovery Waiting for thread 1 sequence 3996

Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION

==============================

I have been doing many times > alter system switch logfile at primary;

But the generated archivelogs are not transported.

Please help how to troubleshoot.

Kind regards,

jc

This post has been answered by racman on Nov 15 2018
Jump to Answer
Comments
Post Details
Added on Nov 15 2018
47 comments
1,350 views