|
|
查看主库和从库的alter.log。也没发现什么问题。
从库的日志:
ARC4: Becoming the 'no FAL' ARCH
Tue Dec 06 11:33:55 2011
ARCt started with pid=48, OS id=6399
ARCn: Becoming the heartbeat ARCH
Tue Dec 06 11:33:55 2011
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
RFS[1]: Assigned to RFS process 6405
RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 5824
Tue Dec 06 11:33:55 2011
RFS[2]: Assigned to RFS process 6407
RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 5828
Tue Dec 06 11:33:55 2011
RFS[3]: Assigned to RFS process 6409
RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 5826
RFS[2]: Opened log for thread 1 sequence 86 dbid 622049834 branch 768747306
Archived Log entry 91 added for thread 1 sequence 86 rlc 768747306 ID 0x25191256 dest 2:
RFS[3]: Selected log 4 for thread 1 sequence 85 dbid 622049834 branch 768747306
Archived Log entry 92 added for thread 1 sequence 85 ID 0x25191256 dest 1:
Tue Dec 06 11:33:56 2011
Spfile /opt/app/oracle/product/11.2.0/dbhome_1/dbs/spfilewind.ora is in old pre-11 format and compatible >= 11.0.0; converting to new H.A.R.D. compliant format.
ARCt: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Tue Dec 06 11:33:57 2011
RFS[4]: Assigned to RFS process 6413
RFS[4]: Identified database type as 'physical standby': Client is LGWR ASYNC pid 5866
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Selected log 4 for thread 1 sequence 87 dbid 622049834 branch 768747306
RFS[4]: Selected log 5 for thread 1 sequence 88 dbid 622049834 branch 768747306
Archived Log entry 93 added for thread 1 sequence 87 ID 0x25191256 dest 1:
Tue Dec 06 11:34:12 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT
Attempt to start background Managed Standby Recovery process (wind)
Tue Dec 06 11:34:12 2011
MRP0 started with pid=53, OS id=6422
MRP0: Background Managed Standby Recovery process started (wind)
Tue Dec 06 11:34:14 2011
RFS[5]: Assigned to RFS process 6424
RFS[5]: Identified database type as 'physical standby': Client is ARCH pid 5824
started logmerger process
Tue Dec 06 11:34:17 2011
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /opt/app/oracle/flash_recovery_area/DB1/archivelog/2011_12_06/o1_mf_1_85_7fv393qy_.arc
Media Recovery Log /opt/app/oracle/flash_recovery_area/DB1/archivelog/2011_12_06/o1_mf_1_86_7fv393jv_.arc
Media Recovery Log /opt/app/oracle/flash_recovery_area/DB1/archivelog/2011_12_06/o1_mf_1_87_7fv395c5_.arc
Media Recovery Waiting for thread 1 sequence 88 (in transit)
Recovery of Online Redo Log: Thread 1 Group 5 Seq 88 Reading mem 0
Mem# 0: /opt/app/oracle/oradata/wind/standbyredolog02.log
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT
Tue Dec 06 11:35:15 2011
RFS[4]: Selected log 4 for thread 1 sequence 89 dbid 622049834 branch 768747306
Tue Dec 06 11:35:15 2011
Archived Log entry 94 added for thread 1 sequence 88 ID 0x25191256 dest 1:
Tue Dec 06 11:35:15 2011
Media Recovery Waiting for thread 1 sequence 89 (in transit)
Recovery of Online Redo Log: Thread 1 Group 4 Seq 89 Reading mem 0
Mem# 0: /opt/app/oracle/oradata/wind/standbyredolog01.log
Tue Dec 06 11:48:44 2011
db_recovery_file_dest_size of 4977 MB is 1.89% 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.
|
|