RFS[18]: Assigned to RFS process

The following errors were seen in the ALERTLOG file of the STANDBY Database if the PRODUCTION Database suddenly shuts down.

(STANDBYDB)

Mon Dec 21 17:53:29 2015

RFS[18]: Assigned to RFS process 15600

RFS[18]: Possible network disconnect with primary database

Mon Dec 21 17:53:29 2015

RFS[16]: Possible network disconnect with primary database

Mon Dec 21 17:53:29 2015

RFS[14]: Possible network disconnect with primary database

Mon Dec 21 17:54:15 2015

Killing 1 processes with pids 15391 (idle RFS by thread/sequence) in order to retry receiving a log after reattaching. Requested by OS process 14652 on instance 2

Mon Dec 21 17:54:17 2015

RFS[11]: Selected log 12 for thread 1 sequence 9902 dbid 1853001179 branch 864558941

In this case, when I checked the database, archive logs were transferred succesfully, but the APPLY operation could not be performed.

(STANDBY DB)

In this case, I thought to restart the RECOVER operation in the STANDBY Database and ran the following query on both NODEs. In the second NODE, the process was completed within a few seconds, the first NODE was stuck.

Because the above process did not work successfully, I closed the database and started again. This process took a long time. Because there were suspended processes.

After the database opened without any problems, I started the RECOVER process again.

It is necessary to check whether the archive logs are being applied. We can see this in two ways.

With SQL Query;

From Alert Log;

In ALERT_LOG file above, after STANDBY DB is altered, the process flow is seen. The step of MEDIA RECOVERY shows that the ARCHIVE LOGS are applied.