精华内容
参与话题
问答
  • rman

    2017-09-21 07:01:00
    rman / target 1.全库备份 RMAN>backup database(RMAN备份的包括当前正在用的参数文件,正在用的控制文件,和所有的数据文件,不包括联机日志文件) 2.备份参数文件(rman只能备份二进制文件) RMAN>backup ...

    >rman / target

    1.全库备份

    RMAN>backup database(RMAN备份的包括当前正在用的参数文件,正在用的控制文件,和所有的数据文件,不包括联机日志文件)

    2.备份参数文件(rman只能备份二进制文件)

    RMAN>backup spflie(备份参数文件,不能备份pfile,因为pfile是文本文件)

    3.备份控制文件

    RMAN>backup current controlfile;

    4.单独备份某一个文件

    RMAN>backup datafile 4;

    5.指定备份某个表空间(一个表空间默认情况下只能有1024个数据文件)

    RMAN>backup tablespace users;

    6.备份多个数据文件

    RMAN>backup datafile 2,4;

    7.备份多个表空间

    RMAN>backup tablespace users,sysaux;

    8.备份归档日志

    RMAN>backup archivelog all;

    9.全库备份

    RMAN>backup full database plus archivelog;

    RMAN>backup archivelog all delete input(删掉原来的归档日志,只留下备份的归档日志)

    10.备份不包括某项

    RMAN>backup database skip readonly;

    RMAN>backup database skip offline;

    11.指定备份

    backup database format '/u01/dbfull_u%';

    12.不指定备份的话,必须有db_rec参数

    sql>show parameter db_rec;(所有默认闪回区,omf目录下的闪回日志,归档日志,rman备份文件.

     

    转载于:https://www.cnblogs.com/gw666/p/7565985.html

    展开全文
  • RMAN

    2016-01-21 18:45:42
    RAMN概述恢复管理器,可以跨越不同的操作系统进行数据库的备份与恢复RMAN的优势: Rman操作简单 自动化功能强 Rman可以忽略备份后未发生改变的block 使用rman可以轻松的创建备份或stabdby数据库 自动执行并行的备份...

    RAMN概述

     恢复管理器,可以跨越不同的操作系统进行数据库的备份与恢复

     RMAN的优势:

       Rman操作简单 自动化功能强

       Rman可以忽略备份后未发生改变的block

       使用rman可以轻松的创建备份或stabdby数据库

       自动执行并行的备份和还原操作

       可以不实际执行的情况下检查文件是否被正确的备份或还原


    第一种连接方式

    [oracle@sq ~]$ rman

    RMAN> connect target /


    第二种连接方式

    [oracle@sq ~]$ rman target /


    ======================================

    立即关闭数据库

    SQL> shutdown immediate;


    启动实例并加载数据库,但不打开

    SQL> startup mount


    更改数据库为归档模式

    SQL> alter database archivelog;


    打开数据库

    SQL> alter database open;


    启用自动归档

    SQL> alter system archive log start;


    查看归档状态

    SQL> archive log list;


    全库恢复要在mount状态

    表恢复可以在open状态


    =========================================

    [oracle@sq admin]$ rman target /

    RMAN> list backup; (查看备份列表)


    (备份表空间)

    RMAN> backup tablespace users;

    RMAN> sql "alter system flush buffer_cache";(rman用sql,清空缓存)


    [oracle@sq orcl]$ rm -rf users01.dbf(删除数据文件)

    SQL> startup force

    ORA-01110: data file 4: '/u01/app/oracle/oradata/orcl/users01.dbf'

    (报错4号文件 没有找到)


    SQL> !

    [oracle@sq ~]$ rman target /

    RMAN> restore datafile 4;(恢复文件)


    RMAN> sql "alter database datafile 4 online";(数据文件在线)

    SQL> startup force(正常运行)


    RAMAN为什么能找到恢复的路径,因为RAMN在备份数据文件的同时也备份了控制文件,通过控制文件的路径来恢复数据文件。一定要记住当数据文件有更新要重新备份。


    备份位置

    [oracle@sq123 dbs]$ cd /oracle/app/flash_recovery_area/TEST/backupset/

    (Rman自动备份控制文件和参数文件

    如果不配置,备份普通表空间的时候就不自动备份控制文件和参数文件)

    =======================================

    全库备份

    1.

    RMAN> backup database;

    RMAN> list backup; 


    2.

    [oracle@sq123 ~]$ cd /oracle/app/oradata/TEST/

    [oracle@sq123 TEST]$ rm -rf *


    3.SQL> startup force (找不到控制文件)


    4.[oracle@sq123 TEST]$ cd /oracle/app/flash_recovery_area/TEST/backupset/2012_03_12/

    (找到o1_mf_ncsnf_TAG20120312T004722_7osowxyj_.bkp)

     

    5.恢复控制文件

    Rman自动备份控制文件和参数文件


    RMAN> restore controlfile from '/oracle/app/flash_recovery_area/TEST/backupset/2012_03_12/o1_mf_ncsnf_TAG20120312T004722_7osowxyj_.bkp';


    RMAN> alter database mount;(数据库可以mount)


    6.[oracle@sq123 TEST]$ ls (控制文件恢复回来了)


    7.恢复数据文件

    RMAN> restore database;

    [oracle@sq123 TEST]$ ls(数据文件恢复回来了)


    8.RMAN> alter database open resetlogs;(报错)

      RMAN> recover database;(报错)

      RMAN> alter database open resetlogs; (可以打开数据库)

    (restore 是还原,文件级的恢复。就是物理文件还原

      recover 是恢复,数据级的恢复。逻辑上恢复)


    SQL> startup force(已经能够重启 恢复成功)

    [oracle@sq123 TEST]$ ls (日志文件也有了)


    ============================================================

    多通道全库备份(提高效率)


    run{

    allocate channel c1 type disk format '/home/oracle/backup1/%u';

    allocate channel c2 type disk format '/home/oracle/backup2/%u';

    sql 'alter system archive log current';

    backup database plus archivelog delete all input;

    sql 'alter system archive log current';

    }





    ((

    %c copy ID

    %p backup piece ID

    %s backup set ID

    %e log sequence

    %h log thread ID

    %d database name

    %n database name(x填充到8个字符)

    %I DBID

    %f file ID

    %F DBID, day, month, year, and sequencer的复合

    %N tablespace name

    %t timestamp

    %M mh mm格式

    %Y year yyyy格式

    ))

    =============================================================

    RMAN 增量备份


    1。

    RMAN> backup incremental level 0 database format='/home/oracle/db_bak/%u';

    (level=0 0级别为全库备份  %u生成唯一一个文件名)

    (增量备份第一备份要为全库备份)


    2.1SQL> create table c1 as select * from dba_objects;

       (产生4w多行记录 占用的块较多)



    (一级增量备份)

    (增量备份级别:

     1.differential 差异备份 认同同级备份.

     2.cumulative 累积增量备份 不认同同级备份 优点:恢复时不需要读取过多的备份集)



    2.2 差异备份 

    RMAN> backup INCREMENTAL LEVEL 1 DATABASE format='/home/oracle/db_bak/%u';



    3.1

    SQL> create table c2 (id int);

    SQL> insert into c2 values(123);

    SQL> commit;

    (产生的数据较少)


    3.2  累积增量备份

    RMAN> backup INCREMENTAL LEVEL 1 CUMULATIVE DATABASE format='/home/oracle/db_bak/%u';


    3.3 

    验证

    比较两次产生的备份片, 3.2步骤 备份片大于 3.1步骤地大小 

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

    脚本备份

    [oracle@sq123 ~]$ vi fullbackup.sh

    #!/bin/bash

    source ~/.bash_profile

    $ORACLE_HOME/bin/rman target / <<EOF

    run {

    allocate channel C1 type disk FORMAT '/home/oracle/db_bak/%u';

    allocate channel C2 type disk FORMAT '/home/oracle/db_bak/%u';

    backup incremental level=0 database format='/home/oracle/db_bak/%u';

    }

    exit;

    EOF



    [oracle@sq123 ~]$ chmod 777 fullbackup.sh 

    [oracle@sq123 ~]$ ./fullbackup.sh 执行


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

    RMAN> list backup;

    RMAN> delete backupset 1; 删除一个


    RMAN> delete backup;

    YES

    (如果备份集中原数据文件被删除 delete检测时出错

    需要先执行RMAN> CROSSCHECK backup; 检测备份)


    检查备份文件是否有效

    RMAN> validate backupset 1;


    删除陈旧的备份(超出冗余保留时间)

       delete obsolete;

    报告陈旧的备份文件

       report  obsolete;

    报告需要备份的文件

       report  need backup;


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

    rman catalog

    采用RMAN方式进行备份,默认是采用NOCATALOG方式的。在这种情况下,LIST出来的备份信息写到了CONTROL FILE里,如果控制文件损坏,如果只能启动到NOMOUNT状态,那么备份信息就不可用。ORACLE建议我们采用CATALOG 方式,将控制文件的LIST信息同步到CATALOG DB中,这样当控制文件有问题时,我们也可以借用于CATALOG DB。


    目录数据库:8.18

    目标数据库:8.111

    环境准备:

    两端开启归档模式

    两端开启监听

    两端传输

    DB111 =

      (DESCRIPTION =

        (ADDRESS_LIST =

          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.8.111)(PORT = 1521))

        )

        (CONNECT_DATA =

          (SERVICE_NAME = TEST)

        )

      )


    DB18 =

      (DESCRIPTION =

        (ADDRESS_LIST =

          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.8.18)(PORT = 1521))

        )

        (CONNECT_DATA =

          (SERVICE_NAME = TEST)

        )

      )







    1.在目录数据库中创建恢复目录所用表空间   

    SQL> create tablespace rmants datafile '/home/oracle/rmants.dbf' size 100m;


    2.在目录数据库中创建RMAN   用户并授权   

    SQL> create user rman identified by rman default tablespace rmants quota unlimited on rmants;


    SQL> grant recovery_catalog_owner to rman;

    SQL> grant resource to rman;

    SQL> grant connect to rman;



    3.在目录数据库中创建恢复目录 

    [oracle@oracle18 ~]$ rman catalog rman/rman

    RMAN> create catalog tablespace rmants;


    4.注册目标数据库到恢复目录

    [oracle@oracle18 ~]$ rman target sys/123456@db111  

    RMAN> connect catalog rman/rman@db18

    RMAN> register database;



    5.下面就可以使用RMAN了 

    备份些东西

    删除目标库控制文件

    修复控制文件


    [oracle@oracle18 ~]$ rman target sys/123456@db111  

    RMAN> connect catalog rman/rman@db18

    RMAN> list backup;

    还能看到备份信息





    ===========================================================

    set controlfile autobackup format for device type disk to '/home/oracle/cf_%F';


    RMAN> restore controlfile from autobackup; (前提控制文件有效状态)


    查看dbid


    select dbid from v$database
















    转载于:https://blog.51cto.com/chenjisong/1737392

    展开全文
  • RMAN备份脚本执行失败,报错如下: RMAN-03002: failure of delete command at 12/30/2013 13:51:36 RMAN-06091: no channel allocated for maintenance (of an appropriate type) 或者是: RMAN-03002: failure of ...

    RMAN备份脚本执行失败,报错如下:
    RMAN-03002: failure of delete command at 12/30/2013 13:51:36
    RMAN-06091: no channel allocated for maintenance (of an appropriate type)

    或者是:
    RMAN-03002: failure of crosscheck command at 12/30/2013 13:51:36
    RMAN-06091: no channel allocated for maintenance (of an appropriate type)

    查看错误代码解释:
    [oracle@rhel75 ~]$ oerr rman 06091
    6091, 1, “no channel allocated for maintenance (of an appropriate type)”
    // *Cause: A command was entered that requires a maintenance channel, and no
    // maintenance channel is allocated, or none of the appropriate type.
    // *Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup
    // pieces, or using the CROSSCHECK or DELETE EXPIRED commands.
    // Proxy copies require a non-DISK channel.

    查看原脚本写法:

    RUN {
    ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
    ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
    send 'NB_ORA_POLICY=XXX, NB_ORA_SERV=XXX,NB_ORA_CLIENT=XXX';
    BACKUP
       filesperset 20
       FORMAT 'al_%s_%p_%t'
       ARCHIVELOG ALL;
       delete noprompt archivelog all completed before 'sysdate-3';
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
    send 'NB_ORA_POLICY=XXX, NB_ORA_SERV=XXX,NB_ORA_CLIENT=XXX';
    BACKUP
        # recommended format
        FORMAT 'cntrl_%s_%p_%t'
        CURRENT CONTROLFILE;
    RELEASE CHANNEL ch00;
    }
    

    看报错代码描述,删除备份片或执行crosscheck或delete expired时需要分配维护通道,则改写脚本如下:

    RUN {
    ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
    ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
    send 'NB_ORA_POLICY=XXX, NB_ORA_SERV=XXX,NB_ORA_CLIENT=XXX';
    BACKUP
        $BACKUP_TYPE
        SKIP INACCESSIBLE
        TAG hot_db_bk_level0
        FILESPERSET 5
        FORMAT 'bk_%s_%p_%t'
        DATABASE;
        sql 'alter system archive log current';
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    ALLOCATE CHANNEL ch00  TYPE 'SBT_TAPE';
    ALLOCATE CHANNEL ch01  TYPE 'SBT_TAPE';
    send 'NB_ORA_POLICY=XXX, NB_ORA_SERV=XXX,NB_ORA_CLIENT=XXX';
    BACKUP
       filesperset 20
       FORMAT 'al_%s_%p_%t'
       ARCHIVELOG ALL;
       #crosscheck archivelog all;
       #delete noprompt archivelog all completed before 'sysdate-3';
    
    RELEASE CHANNEL ch00;
    RELEASE CHANNEL ch01;
    
    ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
    send 'NB_ORA_POLICY=XXX, NB_ORA_SERV=XXX,NB_ORA_CLIENT=XXX';
    BACKUP
        FORMAT 'cntrl_%s_%p_%t'
        CURRENT CONTROLFILE;
    RELEASE CHANNEL ch00;
    }
    
    allocate channel for maintenance device type disk;
    crosscheck archivelog all;
    delete noprompt archivelog all completed before 'sysdate-3';
    RELEASE CHANNEL;
    
    

    ===================
    关于ALLOCATE CHANNEL FOR MAINTENANCE可见官方文档:
    https://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta005.htm#RCMRF103

    Purpose:
    Use the ALLOCATE CHANNEL FOR MAINTENANCE command to manually allocate a channel in preparation for issuing a CHANGE, DELETE, or CROSSCHECK command. You can use the RELEASE CHANNEL command to unallocate the channel.

    Note:
    If you CONFIGURE at least one channel for each device type in your configuration, then you do not need to use ALLOCATE CHANNEL FOR MAINTENANCE. It is recommended that you use configured channels instead of maintenance channels. You can use configured channels for all RMAN I/O to the specified device, not just the maintenance tasks supported by maintenance channels. The configured channels persist across RMAN sessions.

    Prerequisites:
    Execute this command only at the RMAN prompt, not within a RUN block. The target instance must be started. You cannot allocate a maintenance channel to a shared session.

    Usage Notes

    As a rule, you should allocate one maintenance channel for each device. Manually allocated channels and automatic channels are never mixed. In general, you should allocate multiple maintenance channels for a single job only in these situations:

    To enable crosschecking or deletion of all backup pieces or proxy copies, both on disk and tape, with a single command (see Example 2-11)

    To make crosschecking and deleting work correctly in an Oracle RAC configuration in which each backup piece or proxy copy exists only on one node (see Example 2-12)

    RMAN uses the following convention for naming of maintenance channels: ORA_MAINT_devicetype_n, where devicetype refers to DISK or sbt and n refers to the channel number. For example, RMAN uses these names for two manually allocated disk channels:

    ORA_MAINT_DISK_1
    ORA_MAINT_DISK_2

    总结如下:
    (1)用CHANGE, DELETE, or CROSSCHECK命令时需要使用它。
    (2)如果用CONFIGURE命令为每个设备类型分配至少一个通道,则不需要使用ALLOCATE CHANNEL FOR MAINTENANCE,而且建议使用CONFIGURE而不是维护通道。
    (3)这种分配维护通道的命令需要放到run{}外面
    (4)通常应为每个设备分配一个维护通道,手动分配通道和自动分配通道永远不会混合,只有在以下情况下才需要分配多个通道:
    To enable crosschecking or deletion of all backup pieces or proxy copies, both on disk and tape, with a single command (see Example 2-11)

    To make crosschecking and deleting work correctly in an Oracle RAC configuration in which each backup piece or proxy copy exists only on one node (see Example 2-12)
    (5)维护通道命令规则: ORA_MAINT_devicetype_n
    (6)以上报错case中,type应该是disk,而不是sbt,因为要删除的是本地磁盘上的归档文件,而不是带库上的归档文件。

    展开全文
  • 灾备库通过源库的全备archive文件做完全库恢复后,拿到源库的archive日志在灾备库执行recovery恢复时报错:RMAN>recoverdatabaseuntilsequence5873; Startingrecoverat12-OCT-18 usingchannelORA_DISK_1 ...

    灾备库通过源库的全备archive文件做完全库恢复后,拿到源库的archive日志在灾备库执行recovery恢复时报错:

    RMAN> recover database until sequence 5873;
    Starting recover at 12-OCT-18
    using channel ORA_DISK_1
    starting media recovery
    Oracle Error: 
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oraciisdb/ciisdb/system01.dbf'
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 10/12/2018 15:29:39
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of archived log for thread 1 with sequence 5872 and starting SCN of 12769932698065 found to restore

    图片.png


    archive日志列表和路径:

    图片.png

    图片.png


    问题解决:

    通过catalog start with将最新的备份集以及归档日志文件列表导入到控制文中。

    RMAN> catalog start with '/oraciisarch/ciisdb/';     
    using target database control file instead of recovery catalog
    searching for all files that match the pattern /oraciisarch/ciisdb/
    List of Files Unknown to the Database
    =====================================
    File Name: /oraciisarch/ciisdb/1_5876_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5875_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5871_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5872_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5874_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5879_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5877_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5873_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5870_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5878_923330419.dbf
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /oraciisarch/ciisdb/1_5876_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5875_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5871_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5872_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5874_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5879_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5877_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5873_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5870_923330419.dbf
    File Name: /oraciisarch/ciisdb/1_5878_923330419.dbf

    图片.png

    该命令作用为让/oraciisarch/ciisdb整个目录被rman识别。


    再次执行恢复操作:

    RMAN>   recover database until sequence 5873;
    Starting recover at 12-OCT-18
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=699 device type=DISK
    starting media recovery
    archived log for thread 1 with sequence 5872 is already on disk as file /oraciisarch/ciisdb/1_5872_923330419.dbf
    archived log file name=/oraciisarch/ciisdb/1_5872_923330419.dbf thread=1 sequence=5872
    Oracle Error: 
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oraciisdb/ciisdb/system01.dbf'
    media recovery complete, elapsed time: 00:00:03
    Finished recover at 12-OCT-18

    图片.png

    spacer.gif图片.png

    恢复成功。



    转载于:https://blog.51cto.com/3241766/2299369

    展开全文
  • 教程名称:实战Oracle RMAN之数据库备份与恢复视频教程课程目录:【】[实战Oracle.RMAN之数据库备份和恢复系列]RMAN_1【】[实战Oracle.RMAN之数据库备份和恢复系列]RMAN_10【】[实战Oracle.RMAN之数据库备份和恢复...
  • 教程名称:傻瓜式实战Oracle RMAN数据库备份和恢复视频课程目录:【】数据库备份和恢复系列].ITBOBA_RMAN_1【】数据库备份和恢复系列].ITBOBA_RMAN_10【】数据库备份和恢复系列].ITBOBA_RMAN_2【】数据库备份和恢复...
  • rmanRMAN debug on

    2019-09-12 09:11:32
    DEBUG选项用于:–查看生成的PL/SQL–准确判断RMAN命令在何处挂起或出错DEBUG选项是在RMAN提示符下或者在run块内指定的。DEBUG选项会创建大量输出,因此要将输出重定向到跟踪文件:$rmantarget/catalogrman/...
  • RMAN配置

    2019-10-01 14:39:13
    $ rman target / 或rman target sys/password@orcl RMAN> show all;查看系统里所有备份的配置 RMAN> CONFIGURE CONTROLFILE AUTOBACKUP On;打开控制文件自动备份 RMAN> CONFIGURE CONTROLFILE ...
  • RMAN 恢复的时候出错RMAN-06091 RMAN-03023: executing command: SET DBID RMAN> 2> 3> 4> 5> 6> 7> 8> 9> RMAN-08030: allocated channel: c1 RMAN-08500: channel c1: SID=10 device...
  • RMAN备份

    2019-09-19 05:51:39
    1、切换服务器归档模式,如果已经是归档模式可跳过此步:%sqlplus/nolog(启动sqlplus)SQL>conn/assysdba(以DBA身份连接数据库)SQL>shutdownimmediate;(立即关闭数据库)SQL>...
  • RMAN通道

    万次阅读 2017-02-06 14:46:52
    RMAN系统中,它自身有一套参数用于整个RMAN会话中,例如前面提到的SHOW ALL 命令。通过该命令可以查看RMAN的一些系统参数的配置信息。数据库管理员可以使用CONFIGURE 命令对RMAN进行配置,也可以在CONFIGURE 命令...
  • 在进行physical standby搭建过程中,使用rman恢复灾备库,出现报错RMAN-03002 RMAN-06026 RMAN-06100,无法正常恢复数据库。 错误信息: RMAN> RMAN-03090: Starting restore at 2020-07-31 09:40:32 RMAN-06009...
  • RMAN-05501 RMAN-05001

    2019-04-29 09:23:32
    RMAN-05501 RMAN-05001
  • RMAN笔记

    2019-05-13 17:29:00
    Rman常用命令 Preview选项 1) 显示用于还原system表空间数据文件的备份文件 RMAN> restore datafile 2 preview; 2) 显示用于还原特定的表空间的备份文件; RMAN> restore tablespace users preview; 3...
  • 停止RMAN备份

    2020-11-03 20:56:12
    数据库主机在检修窗口需要物理迁移,此时RMAN备份还在进行,需要手动停止。 1、杀掉定时备份脚本进程 [oracle@yxjca]:/home/oracle>ps -ef|grep rman oracle 18743968 19333902 0 00:00:00 - 0:22 rman ...
  • Oracle RMAN

    2019-05-03 01:28:20
    --RMAN --某个时间段备份失败的记录 SELECT * FROM V$RMAN_STATUS WHERE START_TIME >= TO_DATE(&START_TIME, 'YYYY-MM-DD HH24:MI:SS') AND END_TIME <= TO_DATE(&END_TIME, 'YYYY-MM-DD HH24:MI:...

空空如也

1 2 3 4 5 ... 20
收藏数 19,102
精华内容 7,640
关键字:

RMan