Database Backup and Recovery (MOSC)

MOSC Banner

What is the significance of these errors in the primary database alert log?

edited Mar 13, 2020 8:48PM in Database Backup and Recovery (MOSC) 7 commentsAnswered

Hi,

   Since migrating a customer's database to a new platform, and creating a physical standby database on an identical platform, whenever a Level 1 backup is taken on the standby we see errors in the primary database's alert log as follows:

Mon Feb 25 22:00:00 2019

VKRM started with pid=29, OS id=29627

Mon Feb 25 22:12:43 2019

WARN: ARC0: Terminating pid 6348 hung on an I/O operation                                                                   >>>>>>>>>>>>>>>>>>>>>>>

Killing 1 processes with pids 6348 (Process by index) in order to remove hung processes. Requested by OS process 9230       >>>>>>>>>>>>>>>>>>>>>>>

ARC0: Error 16198 due to hung I/O operation to LOG_ARCHIVE_DEST_2                                                           >>>>>>>>>>>>>>>>>>>>>>>

Mon Feb 25 22:12:46 2019

NSA2 started with pid=244, OS id=6188

Mon Feb 25 22:12:50 2019

Thread 1 advanced to log sequence 2958 (LGWR switch)

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center