10.2.0.4 DG 数据文件同步问题处理

on Jul 17 09:01:24 2017
Media Recovery Log /oraarch/2_399352_718202774.dbf
Mon Jul 17 09:02:38 2017
Media Recovery Log /oraarch/1_507473_718202774.dbf
Mon Jul 17 09:03:53 2017
Media Recovery Log /oraarch/1_507474_718202774.dbf
Mon Jul 17 09:05:09 2017
Media Recovery Waiting for thread 1 sequence 507475 (in transit)
Mon Jul 17 09:12:24 2017
RFS[3]: Archived Log: '/oraarch/1_507475_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:12:25 2017
Media Recovery Log /oraarch/1_507475_718202774.dbf
Media Recovery Waiting for thread 2 sequence 399353 (in transit)
Mon Jul 17 09:17:55 2017
RFS[4]: Archived Log: '/oraarch/2_399353_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:17:56 2017
Media Recovery Log /oraarch/2_399353_718202774.dbf
Mon Jul 17 09:18:59 2017
Media Recovery Waiting for thread 1 sequence 507476 (in transit)
Mon Jul 17 09:21:40 2017
RFS[4]: Archived Log: '/oraarch/2_399354_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:25:02 2017
RFS[3]: Archived Log: '/oraarch/1_507476_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:25:05 2017
Media Recovery Log /oraarch/1_507476_718202774.dbf
Mon Jul 17 09:25:15 2017
RFS[4]: Archived Log: '/oraarch/2_399355_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:26:12 2017
Media Recovery Log /oraarch/2_399354_718202774.dbf
Mon Jul 17 09:27:09 2017
Media Recovery Log /oraarch/2_399355_718202774.dbf
Mon Jul 17 09:27:47 2017
Media Recovery Waiting for thread 2 sequence 399356 (in transit)
Mon Jul 17 09:32:27 2017
RFS[4]: Archived Log: '/oraarch/2_399356_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:32:28 2017
Media Recovery Log /oraarch/2_399356_718202774.dbf
Media Recovery Waiting for thread 1 sequence 507477 (in transit)
Mon Jul 17 09:38:08 2017
RFS[4]: Archived Log: '/oraarch/2_399357_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:40:09 2017
RFS[3]: Archived Log: '/oraarch/1_507477_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:40:12 2017
Media Recovery Log /oraarch/1_507477_718202774.dbf
Mon Jul 17 09:40:20 2017
RFS[4]: Archived Log: '/oraarch/2_399358_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:40:33 2017
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 09:40:51 2017
Recovery created file /dev/vg_pedbsv24/rr04G1075
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 09:41:08 2017
Recovery created file /dev/vg_pedbsv24/rr04G1076
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 09:41:26 2017
Recovery created file /dev/vg_pedbsv24/rr04G1077
Successfully added datafile 3263 to media recovery
Datafile #3263: '/dev/vg_pedbsv24/rr04G1075'
Successfully added datafile 3264 to media recovery
Datafile #3264: '/dev/vg_pedbsv24/rr04G1076'
Successfully added datafile 3265 to media recovery
Datafile #3265: '/dev/vg_pedbsv24/rr04G1077'
Mon Jul 17 09:41:45 2017
Media Recovery Log /oraarch/2_399357_718202774.dbf
Mon Jul 17 09:43:00 2017
Media Recovery Log /oraarch/2_399358_718202774.dbf
Mon Jul 17 09:43:57 2017
RFS[4]: Archived Log: '/oraarch/2_399359_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:44:15 2017
Media Recovery Log /oraarch/2_399359_718202774.dbf
Media Recovery Waiting for thread 1 sequence 507478 (in transit)
Mon Jul 17 09:46:23 2017
RFS[3]: Archived Log: '/oraarch/1_507478_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:46:24 2017
Media Recovery Log /oraarch/1_507478_718202774.dbf
Mon Jul 17 09:48:02 2017
RFS[4]: Archived Log: '/oraarch/2_399360_718202774.dbf'
Mon Jul 17 09:48:04 2017
Media Recovery Waiting for thread 2 sequence 399360 (in transit)
Mon Jul 17 09:48:04 2017
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:48:09 2017
Media Recovery Log /oraarch/2_399360_718202774.dbf
Mon Jul 17 09:48:58 2017
Media Recovery Waiting for thread 1 sequence 507479 (in transit)
Mon Jul 17 09:51:24 2017
RFS[4]: Archived Log: '/oraarch/2_399361_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:54:57 2017
RFS[3]: Archived Log: '/oraarch/1_507479_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:55:00 2017
Media Recovery Log /oraarch/1_507479_718202774.dbf
Mon Jul 17 09:55:13 2017
RFS[4]: Archived Log: '/oraarch/2_399362_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 09:55:29 2017
Media Recovery Log /oraarch/2_399361_718202774.dbf
Mon Jul 17 09:56:12 2017
Media Recovery Log /oraarch/2_399362_718202774.dbf
Mon Jul 17 09:56:50 2017
Media Recovery Waiting for thread 2 sequence 399363 (in transit)
Mon Jul 17 10:00:18 2017
RFS[3]: Archived Log: '/oraarch/1_507480_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:00:25 2017
RFS[4]: Archived Log: '/oraarch/2_399363_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:00:26 2017
Media Recovery Log /oraarch/2_399363_718202774.dbf
Media Recovery Log /oraarch/1_507480_718202774.dbf
Mon Jul 17 10:01:02 2017
Media Recovery Waiting for thread 2 sequence 399364 (in transit)
Mon Jul 17 10:01:11 2017
RFS[4]: Archived Log: '/oraarch/2_399364_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:01:12 2017
Media Recovery Log /oraarch/2_399364_718202774.dbf
Media Recovery Waiting for thread 1 sequence 507481 (in transit)
Mon Jul 17 10:07:21 2017
RFS[4]: Archived Log: '/oraarch/2_399365_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:10:58 2017
RFS[3]: Archived Log: '/oraarch/1_507481_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:11:02 2017
Media Recovery Log /oraarch/1_507481_718202774.dbf
Mon Jul 17 10:11:31 2017
RFS[4]: Archived Log: '/oraarch/2_399366_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:11:37 2017
Media Recovery Log /oraarch/2_399365_718202774.dbf
Mon Jul 17 10:12:11 2017
RFS[1]: No standby redo logfiles of size 1823417 blocks exist
Mon Jul 17 10:12:34 2017
Media Recovery Log /oraarch/2_399366_718202774.dbf
Mon Jul 17 10:13:19 2017
RFS[1]: Archived Log: '/oraarch/2_399367_718202774.dbf'
Mon Jul 17 10:13:51 2017
Media Recovery Log /oraarch/2_399367_718202774.dbf
Media Recovery Waiting for thread 1 sequence 507482 (in transit)
Mon Jul 17 10:19:50 2017
RFS[3]: Archived Log: '/oraarch/1_507482_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:19:52 2017
Media Recovery Log /oraarch/1_507482_718202774.dbf
Mon Jul 17 10:20:06 2017
RFS[4]: Archived Log: '/oraarch/2_399368_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:20:30 2017
Media Recovery Log /oraarch/2_399368_718202774.dbf
Mon Jul 17 10:20:57 2017
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:21:16 2017
Recovery created file /dev/vg_pedbsv24/rr04G1083
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:21:37 2017
Recovery created file /dev/vg_pedbsv24/rr04G1084
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:21:59 2017
Recovery created file /dev/vg_pedbsv24/rr04G1085
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:22:19 2017
Recovery created file /dev/vg_pedbsv24/rr04G1086
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:22:38 2017
Recovery created file /dev/vg_pedbsv24/rr04G1087
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:22:58 2017
Recovery created file /dev/vg_pedbsv24/rr04G1088
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:23:18 2017
Recovery created file /dev/vg_pedbsv24/rr04G1089
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:23:39 2017
Recovery created file /dev/vg_pedbsv24/rr04G1090
Successfully added datafile 3266 to media recovery
Datafile #3266: '/dev/vg_pedbsv24/rr04G1083'
Successfully added datafile 3267 to media recovery
Datafile #3267: '/dev/vg_pedbsv24/rr04G1084'
Successfully added datafile 3268 to media recovery
Datafile #3268: '/dev/vg_pedbsv24/rr04G1085'
Successfully added datafile 3269 to media recovery
Datafile #3269: '/dev/vg_pedbsv24/rr04G1086'
Successfully added datafile 3270 to media recovery
Datafile #3270: '/dev/vg_pedbsv24/rr04G1087'
Successfully added datafile 3271 to media recovery
Datafile #3271: '/dev/vg_pedbsv24/rr04G1088'
Successfully added datafile 3272 to media recovery
Datafile #3272: '/dev/vg_pedbsv24/rr04G1089'
Successfully added datafile 3273 to media recovery
Datafile #3273: '/dev/vg_pedbsv24/rr04G1090'
Mon Jul 17 10:24:48 2017
Media Recovery Waiting for thread 2 sequence 399369 (in transit)
Mon Jul 17 10:25:07 2017
RFS[4]: Archived Log: '/oraarch/2_399369_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:25:08 2017
Media Recovery Log /oraarch/2_399369_718202774.dbf
Mon Jul 17 10:25:25 2017
Media Recovery Waiting for thread 1 sequence 507483 (in transit)
Mon Jul 17 10:27:10 2017
RFS[1]: No standby redo logfiles of size 1843191 blocks exist
Mon Jul 17 10:28:03 2017
RFS[1]: Archived Log: '/oraarch/2_399370_718202774.dbf'
Mon Jul 17 10:32:35 2017
RFS[3]: Archived Log: '/oraarch/1_507483_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:32:37 2017
Media Recovery Log /oraarch/1_507483_718202774.dbf
Mon Jul 17 10:32:54 2017
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:33:02 2017
RFS[4]: Archived Log: '/oraarch/2_399371_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:33:11 2017
Recovery created file /dev/vg_pedbsv25/rr04G1005
WARNING: File being created with same name as in Primary
Existing file may be overwritten
Mon Jul 17 10:33:28 2017
Recovery created file /dev/vg_pedbsv25/rr04G1006
Successfully added datafile 3274 to media recovery
Datafile #3274: '/dev/vg_pedbsv25/rr04G1005'
Successfully added datafile 3275 to media recovery
Datafile #3275: '/dev/vg_pedbsv25/rr04G1006'
Mon Jul 17 10:33:42 2017
RFS[1]: No standby redo logfiles of size 1837185 blocks exist
Creating archive destination file : /oraarch/2_399372_718202774.dbf (1837185 blocks)
Mon Jul 17 10:33:42 2017
Errors in file /oracle/admin/TESTDG/udump/TESTDG_rfs_3456.trc:
ORA-00270: error creating archive log /oraarch/2_399372_718202774.dbf
ORA-19504: failed to create file "/oraarch/2_399372_718202774.dbf"
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Mon Jul 17 10:33:42 2017
Errors in file /oracle/admin/TESTDG/udump/TESTDG_rfs_3456.trc:
ORA-00270: error creating archive log /oraarch/2_399372_718202774.dbf
ORA-19504: failed to create file "/oraarch/2_399372_718202774.dbf"
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Mon Jul 17 10:34:05 2017
Media Recovery Log /oraarch/2_399370_718202774.dbf
Mon Jul 17 10:34:44 2017
Media Recovery Log /oraarch/2_399371_718202774.dbf
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #3276 added to control file as 'UNNAMED03276'.
Originally created as:
'/dev/vg_pedbsv25/rr04G1014'
Recovery was unable to create the file as:
'/dev/vg_pedbsv25/rr04G1014'
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #3277 added to control file as 'UNNAMED03277'.
Originally created as:
'/dev/vg_pedbsv25/rr04G1015'
Recovery was unable to create the file as:
'/dev/vg_pedbsv25/rr04G1015'
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #3278 added to control file as 'UNNAMED03278'.
Originally created as:
'/dev/vg_pedbsv25/rr04G1016'
Recovery was unable to create the file as:
'/dev/vg_pedbsv25/rr04G1016'
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #3279 added to control file as 'UNNAMED03279'.
Originally created as:
'/dev/vg_pedbsv25/rr04G1017'
Recovery was unable to create the file as:
'/dev/vg_pedbsv25/rr04G1017'
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #3280 added to control file as 'UNNAMED03280'.
Originally created as:
'/dev/vg_pedbsv25/rr04G1018'
Recovery was unable to create the file as:
'/dev/vg_pedbsv25/rr04G1018'
WARNING: File being created with same name as in Primary
Existing file may be overwritten
File #3281 added to control file as 'UNNAMED03281'.
Originally created as:
'/dev/vg_pedbsv25/rr04G1019'
Recovery was unable to create the file as:
'/dev/vg_pedbsv25/rr04G1019'
Errors with log /oraarch/2_399371_718202774.dbf
MRP0: Background Media Recovery terminated with error 1119
Mon Jul 17 10:34:47 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_3390.trc:
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1019'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1018'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1017'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1016'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1015'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1014'
ORA-27086: unab
Managed Standby Recovery not using Real Time Apply
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Mon Jul 17 10:34:50 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_3390.trc:
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1019'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1018'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1017'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1016'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1015'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
ORA-01119: error in creating database file '/dev/vg_pedbsv25/rr04G1014'
ORA-27086: unab
Mon Jul 17 10:34:50 2017
MRP0: Background Media Recovery process shutdown (TESTDG)
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 20288
RFS[5]: Identified database type as 'physical standby'
Mon Jul 17 10:39:33 2017
RFS[5]: Archived Log: '/oraarch/2_399372_718202774.dbf'
Mon Jul 17 10:41:39 2017
RFS[4]: Archived Log: '/oraarch/2_399373_718202774.dbf'
Mon Jul 17 10:41:39 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[6]: Assigned to RFS process 20387
RFS[6]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:41:44 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[7]: Assigned to RFS process 20398
RFS[7]: Identified database type as 'physical standby'
Mon Jul 17 10:41:56 2017
RFS[3]: Archived Log: '/oraarch/1_507484_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:42:20 2017
RFS[6]: Archived Log: '/oraarch/2_399374_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 10:50:23 2017
RFS[3]: Archived Log: '/oraarch/1_507485_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 11:10:13 2017
RFS[3]: Archived Log: '/oraarch/1_507486_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 11:10:15 2017
RFS[6]: Archived Log: '/oraarch/2_399375_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 11:17:36 2017
RFS[3]: Archived Log: '/oraarch/1_507487_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 11:38:37 2017
RFS[3]: Archived Log: '/oraarch/1_507488_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 11:44:16 2017
RFS[3]: Archived Log: '/oraarch/1_507489_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 11:44:18 2017
RFS[6]: Archived Log: '/oraarch/2_399376_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 12:00:33 2017
RFS[6]: Archived Log: '/oraarch/2_399377_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 12:00:36 2017
RFS[3]: Archived Log: '/oraarch/1_507490_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 12:08:14 2017
RFS[3]: Archived Log: '/oraarch/1_507491_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 12:18:39 2017
RFS[3]: Archived Log: '/oraarch/1_507492_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 12:18:40 2017
RFS[6]: Archived Log: '/oraarch/2_399378_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 12:39:22 2017
RFS[3]: Archived Log: '/oraarch/1_507493_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:06:12 2017
RFS[3]: Archived Log: '/oraarch/1_507494_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:12:51 2017
RFS[3]: Archived Log: '/oraarch/1_507495_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:12:54 2017
RFS[6]: Archived Log: '/oraarch/2_399379_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:20:27 2017
RFS[3]: Archived Log: '/oraarch/1_507496_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:40:15 2017
RFS[3]: Archived Log: '/oraarch/1_507497_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:47:19 2017
RFS[3]: Archived Log: '/oraarch/1_507498_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 13:47:21 2017
RFS[6]: Archived Log: '/oraarch/2_399380_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 14:11:01 2017
RFS[3]: Archived Log: '/oraarch/1_507499_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 14:18:26 2017
RFS[3]: Archived Log: '/oraarch/1_507500_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 14:38:40 2017
RFS[3]: Archived Log: '/oraarch/1_507501_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 14:38:41 2017
RFS[6]: Archived Log: '/oraarch/2_399381_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 14:44:46 2017
RFS[3]: Archived Log: '/oraarch/1_507502_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:06:49 2017
RFS[3]: Archived Log: '/oraarch/1_507503_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:14:08 2017
RFS[3]: Archived Log: '/oraarch/1_507504_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:14:09 2017
RFS[6]: Archived Log: '/oraarch/2_399382_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:36:06 2017
RFS[3]: Archived Log: '/oraarch/1_507505_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:40:40 2017
RFS[3]: Archived Log: '/oraarch/1_507506_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:55:18 2017
RFS[3]: Archived Log: '/oraarch/1_507507_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 15:55:19 2017
RFS[6]: Archived Log: '/oraarch/2_399383_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[6]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 16:12:24 2017
RFS[3]: Archived Log: '/oraarch/1_507508_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 16:19:33 2017
RFS[3]: Archived Log: '/oraarch/1_507509_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 16:22:58 2017
alter database recover managed standby database cancel
Mon Jul 17 16:22:58 2017
ORA-16136 signalled during: alter database recover managed standby database cancel...
Mon Jul 17 16:24:57 2017
Shutting down instance: further logons disabled
Mon Jul 17 16:24:57 2017
Stopping background process CJQ0
Mon Jul 17 16:24:57 2017
Stopping background process MMNL
Mon Jul 17 16:24:58 2017
Stopping background process MMON
Mon Jul 17 16:24:59 2017
Shutting down instance (immediate)
License high water mark = 23
Mon Jul 17 16:24:59 2017
Stopping Job queue slave processes, flags = 7
Mon Jul 17 16:24:59 2017
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Mon Jul 17 16:25:02 2017
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Mon Jul 17 16:25:02 2017
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Jul 17 16:25:07 2017
ARCH shutting down
ARC1: Archival stopped
Mon Jul 17 16:25:12 2017
ARCH shutting down
ARC0: Archival stopped
Mon Jul 17 16:25:14 2017
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Jul 17 16:25:22 2017
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned off. 
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 4096
  sessions                 = 4510
  instance_groups          = third_group
  sga_max_size             = 26843545600
  _enable_NUMA_optimization= FALSE
  __shared_pool_size       = 2667577344
  __large_pool_size        = 167772160
  large_pool_size          = 167772160
  __java_pool_size         = 16777216
  __streams_pool_size      = 0
  spfile                   = /dev/vg_pedbsv13/rr256M1002
  disk_asynch_io           = FALSE
  backup_tape_io_slaves    = TRUE
  _lm_dd_interval          = 30
  sga_target               = 26843545600
  control_files            = /dev/vg_pedbsv11/rr01G1001, /dev/vg_pedbsv12/rr01G1001, /dev/vg_pedbsv13/rr01G1001
  log_file_name_convert    = /dev/vg_pedbsv11/rr500M1001, /dev/vg_pedbsv11/rr500M1001, /dev/vg_pedbsv12/rr500M1003, /dev/vg_pedbsv12
