对于基于生产环境下的数据库的版本升级或者测试新的应用程序的性能及其影响,备份恢复等等,我们可以采取从生产环境以克隆的方式将其克隆到本地而不影响生产数据库的正常使用。实现这个功能我们可以借助rman duplicate方式以及其简单的方式来完成。duplicate方式不同于OS级别的备份,它会为辅助数据库(克隆出来的数据库)生成一个新的dbid,而能够同时将目标数据库(原数据库)与辅助数据库注册到同一个恢复目录。本文描述了使用rman duplicate实现异机数据库克隆。

1、RMAN支持的duplicate类型
  支持基于备份的duplicate方式,其中该方式又分为连接到target DB与不连接target DB,不连接target DB又分为连接到catalog与不连接catalog
  支持基于活动数据库的duplicate方式。更多关于duplicate的描述及duplicate步骤,请参考:基于RMAN的同机数据库克隆  这两种方式可以使用下面的图示简要描述。
             
              From Active DB 
              --------------
              |                                           With recovery catalog connection
  Duplicate   |                                          |--------------------------------
  ------------|              Without target conenction   |
              |             |----------------------------|
              |             |                            |
              --------------|                            |-------------
              From Backups  |                             Without recovery catalog connection
                            |-----------------------------
                             With target connection

2、RMAN异机恢复示意图
  下面的图示是没有连接到target DB,也没有连接到recover catalog方式。基于这种方式实现duplicate,应指定备份文件所在的位置。
  本文下面所演示的试验也是基于该方式,在演示的过程中,磁盘路径,目录,数据文件使用了相同的位置与文件名。
  对于不同位置的duplicate情形,需要对文件位置进行转换,可参考: RMAN 数据库克隆文件位置转换方法 
                                         
          

