今天在进行例检的时候,发现dp在凌晨一点多的时候备份归档日志发生了一些错误,具体的rman报错为

OB2BAR application on "XXXX02" successfully started.

ob2rman.exe started with arguments:
-backup -full

Recovery Manager: Release 9.2.0.6.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

RMAN>
connected to target database: XXXX (DBID=169290886)

RMAN>
connected to recovery catalog database

RMAN>
RMAN> run {
2> allocate channel 'dev_0' type 'sbt_tape'
3> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=XXXX2,OB2BARLIST=XXXX2_arch,OB2BARHOSTNAME=fj_db02)';
4> allocate channel 'dev_1' type 'sbt_tape'
5> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=XXXX2,OB2BARLIST=XXXX2_arch,OB2BARHOSTNAME=fj_db02)';
6> allocate channel 'dev_2' type 'sbt_tape'
7> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=XXXX2,OB2BARLIST=XXXX2_arch,OB2BARHOSTNAME=fj_db02)';
8> allocate channel 'dev_3' type 'sbt_tape'
9> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=XXXX2,OB2BARLIST=XXXX2_arch,OB2BARHOSTNAME=fj_db02)';
10> crosscheck archivelog from time 'sysdate-1' until time 'sysdate';
11> backup
12> format 'XXXX2_arch<XXXX2_%s:%t:%p>.dbf'
13> archivelog like '/archlog2/XXXX2%'
14> delete input;
15> }
allocated channel: dev_0
channel dev_0: sid=251 devtype=SBT_TAPE
channel dev_0: Data Protector A.05.50/330

allocated channel: dev_1
channel dev_1: sid=276 devtype=SBT_TAPE
channel dev_1: Data Protector A.05.50/330

allocated channel: dev_2
channel dev_2: sid=204 devtype=SBT_TAPE
channel dev_2: Data Protector A.05.50/330

allocated channel: dev_3
channel dev_3: sid=301 devtype=SBT_TAPE
channel dev_3: Data Protector A.05.50/330

validation succeeded for archived log
archive log filename=/archlog1/XXXX_1_21584.arc recid=38312 stamp=681012033
validation succeeded for archived log
archive log filename=/archlog1/XXXX_1_21585.arc recid=38315 stamp=681032056
Crosschecked 2 objects

Starting backup at 03/09/2009 [09:16:19]
released channel: dev_0
released channel: dev_1
released channel: dev_2
released channel: dev_3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/09/2009 09:16:19
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog

RMAN> **end-of-file**

RMAN>

Recovery Manager complete.

今天做设备验收,在查看cpu个数的时候,发现的一条命令 查看全文

最近在做巡检的时候发现,有台数据库服务器归档日志备份经常会出现一些问题,"specification does not match any archive log in the recovery catalog"，估计是arch目录中的文件名称和catalog中的文件名称有差异.所以此时需要手工执行crosscheck过程，之后Rman备份可以恢复正常.

如果你分析一个表，却导致SQL没有选择正确的执行计划，你就应该rollback你的操作。有统计信息的备份吗？

没有。之前没有用dbms_stats.export_table_stats进行备份。

你的版本是10g还是9i?

10g.

OK.你说不定还能survive。是用analyze分析的还是dbms_stats分析的？

analyze做的。

OK。这回完了。你survive不了了。 查看全文

最近升级脚本老是发现主外健的一些冲突,造成数据不完整,于是这里了一个脚本,怎么查那些数据造成主外健冲突 查看全文