我是靠谱客的博主 大方乌龟,最近开发中收集的这篇文章主要介绍nbu备份oracle中途停止,NBU备份问题 - Oracle数据库管理 - ITPUB论坛-中国专业的IT技术社区...,觉得挺不错的,现在分享给大家,希望可以做个参考。

概述

各位大神问题下,我有个脚本是NBU(备RAC),先备全库(1节点)加控制文件,alter system archive log current,再备归档。但是每次备归档的时候只是偶尔才会成功,每次都报没有这个归档日志,但是我第二天来的时候查看这个归档的生成时间要比他备份的时间早,下面是备份日志和归档生成的时间。

Script /usr/openv/scripts/dbfull.sh

==== ended in error on Wed Nov 26 17:10:36 CST 2014 ====

Script /usr/openv/scripts/dbfull.sh

==== started on Wed Nov 26 17:11:54 CST 2014 ====

RMAN: /u01/app/oracle/product/10.2.0/db_1/bin/rman

ORACLE_SID: hcmsdb1

ORACLE_USER: oracle

ORACLE_HOME: /u01/app/oracle/product/10.2.0/db_1

NB_ORA_FULL: 1

NB_ORA_INCR: 0

NB_ORA_CINC: 0

NB_ORA_SERV: backupserver

NB_ORA_POLICY: zjdb01_OracleRac_database

Full backup requested

Recovery Manager: Release 10.2.0.4.0 - Production on Wed Nov 26 17:11:54 2014

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

connected to target database: HCMSDB (DBID=3581989259)

using target database control file instead of recovery catalog

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39>

allocated channel: ch00

channel ch00: sid=956 instance=hcmsdb1 devtype=SBT_TAPE

channel ch00: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

allocated channel: ch01

channel ch01: sid=909 instance=hcmsdb1 devtype=SBT_TAPE

channel ch01: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

sent command to channel: ch00

sent command to channel: ch01

Starting backup at 26-NOV-14

channel ch00: starting incremental level 0 datafile backupset

channel ch00: specifying datafile(s) in backupset

input datafile fno=00001 name=+DATA_DG/hcmsdb/datafile/system.259.737393425

input datafile fno=00007 name=+DATA_DG/hcmsdb/datafile/users.271.829496535

input datafile fno=00004 name=+DATA_DG/hcmsdb/datafile/undotbs2.263.737393451

input datafile fno=00008 name=+DATA_DG/hcmsdb/datafile/system.272.858331969

channel ch00: starting piece 1 at 26-NOV-14

channel ch01: starting incremental level 0 datafile backupset

channel ch01: specifying datafile(s) in backupset

input datafile fno=00006 name=+DATA_DG/hcmsdb/datafile/system.270.829496401

input datafile fno=00005 name=+DATA_DG/hcmsdb/datafile/users.264.737393457

input datafile fno=00003 name=+DATA_DG/hcmsdb/datafile/sysaux.261.737393445

input datafile fno=00002 name=+DATA_DG/hcmsdb/datafile/undotbs1.260.737393441

channel ch01: starting piece 1 at 26-NOV-14

channel ch00: finished piece 1 at 26-NOV-14

piece handle=bk_18740_1_864666716 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch00: backup set complete, elapsed time: 00:15:45

channel ch00: starting incremental level 0 datafile backupset

channel ch00: specifying datafile(s) in backupset

including current control file in backupset

channel ch00: starting piece 1 at 26-NOV-14

channel ch00: finished piece 1 at 26-NOV-14

piece handle=bk_18742_1_864667661 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch00: backup set complete, elapsed time: 00:02:16

channel ch00: starting incremental level 0 datafile backupset

channel ch00: specifying datafile(s) in backupset

including current SPFILE in backupset

channel ch00: starting piece 1 at 26-NOV-14

channel ch00: finished piece 1 at 26-NOV-14

piece handle=bk_18743_1_864667797 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch00: backup set complete, elapsed time: 00:01:56

channel ch01: finished piece 1 at 26-NOV-14

piece handle=bk_18741_1_864666716 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch01: backup set complete, elapsed time: 04:38:45

Finished backup at 26-NOV-14

sql statement: alter system archive log current

released channel: ch00

released channel: ch01

allocated channel: ch00

channel ch00: sid=956 instance=hcmsdb1 devtype=SBT_TAPE

channel ch00: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

allocated channel: ch01

channel ch01: sid=909 instance=hcmsdb1 devtype=SBT_TAPE

channel ch01: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

Starting backup at 26-NOV-14

current log archived

released channel: ch00

released channel: ch01

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 11/26/2014 21:50:51

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

ORA-19625: error identifying file /arch/2_62737_737393419.dbf

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

RMAN> RMAN>

Recovery Manager complete.

Script /usr/openv/scripts/dbfull.sh

==== ended in error on Wed Nov 26 21:50:57 CST 2014 ====

Script /usr/openv/scripts/dbfull.sh

==== started on Wed Nov 26 22:01:00 CST 2014 ====

RMAN: /u01/app/oracle/product/10.2.0/db_1/bin/rman

ORACLE_SID: hcmsdb1

ORACLE_USER: oracle

ORACLE_HOME: /u01/app/oracle/product/10.2.0/db_1

NB_ORA_FULL: 1

NB_ORA_INCR: 0

NB_ORA_CINC: 0

NB_ORA_SERV: backupserver

NB_ORA_POLICY: zjdb01_OracleRac_database

