Oracle

幫助解釋 Oracle RMAN 結果

  • March 31, 2016

我對 Oracle 非常陌生，必須在處於 NOARCHIVELOG 模式的 11g 數據庫上進行備份。下面是輸出。它聲稱備份失敗，但我有一個適當大小的文件，我希望在其中創建備份。

有人可以幫我解釋這個日誌嗎？

Recovery Manager: Release 11.2.0.3.0 - Production on Wed Mar 30 20:30:27 2016

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

connected to target database: HS (DBID=3540555849)


RMAN> RUN {

2> 

3> CONFIGURE COMPRESSION ALGORITHM 'HIGH';

4> 

5> show all;

6> 

7> shutdown immediate;

8> 

9> startup mount;

10> 

11> backup database;

12> 

13> alter database open;

14> 

15> }

16> 

17> LIST BACKUP SUMMARY ;

18> 

19> EXIT 

using target database control file instead of recovery catalog

new RMAN configuration parameters:

CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;

new RMAN configuration parameters are successfully stored


RMAN configuration parameters for database with db_unique_name HS are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\APP\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFHS.ORA'; # default
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area    4275781632 bytes
Fixed Size                     2262048 bytes
Variable Size               2818575328 bytes
Database Buffers            1442840576 bytes
Redo Buffers                  12103680 bytes
Starting backup at 30-MAR-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=395 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00005 name=D:\APP\ORACLE\ORADATA\HS\HS_F0_SVMC.CID
input datafile file number=00003 name=D:\APP\ORACLE\ORADATA\HS\UNDOTBS01.DBF
input datafile file number=00006 name=D:\APP\ORACLE\ORADATA\HS\AUDIT_DATA.DBF
input datafile file number=00002 name=D:\APP\ORACLE\ORADATA\HS\SYSAUX01.DBF
input datafile file number=00001 name=D:\APP\ORACLE\ORADATA\HS\SYSTEM01.DBF
input datafile file number=00007 name=D:\APP\ORACLE\ORADATA\HS\AUDIT_IDX.DBF
input datafile file number=00004 name=D:\APP\ORACLE\ORADATA\HS\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 30-MAR-16
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/30/2016 20:32:43
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 67108864 bytes disk space from 4322230272 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 30-MAR-16
channel ORA_DISK_1: finished piece 1 at 30-MAR-16
piece handle=D:\APP\ORACLE\FAST_RECOVERY_AREA\HS\BACKUPSET\2016_03_30\O1_MF_NCSNF_TAG20160330T203107_CHRW1F69_.BKP tag=TAG20160330T203107 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

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

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

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



RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/30/2016 20:32:43

ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim 67108864 bytes disk space from 4322230272 limit



Recovery Manager complete.

讓我們看看 Oracle 提供的oerr實用程序對您的錯誤有何看法。

[oracle@testsrv Desktop]$ oerr ora 19804

ORA-19804 無法從 %s 限制中回收 %s 字節磁碟空間

原因： Oracle 無法從 DB_RECOVERY_FILE_DEST_SIZE 限制中回收指定字節的磁碟空間。

**措施：**有五種可能的解決方案：

  1. 使用 RMAN 經常備份恢復區。

  2. 考慮更改 RMAN 保留策略。

  3. 考慮更改 RMAN 歸檔日誌刪除策略。

4）增加磁碟空間並增加DB_RECOVERY_FILE_DEST_SIZE。

  1. 使用 RMAN 從恢復區刪除文件。

ORA-19809 恢復文件超出限制

**原因：**超過了 DB_RECOVERY_FILE_DEST_SIZE 指定的恢復文件的限制。

**措施：**有五種可能的解決方案：

  1. 使用 RMAN 經常備份恢復區。

  2. 考慮更改 RMAN 保留策略。

  3. 考慮更改 RMAN 歸檔日誌刪除策略。

4）增加磁碟空間並增加DB_RECOVERY_FILE_DEST_SIZE。

  1. 使用 RMAN 從恢復區刪除文件。

將 RMAN 通道的db_recovery_file_dest_size大小或指定格式增加到不同的位置。

例子

SQL> conn / as sysdba
SQL> alter system set db_recovery_file_dest_size=30G;

您應該注意定義為快速恢復區域的磁碟的實際磁碟空間大小。如果您想將您的背部儲存在快閃記憶體恢復區以外的其他位置，那麼您可以分配通道，如下所示。

跑步
{
分配通道磁碟 1 設備類型磁碟格式 'E:\%U';
備份數據庫加存檔；
}

引用自：https://dba.stackexchange.com/questions/133890

相關問答

Oracle

Oracle 11.2.0.4：使用 RMAN 進行備份的基本資訊

  • January 20, 2017
檢視問答
Oracle

Oracle 11.2：基於全冷備份加expdp的備份恢復策略

  • January 19, 2017
檢視問答
Oracle

oracle rman 連接到未掛載狀態的數據庫

  • May 14, 2016
檢視問答
Oracle

Oracle TDE 加密表的 RMAN 解密備份

  • August 5, 2022
檢視問答
Oracle

每天恢復oracle數據庫12C增量備份

  • February 22, 2022
檢視問答
Oracle

RMAN - 忽略歸檔日誌刪除策略

  • September 22, 2021
檢視問答