- 論壇徽章:
- 0
|
本帖最后由 xc5sm 于 2012-06-20 10:14 編輯
Master:win 2008 R2 +NBU7.0
Client: Esxi4.0下的Linux 5.X+Oracle 10g+nbu7.0（rac）
備的是第一個節(jié)點。
之前幾個月一直能正常備份，前一段時間突然出現(xiàn)備份時，客戶端系統(tǒng)就會自動重啟，在客戶端測試rman備份到本地硬盤能正常備份。切換到備第二個節(jié)點rman備到存儲上也會自動重啟。
數(shù)據(jù)庫平時能正常使用。
hot_database_backup.sh.out 內(nèi)容如下：
Script /oracle/hot_database_backup.sh
Recovery Manager: Release 10.2.0.5.0 - Production on Sun May 6 22:23:10 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: orc (DBID=4178690871)
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> 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>
allocated channel: ch00
channel ch00: sid=123 instance=orc1 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
allocated channel: ch01
channel ch01: sid=144 instance=orc1 devtype=SBT_TAPE
channel ch01: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
Starting backup at 06-MAY-12
channel ch00: starting incremental level 1 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00012 name=/oradata/orc/ASIT/TBS_SHSJ.dbf
input datafile fno=00005 name=/oradata/orc/undotbs02.dbf
input datafile fno=00004 name=/oradata/orc/users01.dbf
channel ch00: starting piece 1 at 06-MAY-12
channel ch01: starting incremental level 1 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00013 name=/oradata/orc/ASIT/TBS_SHSJ_INDEX.dbf
input datafile fno=00008 name=/oradata/orc/ASIT/TBS_MH_BASE.dbf
input datafile fno=00010 name=/oradata/orc/ASIT/TBS_ASIT_BASE.dbf
input datafile fno=00003 name=/oradata/orc/sysaux01.dbf
input datafile fno=00002 name=/oradata/orc/undotbs01.dbf
channel ch01: starting piece 1 at 06-MAY-12
channel ch01: finished piece 1 at 06-MAY-12
piece handle=bk_1168_1_782605397 tag=HOT_DB_BK_LEVEL0 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch01: backup set complete, elapsed time: 00:01:25
channel ch01: starting incremental level 1 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00006 name=/oradata/orc/ASIT/TBS_MH_DATA.dbf
input datafile fno=00007 name=/oradata/orc/ASIT/TBS_MH_INDEX.dbf
input datafile fno=00009 name=/oradata/orc/ASIT/TBS_ASIT_DIC.dbf
input datafile fno=00011 name=/oradata/orc/ASIT/TBS_ASIT_INDEX.dbf
input datafile fno=00001 name=/oradata/orc/system01.dbf
channel ch01: starting piece 1 at 06-MAY-12
報800二個月還沒有分析出原因，系統(tǒng)重啟沒有core文件生成。但是用 echo "c" > /proc/sysrq-trigger故意讓系統(tǒng)崩潰會產(chǎn)生core文件。
oracle日志中有報錯信息，但好像不影響oracle使用，很多這樣的報錯信息：
Wed May 09 00:49:19 CST 2012
Error 2068 trapped in 2PC on transaction 9.39.52357. Cleaning up.
Error stack returned to user:
ORA-02068: following severe error from IIMSDBLINK
ORA-03135: connection lost contact
Wed May 09 00:49:40 CST 2012
Error 2068 trapped in 2PC on transaction 4.26.50770. Cleaning up.
Error stack returned to user:
ORA-02068: following severe error from LLSMSDBLINK
ORA-03135: connection lost contact
這個帖子發(fā)了二遍了，還請有經(jīng)驗的幫幫忙 |
|
免費注冊
發(fā)表于 2012-06-20 10:12
發(fā)表于 2012-06-20 16:13