3、实战RMAN异机克隆

  1. --环境:
  2. --目标数据库: 192.168.7.25/sybo3 /u01/database/sybo3 主机名:linux3
  3. --辅助数据库: 192.168.7.26/sybo3 /u01/database/sybo3 主机名:linux4 目标数据库与辅助数据库使用相同的文件位置
  4. --说明:
  5. --本次演示使用了备份文件,没有连接到catalog,也没有连接到target DB
  6. --对于下面描述过程中,如创建参数文件,密码文件,监听等等有不甚了解的,可参考下面链接中有关文章的描述。
  7. --http://blog.csdn.net/robinson_0612/article/category/827734 (体系结构相关)
  8. --http://blog.csdn.net/robinson_0612/article/category/828434 (网络配置相关)
  9. [oracle@linux3 database]$ cat /etc/issue
  10. Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)
  11. Kernel \r on an \m
  12.  
  13. SQL> select * from v$version where rownum<2;
  14.  
  15. BANNER
  16. --------------------------------------------------------------------------------
  17. Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
  18.  
  19. a、备份及ftp目标数据库
  20. --目标数据库存在的表及其内容,用于后续验证
  21. SQL> select * from t;
  22.  
  23. NAME ACTION
  24. ---------- --------------------
  25. Robinson Transfer DB
  26. Jackson Transfer DB by rman
  27.  
  28. --下面备份目标数据库并ftp到辅助数据库所在的主机
  29. $ export ORACLE_SID=sybo3
  30. $ rman target /
  31. RMAN> backup database include current controlfile plus archivelog delete input;
  32. $ scp -r fra 192.168.7.26:/u01/database/sybo3/ -->如果有必要将将备份文件打包,此处fra目录是闪回区
  33.  
  34. --Author : Robinson
  35. --Blog : http://blog.csdn.net/robinson_0612
  36.  
  37. --ftp参数文件,如果没有pfile文件,可从target db生成。 create pfile from spfile;
  38. $ scp $ORACLE_HOME/dbs/initsybo3.ora 192.168.7.26:$ORACLE_HOME/dbs
  39.  
  40. b、创建相应的dump文件夹
  41. [oracle@linux4 database]$ more sybo3.sh
  42. #!/bin/sh
  43. mkdir -p /u01/database
  44. mkdir -p /u01/database/sybo3/adump
  45. mkdir -p /u01/database/sybo3/controlf
  46. mkdir -p /u01/database/sybo3/fra
  47. mkdir -p /u01/database/sybo3/oradata
  48. mkdir -p /u01/database/sybo3/redo
  49. mkdir -p /u01/database/sybo3/dpdump
  50. mkdir -p /u01/database/sybo3/pfile
  51. [oracle@linux4 database]$ ./sybo3.sh
  52.  
  53. c、配置辅助实例参数文件
  54. --由于auxiliary DBtarget DB不存在文件位置转换,因此无需作任何修改。下面是target DB 复制到auxiliary的参数文件内容
  55. [oracle@linux4 ~]$ more /u01/oracle/db_1/dbs/initsybo3.ora
  56. sybo3.__db_cache_size=113246208
  57. sybo3.__java_pool_size=4194304
  58. sybo3.__large_pool_size=4194304
  59. sybo3.__oracle_base='/u01/oracle'#ORACLE_BASE set from environment
  60. sybo3.__pga_aggregate_target=150994944
  61. sybo3.__sga_target=226492416
  62. sybo3.__shared_io_pool_size=0
  63. sybo3.__shared_pool_size=96468992
  64. sybo3.__streams_pool_size=0
  65. *.audit_file_dest='/u01/database/sybo3/adump/'
  66. *.audit_trail='db'
  67. *.compatible='11.2.0.0.0'
  68. *.control_files='/u01/database/sybo3/controlf/control01.ctl','/u01/database/sybo3/controlf/control02.ctl'
  69. *.db_block_size=8192
  70. *.db_domain='orasrv.com'
  71. *.db_name='sybo3'
  72. *.db_recovery_file_dest='/u01/database/sybo3/fra'
  73. *.db_recovery_file_dest_size=4039114752
  74. *.dg_broker_config_file1='/u01/database/sybo3/db_broker/dr1sybo3.dat'
  75. *.dg_broker_config_file2='/u01/database/sybo3/db_broker/dr2sybo3.dat'
  76. *.dg_broker_start=FALSE
  77. *.diagnostic_dest='/u01/database/sybo3'
  78. *.log_archive_dest_1=''
  79. *.memory_target=374341632
  80. *.open_cursors=300
  81. *.processes=150
  82. *.remote_login_passwordfile='EXCLUSIVE'
  83. *.undo_tablespace='UNDOTBS1'
  84.  
  85. d、生成辅助实例密码文件
  86. --直接使用orapwd命令完成
  87. $ orapwd file=/u01/oracle/db_1/dbs/orapwsybo3 password=oracle entries=10
  88.  
  89. e、实施数据库克隆
  90. --由于此次测试无需连接到targetcatalog,因此可以跳过配置监听,可在克隆完毕后再配置
  91. [oracle@linux4 ~]$ export ORACLE_SID=sybo3
  92. [oracle@linux4 ~]$ sqlplus / as sysdba
  93. SQL> startup nomount; -->启动辅助实例到nomount状态
  94. [oracle@linux4 ~]$ rman auxiliary / -->直接使用auxiliary / 方式连接到辅助数据库
  95.  
  96. connected to auxiliary database: SYBO3 (not mounted)
  97.  
  98. RMAN> duplicate target database to sybo3 spfile
  99. 2> backup location '/u01/database/sybo3/fra/SYBO3'
  100. 3> nofilenamecheck;
  101.  
  102. Starting Duplicate Db at 31-JUL-13
  103.  
  104. contents of Memory Script:
  105. {
  106. restore clone spfile to '/u01/oracle/db_1/dbs/spfilesybo3.ora' from --->从自动备份还原spfile文件
  107. '/u01/database/sybo3/fra/SYBO3/autobackup/2013_07_31/o1_mf_s_822220850_8zjy9lp8_.bkp';
  108. sql clone "alter system set spfile= ''/u01/oracle/db_1/dbs/spfilesybo3.ora''";
  109. }
  110. executing Memory Script
  111.  
  112. Starting restore at 31-JUL-13
  113. allocated channel: ORA_AUX_DISK_1
  114. channel ORA_AUX_DISK_1: SID=134 device type=DISK
  115.  
  116. channel ORA_AUX_DISK_1: restoring spfile from AUTOBACKUP /u01/database/sybo3/fra/SYBO3/autobackup/2013_07_31/o1_mf_s_822220850_8zjy9lp8_.bkp
  117. channel ORA_AUX_DISK_1: SPFILE restore from AUTOBACKUP complete
  118. Finished restore at 31-JUL-13
  119.  
  120. sql statement: alter system set spfile= ''/u01/oracle/db_1/dbs/spfilesybo3.ora''
  121.  
  122. contents of Memory Script:
  123. {
  124. sql clone "alter system set db_name = --->修改spfile并重启辅助实例
  125. ''SYBO3'' comment=
  126. ''duplicate'' scope=spfile";
  127. shutdown clone immediate;
  128. startup clone nomount;
  129. }
  130. executing Memory Script
  131.  
  132. sql statement: alter system set db_name = ''SYBO3'' comment= ''duplicate'' scope=spfile
  133.  
  134. Oracle instance shut down
  135.  
  136. connected to auxiliary database (not started)
  137. Oracle instance started
  138.  
  139. Total System Global Area 376635392 bytes
  140.  
  141. Fixed Size 1336652 bytes
  142. Variable Size 285215412 bytes
  143. Database Buffers 83886080 bytes
  144. Redo Buffers 6197248 bytes
  145.  
  146. contents of Memory Script:
  147. {
  148. sql clone "alter system set db_name =
  149. ''SYBO3'' comment=
  150. ''Modified by RMAN duplicate'' scope=spfile";
  151. sql clone "alter system set db_unique_name =
  152. ''SYBO3'' comment=
  153. ''Modified by RMAN duplicate'' scope=spfile";
  154. shutdown clone immediate;
  155. startup clone force nomount -->下面的命令用于还原控制文件
  156. restore clone primary controlfile from '/u01/database/sybo3/fra/SYBO3/autobackup/2013_07_31/o1_mf_s_822220850_8zjy9lp8_.bkp';
  157. alter clone database mount;
  158. }
  159. executing Memory Script
  160.  
  161. sql statement: alter system set db_name = ''SYBO3'' comment= ''Modified by RMAN duplicate'' scope=spfile
  162.  
  163. sql statement: alter system set db_unique_name = ''SYBO3'' comment= ''Modified by RMAN duplicate'' scope=spfile
  164.  
  165. Oracle instance shut down
  166.  
  167. Oracle instance started
  168.  
  169. Total System Global Area 376635392 bytes
  170.  
  171. Fixed Size 1336652 bytes
  172. Variable Size 285215412 bytes
  173. Database Buffers 83886080 bytes
  174. Redo Buffers 6197248 bytes
  175.  
  176. Starting restore at 31-JUL-13
  177. allocated channel: ORA_AUX_DISK_1
  178. channel ORA_AUX_DISK_1: SID=133 device type=DISK
  179.  
  180. channel ORA_AUX_DISK_1: restoring control file
  181. channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
  182. output file name=/u01/database/sybo3/controlf/control01.ctl
  183. output file name=/u01/database/sybo3/controlf/control02.ctl
  184. Finished restore at 31-JUL-13
  185.  
  186. database mounted
  187. released channel: ORA_AUX_DISK_1
  188. allocated channel: ORA_AUX_DISK_1
  189. channel ORA_AUX_DISK_1: SID=133 device type=DISK
  190. RMAN-05538: WARNING: implicitly using DB_FILE_NAME_CONVERT
  191.  
  192. contents of Memory Script:
  193. {
  194. set until scn 1177881; --->设置时点恢复scn,修改datafile name.
  195. set newname for datafile 1 to
  196. "/u01/database/sybo3/oradata/system01.dbf";
  197. set newname for datafile 2 to
  198. "/u01/database/sybo3/oradata/sysaux01.dbf";
  199. set newname for datafile 3 to
  200. "/u01/database/sybo3/oradata/undotbs01.dbf";
  201. set newname for datafile 4 to
  202. "/u01/database/sybo3/oradata/users01.dbf";
  203. set newname for datafile 5 to
  204. "/u01/database/sybo3/oradata/example01.dbf";
  205. restore --->该命令用于还原辅助数据库
  206. clone database
  207. ;
  208. }
  209. executing Memory Script
  210.  
  211. executing command: SET until clause
  212.  
  213. executing command: SET NEWNAME
  214.  
  215. executing command: SET NEWNAME
  216.  
  217. executing command: SET NEWNAME
  218.  
  219. executing command: SET NEWNAME
  220.  
  221. executing command: SET NEWNAME
  222.  
  223. Starting restore at 31-JUL-13
  224. using channel ORA_AUX_DISK_1
  225.  
  226. channel ORA_AUX_DISK_1: starting datafile backup set restore
  227. channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
  228. channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/database/sybo3/oradata/system01.dbf
  229. channel ORA_AUX_DISK_1: restoring datafile 00002 to /u01/database/sybo3/oradata/sysaux01.dbf
  230. channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/database/sybo3/oradata/undotbs01.dbf
  231. channel ORA_AUX_DISK_1: restoring datafile 00004 to /u01/database/sybo3/oradata/users01.dbf
  232. channel ORA_AUX_DISK_1: restoring datafile 00005 to /u01/database/sybo3/oradata/example01.dbf
  233. channel ORA_AUX_DISK_1: reading from backup piece /u01/database/sybo3/fra/SYBO3/backupset/2013_07_31/o1_mf_nnndf_TAG20130731T103921_8zjy6s8p_.bkp
  234. channel ORA_AUX_DISK_1: piece handle=/u01/database/sybo3/fra/SYBO3/backupset/2013_07_31/o1_mf_nnndf_TAG20130731T103921_8zjy6s8p_.bkp
  235. tag=TAG20130731T103921
  236. channel ORA_AUX_DISK_1: restored backup piece 1
  237. channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:25
  238. Finished restore at 31-JUL-13
  239.  
  240. contents of Memory Script:
  241. {
  242. switch clone datafile all; --->更新数据文件信息到控制文件
  243. }
  244. executing Memory Script
  245.  
  246. datafile 1 switched to datafile copy
  247. input datafile copy RECID=1 STAMP=822223969 file name=/u01/database/sybo3/oradata/system01.dbf
  248. datafile 2 switched to datafile copy
  249. input datafile copy RECID=2 STAMP=822223969 file name=/u01/database/sybo3/oradata/sysaux01.dbf
  250. datafile 3 switched to datafile copy
  251. input datafile copy RECID=3 STAMP=822223969 file name=/u01/database/sybo3/oradata/undotbs01.dbf
  252. datafile 4 switched to datafile copy
  253. input datafile copy RECID=4 STAMP=822223969 file name=/u01/database/sybo3/oradata/users01.dbf
  254. datafile 5 switched to datafile copy
  255. input datafile copy RECID=5 STAMP=822223969 file name=/u01/database/sybo3/oradata/example01.dbf
  256.  
  257. contents of Memory Script:
  258. {
  259. set until scn 1177881;
  260. recover --->recover 辅助数据库以及删除日志
  261. clone database
  262. delete archivelog
  263. ;
  264. }
  265. executing Memory Script
  266.  
  267. executing command: SET until clause
  268.  
  269. Starting recover at 31-JUL-13
  270. using channel ORA_AUX_DISK_1
  271.  
  272. starting media recovery
  273.  
  274. channel ORA_AUX_DISK_1: starting archived log restore to default destination
  275. channel ORA_AUX_DISK_1: restoring archived log
  276. archived log thread=1 sequence=41
  277. channel ORA_AUX_DISK_1: reading from backup piece /u01/database/sybo3/fra/SYBO3/backupset/2013_07_31/o1_mf_annnn_TAG20130731T104049_8zjy9k8g_.bkp
  278. channel ORA_AUX_DISK_1: piece handle=/u01/database/sybo3/fra/SYBO3/backupset/2013_07_31/o1_mf_annnn_TAG20130731T104049_8zjy9k8g_.bkp
  279. tag=TAG20130731T104049
  280. channel ORA_AUX_DISK_1: restored backup piece 1
  281. channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
  282. archived log file name=/u01/database/sybo3/fra/SYBO3/archivelog/2013_07_31/o1_mf_1_41_8zk1c4xq_.arc thread=1 sequence=41
  283. channel clone_default: deleting archived log(s)
  284. archived log file name=/u01/database/sybo3/fra/SYBO3/archivelog/2013_07_31/o1_mf_1_41_8zk1c4xq_.arc RECID=1 STAMP=822223972
  285. media recovery complete, elapsed time: 00:00:01
  286. Finished recover at 31-JUL-13
  287.  
  288. contents of Memory Script:
  289. {
  290. shutdown clone immediate; --->相关参数修改
  291. startup clone nomount;
  292. sql clone "alter system set db_name =
  293. ''SYBO3'' comment=
  294. ''Reset to original value by RMAN'' scope=spfile";
  295. sql clone "alter system reset db_unique_name scope=spfile";
  296. shutdown clone immediate;
  297. startup clone nomount;
  298. }
  299. executing Memory Script
  300.  
  301. database dismounted
  302. Oracle instance shut down
  303.  
  304. connected to auxiliary database (not started)
  305. Oracle instance started
  306.  
  307. Total System Global Area 376635392 bytes
  308.  
  309. Fixed Size 1336652 bytes
  310. Variable Size 285215412 bytes
  311. Database Buffers 83886080 bytes
  312. Redo Buffers 6197248 bytes
  313.  
  314. sql statement: alter system set db_name = ''SYBO3'' comment= ''Reset to original value by RMAN'' scope=spfile
  315.  
  316. sql statement: alter system reset db_unique_name scope=spfile
  317.  
  318. Oracle instance shut down
  319.  
  320. connected to auxiliary database (not started)
  321. Oracle instance started
  322.  
  323. Total System Global Area 376635392 bytes
  324.  
  325. Fixed Size 1336652 bytes
  326. Variable Size 285215412 bytes
  327. Database Buffers 83886080 bytes
  328. Redo Buffers 6197248 bytes
  329. sql statement: CREATE CONTROLFILE REUSE SET DATABASE "SYBO3" RESETLOGS ARCHIVELOG --->重建控制文件,隐式重置了dbid
  330. MAXLOGFILES 16
  331. MAXLOGMEMBERS 3
  332. MAXDATAFILES 100
  333. MAXINSTANCES 8
  334. MAXLOGHISTORY 292
  335. LOGFILE
  336. GROUP 1 SIZE 50 M ,
  337. GROUP 2 SIZE 50 M ,
  338. GROUP 3 SIZE 50 M
  339. DATAFILE
  340. '/u01/database/sybo3/oradata/system01.dbf'
  341. CHARACTER SET AL32UTF8
  342.  
  343. contents of Memory Script:
  344. {
  345. set newname for tempfile 1 to
  346. "/u01/database/sybo3/oradata/temp01.dbf";
  347. switch clone tempfile all;
  348. catalog clone datafilecopy "/u01/database/sybo3/oradata/sysaux01.dbf",
  349. "/u01/database/sybo3/oradata/undotbs01.dbf",
  350. "/u01/database/sybo3/oradata/users01.dbf",
  351. "/u01/database/sybo3/oradata/example01.dbf";
  352. switch clone datafile all;
  353. }
  354. executing Memory Script
  355.  
  356. executing command: SET NEWNAME
  357.  
  358. renamed tempfile 1 to /u01/database/sybo3/oradata/temp01.dbf in control file
  359.  
  360. cataloged datafile copy
  361. datafile copy file name=/u01/database/sybo3/oradata/sysaux01.dbf RECID=1 STAMP=822223994
  362. cataloged datafile copy
  363. datafile copy file name=/u01/database/sybo3/oradata/undotbs01.dbf RECID=2 STAMP=822223994
  364. cataloged datafile copy
  365. datafile copy file name=/u01/database/sybo3/oradata/users01.dbf RECID=3 STAMP=822223994
  366. cataloged datafile copy
  367. datafile copy file name=/u01/database/sybo3/oradata/example01.dbf RECID=4 STAMP=822223994
  368.  
  369. datafile 2 switched to datafile copy
  370. input datafile copy RECID=1 STAMP=822223994 file name=/u01/database/sybo3/oradata/sysaux01.dbf
  371. datafile 3 switched to datafile copy
  372. input datafile copy RECID=2 STAMP=822223994 file name=/u01/database/sybo3/oradata/undotbs01.dbf
  373. datafile 4 switched to datafile copy
  374. input datafile copy RECID=3 STAMP=822223994 file name=/u01/database/sybo3/oradata/users01.dbf
  375. datafile 5 switched to datafile copy
  376. input datafile copy RECID=4 STAMP=822223994 file name=/u01/database/sybo3/oradata/example01.dbf
  377.  
  378. contents of Memory Script:
  379. {
  380. Alter clone database open resetlogs;
  381. }
  382. executing Memory Script
  383.  
  384. database opened
  385. Finished Duplicate Db at 31-JUL-13
  386.  
  387. --对于那些没有连接到target db或者catalog而使用duplicate方式克隆的数据库,必须要指定BACKUP LOCATION,否则收到如下错误提示。
  388. --这是由于所有和备份相关的信息,包括备份位置都记录在catalogcontrolfile里,但是duplicate方式发布命令时,此时controlfile还没有还原。
  389. --RMAN-05546: DUPLICATE without TARGET and CATALOG connections requires that BACKUP LOCATION is specified
  390.  
  391. f、验证结果(根据需要创建监听)
  392. [oracle@linux4 ~]$ sqlplus / as sysdba
  393.  
  394. SQL> select instance_name,host_name from v$instance;
  395.  
  396. INSTANCE_NAME HOST_NAME
  397. ---------------- ------------------------------
  398. sybo3 linux4.orasrv.com
  399.  
  400. SQL> select * from t;
  401.  
  402. NAME ACTION
  403. ---------- --------------------
  404. Robinson Transfer DB
  405. Jackson Transfer DB by rman

