ARCH Process Killed – Fix Without Restart

Hi all,
What if your arch processes hangs or get killed? How to keep archive going without restart database?

Take a look…

Problem:

Current log# 2 seq# 1484 mem# 1: +DGFRA/dbprod01/onlinelog/group_2.380.898680659
ARC1: Detected ARCH process failure
ARC1: STARTING ARCH PROCESSES
ARC1: STARTING ARCH PROCESSES COMPLETE
Master archival failure: 28
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance dbprod01_1 - Archival Error
ORA-00028: your session has been killed
LGWR: Detected ARCH process failure
Thread 1 advanced to log sequence 1485 (LGWR switch)
Current log# 5 seq# 1485 mem# 0: +DGFRA/dbprod01/onlinelog/group_5.870.898689599
Fri Apr 26 10:51:36 2016
Master archival failure: 28
Fri Apr 26 10:52:00 2016

Solution:
Increase your arch processes number… 😉

ALTER SYSTEM SET log_archive_max_processes=8 SCOPE=BOTH;
Fri Apr 26 10:55:15 2016
ARC4 started with pid=59, OS id=76169
Fri Apr 26 10:55:15 2016
ARC5 started with pid=60, OS id=76171
Fri Apr 26 10:55:15 2016
ARC6 started with pid=61, OS id=76173
Fri Apr 26 10:55:15 2016
ARC7 started with pid=62, OS id=76175

Matheus.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from grepOra

Subscribe now to keep reading and get access to the full archive.

Continue reading