SQL> select name,db_unique_name,database_role from v$database; 

NAME      DB_UNIQUE_NAME                 DATABASE_ROLE
--------- ------------------------------ ----------------
FBDB      fbdb                           PRIMARY

SQL> select name,db_unique_name,database_role from v$database; 

NAME      DB_UNIQUE_NAME                 DATABASE_ROLE
--------- ------------------------------ ----------------
FBDB      fbdb2                          PHYSICAL STANDBY

Thu Jun 28 13:13:03 2018
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =36
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /opt/oracle/product/11gR2/db/dbs/spfilefbdb2.ora
System parameters with non-default values:
  processes                = 200
  memory_target            = 1568M
  control_files            = "/opt/oracle/oradata/fbdb/control01.ctl"
  log_file_name_convert    = "/opt/oracle/oradata/fbdb/"
  log_file_name_convert    = "/opt/oracle/oradata/fbdb2/"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  log_archive_dest_1       = "location=/opt/oracle/flash_recovery_area/FBDB2/ valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_na
me=fbdb2"
  log_archive_dest_2       = "service=fbdb.4.ru ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=fbdb"
  log_archive_dest_state_1 = "ENABLE"
  log_archive_dest_state_2 = "ENABLE"
  fal_client               = "fbdb2"
  fal_server               = "fbdb"
  log_archive_config       = "dg_config=(fbdb,fbdb2)"
  log_archive_format       = "log_%s_%t_%r.arc"
  db_recovery_file_dest    = "/opt/oracle/flash_recovery_area"
  db_recovery_file_dest_size= 3882M
  standby_file_management  = "AUTO"
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = "4.ru"
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=fbdbXDB)"
  audit_file_dest          = "/opt/oracle/admin/fbdb/adump"
  optimizer_features_enable= "11.1.0.7"
  audit_trail              = "DB"
  db_name                  = "fbdb"
  db_unique_name           = "fbdb2"
  open_cursors             = 300
  diagnostic_dest          = "/opt/oracle"