/rr500M1003, /dev/vg_pedbsv12/rr500M1001, /dev/vg_pedbsv12/rr500M1001, /dev/vg_pedbsv13/rr500M1003, /dev/vg_pedbsv13/rr500M1003, /de
v/vg_pedbsv13/rr500M1001, /dev/vg_pedbsv13/rr500M1001, /dev/vg_pedbsv11/rr500M1003, /dev/vg_pedbsv11/rr500M1003, /dev/vg_pedbsv11/rr
500M1002, /dev/vg_pedbsv11/rr500M1002, /dev/vg_pedbsv12/rr500M1004, /dev/vg_pedbsv12/rr500M1004, /dev/vg_pedbsv12/rr500M1002, /dev/v
g_pedbsv12/rr
  db_block_size            = 8192
  __db_cache_size          = 23924310016
  db_writer_processes      = 16
  compatible               = 10.2.0.3.0
  log_archive_config       = dg_config=(PEDBDB,TESTDG)
  log_archive_dest_1       = location=/oraarch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=TESTDG
  log_archive_dest_state_1 = enable
  fal_client               = TESTDG
  fal_server               = PEDBDB1, PEDBDB2
  log_buffer               = 64002048
  db_files                 = 6000
  db_file_multiblock_read_count= 16
  cluster_database         = FALSE
  standby_file_management  = AUTO
  _gc_undo_affinity        = FALSE
  _gc_affinity_time        = 0
  thread                   = 1
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  _in_memory_undo          = FALSE
  _undo_autotune           = FALSE
  undo_retention           = 10800
  _kks_use_mutex_pin       = FALSE
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = 
  service_names            = TESTDG
  dispatchers              = (PROTOCOL=TCP) (SERVICE=TESTDGXDB)
  local_listener           = (address=(protocol=tcp)(host=10.70.1.200)(port=1521))
  remote_listener          = 
  job_queue_processes      = 100
  parallel_instance_group  = third_group
  background_dump_dest     = /oracle/admin/TESTDG/bdump
  user_dump_dest           = /oracle/admin/TESTDG/udump
  core_dump_dest           = /oracle/admin/TESTDG/cdump
  audit_file_dest          = /oracle/admin/TESTDG/adump
  hpux_sched_noage         = 178
  db_name                  = PEDBDB
  db_unique_name           = TESTDG
  open_cursors             = 1000
  optimizer_mode           = ALL_ROWS
  _px_rownum_pd            = FALSE
  optimizer_index_cost_adj = 100
  optimizer_index_caching  = 0
  _subquery_pruning_enabled= FALSE
  pga_aggregate_target     = 6442450944