4、后记
  a、在异机克隆时,如果auxiliary DB使用了与target DB相同的磁盘配置,目录结构以及文件名时,必须指定NOFILENAMECHECK。
       NOFILENAMECHECK可以阻止检查target DB的数据文件及联机日志文件是否处于正常使用的状态。而auxiliary DB与target DB的磁盘配置,
       目录结构以及文件名任一不同时,应避免使用NOFILENAMECHECK。
  b、对于没有连接到target DB或catalog的情形,应使用BACKUP LOCATION '<bak_dir>'指定备份文件所在的位置。

相关参考
    RMAN 数据库克隆文件位置转换方法

基于 RMAN 的同机数据库克隆

基于用户管理的同机数据库克隆

Oracle 冷备份

Oracle 热备份

Oracle 备份恢复概念

Oracle 实例恢复

Oracle 基于用户管理恢复的处理

SYSTEM 表空间管理及备份恢复

SYSAUX表空间管理及恢复

Oracle 基于备份控制文件的恢复(unsing backup controlfile)

RMAN 概述及其体系结构

RMAN 配置、监控与管理

RMAN 备份详解

RMAN 还原与恢复

RMAN catalog 的创建和使用

基于catalog 创建RMAN存储脚本

基于catalog 的RMAN 备份与恢复

