130506datafile和tablespace offline区别

tablespace offline是将tablespace 离线有normal等选项

，命令为 alter tablespace users offline normal;

SQL> select tablespace_name, status from dba_tablespaces;

TABLESPACE_NAME STATUS

------------------------------ ---------

SYSTEM ONLINE

SYSAUX ONLINE

UNDOTBS1 ONLINE

USERS OFFLINE

EXAMPLE ONLINE

UNDO_NOGUARANTEE ONLINE

UNDO_GUARANTEE ONLINE

NONCRIT ONLINE

TEST121217 ONLINE

SMALL ONLINE

TEMP02 ONLINE

INDEX_TEST1 ONLINE

NEW_TBS OFFLINE

将datafile offline，需要注意当online时需要进行meida recovery；

11:02:37 SYS@TEST>ALTER DATABASE DATAFILE 13 OFFLINE;

Database altered.

11:13:56 SYS@TEST>ALTER DATABASE DATAFILE 13 ONLINE;

ALTER DATABASE DATAFILE 13 ONLINE

ERROR at line 1:

ORA-01113: file 13 needs media recovery

ORA-01110: data file 13: 'D:\ORACLE\ORADATA\TEST\NEW_TBS.DBF'

11:02:37 SYS@TEST>ALTER DATABASE DATAFILE 13 OFFLINE;

Database altered.

11:13:56 SYS@TEST>ALTER DATABASE DATAFILE 13 ONLINE;

ALTER DATABASE DATAFILE 13 ONLINE

ERROR at line 1:

ORA-01113: file 13 needs media recovery

ORA-01110: data file 13: 'D:\ORACLE\ORADATA\TEST\NEW_TBS.DBF'

RMAN> RESTORE DATAFILE 13;

Starting restore at 07-MAY-13

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=148 device type=DISK

creating datafile file number=13 name=D:\ORACLE\ORADATA\TEST\NEW_TBS.DBF

restore not done; all files read only, offline, or already restored

Finished restore at 07-MAY-13

需要注意的是只是需要进行recover，并不需要restore，因为文件本身存在未损坏，recover是要将归档日志应用到离线的文件

RMAN> RECOVER DATAFILE 13;

Starting recover at 07-MAY-13

using channel ORA_DISK_1

starting media recovery

archived log for thread 1 with sequence 15 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_15_8J17J7Y8_.ARC

archived log for thread 1 with sequence 16 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_16_8J2FXDRL_.ARC

archived log for thread 1 with sequence 17 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_17_8J2HFHJY_.ARC

archived log for thread 1 with sequence 18 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_18_8J2HS7PW_.ARC

archived log for thread 1 with sequence 19 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_25\O1_MF_1_19_8J4CP21K_.ARC

archived log for thread 1 with sequence 20 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_20_8KKQFN9C_.ARC

archived log for thread 1 with sequence 21 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_21_8KKQFS1Q_.ARC

archived log for thread 1 with sequence 22 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_22_8KKQFYK6_.ARC

archived log for thread 1 with sequence 23 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_23_8KKQG35K_.ARC

archived log for thread 1 with sequence 24 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_24_8KKQG7WO_.ARC

archived log for thread 1 with sequence 25 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_25_8KKQGDNP_.ARC

archived log for thread 1 with sequence 26 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_19\O1_MF_1_26_8L6FQ13F_.ARC

archived log for thread 1 with sequence 27 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_27\O1_MF_1_27_8LVD2GR3_.ARC

archived log for thread 1 with sequence 28 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_27\O1_MF_1_28_8LVD2N14_.ARC

archived log for thread 1 with sequence 29 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_03_19\O1_MF_1_29_8NHZR642_.ARC

archived log for thread 1 with sequence 30 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_03_21\O1_MF_1_30_8NO5VRRQ_.ARC

archived log for thread 1 with sequence 31 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_03_25\O1_MF_1_31_8NZT0GN7_.ARC

archived log for thread 1 with sequence 32 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_09\O1_MF_1_32_8P71V8S6_.ARC

archived log for thread 1 with sequence 33 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_09\O1_MF_1_33_8P78BBX3_.ARC

archived log for thread 1 with sequence 34 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_11\O1_MF_1_34_8PDOSG43_.ARC

archived log for thread 1 with sequence 35 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_13\O1_MF_1_35_8PKLTO7H_.ARC

archived log for thread 1 with sequence 36 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_13\O1_MF_1_36_8PKM1G58_.ARC