Mon Jul 17 16:25:24 2017
WARNING:Oracle instance running on a system with low open file descriptor 
        limit. Tune your system to increase this limit to avoid 
        severe performance degradation.
PMON started with pid=2, OS id=5297
PSP0 started with pid=3, OS id=5299
MMAN started with pid=4, OS id=5301
DBW0 started with pid=5, OS id=5303
DBW1 started with pid=6, OS id=5305
DBW2 started with pid=7, OS id=5307
DBW3 started with pid=8, OS id=5309
DBW4 started with pid=9, OS id=5311
DBW5 started with pid=10, OS id=5313
DBW6 started with pid=11, OS id=5315
DBW7 started with pid=12, OS id=5317
DBW8 started with pid=13, OS id=5319
DBW9 started with pid=14, OS id=5321
DBWa started with pid=15, OS id=5323
DBWb started with pid=16, OS id=5325
DBWc started with pid=17, OS id=5327
DBWd started with pid=18, OS id=5329
DBWe started with pid=19, OS id=5331
DBWf started with pid=20, OS id=5333
LGWR started with pid=21, OS id=5335
CKPT started with pid=22, OS id=5337
SMON started with pid=23, OS id=5339
RECO started with pid=24, OS id=5341
CJQ0 started with pid=25, OS id=5343
MMON started with pid=26, OS id=5345
Mon Jul 17 16:25:25 2017
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=27, OS id=5347
Mon Jul 17 16:25:25 2017
starting up 1 shared server(s) ...
Mon Jul 17 16:25:33 2017
ALTER DATABASE   MOUNT
Mon Jul 17 16:25:37 2017
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=31, OS id=5354
Mon Jul 17 16:25:37 2017
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Jul 17 16:25:37 2017
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=32, OS id=5356
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Mon Jul 17 16:25:38 2017
Successful mount of redo thread 1, with mount id 4018407037
Mon Jul 17 16:25:38 2017
Physical Standby Database mounted.
Completed: ALTER DATABASE   MOUNT
Mon Jul 17 16:26:34 2017
alter database recover managed standby database disconnect from session
Mon Jul 17 16:26:34 2017
Attempt to start background Managed Standby Recovery process (TESTDG)
MRP0 started with pid=33, OS id=5399
Mon Jul 17 16:26:34 2017
MRP0: Background Managed Standby Recovery process started (TESTDG)
Managed Standby Recovery not using Real Time Apply
Mon Jul 17 16:26:55 2017
MRP0: Background Media Recovery terminated with error 1111
Mon Jul 17 16:26:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_5399.trc:
ORA-01111: name for data file 3276 is unknown - rename to correct file
ORA-01110: data file 3276: '/oracle/OraHome_1/dbs/UNNAMED03276'
ORA-01157: cannot identify/lock data file 3276 - see DBWR trace file
ORA-01111: name for data file 3276 is unknown - rename to correct file
ORA-01110: data file 3276: '/oracle/OraHome_1/dbs/UNNAMED03276'
Mon Jul 17 16:26:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_5399.trc:
ORA-01111: name for data file 3276 is unknown - rename to correct file
ORA-01110: data file 3276: '/oracle/OraHome_1/dbs/UNNAMED03276'
ORA-01157: cannot identify/lock data file 3276 - see DBWR trace file
ORA-01111: name for data file 3276 is unknown - rename to correct file
ORA-01110: data file 3276: '/oracle/OraHome_1/dbs/UNNAMED03276'
Mon Jul 17 16:26:55 2017
MRP0: Background Media Recovery process shutdown (TESTDG)
Mon Jul 17 16:26:56 2017
Completed: alter database recover managed standby database disconnect from session
Mon Jul 17 16:27:22 2017
Using STANDBY_ARCHIVE_DEST parameter default value as /oraarch
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 5434
RFS[1]: Identified database type as 'physical standby'
Mon Jul 17 16:27:22 2017
RFS LogMiner: Client disabled from further notification
Mon Jul 17 16:28:10 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 5459
RFS[2]: Identified database type as 'physical standby'
Mon Jul 17 16:39:43 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 5998
RFS[3]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 16:39:43 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 6000
RFS[4]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 16:40:00 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 6017
RFS[5]: Identified database type as 'physical standby'
RFS[5]: No standby redo logfiles of size 745113 blocks exist
Mon Jul 17 16:40:16 2017
RFS[5]: Archived Log: '/oraarch/2_399384_718202774.dbf'
Mon Jul 17 16:40:17 2017
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[6]: Assigned to RFS process 6019
RFS[6]: Identified database type as 'physical standby'
RFS[6]: No standby redo logfiles of size 1841661 blocks exist
Mon Jul 17 16:41:08 2017
RFS[6]: Archived Log: '/oraarch/1_507510_718202774.dbf'
Mon Jul 17 16:44:26 2017
RFS[3]: Archived Log: '/oraarch/1_507511_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:06:56 2017
RFS[3]: Archived Log: '/oraarch/1_507512_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:14:17 2017
RFS[3]: Archived Log: '/oraarch/1_507513_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:14:19 2017
RFS[4]: Archived Log: '/oraarch/2_399385_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:30:16 2017
RFS[4]: Archived Log: '/oraarch/2_399386_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:30:16 2017
RFS[3]: Archived Log: '/oraarch/1_507514_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:40:37 2017
RFS[3]: Archived Log: '/oraarch/1_507515_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:45:07 2017
RFS[3]: Archived Log: '/oraarch/1_507516_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 17:45:10 2017
RFS[4]: Archived Log: '/oraarch/2_399387_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 18:06:54 2017
RFS[3]: Archived Log: '/oraarch/1_507517_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 18:13:12 2017
RFS[3]: Archived Log: '/oraarch/1_507518_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 18:36:22 2017
RFS[4]: Archived Log: '/oraarch/2_399388_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 18:36:22 2017
RFS[3]: Archived Log: '/oraarch/1_507519_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 18:41:11 2017
RFS[3]: Archived Log: '/oraarch/1_507520_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 18:46:02 2017
RFS[3]: Archived Log: '/oraarch/1_507521_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 19:08:02 2017
RFS[3]: Archived Log: '/oraarch/1_507522_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 19:08:04 2017
RFS[4]: Archived Log: '/oraarch/2_399389_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 19:17:39 2017
RFS[3]: Archived Log: '/oraarch/1_507523_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 19:38:21 2017
RFS[3]: Archived Log: '/oraarch/1_507524_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 19:42:53 2017
RFS[3]: Archived Log: '/oraarch/1_507525_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 19:42:55 2017
RFS[4]: Archived Log: '/oraarch/2_399390_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 20:08:12 2017
RFS[3]: Archived Log: '/oraarch/1_507526_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 20:15:29 2017
RFS[3]: Archived Log: '/oraarch/1_507527_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 20:36:16 2017
RFS[3]: Archived Log: '/oraarch/1_507528_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 20:36:16 2017
RFS[4]: Archived Log: '/oraarch/2_399391_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 20:40:24 2017
RFS[3]: Archived Log: '/oraarch/1_507529_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 21:07:45 2017
RFS[3]: Archived Log: '/oraarch/1_507530_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Mon Jul 17 21:16:06 2017




















