2. 程式人生 > >RMAN遷移數據庫（不改變文件目錄）

RMAN遷移數據庫（不改變文件目錄）

阿新 • • 發佈：2018-11-06
ins implicit open fix edi pattern created sta 備份


1、目標庫創建相應目錄
mkdir -p /u01/app/oracle/oradata/orcl
mkdir -p /u01/app/oracle/fast_recovery_area/ORCL
mkdir -p /u01/app/oracle/admin/orcl/{a,dp}dump

2、目標庫創建密碼文件
orapwd file=orapworcl password=oracle

3、原庫備份
RMAN> backup as compressed backupset database plus archivelog;

4、將原庫備份傳輸到目標庫
在目標庫創建目錄存放原庫傳輸過來的原庫備份
mkdir –p /home/oracle/bak
mkdir –p /home/oracle/autobak
利用scp工具傳輸，具體不詳細介紹。

5、[oracle@orcl ~]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Nov 5 11:19:38 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to target database: (not started)
RMAN> set dbid 238796283
executing command: SET DBID

6、
RMAN> startup nomount

startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file ‘/u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora‘

starting Oracle instance without parameter file for retrieval of spfile
Oracle instance started

Total System Global Area 159019008 bytes

Fixed Size 1343612 bytes
Variable Size 75501444 bytes
Database Buffers 79691776 bytes
Redo Buffers 2482176 bytes

RMAN> restore spfile to pfile ‘/u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora‘ from ‘/home/oracle/autobak/o1_mf_s_991416863_fy03o039_.bkp‘;

Starting restore at 05-NOV-18
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK

channel ORA_DISK_1: restoring spfile from AUTOBACKUP /home/oracle/autobak/o1_mf_s_991416863_fy03o039_.bkp
channel ORA_DISK_1: SPFILE restore from AUTOBACKUP complete
Finished restore at 05-NOV-18

RMAN> exit


Recovery Manager complete.
[oracle@fz-orcl autobak]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Mon Nov 5 18:28:15 2018

Copyright (c) 1982, 2011, Oracle. All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SYS@orcl>select status from v$instance;

STATUS
------------
STARTED

SYS@orcl>create spfile from pfile;

File created.

SYS@orcl>shutdown immediate
ORA-01507: database not mounted


ORACLE instance shut down.
SYS@orcl>startup nomount
ORACLE instance started.

Total System Global Area 472887296 bytes
Fixed Size 1345716 bytes
Variable Size 289408844 bytes
Database Buffers 176160768 bytes
Redo Buffers 5971968 bytes
SYS@orcl>show parameter spfile

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string /u01/app/oracle/product/11.2.0
/db_1/dbs/spfileorcl.ora
SYS@orcl>exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@fz-orcl autobak]$ rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Nov 5 18:29:57 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to target database: ORCL (not mounted)

RMAN> restore controlfile from ‘/home/oracle/autobak/o1_mf_s_991416863_fy03o039_.bkp‘;

Starting restore at 05-NOV-18
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/fast_recovery_area/orcl/control02.ctl
Finished restore at 05-NOV-18

RMAN> alter database mount;

database mounted
released channel: ORA_DISK_1

RMAN> catalog start with ‘/home/oracle/bak‘;

Starting implicit crosscheck backup at 05-NOV-18
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 05-NOV-18

Starting implicit crosscheck copy at 05-NOV-18
using channel ORA_DISK_1
using channel ORA_DISK_2
Crosschecked 2 objects
Finished implicit crosscheck copy at 05-NOV-18

searching for all files in the recovery area
cataloging files...
no files cataloged

searching for all files that match the pattern /home/oracle/bak

List of Files Unknown to the Database
=====================================
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173422_fy03nylc_.bkp
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173202_fy03jlmo_.bkp
File Name: /home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03jolp_.bkp
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173202_fy03jllk_.bkp
File Name: /home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03joyn_.bkp
File Name: /home/oracle/bak/o1_mf_s_991416863_fy03o039_.bkp
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173202_fy03jms6_.bkp

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173422_fy03nylc_.bkp
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173202_fy03jlmo_.bkp
File Name: /home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03jolp_.bkp
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173202_fy03jllk_.bkp
File Name: /home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03joyn_.bkp
File Name: /home/oracle/bak/o1_mf_s_991416863_fy03o039_.bkp
File Name: /home/oracle/bak/o1_mf_annnn_TAG20181105T173202_fy03jms6_.bkp
RMAN> restore database;

Starting restore at 05-NOV-18
using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/orcl/rc_data.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03joyn_.bkp
channel ORA_DISK_2: starting datafile backup set restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
channel ORA_DISK_2: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_2: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_2: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_2: reading from backup piece /home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03jolp_.bkp
channel ORA_DISK_2: piece handle=/home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03jolp_.bkp tag=TAG20181105T173205
channel ORA_DISK_2: restored backup piece 1
channel ORA_DISK_2: restore complete, elapsed time: 00:01:57
channel ORA_DISK_1: piece handle=/home/oracle/bak/o1_mf_nnndf_TAG20181105T173205_fy03joyn_.bkp tag=TAG20181105T173205
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:02:27
Finished restore at 05-NOV-18
RMAN> alter database open resetlogs;

database opened

RMAN> exit

RMAN遷移數據庫（不改變文件目錄）

相關推薦

RMAN遷移數據庫（不改變文件目錄）

ins implicit open fix edi pattern created sta 備份 1、目標庫創建相應目錄mkdir -p /u01/app/oracle/oradata/orclmkdir -p /u01/app/oracle/fast_recovery_a

MySQL遷移數據庫（mysqldump）

