RMAN 备份恢复系列之controlfile恢复

最新推荐文章于 2025-04-29 09:25:03 发布
最新推荐文章于 2025-04-29 09:25:03 发布
阅读量3.3k 收藏 4
点赞数
分类专栏： OCM Training RMAN备份与恢复 备份与恢复 文章标签： oracle rman 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/zhuke0203/article/details/71246086
版权

实验环境

  • 操作系统 Redhat5.4 x86
  • 数据库版本 oracle 11gR2 (11.2.0.1.0)
  • 实验前已经做了RMAN全量备份包括controlfile、spfile

实验模拟

部分controlfile文件损坏或丢失

案例模拟

查询数据库中控制文件信息

SQL> col name for a60
SQL> set line 180
SQL> select * from v$controlfile;
STATUS  NAME                                 IS_ BLOCK_SIZE FILE_SIZE_BLKS
------- ------------------------------------------------------------ --- ---------- --------------
    /u01/app/oracle/oradata/PROD/disk1/control1          NO       16384        580
    /u01/app/oracle/oradata/PROD/disk2/control2          NO       16384        580
    /u01/app/oracle/oradata/PROD/disk3/control3          NO       16384        580

SQL> 
SQL> 
SQL> 
SQL> show parameter control

NAME                     TYPE    VALUE
------------------------------------ ----------- ------------------------------
control_file_record_keep_time        integer     7
control_files                string  /u01/app/oracle/oradata/PROD/d
                         isk1/control1, /u01/app/oracle
                         /oradata/PROD/disk2/control2,
                         /u01/app/oracle/oradata/PROD/d
                         isk3/control3
control_management_pack_access       string  DIAGNOSTIC+TUNING
SQL>

删除部分controlfile文件
至少保留一份controlfile文件没有被损坏或丢失。
本例删除control1 和control3 保留control2文件。

SQL> !rm /u01/app/oracle/oradata/PROD/disk1/control1

SQL> !rm /u01/app/oracle/oradata/PROD/disk3/control3

SQL> !ls /u01/app/oracle/oradata/PROD/disk1/control1
ls: /u01/app/oracle/oradata/PROD/disk1/control1: No such file or directory
SQL> 
SQL> !ls /u01/app/oracle/oradata/PROD/disk2/control2
/u01/app/oracle/oradata/PROD/disk2/control2

SQL> !ls /u01/app/oracle/oradata/PROD/disk3/control3
ls: /u01/app/oracle/oradata/PROD/disk3/control3: No such file or directory

重启数据库
重启数据库提示以下报错：

SQL> shutdown immediate;
Database closed.
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u01/app/oracle/oradata/PROD/disk1/control1'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3


SQL> select status from v$instance;

STATUS
------------
MOUNTED

SQL>                
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.

Total System Global Area  836976640 bytes
Fixed Size          1339740 bytes
Variable Size         658509476 bytes
Database Buffers      171966464 bytes
Redo Buffers            5160960 bytes
ORA-00205: error in identifying control file, check alert log for more info


SQL>

检查alert日志发现以下报错信息：

Fri May 05 22:03:43 2017
ALTER DATABASE   MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u01/app/oracle/oradata/PROD/disk3/control3'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u01/app/oracle/oradata/PROD/disk1/control1'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-205 signalled during: ALTER DATABASE   MOUNT...
Fri May 05 22:03:43 2017
Checker run found 2 new persistent data failures

alert 日志文件提示 control1 control3 丢失文件不存在。

案例恢复

由于三份文件中的内容是完全相同的，因此我们可以通过操作系统命令从已存在的control2，分别复制出control1，control3文件，要保持文件名以及绝对路径与损坏前相同，如果因为存储故障短时间内无法保证文件路径以及文件名一致，则需要修改spfile文件中control_files参数的值。