SQL> SELECT THREAD#, APPLIED,max(SEQUENCE#) FROM V$ARCHIVED_LOG where APPLIED='YES' group by THREAD#,APPLIED;


   THREAD# APP MAX(SEQUENCE#)
---------- --- --------------
         1 YES         507482
         2 YES         399370
 
是主库那边新增了数据文件，但是备端同步应用的时候发现无法新增，然后自动生成了一个文件名并放到默认的dbs路径下。
这也就是导致日志无法应用的原因了。导致归档日志不断堆积。
ds：
col file_name format a33
col tablespace_name format a28
select file_id,file_name,tablespace_name from dba_data_files where file_id in (3293,3294,3295,3296);


   FILE_ID FILE_NAME                         TABLESPACE_NAME
---------- --------------------------------- ----------------------------
      3286 /dev/vg_pedbsv25/rr04G1021         IDX_PAR_07
      3287 /dev/vg_pedbsv25/rr04G1022         IDX_PAR_07
      3288 /dev/vg_pedbsv25/rr04G1023         IDX_PAR_07
      3289 /dev/vg_pedbsv25/rr04G1024         IDX_PAR_07
      3290 /dev/vg_pedbsv25/rr04G1025         IDX_PAR_07
      3291 /dev/vg_pedbsv25/rr04G1026         IDX_PAR_07


alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03293' as '/dev/vg_pedbsv25/rr04G1028';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03294' as '/dev/vg_pedbsv25/rr04G1029';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03288' as '/dev/vg_pedbsv25/rr04G1023';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03289' as '/dev/vg_pedbsv25/rr04G1024';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03290' as '/dev/vg_pedbsv25/rr04G1025';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03292' as '/dev/vg_pedbsv25/rr04G1027';
 
alter database recover managed standby database disconnect from session;


dt:
select file#,ts#,status,name from v$datafile where file#=3285;


     FILE#        TS# STATUS  NAME
---------- ---------- ------- -----------------------
      3276       1056 RECOVER /oracle/OraHome_1/dbs/UNNAMED03276


从这里看，因为主备使用了裸设备，所以在主库新增数据文件的时候，备库无法正常创建。如果使用的filesystem或者asm存储，那么可以避免该问题的发生。






修改参数 standby_file_management


将standby_file_management设为手动模式
alter system set standby_file_management='MANUAL' scope=both;
alter system set standby_file_management='AUTO' scope=both;


-- 重新创建24号文件
alter database create datafile '/oracle/app/product/10g/db_1/dbs/UNNAMED00024' as '/dev/rora_users01';


使用alter database create datafile ... as ...来迁移，首先要把datafile offline
SQL> alter database create datafile '/opt/app/oradata/test/ht1.dbf' as '/opt/app/oradata/test/hts.dbf';
Database altered.
检查一下
SQL> select name from v$datafile;
NAME
--------------------------------------------------------------------------------
/opt/app/oradata/test/system01.dbf
/opt/app/oradata/test/undotbs01.dbf
/opt/app/oradata/test/indx01.dbf
/opt/app/oradata/test/tools01.dbf
/opt/app/oradata/test/users01.dbf
/opt/app/oradata/test/hts.dbf
6 rows selected.




alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03276' as '/dev/vg_pedbsv25/rr04G1014';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03277' as '/dev/vg_pedbsv25/rr04G1015';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03278' as '/dev/vg_pedbsv25/rr04G1016';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03279' as '/dev/vg_pedbsv25/rr04G1017';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03280' as '/dev/vg_pedbsv25/rr04G1018';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03281' as '/dev/vg_pedbsv25/rr04G1019';
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03285' as '/dev/vg_pedbsv25/rr04G1020';








select file#,ts#,status,name from v$datafile where file#=122;


select file#,ts#,status,name from v$datafile where name='/dev/vg_pedbsv25/rr04G1018'




-- 再次应用归档
alter database recover managed standby database cancel;
alter database recover managed standby database disconnect from session;


































Tue Jul 18 11:16:12 2017
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03279' as '/dev/vg_pedbsv25/rr04G1017'
Tue Jul 18 11:16:29 2017
Completed: alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03279' as '/dev/vg_pedbsv25/rr04G1017'
Tue Jul 18 11:16:31 2017
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03280' as '/dev/vg_pedbsv25/rr04G1018'
Tue Jul 18 11:16:36 2017
RFS[3]: Archived Log: '/oraarch/1_507591_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles of size 1843200 blocks exist
Tue Jul 18 11:16:38 2017
RFS[4]: Archived Log: '/oraarch/2_399413_718202774.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: No standby redo logfiles of size 1843200 blocks exist
Tue Jul 18 11:16:48 2017
Completed: alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03280' as '/dev/vg_pedbsv25/rr04G1018'
Tue Jul 18 11:16:50 2017
alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03281' as '/dev/vg_pedbsv25/rr04G1019'
Tue Jul 18 11:17:07 2017
Completed: alter database create datafile '/oracle/OraHome_1/dbs/UNNAMED03281' as '/dev/vg_pedbsv25/rr04G1019'




 Tue Jul 18 11:22:27 2017