RMAN 备份路径困惑

自定义 RMAN 显示的日期时间格式

只读表空间的备份与恢复

Oracle 基于用户管理的不完全恢复

理解 using backup controlfile

使用RMAN实现异机备份恢复(WIN平台)

使用RMAN迁移文件系统数据库到ASM

基于Linux下 Oracle 备份策略(RMAN)

Linux 下RMAN备份shell脚本

使用RMAN迁移数据库到异机

RMAN 提示符下执行SQL语句

Oracle 基于 RMAN 的不完全恢复(incomplete recovery by RMAN)

rman 还原归档日志(restore archivelog)

基于RMAN的异机数据库克隆(rman duplicate)的更多相关文章

  1. 利用rman进行异机还原(目录相同)

    利用rman进行异机还原(目录相同) 源始库:192.168.201.2 目标库:192.168.201.3 --192.168.201.2 --rman [oracle@db01 ~]$ rman ...

  2. 使用rman备份异机恢复数据库

    一.RMAN备份源库注意点: 最好保留rman备份日志 $rman target / log=backup.log RMAN>run { allocate channel t1 type dis ...

  3. Hyper-V安装Oracle Linux6_4 Oracle db 12c并使用rman做异机恢复

    本文记录在Windows Server 2012 R2上安装Oracle Enterprise Linux 6.4以及使用RMAN进行进行异机恢复的过程. Windows服务器增加Hyper-V功能 ...

  4. RMAN - 备份异机恢复

    OS: Oracle Linux Server release 5.7 DB: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - ...

  5. RMAN 备份异机恢复 并创建新DBID

    测试平台信息: Oracle:11gR2 操作系统:Redhat 5.5 Target DB:dave   几点说明: (1)RMAN 异机恢复的时候,db_name必须相同. 如果说要想改成其他的实 ...

  6. Oracle之使用rman进行异机恢复测试记录

    本次测试目的是从生产数据库导出rman备份然后在测试数据库恢复 1,拷贝备份至相应目录 2,进入rman rman target \ 3,关闭数据库 shutdown 4,以nomount模式启动数据 ...

  7. RMAN冷备份异机还原

    1:环境准备 在新的服务器上安装ORACLE实例,安装过程中需要注意源服务器与目标服务器的ORACLE_SID一致,另外确保安装路径与源路径一致(不仅是安装目录,甚至包括数据文件.控制文件目录.联机重 ...

  8. RAC数据库的RMAN备份异机恢复到单节点数据库

    1.首先在rac环境用rman备份数据库.[oracle@rac1 admin]$ rman target /run{allocate channel c1 device type disk conn ...

  9. Rman备份异机恢复

    最后更新时间:2018/12/29 前置条件 已准备一台安装好Centos6+oracle11gr2 软件的服务器; 只安装了 oracle 数据库软件,需要手工创建以下目录: #环境变量 expor ...

随机推荐

  1. Spring 中各种通知

    <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.sp ...

  2. 【POJ2104】【整体二分+树状数组】区间第k大

    Description You are working for Macrohard company in data structures department. After failing your ...

  3. 【HDU4348】【主席树】To the moon

    Problem Description BackgroundTo The Moon is a independent game released in November 2011, it is a r ...

  4. TIFF6 Packbit algorithm

    “Packbits” from ISO 12369 参考TIFF 6.0 Specification,点击TIFF, Version 6.0: @Section 9: PackBits Compres ...

  5. 工厂方法模式(Factory Method)

    1.本质:延迟到子类来选择实现 2.示意图: 3.主要功能: 让父类在不知道具体实现的情况下,完成自身功能的调用 类似于注入 4.备注: 1.工厂方法中,通常父类是一个抽象类,里面包含创建对象的抽象工 ...

  6. visualSVN server库迁移(转)

    转自:http://blog.csdn.net/yuhuijun_1/article/details/9762683 首先,VisualSVN Server Manager,包含两个路径,一个是安装路 ...

  7. 在easyui dialog的子页面内如何关闭弹窗

    因项目需要在dialog中添加滚动条,所以就在div中加了iframe: <div id="applyRefundDialog" style="display:no ...

  8. Python开发【第一章】:Python简介和入门

    Python简介 Python的创始人为Guido van Rossum.1989年圣诞节期间,在阿姆斯特丹,Guido为了打发圣诞节的无趣,决心开发一个新的脚本解释程序,做为ABC 语言的一种继承. ...

  9. App适配iPhone 6/ Plus和iOS 8:10条小秘诀

    App适配iPhone 6/ Plus和iOS 8:10条小秘诀   iPhone 6iOS 8适配   (原文:raywenderlich 作者:Jack Wu 译者:@TurtleFromMars ...

  10. Linux——搭建PHP开发环境第三步:mysql

    原文链接:http://www.jb51.net/article/83647.htm 1.第一步就是看linu是否安装了mysql,经过rpm -qa|grep mysql查看到centos下安装了m ...