恢复前与恢复后文件名以及路径不变情况：
[oracle@node1 ~]$ cp /u01/app/oracle/oradata/PROD/disk2/control2 /u01/app/oracle/oradata/PROD/disk1/control1
[oracle@node1 ~]$ cp /u01/app/oracle/oradata/PROD/disk2/control2 /u01/app/oracle/oradata/PROD/disk3/control3
[oracle@node1 ~]$ ls /u01/app/oracle/oradata/PROD/disk1/control1
/u01/app/oracle/oradata/PROD/disk1/control1
[oracle@node1 ~]$ ls /u01/app/oracle/oradata/PROD/disk3/control3
/u01/app/oracle/oradata/PROD/disk3/control3
[oracle@node1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Fri May 5 22:18:43 2017

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


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

SQL> select status from v$instance;

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

SQL> alter database mount;

Database altered.

SQL> alter database open;   

Database altered.

SQL> select status from v$instance;

STATUS
------------
OPEN

RMAN命令恢复法：

[oracle@node1 ~]$ rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Fri May 5 22:31:14 2017

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

connected to target database: PROD (not mounted)

RMAN>
RMAN> list failure;

using target database control file instead of recovery catalog
List of Database Failures
=========================

Failure ID Priority Status    Time Detected Summary
---------- -------- --------- ------------- -------
828        CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control3 is missing
822        CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control1 is missing

RMAN> advise failure;

List of Database Failures
=========================

Failure ID Priority Status    Time Detected Summary
---------- -------- --------- ------------- -------
828        CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control3 is missing
822        CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control1 is missing

analyzing automatic repair options; this may take some time
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
analyzing automatic repair options complete

Mandatory Manual Actions
========================
no manual actions available

Optional Manual Actions
=======================
no manual actions available

Automated Repair Options
========================
Option Repair Description
------ ------------------
1      Use a multiplexed copy to restore control file /u01/app/oracle/oradata/PROD/disk2/control3  
  Strategy: The repair includes complete media recovery with no data loss
  Repair script: /u01/app/oracle/diag/rdbms/prod/PROD/hm/reco_89851306.hm

RMAN> repair failure;

Strategy: The repair includes complete media recovery with no data loss
Repair script: /u01/app/oracle/diag/rdbms/prod/PROD/hm/reco_89851306.hm

contents of repair script:
   # restore control file using multiplexed copy
   restore controlfile from '/u01/app/oracle/oradata/PROD/disk2/control2';
   sql 'alter database mount';

Do you really want to execute the above repair (enter YES or NO)? YES
executing repair script

Starting restore at 05-MAY-17
using channel ORA_DISK_1

channel ORA_DISK_1: copied control file copy
output file name=/u01/app/oracle/oradata/PROD/disk2/control1
output file name=/u01/app/oracle/oradata/PROD/disk2/control2
output file name=/u01/app/oracle/oradata/PROD/disk2/control3
Finished restore at 05-MAY-17

sql statement: alter database mount
released channel: ORA_DISK_1
repair failure complete

Do you want to open the database (enter YES or NO)? YES
database opened

RMAN> exit


Recovery Manager complete.
[oracle@node1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Fri May 5 22:36:23 2017

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


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

SQL> select status from v$instance;

STATUS
------------
OPEN

SQL> select name from v$controlfile;

NAME
--------------------------------------------------------------------------------
/u01/app/oracle/oradata/PROD/disk2/control1
/u01/app/oracle/oradata/PROD/disk2/control2
/u01/app/oracle/oradata/PROD/disk2/control3

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@node1 ~]$ ls -la /u01/app/oracle/oradata/PROD/disk2/control*
-rw-r----- 1 oracle oinstall 9519104 May  5 22:37 /u01/app/oracle/oradata/PROD/disk2/control1
-rw-r----- 1 oracle oinstall 9519104 May  5 22:37 /u01/app/oracle/oradata/PROD/disk2/control2
-rw-r----- 1 oracle oinstall 9519104 May  5 22:37 /u01/app/oracle/oradata/PROD/disk2/control3
[oracle@node1 ~]$
恢复前与恢复后文件名以及路径发生变化的情况：

模拟disk1、disk3两块存放controlfile文件的磁盘都损坏了段时间内无法恢复，临时将control1、control3文件存放在disk2目录下，与control2保持一致，步骤如下：

SQL> alter system set control_files='/u01/app/oracle/oradata/PROD/disk2/control1','/u01/app/oracle/oradata/PROD/disk2/control2','/u01/app/oracle/oradata/PROD/disk2/control3' scope=spfile;

System altered.

SQL> !cp /u01/app/oracle/oradata/PROD/disk2/control2 /u01/app/oracle/oradata/PROD/disk2/control1

SQL> !cp /u01/app/oracle/oradata/PROD/disk2/control2 /u01/app/oracle/oradata/PROD/disk2/control3

SQL> shutdown immediate;
ORA-01507: database not mounted


ORACLE instance shut down.
SQL> startup;
ORACLE instance started.

Total System Global Area  836976640 bytes
Fixed Size          1339740 bytes
Variable Size         658509476 bytes
Database Buffers      171966464 bytes
Redo Buffers            5160960 bytes
Database mounted.
Database opened.
SQL> select name from v$controlfile;

NAME
--------------------------------------------------------------------------------
/u01/app/oracle/oradata/PROD/disk2/control1
/u01/app/oracle/oradata/PROD/disk2/control2
/u01/app/oracle/oradata/PROD/disk2/control3

SQL>

全部controlfile文件都损坏或丢失

案例模拟

手动删除所有控制文件：

[oracle@node1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Fri May 5 22:40:30 2017

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


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

SQL> select name from v$controlfile;

NAME
--------------------------------------------------------------------------------
/u01/app/oracle/oradata/PROD/disk2/control1
/u01/app/oracle/oradata/PROD/disk2/control2
/u01/app/oracle/oradata/PROD/disk2/control3

SQL> !rm /u01/app/oracle/oradata/PROD/disk2/control*

SQL> !ls /u01/app/oracle/oradata/PROD/disk2/control*
ls: /u01/app/oracle/oradata/PROD/disk2/control*: No such file or directory

SQL> shutdown immediate;
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u01/app/oracle/oradata/PROD/disk2/control1'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
SQL>                
SQL> shutdown abort;
ORACLE instance shut down.
SQL> 
SQL> startup;
ORACLE instance started.

Total System Global Area  836976640 bytes
Fixed Size          1339740 bytes
Variable Size         658509476 bytes
Database Buffers      171966464 bytes
Redo Buffers            5160960 bytes
ORA-00205: error in identifying control file, check alert log for more info

SQL>

案例恢复

利用RMAN从之前的备份中进行恢复：

[oracle@node1 ~]$ rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Fri May 5 22:42:09 2017

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

connected to target database: PROD (not mounted)

RMAN> list failure;

using target database control file instead of recovery catalog
List of Database Failures
=========================

Failure ID Priority Status    Time Detected Summary
---------- -------- --------- ------------- -------
1071       CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control3 is missing
1068       CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control2 is missing
1065       CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control1 is missing

RMAN> advise failure;

List of Database Failures
=========================

Failure ID Priority Status    Time Detected Summary
---------- -------- --------- ------------- -------
1071       CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control3 is missing
1068       CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control2 is missing
1065       CRITICAL OPEN      05-MAY-17     Control file /u01/app/oracle/oradata/PROD/disk2/control1 is missing

analyzing automatic repair options; this may take some time
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
analyzing automatic repair options complete

Mandatory Manual Actions
========================
no manual actions available

Optional Manual Actions
=======================
1. If file /u01/app/oracle/oradata/PROD/disk2/control3 was unintentionally renamed or moved, restore it
2. If file /u01/app/oracle/oradata/PROD/disk2/control2 was unintentionally renamed or moved, restore it
3. If file /u01/app/oracle/oradata/PROD/disk2/control1 was unintentionally renamed or moved, restore it
4. If a standby database is available, then perform a Data Guard failover initiated from the standby

Automated Repair Options
========================
Option Repair Description
------ ------------------
1      Restore a backup control file  
  Strategy: The repair includes complete media recovery with no data loss
  Repair script: /u01/app/oracle/diag/rdbms/prod/PROD/hm/reco_2346970307.hm

RMAN> repair failure;

Strategy: The repair includes complete media recovery with no data loss
Repair script: /u01/app/oracle/diag/rdbms/prod/PROD/hm/reco_2346970307.hm

contents of repair script:
   # restore control file
   restore controlfile from autobackup;
   sql 'alter database mount';

Do you really want to execute the above repair (enter YES or NO)? YES
executing repair script

Starting restore at 05-MAY-17
using channel ORA_DISK_1

recovery area destination: /u01/app/oracle/flash_recovery_area
database name (or database unique name) used for search: PROD
channel ORA_DISK_1: AUTOBACKUP /u01/app/oracle/flash_recovery_area/PROD/autobackup/2017_05_05/o1_mf_s_943223985_djs3olf9_.bkp found in the recovery area
AUTOBACKUP search with format "%F" not attempted because DBID was not set
channel ORA_DISK_1: restoring control file from AUTOBACKUP /u01/app/oracle/flash_recovery_area/PROD/autobackup/2017_05_05/o1_mf_s_943223985_djs3olf9_.bkp
channel ORA_DISK_1: control file restore from AUTOBACKUP complete
output file name=/u01/app/oracle/oradata/PROD/disk2/control1
output file name=/u01/app/oracle/oradata/PROD/disk2/control2
output file name=/u01/app/oracle/oradata/PROD/disk2/control3
Finished restore at 05-MAY-17

sql statement: alter database mount
released channel: ORA_DISK_1
repair failure complete

RMAN>

至此，数据库控制文件恢复已经完成，注意每次进行玩以后及时做一次rman的全量备份。

使用rman恢复控制文件
一抹曦阳-Oracle
10-11 1万+
控制文件(controlfile)丢失恢复 基于控制文件的复合多路径性，它的丢失分为两种，一种是其中某个控制文件的损坏或丢失，另外一种是所有控制文件均丢失。基于第一种情况，只需把好的控制文件复制一份在损坏或丢失的那个控制文件路径下即可。第二种情况下则需要通过备份信息来对控制文件进行恢复或手工重建控制文件。 丢失单一控制文件的判断及恢复 /u01/app/oracle/or
oracle rman backup controlfile,RMAN的controlfile和catalog同步
weixin_35268264的博客
04-08 602
RMAN的controlfile和catalog同步当我们使用catalog来代替controlfile做为rman repository时，有关备份的元数据信息也会在controlfil中存的，这样当在使用rman时，即使catalog临时不可用也可以使用controlfile中的信息.在下次能连接catalog的时候，我们使用resync catalog也可以再次手动动步controlfile...
使用rman工具备份及恢复
最新发布
qq_22201881的博客
04-29 815
第一个全备是 5 天前生成的，第二个全备是十天前生成的，而最早一个全备是 15 天前备份 的，那么十天前生成的备份及之后的归档日志必须保留，而 15 天前的那个备份会成为废弃备份(obsolete)。如果取消 ALLOCATE CHANNEL 语句，则通道数按全局变量 PARALLELISM 指定，假定为 1，那 20 个文件，FILESPERSET=8 该是怎样的结果：一个通道干活，8 个文件组成一个备份集，每备份集对一个备份片，完成一个备份集再接下一个备份集。只备份自某次备份以来发生变化的数据块。
RMAN 恢复 Controlfile
qq_31144297的博客
05-04 516
RMAN 恢复 Controlfile 两种情况： a.部分丢失（有2份controlfile，只丢失其中1份）； b.全部丢失（前提是必须有做备份才能恢复）； 一、部分丢失 a.检查确定是否有多个controlfile： 进入sqlplus，执行如下命令： SQL> select name from v$controlfile; NAME -------------
oracle丢失控制文件恢复,rman之丢失controlfile 控制文件恢复
weixin_42378997的博客
04-09 859
如果controlfile 丢失对数据库来说也是灾难性的，下面说说如何恢复controlfile的几种方法1. 使用RMAN工具备份恢复controlfileRMAN参数选项”CONFIGURE CONTROLFILE AUTOBACKUP ON/OFF”定义为”ON”，则任意一次RMAN备份都会自动备份controlfile，比如备份tablespace；定义为”OFF”，则不会自动备份c...
rman restore controlfile
STEPHEN_ORACLE 'S LIFE
09-02 624
这篇文章主要是运用rman新增一个控制文件，并且在实验过程中发现了一些问题首先生成一个参数文件RMAN> restore spfile to pfile '/tmp/001.ora' 2> ;Starting restore at 14-AUG-17 using target database control file instead of recovery catalog allocated
Oracle19c rac备份数据通过rman恢复到单实例
07-02
本文将以一个具体案例为基础，详细介绍如何通过RMAN将Oracle 19c RAC的备份数据恢复到单实例环境。 #### 准备阶段 1. **环境配置**： - 在目标服务器上配置环境变量，确保与源RAC环境一致。 - 安装相同版本的...
Oracle 12c备份恢复-RMAN工具技术手册
12-27
Oracle 12c 备份恢复-RMAN 工具技术手册 本文档旨在提供 Oracle 12c 备份恢复的技术手册，主要介绍 RMAN 工具的概念、架构、备份类型和使用方法。 一、RMAN 概念 RMAN（Recovery Manager）是 Oracle 推荐的备份和...
DBA之路--RMAN备份与恢复01_RMAN体系架构
Princesk的博客
06-05 3123
由1.6我们可知道，rman在实际使用时会在SGA或PGA构筑缓冲区，同时通过1这些缓冲区将数据文件写入到块。这种缓冲区有实际分为两种输入缓冲区，填充从备份文件中读取的数据块#输入内存缓冲区 备份数据库时，输入内存缓冲区大小和数目取决于实际执行的备份命令，或者说时一个备份中多路复用的文件数量。
ORACLE 数据库RMAN备份恢复
09-11
2. **检查归档模式**：确认数据库是否已经配置为归档模式，这是进行RMAN备份的前提条件之一。 ```sql ARCHIVELOG LIST; ``` 3. **修改数据库模式**：如果当前数据库不是归档模式，则需要将其转换为归档模式。 `...
rman备份恢复实例
04-24
根据提供的文件内容，本文将详细解释RMAN（Recovery Manager）在Oracle数据库...以上就是RMAN备份与恢复的核心流程和技术要点。通过这些步骤，可以有效地管理Oracle数据库的备份与恢复过程，确保数据的安全性和可靠性。
使用RMAN备份与恢复数据库（3）——控制文件的备份与恢复
睿思达DBA
04-09 1013
使用RMAN备份与恢复数据库（3）——控制文件的备份与恢复 控制文件是一个跟踪数据库的二进制文件，每个数据库有唯一的控制文件，可以维护多个相同的拷贝。控制文件是oracle数据库用来查找数据库文件，并从总体上管理数据库状态的文件。控制文件包含以下信息： （1）数据库名称和数据库唯一标识符（DBID）； （2）创建数据库的时间戳； （3）有关数据库文件、联机重做日志、归档日志的信息； （4）表空间的...
利用RMAN备份恢复CONTROLFILE
congtudi4111的博客
04-29 154
RMAN> show all; RMAN 配置参数为:CONFIGURE RETENTION POLICY TO REDUNDANCY 2;CONFIGURE BACKUP OPTIMIZATION OFF; # def...
还原oracle控制文件位置,rman还原控制文件（一）
weixin_42592399的博客
04-07 679
如果丢失或损坏所有的控制文件就需要从备份中还原控制文件。restore controlfile命令用来还原控制文件。在还原控制文件后需要对数据亩执行完全介质恢复并以resetlog选项来打开数据库。RMAN可以将控制文件还原到它的默认存储位置，也可以使用restore controlfile ... to destination来指定位置。从已经知的控制文件备份中还原控制文件SQL> sho...
oracle 11g 从rman全备中恢复控制文件,RMAN备份恢复（控制文件）
weixin_36292971的博客
04-03 510
控制文件怎么做备份假如删除了一个控制文件，只需要将没有删除的控制文件拷贝一份，然后重命名就可以恢复了；备份控制文件的语句：RMAN> list backup of controlfile;----查看备份文件的语句；没有开启自动备份，却有备份，这样的备份我们叫隐式备份；RMAN> show all;RMAN configurationparameters for database wi...
控制文件的备份与恢复（RMAN工具）
搞怪的索引
08-11 1758
本篇说明控制文件在全部丢失的情况下，利用Rman工具自动备份的控制文件转储并回复数据库； 之前写过一篇关于手动“控制文件的备份与恢复” ，请查阅：http://blog.youkuaiyun.com/perfect_db/article/details/8805111 数据库版本 SQL> select * from v$version; BANNER -----------------
RMAN备份恢复（控制文件）
congwei2855的博客
03-16 380
1 控制文件中存在什么： ---...
使用rman恢复控制文件 -- 转载的
qq_41468794的博客
07-16 479
控制文件(controlfile)丢失恢复 基于控制文件的复合多路径性，它的丢失分为两种，一种是其中某个控制文件的损坏或丢失，另外一种是所有控制文件均丢失。基于第一种情况，只需把好的控制文件复制一份在损坏或丢失的那个控制文件路径下即可。第二种情况下则需要通过备份信息来对控制文件进行恢复或手工重建控制文件。 丢失单一控制文件的判断及恢复 /u01/app/oracle/oradata/test0924/control01.ctl   数据库无法正常关闭，因为在关闭的时候必须向控制文件中更新scn号
rman restore controlfile 多种办法
jnrjian的博客
08-30 826
There are many ways to restore the controlfile for recovery using RMAN. This note provides several examples of how to get the controlfile back quickly so the restore of the database can be started asap. Note: If you do not specify where to restore the con
Linux环境下Oracle9i RMAN备份恢复教程
"Linux环境下Oracle9i数据库的RMAN备份和恢复流程" 在Oracle数据库管理中，RMAN（恢复管理器）是用于数据库备份、恢复和维护的强大工具。在Linux操作系统中，Oracle9i版本的数据库管理员需要熟悉如何使用RMAN进行...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值