alter database recover managed standby database disconnect from session
Tue Jul 18 11:22:27 2017
Attempt to start background Managed Standby Recovery process (TESTDG)
MRP0 started with pid=37, OS id=23722
Tue Jul 18 11:22:27 2017
MRP0: Background Managed Standby Recovery process started (TESTDG)
Managed Standby Recovery not using Real Time Apply
Tue Jul 18 11:22:33 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:22:33 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3804 - see DBWR trace file
ORA-01110: data file 3804: '/dev/vg_pedbsv15/rr04G1061'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:22:33 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3805 - see DBWR trace file
ORA-01110: data file 3805: '/dev/vg_pedbsv15/rr04G1166'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:22:33 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3806 - see DBWR trace file
ORA-01110: data file 3806: '/dev/vg_pedbsv15/rr04G1167'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:22:33 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3807 - see DBWR trace file
ORA-01110: data file 3807: '/dev/vg_pedbsv15/rr04G1170'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:22:33 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3808 - see DBWR trace file
ORA-01110: data file 3808: '/dev/vg_pedbsv15/rr04G1171'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:22:51 2017
MRP0: Some datafile became unidentified! Retry recovery...
Tue Jul 18 11:22:51 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:22:51 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:22:51 2017
Completed: alter database recover managed standby database disconnect from session
Tue Jul 18 11:23:11 2017
Managed Standby Recovery not using Real Time Apply
Tue Jul 18 11:23:12 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:12 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3804 - see DBWR trace file
ORA-01110: data file 3804: '/dev/vg_pedbsv15/rr04G1061'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:12 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3805 - see DBWR trace file
ORA-01110: data file 3805: '/dev/vg_pedbsv15/rr04G1166'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:12 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3806 - see DBWR trace file
ORA-01110: data file 3806: '/dev/vg_pedbsv15/rr04G1167'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:12 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3807 - see DBWR trace file
ORA-01110: data file 3807: '/dev/vg_pedbsv15/rr04G1170'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:12 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3808 - see DBWR trace file
ORA-01110: data file 3808: '/dev/vg_pedbsv15/rr04G1171'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
MRP0: Some datafile became unidentified! Retry recovery...
Tue Jul 18 11:23:13 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:23:13 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:23:33 2017
Managed Standby Recovery not using Real Time Apply
Tue Jul 18 11:23:34 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:34 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3804 - see DBWR trace file
ORA-01110: data file 3804: '/dev/vg_pedbsv15/rr04G1061'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:34 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3805 - see DBWR trace file
ORA-01110: data file 3805: '/dev/vg_pedbsv15/rr04G1166'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:34 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3806 - see DBWR trace file
ORA-01110: data file 3806: '/dev/vg_pedbsv15/rr04G1167'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:34 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3807 - see DBWR trace file
ORA-01110: data file 3807: '/dev/vg_pedbsv15/rr04G1170'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:34 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3808 - see DBWR trace file
ORA-01110: data file 3808: '/dev/vg_pedbsv15/rr04G1171'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
MRP0: Some datafile became unidentified! Retry recovery...
Tue Jul 18 11:23:35 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:23:35 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:23:55 2017
Managed Standby Recovery not using Real Time Apply
Tue Jul 18 11:23:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3804 - see DBWR trace file
ORA-01110: data file 3804: '/dev/vg_pedbsv15/rr04G1061'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3805 - see DBWR trace file
ORA-01110: data file 3805: '/dev/vg_pedbsv15/rr04G1166'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3806 - see DBWR trace file
ORA-01110: data file 3806: '/dev/vg_pedbsv15/rr04G1167'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3807 - see DBWR trace file
ORA-01110: data file 3807: '/dev/vg_pedbsv15/rr04G1170'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:23:55 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3808 - see DBWR trace file
ORA-01110: data file 3808: '/dev/vg_pedbsv15/rr04G1171'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
MRP0: Some datafile became unidentified! Retry recovery...
Tue Jul 18 11:23:56 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:23:57 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:24:17 2017
Managed Standby Recovery not using Real Time Apply
Tue Jul 18 11:24:17 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:17 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3804 - see DBWR trace file
ORA-01110: data file 3804: '/dev/vg_pedbsv15/rr04G1061'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:17 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3805 - see DBWR trace file
ORA-01110: data file 3805: '/dev/vg_pedbsv15/rr04G1166'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:17 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3806 - see DBWR trace file
ORA-01110: data file 3806: '/dev/vg_pedbsv15/rr04G1167'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:17 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3807 - see DBWR trace file
ORA-01110: data file 3807: '/dev/vg_pedbsv15/rr04G1170'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:17 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3808 - see DBWR trace file
ORA-01110: data file 3808: '/dev/vg_pedbsv15/rr04G1171'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
MRP0: Some datafile became unidentified! Retry recovery...
Tue Jul 18 11:24:18 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:24:18 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:24:38 2017
Managed Standby Recovery not using Real Time Apply
Tue Jul 18 11:24:39 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:39 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3804 - see DBWR trace file
ORA-01110: data file 3804: '/dev/vg_pedbsv15/rr04G1061'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:39 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3805 - see DBWR trace file
ORA-01110: data file 3805: '/dev/vg_pedbsv15/rr04G1166'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:39 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3806 - see DBWR trace file
ORA-01110: data file 3806: '/dev/vg_pedbsv15/rr04G1167'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:39 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3807 - see DBWR trace file
ORA-01110: data file 3807: '/dev/vg_pedbsv15/rr04G1170'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
Tue Jul 18 11:24:39 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_dbw0_5303.trc:
ORA-01157: cannot identify/lock data file 3808 - see DBWR trace file
ORA-01110: data file 3808: '/dev/vg_pedbsv15/rr04G1171'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10
MRP0: Background Media Recovery terminated with error 1110
MRP0: Some datafiles may have become inaccessible.
Tue Jul 18 11:24:40 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:24:40 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_23722.trc:
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
ORA-01157: cannot identify/lock data file 3803 - see DBWR trace file
ORA-01110: data file 3803: '/dev/vg_pedbsv15/rr04G1059'
Tue Jul 18 11:24:40 2017
MRP0: Background Media Recovery process shutdown (TESTDG)