archived log for thread 1 with sequence 37 is already on disk as file D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_05_07\O1_MF_1_37_8RJRK8J7_.ARC

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_15_8J17J7Y8_.ARC thread=1 sequence=15

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_16_8J2FXDRL_.ARC thread=1 sequence=16

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_17_8J2HFHJY_.ARC thread=1 sequence=17

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_24\O1_MF_1_18_8J2HS7PW_.ARC thread=1 sequence=18

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_01_25\O1_MF_1_19_8J4CP21K_.ARC thread=1 sequence=19

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_20_8KKQFN9C_.ARC thread=1 sequence=20

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_21_8KKQFS1Q_.ARC thread=1 sequence=21

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_22_8KKQFYK6_.ARC thread=1 sequence=22

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_23_8KKQG35K_.ARC thread=1 sequence=23

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_24_8KKQG7WO_.ARC thread=1 sequence=24

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_11\O1_MF_1_25_8KKQGDNP_.ARC thread=1 sequence=25

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_19\O1_MF_1_26_8L6FQ13F_.ARC thread=1 sequence=26

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_27\O1_MF_1_27_8LVD2GR3_.ARC thread=1 sequence=27

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_02_27\O1_MF_1_28_8LVD2N14_.ARC thread=1 sequence=28

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_03_19\O1_MF_1_29_8NHZR642_.ARC thread=1 sequence=29

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_03_21\O1_MF_1_30_8NO5VRRQ_.ARC thread=1 sequence=30

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_03_25\O1_MF_1_31_8NZT0GN7_.ARC thread=1 sequence=31

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_09\O1_MF_1_32_8P71V8S6_.ARC thread=1 sequence=32

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_09\O1_MF_1_33_8P78BBX3_.ARC thread=1 sequence=33

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_11\O1_MF_1_34_8PDOSG43_.ARC thread=1 sequence=34

archived log file name=D:\ORACLE\FLASH_RECOVERY_AREA\TEST\ARCHIVELOG\2013_04_13\O1_MF_1_35_8PKLTO7H_.ARC thread=1 sequence=35

media recovery complete, elapsed time: 00:00:05

Finished recover at 07-MAY-13

转载于:https://blog.51cto.com/1310976/1194737

130506datafile和tablespace offline区别相关推荐

ALTER DATABASE 与 ALTER TABLESPACE OFFLINE的区别
一．DataFile脱机或联机的两种方法: ① ALTER DATABASE 语句修改单独的DataFile ② ALTER TABLESPACE 语句修改所有的DataFile 1.在ARCHIVR ...
ORACLE表空间与数据文件OFFLINE区别
(一)OFFLINE TABLESPACE ALTER TABLESAPCE OFFLINE可用选项包括NORMAL, TEMPORARY, IMMEDIATE, FOR RECOVERY OFFLI ...
oracle联机和脱机什么意思,Oracle 表空间联机（online）与脱机（offline）
数据库管理员可以在数据库处于开启(open)状态时令除 SYSTEM 表空间(tablespace)之外的任何表空间联机(online)(可访问)或脱机(offline)(不可访问).SYSTEM 表 ...
Oracle数据库之表空间（tablespace）---面试再也不害怕系列之一
Oracle数据库的江湖地位不用多说,懂得都懂,大型公司基本必备的数据库,没有之一.在咱们国家,虽然有喊口号--去o化,可口号喊得在响亮,身体却很诚实,因此,Oracle也是运维或者开发面试时所需要掌 ...
Drop tablespace
打算drop tablespace,要怎么确定tablespace里有没有内容或者对象呢? 各种查询数据字典,dba_tables.dba_indexes.dba_lobs.dba_procedure ...
oracle 表空间 Managing Tablespace Data Files
一.Objectives Define the purpose of tablespaces and data files(定义的表空间和数据文件的目的) Create tablespaces Man ...
oracle表启用online,Oracle 表空间联机（online）与脱机（offline）
数据库管理员可以在数据库处于开启(open)状态时令除 SYSTEM 表空间(tablespace)之外的任何表空间联机(online)(可访问)或脱机(offline)(不可访问).SYSTEM 表 ...
oracle offline 删除表,Oracle offline 表空间详解
表空间详解一.Offline的整体效果:offline以后,未完成的事物可以提交或回滚,但不能发起新的事物,也不能进行查询. 二.Offline的语法: ALTER TABLESPACE table ...
oracle技术之检查点及SCN深入研究
一.检查点概述大多数关系型数据库都采用"在提交时并不强迫针对数据块的修改完成"而是"提交时保证修改记录(以重做日志的形式)写入日志文件"的机制,来获得性能的优 ...

130506datafile和tablespace offline区别

130506datafile和tablespace offline区别相关推荐

最新文章

热门文章