指定表 image test style span .com toc log ase 一、導出導入所有數據庫的數據 　　1.導出 　　　mysqldump -u root -p123456 --all-databases > all.sql 　　　 　　2.導入

linux CentOS7最小化安裝環境靜默安裝Oracle11GR2數據庫（修改配置文件）

shmall file-max 數據庫 安裝 tex rap png img entos linux CentOS7最小化安裝環境靜默安裝Oracle11GR2數據庫（修改配置文件） 一、修改內核文件： vim /etc/sysctl.conf 按一次 "i&qu

linux CentOS7最小化安裝環境靜默安裝Oracle11GR2數據庫（靜默創建實例）

修改 無需 b2b f11 log mar RoCE 這一 rac 執行安裝前的準備工作： 1.安裝操作系統：http://blog.51cto.com/mflag/23003592.安裝依賴包:http://blog.51cto.com/mflag/23009093.上

MyBatis中sqlSession操作數據庫，不報錯但無法實現數據修改（增、改、刪）

修改 () brush light pub clas java bat job public void addCustomerTest() throws Exception { SqlSession sqlSession = MyBatisUtils.ge

Java學習總結（十五）——MySQL數據庫（上）—增，刪，改與部分查詢語句

MySQL數據庫 增 刪 改 查 一．MySQL簡介及在DOS下操作MySQL1.MySQL是一種中型關系型數據庫管理系統（DBMS,Database Management System）。註意：關系型數據庫是按照表的方式存儲數據的2.DOS環境下操作MySQL（1）進入MySQL環境：（

【翻譯自mos文章】使用asm來部署 超大數據庫（10TB到PB 範圍）--針對oracle 10G

2個 數值 acl 5.1 transport after 例如 clas rain 使用asm來部署 超大數據庫（10TB到PB 範圍） 參考原文： Deployment of very large databases (10TB to PB range) with

【數據庫】MySQL數據庫（二）

關閉數據庫 dos命令 medium 數據庫密碼 gin mysql tables 日期 導出數據 一、數據庫文件的導出 1.在DOS命令行下導出數據庫(帶數據) mysqldump -u root -p 數據庫名 > E:\wamp\www\lamp175\lam

【數據庫】MySQL數據庫（三）

沒有 特殊 進行 主鍵索引 rst ble 刪除 索引 可能 一、MySQL當中的索引： 數組當中我們見過索引；它的好處就是能夠快速的通過下標、索引將一個信息查到；或者說 能夠快速的定位到一個信息； 1.MySQL中的索引是什麽？ 它是將我們表中具有索引的那個字段，

【數據庫】MySQL數據庫（一）

管理系統 ins 我的電腦 使用 語句 命令行 mar alt rac 一、MySQL數據庫系統 MySQL數據庫系統就是用來對數據庫、數據的一些管理 二、數據庫系統 1.數據庫 就是用來存儲各種數據的 2.數據庫管理系統 就是用來管理各種數據庫的數據的一個系統

4.非關系型數據庫（Nosql）之mongodb：普通索引，唯一索引

log 索引 xpl sys watermark lang mon style gravity  一：普通索引 1創建一個新的數據庫 > use toto; switched to db toto

ORA-00064 processes設置過大導致數據庫打不開

oracle processes ora-00064 processes設置過大導致數據庫打不開在processes設置過大後，可能導致數據庫打不開，開啟數據庫後會報錯：SQL> startup ORA-00064: object is too large to allocate on t

使用Lotus Enterprise Integrator （LEI）將Domino附件移至關系數據庫（圖文過程）

art 成功 extern nal ext http 沒有 其中 需要 參考IBM解決方案：http://www.ibm.com/developerworks/cn/lotus/LEI-attachments/index.html 轉載請註明出處：http://blog.

安卓數據庫 找不到表

安卓數據庫 let 系統默認 ado open actor sse filename 創建失敗 自己建一個表，放在assets目錄下 package mine; import android.annotation.SuppressLint;import android.co

數據庫（1）

數據 let ant ont strong 授權 結構化 分類 操作 SQL（結構化查詢語句） 分類 　　DML（數據操作語言） 　　　　insert（增加） update（修改） delete（刪除） 　　DCL（數據控制語言） 　　　　gra

數據庫（3）

cat rop pan 建表 -s rim var 數據 mar DDL 　　a.create table (創建表) 　　　　語法：create table 表名(列名 列數據類型...) 　　　　　　eg：create table stu(

數據庫（7）

src -- str left join 技術分享 bsp select 條件 一個 多表連接（就是把多個表變成一個表再去操作） 內連接（inner join...on） 　　select... 　　from 表1 inner join 表2 on 連接條件

Python 3.5 連接Mysql數據庫（pymysql 方式）

ima 用戶名 oca rim 遊標對象 ide char 名稱 etc 由於 MySQLdb 模塊還不支持 Python3.x，官方的Mysql連接包只支持到3.4，所以 Python3.5 如果想連接MySQL需要安裝 pymysql 模塊。 pymysql 模塊可以通

python操作數據庫（MySQL、redis）

absolut lec pen 鏈接 hone key imp iam sql 1、Python3操作MySQL數據庫需要安裝一個第三方模塊(pymysql)：pip install pymysql；操作redis需要安裝redis模塊(redis)：pip install

再看數據庫——（1）存儲過程

靈活 技術分享 ted pop 能夠 數據庫對象 順序 記錄 爸爸 當我們運行一個比較簡單的操作時，一般都是用SQL語句。可是當邏輯越來越復雜時，只使用順序運行的SQL語句序列表現出非常大的局限性。這時，就能夠考慮用還有一種方法了。那就是存儲過程。