重启备库
















Tue Jul 18 11:40:34 2017
Media Recovery Log /oraarch/2_399375_718202774.dbf
Media Recovery Log /oraarch/1_507485_718202774.dbf
Tue Jul 18 11:41:02 2017
File #3285 added to control file as 'UNNAMED03285' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
File #3286 added to control file as 'UNNAMED03286' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
File #3287 added to control file as 'UNNAMED03287' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
File #3288 added to control file as 'UNNAMED03288' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
File #3289 added to control file as 'UNNAMED03289' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
File #3290 added to control file as 'UNNAMED03290' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
File #3291 added to control file as 'UNNAMED03291' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
Tue Jul 18 11:41:26 2017
Errors with log /oraarch/1_507485_718202774.dbf
MRP0: Background Media Recovery terminated with error 1274
Tue Jul 18 11:41:26 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_24270.trc:
ORA-01274: cannot add datafile '/dev/vg_pedbsv25/rr04G1026' - file could not be created
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Tue Jul 18 11:41:29 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_24270.trc:
ORA-01274: cannot add datafile '/dev/vg_pedbsv25/rr04G1026' - file could not be created
Tue Jul 18 11:41:29 2017
MRP0: Background Media Recovery process shutdown (TESTDG)










alter system set standby_file_management='AUTO' scope=both;






ue Jul 18 11:47:02 2017
MRP0: Background Media Recovery terminated with error 1111
Tue Jul 18 11:47:02 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_24920.trc:
ORA-01111: name for data file 3285 is unknown - rename to correct file
ORA-01110: data file 3285: '/oracle/OraHome_1/dbs/UNNAMED03285'
ORA-01157: cannot identify/lock data file 3285 - see DBWR trace file
ORA-01111: name for data file 3285 is unknown - rename to correct file
ORA-01110: data file 3285: '/oracle/OraHome_1/dbs/UNNAMED03285'
Tue Jul 18 11:47:02 2017
Errors in file /oracle/admin/TESTDG/bdump/TESTDG_mrp0_24920.trc:
ORA-01111: name for data file 3285 is unknown - rename to correct file
ORA-01110: data file 3285: '/oracle/OraHome_1/dbs/UNNAMED03285'
ORA-01157: cannot identify/lock data file 3285 - see DBWR trace file
ORA-01111: name for data file 3285 is unknown - rename to correct file
ORA-01110: data file 3285: '/oracle/OraHome_1/dbs/UNNAMED03285'
Tue Jul 18 11:47:02 2017
MRP0: Background Media Recovery process shutdown (TESTDG)
Tue Jul 18 11:47:03 2017
Completed: alter database recover managed standby database disconnect from session


SQL> alter system set standby_file_management='AUTO' scope=both;
alter system set standby_file_management='AUTO' scope=both
*
ERROR at line 1:
ORA-01565: error in identifying file '/dev/vg_pedbsv13/rr256M1002'
ORA-27086: unable to lock file - already in use
HPUX-ia64 Error: 46: No locks available
Additional information: 10