Heim >Datenbank >MySQL-Tutorial >RMAN备份中常见的问题

RMAN备份中常见的问题

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB
WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOriginal
2016-06-07 17:25:531102Durchsuche

1:ORA-01031insufficient privileges gpasswd -d Oracle dba --将oracle移除出dba组 查看oracle属性 uid=500(oracle) gid=500(

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

linux

Stellungnahme:
Der Inhalt dieses Artikels wird freiwillig von Internetnutzern beigesteuert und das Urheberrecht liegt beim ursprünglichen Autor. Diese Website übernimmt keine entsprechende rechtliche Verantwortung. Wenn Sie Inhalte finden, bei denen der Verdacht eines Plagiats oder einer Rechtsverletzung besteht, wenden Sie sich bitte an admin@php.cn