Rman备份中常见的问题

1:ORA-01031insufficient privileges

gpasswd  -d oracle dba --将oracle移除出dba组

查看oracle属性

uid=500(oracle) gid=500(oinstall) groups=500(oinstall)

[oracle@oracle10g ~]$ rman target  /
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jan 21 14:07:11 2013
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges

解决:

usermod  -d /home/oracle/ -G dba  oracle --将oracle用户加入dba组

[root@oracle10g ~]# usermod  -d /home/oracle/ -G dba oracle
[root@oracle10g ~]# su - oracle
[oracle@oracle10g ~]$ rman target  /
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jan 21 14:08:34 2013
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
connected to target database: PURPLE (DBID=2860377939)


2:Handling Disk Space Issues

ORA-19504: failed to create file "/oraback/BRDSTN/bsi2phe7_1_1"
ORA-27004: unable to write the header block of file

解决:

• Change the backup location to an area that has more space.
•Add disk space to the backup location.
•If using a flash recovery area (FRA), then either move the FRA or increase its size.
• Change the retention policy to fewer days or fewer backups.
•Delete old backup files that are no longer required

alter system set db_recovery_file_dest='/oraback02/FRA';

alter system set db_recovery_file_dest_size=100g;


3:RMAN-06059 Error

RMAN> backup database plus archivelog;
Starting backup at 21-JAN-13
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=141 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 01/21/2013 14:14:52
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /oracle/archivelog/1_1_805026198.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

解决:

RMAN> crosscheck archivelog all;


4:Terminating RMAN Processes

•Pre ss Ctrl+C from the RMAN interface. This approach, of course, works only if per-formed from the online session responsible for the process you want to terminate.
•Manually kill the OS process.

kill -9 4123 
•Terminate the server session corresponding to an RMAN channel using an alter  system kill SQL statement

SQL>SELECT s.sid ,s.serial# ,p.spid ,s.client_info FROM v$process p, v$session s WHERE p.addr = s.paddr AND client_info LIKE '%rman%';
SQL>alter system kill session '158,122';


5:Diagnosing NLS Character Set Issues

ORA-12705: Cannot access NLS data files or invalid environment specified

• There’s a mismatch between the NLS character set of the client and that of the database server.

•You have an NLS-related operating system variable that has been set incorrectly.


SQL> conn /as sysdba
Connected.
SQL> select value from v$nls_parameters where parameter = 'NLS_CHARACTERSET';

VALUE
----------------------------------------------------------------
ZHS16GBK


6:Logging RMAN Output--记录rman日志

rman target / log=rman_output.log--操作系统级别

RMAN> spool log to rman_output.log --Rman命令行
RMAN> set echo on
RMAN> backup database;
RMAN> spool log off;


7:Viewing RMAN Command History

SQL>select sid, recid, output from v$rman_output   order by recid


8:Enabling RMAN’s Debug Output

--OS

rman target / debug=all log=rman_output.log

rman target / debug=io --

--Fr om Within RMAN

RMAN> spool log to rman_output.log
RMAN> debug on
RMAN> set echo on
RMAN> backup database;
RMAN> debug off
RMAN> spool log off

--W hen Configuring a Channel

RMAN> configure channel device type disk debug=5 trace=5;


9:Enabling Granular Time Reporting

export  NLS_DATE_FORMAT 'dd-mon-yyyy hh24:mi:ss'

 NLS_DATE_FORMAT 'dd-mon-yyyy hh24:mi:ss'



10:RMAN-03009  ORA-19804

输入数据文件: 文件号=00050 名称=+ORADATA/purple/datafile/undotbs202.dbf
输入数据文件: 文件号=00051 名称=+ORADATA/purple/datafile/user01.dbf
输入数据文件: 文件号=00052 名称=+ORADATA/purple/datafile/users02.dbf
输入数据文件: 文件号=00001 名称=+ORADATA/purple/datafile/system.256.762094681
输入数据文件: 文件号=00002 名称=+ORADATA/purple/datafile/sysaux.257.762094681
输入数据文件: 文件号=00046 名称=+ORADATA/purple/datafile/system02.dbf
输入数据文件: 文件号=00003 名称=+ORADATA/purple/datafile/undotbs1.258.762094683
输入数据文件: 文件号=00005 名称=+ORADATA/purple/datafile/undotbs2.267.762094901
输入数据文件: 文件号=00004 名称=+ORADATA/purple/datafile/users.259.762094683
通道4 正在启动段 1与23-1月-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: backup 命令(t4 通道上,在01/23/2013 17:18:42上)失败
ORA-19809: 超出了恢复文件数的限制
ORA-19804: 无法回收53477376字节磁盘空间(从4196401152限制中)

你可能感兴趣的:(读书笔记,Oracle,Backup,&,Recovery)