Categotry Archives: rman备份恢复

RMAN-06820 During Backup at dataguard

0

Posted on by

在数据库版本 11.2.0.4 dataguard上备份有以下的错误:

	Starting backup at 2016-03-15 14:12:35

	RMAN-06820: WARNING: failed to archive current log at primary database

	ORACLE error from target database: 

	ORA-17629: Cannot connect to the remote database server

	ORA-17627: ORA-00942: table or view does not exist

 

需要把登入方式修改下

 

SOLUTION

Workaround

Do not use operating system authentication to login with RMAN. Use a username and password.

That is, do not use just the "/" (operating system authentication) connect to the standby database:

$ rman target /


Instead put in the username and password for the SYSDBA user:


$ rman sys/password

 

ORA-00600[KGEADE_IS_0]错误解决

0

Posted on by

在RAC ASM文件系统恢复到单机文件系统,open resetlogs 报错:

ORA-00600: internal error code, arguments: [kgeade_is_0], [], [], [], [], [], [], []
ORA-600 signalled during: alter database open resetlogs...
Errors in file /u01/app/oracle/admin/orcl/udump/orcl_ora_10861.trc:
ORA-00313: open failed for members of log group 11 of thread 1
ORA-00312: online log 11 thread 1: '+DATA1/orcl/datafile/redo111'
ORA-17503: ksfdopn:2 Failed to open file +DATA1/orcl/datafile/redo111
ORA-15001: diskgroup "DATA1" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
ORA-00312: online log 11 thread 1: '+DATA1/orcl/onlinelog/redo111'
ORA-17503: ksfdopn:2 Failed to open file +DATA1/orcl/onlinelog/redo111
ORA-15001: diskgroup "DATA1" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager

 

在MOS上查询了一下,是一个bug:

To implement a solution for Bug:7207932, please execute any of the below alternative solutions:

  • Upgrade to 11.1

OR

  • Apply patchset 10.2.0.5 in which Bug:7207932 is fixed.

OR

OR

  • A possible workaround is to recreate the controlfile and specifying new filenames in the controlfile. If this does not work, then apply the patch for Bug:7207932.

 

即通过2种方法来实现:

1.打补丁,或者升级。

        1.shutdown database
        2.unzip  p7207932_10204_Linux-x86-64.zip
        3.cd 7207932
        4.$ORACLE_HOME/OPatch/opatch apply

2.重建控制文件,更新里面的路径。

        1.alter database backup controlfile to trace as '/u01/controlfile.log'
        2.recreate controlfile (更新里面redo的路径)

 

     

 

RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file

0

Posted on by

在物理备库上更改rman的 RETENTION POLICY参数报下面的错:

RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 366 DAYS;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 05/07/2013 13:31:48
RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file

 

mos:有2个解决方案:

1.现在主库上修改,然后重建备库的控制文件

2.直接用rman手动删除过期的备份文件

 

 

具体如下:

 

 

Option 1 :- Recreate standby controlfile from Primary

Once the Retention policy has been changed in Primary. Recreate the Standby controlfile from the Primary.

On the primary database, create the control file for the standby database, as shown in the following example:


SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/disk1/oracle/oradata/standby/payroll2.ctl';

On standby renaming the existing standby controlfile .

Now Copy the new standby controlfile from primary  to standby server in same location and name where it existed on standby database. if copying to different location make changes pfile/spfile to point to new this standby controlfile.

Mount the standby database and check the location of datafile and logfiles are pointing to standby location and not production .

 

Now do

 

Rman> Show retention policy ;

 

 

 

 

Option 2 : – Use Delete obsolete option

 This option doesnot change the retention policy in Rman configuration.

 Its a Temporary workaround at run time.

You can use the following option to Delete Obsolete backups on Standby

On Standby

 

Rman>Connect target /

Rman> delete noprompt obsolete recovery window of 14 days

If you want rman to prompt the backuppiece name before delete run

 

Rman> delete  obsolete recovery window of 14 days