梦想有多远

物理备库的升级（9.2–10.2 或者10.1-10.2)
步骤如下：
一、看下oracle数据的升级向导，看是否满足相关规定
二、On the primary and standby systems, log in to each system as the owner of the Oracle software directory,
and set the environment to the existing (9.2 or 10.1) installation
三、在主库停止所有的用户活动

(全文…)

DATAGURAD常见错误：
1 
ERROR at line 1:
ORA-01511: error in renaming log/datafiles
ORA-01270: RENAME operation is not allowed if STANDBY_FILE_MANAGEMENT is auto

因为你在备库standby_file_management为auto必须改为手动，才能重命名

以下操作需要手动。
ALTER DATABASE RENAME

ALTER DATABASE ADD/DROP LOGFILE

ALTER DATABASE ADD/DROP STANDBY LOGFILE MEMBER

ALTER DATABASE CREATE DATAFILE AS

(全文…)

alter database add standby logfile group ‘’size
alter database add standby logfile member ” to group n
alter database commit to switchover to primary|physical logical standby with|without session shutdown wait|nowait
alter database create physical|logical standby controlfile a ” [reuse]
alter database drop standby logfile logfile_descriptor
alter database drop standby logfile member ‘filename’[no] force logging
alter database mount standby database
alter database open
alter database prepare to switchover to [primary]|physical|logical [with|without session shutdown ] [wait|nowait]
alter database recover managed standby database [[NODELAY][DISCONNECT [FROM SESSION]][NOPARALLEL|PARALLEL [integer]][UNTIL CHANGE scn][USING CURRENT LOGFILE] ]
alter database RECOVER MANAGED STANDBY DATABASE CANCEL [[NOWAIT]|[WAIT][IMMEDIATE] ]
alter database RECOVER MANAGED STANDBY DATABASE FINISH [FORCE][NOWAIT|WAIT] ]
alter database REGISTER [OR REPLACE] [PHYSICAL|LOGICAL] LOGFILE filespec
alter database RECOVER TO LOGICAL STANDBY new_database_name
alter database RESET DATABASE TO INCARNATION integer
alter database START LOGICAL STANDBY APPLY INITIAL [scn-value] ] [NEW PRIMARY dblink]
alter database {STOP|ABORT} LOGICAL STANDBY APPLY
alter database ACTIVATE [PHYSICAL|LOGICAL] STANDBY DATABASE FINISH APPLY]

一、AFFIRM和NOAFFIRM
作用：控制日志传输服务是异步还是同步写日志数据到磁盘
AFFIRM：在日志写进程进行之前，所以的归档日志和备库日志必须同步写完
NOFFIRM:在主库的日志写进程不等所有磁盘IO完成

缺省的是NOFFIRM
使用AFFIRM时，可以确保以下三点：
1能确保数据没有丢失在主库失败后
2 可以在本地或远程使用
3 影响主库的性能
LGWR和AFFIRM，日志写进程同步写REDO DATA到磁盘，在DISK写完前，控制权不交给用户，还有主库的在线日志可能不可用在归档完成之前

(全文…)