先介绍下managed_standby和日志应用有关 [Standby上]
desc v$managed_standby;
Name Null? Type
—————————————– ——– —————————-
PROCESS VARCHAR2(9)
PID NUMBER
STATUS VARCHAR2(12)
CLIENT_PROCESS VARCHAR2(8)
CLIENT_PID VARCHAR2(40)
CLIENT_DBID VARCHAR2(40)
GROUP# VARCHAR2(40)
RESETLOG_ID NUMBER
THREAD# NUMBER
SEQUENCE# NUMBER
BLOCK# NUMBER
BLOCKS NUMBER
DELAY_MINS NUMBER
KNOWN_AGENTS NUMBER
ACTIVE_AGENTS NUMBER
通过我们都会查看PROCESS,STATUS
SQL> select process,status from v$managed_standby;
PROCESS STATUS——— ————
ARCH CLOSING
ARCH CLOSING
RFS IDLE
MRP0 WAIT_FOR_LOG
RFS IDLE
RFS IDLE
其中process列如下选项:
· RFS - Remote file server(负责接收远程日志文件)· MRP0 - Detached recovery server process(负责应用恢复接收的日志· MR(fg) - Foreground recovery session· ARCH - Archiver process· FGRD· LGWR· RFS(FAL)· RFS(NEXP)· LNS network server processSTATUS列有如下选项:· UNUSED - No active process· ALLOCATED - Process is active but not currently connected to a primary database· CONNECTED - Network connection established to a primary database· ATTACHED - Process is actively attached and communicating to a primary database· IDLE - Process is not performing any activities· ERROR - Process has failed· OPENING - Process is opening the archived redo log· CLOSING - Process has completed archival and is closing the archived redo log(标示当前没有可应用归档日志)· WRITING - Process is actively writing redo data to the archived redo log· RECEIVING - Process is receiving network communication· ANNOUNCING - Process is announcing the existence of a potential dependent archived redo log· REGISTERING - Process is registering the existence of a completed dependent archived redo log· WAIT_FOR_LOG - Process is waiting for the archived redo log to be completed(一般正常状态)· WAIT_FOR_GAP - Process is waiting for the archive gap to be resolved· APPLYING_LOG - Process is actively applying the archived redo log to the standby databasesequence#列:如果日志应用出现什么问题,可以查看在等待那个日志应用
和数据文件管理相关的视图
v$archive_gap 主要可以用来查看备库丢失了那些日志
desc v$archive_gap;
Name Null? Type
—————————————– ——– —————————-
THREAD# NUMBER
LOW_SEQUENCE# NUMBER
HIGH_SEQUENCE# NUMBER
如果有GAP可以手动注册日志,alter database register logfile ‘文件名’
配置了FAL_SERVER FAL_CLIENT就没问题
shou
如果日志无法传送,可以查看 v$archive_dest;
select dest_name,status,error from v$archive_dest
DEST_NAME STATUS ERROR
——————– ———- ——————————
LOG_ARCHIVE_DEST_1 VALID
LOG_ARCHIVE_DEST_2 VALID
LOG_ARCHIVE_DEST_3 INACTIVE
LOG_ARCHIVE_DEST_4 INACTIVE
LOG_ARCHIVE_DEST_5 INACTIVE
LOG_ARCHIVE_DEST_6 INACTIVE
LOG_ARCHIVE_DEST_7 INACTIVE
LOG_ARCHIVE_DEST_8 INACTIVE
LOG_ARCHIVE_DEST_9 INACTIVE
LOG_ARCHIVE_DEST_10 INACTIVE
STANDBY_ARCHIVE_DEST VALID
如果状态 为VALID说明没问题 ,如果有错误则更具ERROR里信息处理:
v$archive_dest_status 视图可以查看备库的状态,保护模式,归档日志路径状态
select dest_name,status,database_mode,recovery_mode,protection_mode from v$archive_dest_status
DEST_NAME STATUS DATABASE_MODE RECOVERY_MODE PROTECTION_MODE
——————– ———- ——————– ——————– ——————–
LOG_ARCHIVE_DEST_1 VALID MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_2 VALID MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_3 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_4 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_5 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_6 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_7 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_8 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_9 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
LOG_ARCHIVE_DEST_10 INACTIVE MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
STANDBY_ARCHIVE_DEST VALID MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE
v$archived_log可以查看日志的一些信息 ,包括日志名字,应用时间,是否应用
select first_time,applied,sequence#,status,next_time from v$archived_log
FIRST_TIM APP SEQUENCE# STATUS NEXT_TIME
——— — ———- ———- ———
06-DEC-07 YES 37 A 06-DEC-07
06-DEC-07 YES 38 A 06-DEC-07
06-DEC-07 YES 39 A 06-DEC-07
06-DEC-07 YES 40 A 07-DEC-07
07-DEC-07 YES 41 A 07-DEC-07
07-DEC-07 YES 42 A 07-DEC-07
07-DEC-07 YES 43 A 07-DEC-07
07-DEC-07 YES 44 A 07-DEC-07
07-DEC-07 YES 45 A 07-DEC-07
9 rows selected.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/35489/viewspace-374905/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/35489/viewspace-374905/