when i am issuing duplicate command from standby database. show some statics on screen that goes well but stuck in datafile copy mode.and in alertlog file i found this....
Mon Jul 22 14:58:37 2019
PMON started with pid=2, OS id=1944
Mon Jul 22 14:58:37 2019
PSP0 started with pid=3, OS id=256
Mon Jul 22 14:58:38 2019
VKTM started with pid=4, OS id=584 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Mon Jul 22 14:58:39 2019
GEN0 started with pid=5, OS id=3068
Mon Jul 22 14:58:39 2019
DIAG started with pid=6, OS id=1800
Mon Jul 22 14:58:39 2019
DBRM started with pid=7, OS id=1628
Mon Jul 22 14:58:39 2019
DIA0 started with pid=8, OS id=2896
Mon Jul 22 14:58:39 2019
MMAN started with pid=9, OS id=2756
Mon Jul 22 14:58:39 2019
DBW0 started with pid=10, OS id=2828
Mon Jul 22 14:58:39 2019
LGWR started with pid=11, OS id=2592
Mon Jul 22 14:58:39 2019
CKPT started with pid=12, OS id=192
Mon Jul 22 14:58:39 2019
SMON started with pid=13, OS id=2800
Mon Jul 22 14:58:39 2019
RECO started with pid=14, OS id=1996
Mon Jul 22 14:58:39 2019
MMON started with pid=15, OS id=872
Mon Jul 22 14:58:39 2019
MMNL started with pid=16, OS id=1592
ORACLE_BASE from environment = D:\app\Administrator
Mon Jul 22 15:01:50 2019
Using STANDBY_ARCHIVE_DEST parameter default value as d:\oracle\oradata\BVKORA\archive
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:02:12 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:07:51 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:08:52 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:09:52 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:10:52 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:11:53 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:12:53 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:13:54 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:14:54 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:15:54 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:16:55 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:17:58 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:18:59 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:19:59 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:21:00 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:22:00 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:23:00 2019
destination database instance is 'started' not 'mounted'
Mon Jul 22 15:23:46 2019
RFS connections have been disallowed
alter database mount standby database
Set as converted control file due to db_unique_name mismatch
Changing di2dbun from bvkora to bvkora_icg
ARCH: STARTING ARCH PROCESSES
Mon Jul 22 15:23:51 2019
ARC0 started with pid=21, OS id=2812
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Mon Jul 22 15:23:52 2019
ARC1 started with pid=22, OS id=1608
Mon Jul 22 15:23:52 2019
ARC2 started with pid=23, OS id=1068
Mon Jul 22 15:23:52 2019
Successful mount of redo thread 1, with mount id 419331267
Mon Jul 22 15:23:52 2019
ARC3 started with pid=24, OS id=2788
Mon Jul 22 15:23:52 2019
ARC4 started with pid=25, OS id=2868
Mon Jul 22 15:23:52 2019
ARC5 started with pid=26, OS id=2152
Mon Jul 22 15:23:52 2019
ARC6 started with pid=27, OS id=2296
Physical Standby Database mounted.
Lost write protection disabled
Mon Jul 22 15:23:52 2019
ARC7 started with pid=28, OS id=1304
Mon Jul 22 15:23:52 2019
ARC8 started with pid=29, OS id=1604
Mon Jul 22 15:23:52 2019
ARC9 started with pid=30, OS id=1104
Mon Jul 22 15:23:52 2019
ARCa started with pid=31, OS id=2332
Mon Jul 22 15:23:52 2019
ARCb started with pid=32, OS id=2912
Mon Jul 22 15:23:52 2019
ARCc started with pid=33, OS id=2384
Mon Jul 22 15:23:52 2019
ARCd started with pid=34, OS id=1556
Mon Jul 22 15:23:52 2019
ARCe started with pid=35, OS id=1532
Mon Jul 22 15:23:52 2019
ARCf started with pid=36, OS id=1432
Mon Jul 22 15:23:52 2019
ARCg started with pid=37, OS id=2876
Mon Jul 22 15:23:52 2019
ARCh started with pid=38, OS id=2744
Mon Jul 22 15:23:52 2019
ARCi started with pid=39, OS id=664
Mon Jul 22 15:23:52 2019
ARCj started with pid=40, OS id=2736
Mon Jul 22 15:23:52 2019
ARCk started with pid=41, OS id=2164
Mon Jul 22 15:23:52 2019
ARCl started with pid=42, OS id=1660
Mon Jul 22 15:23:52 2019
ARCm started with pid=43, OS id=2980
Mon Jul 22 15:23:52 2019
ARCn started with pid=44, OS id=2188
Mon Jul 22 15:23:52 2019
ARCo started with pid=45, OS id=1792
Mon Jul 22 15:23:52 2019
ARCp started with pid=46, OS id=2104
Mon Jul 22 15:23:52 2019
ARCq started with pid=47, OS id=712
Mon Jul 22 15:23:52 2019
ARCr started with pid=48, OS id=2428
Mon Jul 22 15:23:52 2019
ARCs started with pid=49, OS id=2900
Mon Jul 22 15:23:52 2019
ARCt started with pid=50, OS id=2320
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC8: Becoming the 'no FAL' ARCH
ARCa: Becoming the heartbeat ARCH
ARCa: Becoming the active heartbeat ARCH
Completed: alter database mount standby database
ARCt: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\BVKORA\RDO_01A.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\BVKORA\RDO_01A.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: 'D:\ORACLE\ORADATA\BVKORA\RDO_02A.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: 'D:\ORACLE\ORADATA\BVKORA\RDO_02A.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'D:\ORACLE\ORADATA\BVKORA\RDO_03A.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'D:\ORACLE\ORADATA\BVKORA\RDO_03A.LOG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: 'D:\ORACLE\ORADATA\BVKORA\STBY_REDO1'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 4 of thread 1
ORA-00312: online log 4 thread 1: 'D:\ORACLE\ORADATA\BVKORA\STBY_REDO1'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 5 of thread 1
ORA-00312: online log 5 thread 1: 'D:\ORACLE\ORADATA\BVKORA\STBY_REDO2'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\bvkora_icg\bvkora_icg\trace\bvkora_icg_lgwr_2592.trc:
ORA-00313: open failed for members of log group 5 of thread 1
ORA-00312: online log 5 thread 1: 'D:\ORACLE\ORADATA\BVKORA\STBY_REDO2'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.