Thu Jun 28 13:13:04 2018
PMON started with pid=2, OS id=27931
Thu Jun 28 13:13:04 2018
VKTM started with pid=3, OS id=27933 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Thu Jun 28 13:13:04 2018
GEN0 started with pid=4, OS id=27937
Thu Jun 28 13:13:04 2018
DIAG started with pid=5, OS id=27939
Thu Jun 28 13:13:04 2018
DBRM started with pid=6, OS id=27941
Thu Jun 28 13:13:04 2018
PSP0 started with pid=7, OS id=27943
Thu Jun 28 13:13:04 2018
DIA0 started with pid=8, OS id=27945
Thu Jun 28 13:13:04 2018
MMAN started with pid=9, OS id=27947
Thu Jun 28 13:13:04 2018
DBW0 started with pid=10, OS id=27949
Thu Jun 28 13:13:04 2018
DBW1 started with pid=11, OS id=27951
Thu Jun 28 13:13:04 2018
LGWR started with pid=12, OS id=27953
Thu Jun 28 13:13:04 2018
CKPT started with pid=13, OS id=27955
Thu Jun 28 13:13:04 2018
SMON started with pid=14, OS id=27957
Thu Jun 28 13:13:04 2018
RECO started with pid=15, OS id=27959
Thu Jun 28 13:13:04 2018
MMON started with pid=16, OS id=27961
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu Jun 28 13:13:04 2018
MMNL started with pid=17, OS id=27963
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
Thu Jun 28 13:13:04 2018
ALTER DATABASE   MOUNT
ARCH: STARTING ARCH PROCESSES
Thu Jun 28 13:13:11 2018
ARC0 started with pid=21, OS id=27983
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Thu Jun 28 13:13:12 2018
ARC1 started with pid=22, OS id=27985
Thu Jun 28 13:13:12 2018
ARC2 started with pid=23, OS id=27987
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Thu Jun 28 13:13:12 2018
ARC3 started with pid=24, OS id=27989
Successful mount of redo thread 1, with mount id 2524904035
Physical Standby Database mounted.
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Thu Jun 28 13:13:12 2018
ALTER DATABASE OPEN
AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby Recovery starting Real Time Apply
Media Recovery Log /opt/oracle/flash_recovery_area/FBDB2/log_45179_1_739062520.arc
Thu Jun 28 13:13:13 2018
Using STANDBY_ARCHIVE_DEST parameter default value as /opt/oracle/flash_recovery_area/FBDB2/
RFS[1]: Assigned to RFS process 27997
RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 10338
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Thu Jun 28 13:13:13 2018
RFS[2]: Assigned to RFS process 28000
RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 13164
Thu Jun 28 13:13:14 2018
RFS[3]: Assigned to RFS process 28003
RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 10330
RFS[1]: Opened log for thread 1 sequence 45258 dbid -2011023244 branch 739062520
Thu Jun 28 13:13:15 2018
RFS[4]: Assigned to RFS process 28006
RFS[4]: Identified database type as 'physical standby': Client is LGWR ASYNC pid 10340
RFS[3]: Opened log for thread 1 sequence 45257 dbid -2011023244 branch 739062520
RFS[2]: Selected log 4 for thread 1 sequence 45256 dbid -2011023244 branch 739062520
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Selected log 5 for thread 1 sequence 45268 dbid -2011023244 branch 739062520
Archived Log entry 96 added for thread 1 sequence 45258 rlc 739062520 ID 0x88226174 dest 2:
Archived Log entry 97 added for thread 1 sequence 45257 rlc 739062520 ID 0x88226174 dest 2:
Thu Jun 28 13:13:18 2018
RFS[5]: Assigned to RFS process 28009
RFS[5]: Identified database type as 'physical standby': Client is ARCH pid 10338
Thu Jun 28 13:13:18 2018
RFS[6]: Assigned to RFS process 28012
RFS[6]: Identified database type as 'physical standby': Client is ARCH pid 10330
RFS[5]: Opened log for thread 1 sequence 45259 dbid -2011023244 branch 739062520
RFS[6]: Opened log for thread 1 sequence 45260 dbid -2011023244 branch 739062520
Thu Jun 28 13:13:20 2018
RFS[7]: Assigned to RFS process 28015
RFS[7]: Identified database type as 'physical standby': Client is ARCH pid 13164
Archived Log entry 98 added for thread 1 sequence 45256 ID 0x88226174 dest 1:
Thu Jun 28 13:13:21 2018
Archived Log entry 99 added for thread 1 sequence 45268 ID 0x88226174 dest 1:
RFS[4]: Selected log 4 for thread 1 sequence 45269 dbid -2011023244 branch 739062520
Archived Log entry 100 added for thread 1 sequence 45260 rlc 739062520 ID 0x88226174 dest 2:
Archived Log entry 101 added for thread 1 sequence 45259 rlc 739062520 ID 0x88226174 dest 2:
RFS[7]: Opened log for thread 1 sequence 45261 dbid -2011023244 branch 739062520
RFS[5]: Opened log for thread 1 sequence 45263 dbid -2011023244 branch 739062520
Archived Log entry 102 added for thread 1 sequence 45261 rlc 739062520 ID 0x88226174 dest 2:
RFS[6]: Opened log for thread 1 sequence 45262 dbid -2011023244 branch 739062520
Thu Jun 28 13:13:24 2018
Media Recovery Log /opt/oracle/flash_recovery_area/FBDB2/log_45180_1_739062520.arc
Archived Log entry 103 added for thread 1 sequence 45262 rlc 739062520 ID 0x88226174 dest 2:
RFS[7]: Opened log for thread 1 sequence 45264 dbid -2011023244 branch 739062520
Archived Log entry 104 added for thread 1 sequence 45263 rlc 739062520 ID 0x88226174 dest 2:
Archived Log entry 105 added for thread 1 sequence 45264 rlc 739062520 ID 0x88226174 dest 2:
RFS[5]: Opened log for thread 1 sequence 45266 dbid -2011023244 branch 739062520
RFS[6]: Opened log for thread 1 sequence 45265 dbid -2011023244 branch 739062520
RFS[7]: Opened log for thread 1 sequence 45267 dbid -2011023244 branch 739062520
Thu Jun 28 13:13:29 2018
Archived Log entry 106 added for thread 1 sequence 45266 rlc 739062520 ID 0x88226174 dest 2:
Archived Log entry 107 added for thread 1 sequence 45267 rlc 739062520 ID 0x88226174 dest 2:
Thu Jun 28 13:13:29 2018
Archived Log entry 108 added for thread 1 sequence 45265 rlc 739062520 ID 0x88226174 dest 2:
Thu Jun 28 13:13:37 2018
Incomplete Recovery applied until change 3808347129 time 06/24/2018 01:27:54
Completed standby crash recovery.
Thu Jun 28 13:13:37 2018
SMON: enabling cache recovery
Dictionary check beginning
Thu Jun 28 13:13:37 2018
Errors in file /opt/oracle/diag/rdbms/fbdb2/fbdb2.4.ru/trace/fbdb2.4.ru_dbw0_27949:
ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
ORA-01110: data file 201: '/opt/oracle/oradata/fbdb/temp01.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /opt/oracle/diag/rdbms/fbdb2/fbdb2.4.ru/trace/fbdb2.4.ru_dbw0_27949:
ORA-01186: file 201 failed verification tests
ORA-01157: cannot identify/lock data file 201 - see DBWR trace file
ORA-01110: data file 201: '/opt/oracle/oradata/fbdb/temp01.dbf'
File 201 not verified due to error ORA-01157
Dictionary check complete
Re-creating tempfile /opt/oracle/oradata/fbdb/temp01.dbf
Database Characterset is AL32UTF8
No Resource Manager plan active
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
   then disabled.
**********************************************************
replication_dependency_tracking turned off (no async multimaster replication found)
Physical standby database opened for read only access.
Thu Jun 28 13:13:40 2018
db_recovery_file_dest_size of 3882 MB is 0.00% 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.
Completed: ALTER DATABASE OPEN

RMAN> CATALOG RECOVERY AREA;

using target database control file instead of recovery catalog
searching for all files in the recovery area
no files found to be unknown to the database

List of files in Recovery Area not managed by the database
==========================================================
File Name: /opt/oracle/flash_recovery_area/FBDB2/log_45161_1_739062520.arc
  RMAN-07526: Reason: File is not an Oracle Managed File
File Name: /opt/oracle/flash_recovery_area/FBDB2/log_45162_1_739062520.arc
  RMAN-07526: Reason: File is not an Oracle Managed File
....

File Name: /opt/oracle/flash_recovery_area/FBDB2/log_45265_1_739062520.arc
  RMAN-07526: Reason: File is not an Oracle Managed File

number of files not managed by recovery area is 108, totaling 3.92GB