Full backup requested

Recovery Manager: Release 10.2.0.4.0 - Production on Wed Nov 26 22:01:00 2014

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

connected to target database: HCMSDB (DBID=3581989259)

using target database control file instead of recovery catalog

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39>

allocated channel: ch00

channel ch00: sid=955 instance=XXXXX devtype=SBT_TAPE

channel ch00: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

allocated channel: ch01

channel ch01: sid=882 instance=XXXXX devtype=SBT_TAPE

channel ch01: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

sent command to channel: ch00

sent command to channel: ch01

Starting backup at 26-NOV-14

channel ch00: starting incremental level 0 datafile backupset

channel ch00: specifying datafile(s) in backupset

input datafile fno=00001 name=+XXXXX /XXXXX /XXXXX /system.259.737393425

input datafile fno=00007 name=+XXXXX /XXXXX /XXXXX /users.271.829496535

input datafile fno=00004 name=+XXXXX /XXXXX /XXXXX /datafile/undotbs2.263.737393451

input datafile fno=00008 name=+XXXXX /XXXXX /XXXXX /system.272.858331969

channel ch00: starting piece 1 at 26-NOV-14

channel ch01: starting incremental level 0 datafile backupset

channel ch01: specifying datafile(s) in backupset

input datafile fno=00006 name=+XXXXX /XXXXX /XXXXX /system.270.829496401

input datafile fno=00005 name=+XXXXX /XXXXX /XXXXX /users.264.737393457

input datafile fno=00003 name=+XXXXX /XXXXX /XXXXX /sysaux.261.737393445

input datafile fno=00002 name=+XXXXX /XXXXX /XXXXX /undotbs1.260.737393441

channel ch01: starting piece 1 at 26-NOV-14

channel ch01: finished piece 1 at 26-NOV-14

piece handle=bk_18750_1_864684083 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch01: backup set complete, elapsed time: 00:26:35

channel ch01: starting incremental level 0 datafile backupset

channel ch01: specifying datafile(s) in backupset

including current control file in backupset

channel ch01: starting piece 1 at 26-NOV-14

channel ch01: finished piece 1 at 26-NOV-14

piece handle=bk_18751_1_864685678 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch01: backup set complete, elapsed time: 00:10:36

channel ch01: starting incremental level 0 datafile backupset

channel ch01: specifying datafile(s) in backupset

including current SPFILE in backupset

channel ch01: starting piece 1 at 26-NOV-14

channel ch01: finished piece 1 at 26-NOV-14

piece handle=bk_18752_1_864686314 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch01: backup set complete, elapsed time: 00:08:46

channel ch00: finished piece 1 at 27-NOV-14

piece handle=bk_18749_1_864684083 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0

channel ch00: backup set complete, elapsed time: 02:17:33

Finished backup at 27-NOV-14

sql statement: alter system archive log current

released channel: ch00

released channel: ch01

allocated channel: ch00

channel ch00: sid=955 instance=hcmsdb1 devtype=SBT_TAPE

channel ch00: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

allocated channel: ch01

channel ch01: sid=882 instance=hcmsdb1 devtype=SBT_TAPE

channel ch01: Veritas NetBackup for Oracle - Release 7.1 (2011020316)

Starting backup at 27-NOV-14

current log archived

released channel: ch00

released channel: ch01

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 11/27/2014 00:19:06

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

ORA-19625: error identifying file /arch/2_62737_737393419.dbf

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

RMAN> RMAN>

Recovery Manager complete.

Script /usr/openv/scripts/dbfull.sh

==== ended in error on Thu Nov 27 00:19:07 CST 2014 ====

这是这个找不到的归档生成的时间:Nov 26 21:40 2_62737_737393419.dbf

还有他为什么会备份两次?

第一个库是执行的一个单个的备归档的脚本,然后再执行一个备全库的脚本(这里又备了一次归档)

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

这是第二个库的报错。这个库是先备的归档日志。

Starting backup at 2014-11-26 20:46:11

released channel: ch00

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 11/26/2014 20:46:11

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

ORA-19625: error identifying file

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Starting backup at 2014-11-26 22:40:57

released channel: ch01

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 11/26/2014 22:40:57

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

ORA-19625: error identifying file /arch2/2_3226_768595054.dbf

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

第一个归档日志确实不在(请问没有删除的情况下为什么会不在?)

第二个归档日志生成的时间(有但是去在备份的时候报没有):26 20:51 2_3226_768595054.dbf

第二个库也是执行的一个单个的备归档的脚本,然后再执行一个备全库的脚本(这里又备了一次归档)。但是在备归档的日志也没有找到/arch1/1_5221_768595054.dbf这个归档的信息。

但是有的时候这两个库就不会报这样的错,就直接备份成功了。

最后

以上就是大方乌龟为你收集整理的nbu备份oracle中途停止,NBU备份问题 - Oracle数据库管理 - ITPUB论坛-中国专业的IT技术社区...的全部内容,希望文章能够帮你解决nbu备份oracle中途停止,NBU备份问题 - Oracle数据库管理 - ITPUB论坛-中国专业的IT技术社区...所遇到的程序开发问题。

如果觉得靠谱客网站的内容还不错,欢迎将靠谱客网站推荐给程序员好友。

本图文内容来源于网友提供,作为学习参考使用,或来自网络收集整理,版权属于原作者所有。
点赞(46)

评论列表共有 0 条评论

立即
投稿
返回
顶部