rman创建备库报错问题处理记录

2024-03-21 18:18

本文主要是介绍rman创建备库报错问题处理记录,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!



报错1:
[oracle@dgcrm ~]$ rman target sys/123456@CRM auxiliary sys/123456@DGCRM


Recovery Manager: Release 11.2.0.4.0 - Production on Thu Dec 1 10:26:53 2016


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


connected to target database: CRM (DBID=991422785)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA


监听配置不对




报错2:


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/01/2016 18:37:56
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on prmy4 channel at 12/01/2016 18:37:56
ORA-17628: Oracle error 19505 returned by remote Oracle server


主备库的数据库文件路径不对,又没有加b_file_name_convert、log_file_name_convert,报错




如:控制文件的目录没有创建
[oracle@oracle_backup oradata]$ cd /u01/app/oracle/oradata/CRM/
-bash: cd: /u01/app/oracle/oradata/CRM/: No such file or directory
[oracle@oracle_backup oradata]$ mkdir -p /u01/app/oracle/oradata/CRM/
[oracle@oracle_backup oradata]$ mkdir -p /oradata/hzjxc




报错3:
DBGSQL:     TARGET> begin :fhdbi := dbms_rcvcat.getDbid; end;
DBGSQL:        sqlcode = 6550
DBGSQL:         B :fhdbi = 32767
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/01/2016 10:58:37
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-06550: line 1, column 17:
PLS-00201: identifier 'DBMS_RCVCAT.GETDBID' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored


一些配置修改了,rman需要登录连接




报错4:
rman target sys/123456@CRM auxiliary /


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/01/2016 10:24:46
RMAN-05501: aborting duplication of target database
RMAN-06217: not connected to auxiliary database with a net service name


辅助库不能本地方式连接






报错5:
SQL> startup nomount
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00130: invalid listener address '(ADDRESS=(PROTOCOL=TCP)(HOST=Redhat6.5T)(PORT=1521))'


--alert.log---
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/app/oracle/11204
System name:    Linux
Node name:      Redhat6.5T
Release:        2.6.32-431.el6.x86_64
Version:        #1 SMP Sun Nov 10 22:19:54 EST 2013
Machine:        x86_64
VM name:        VMWare Version: 6
Using parameter settings in server-side pfile /u01/app/oracle/11204/dbs/initCRM.ora
System parameters with non-default values:
  processes                = 1500
  sessions                 = 2272
  sga_target               = 46720M
  control_files            = "/u01/app/oracle/oradata/CRM/control01.ctl"
  control_files            = "/oradata/fast_recovery_area/CRM/control02.ctl"
  control_files            = "/u01/app/oracle/oradata/CRM/control03.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.4.0"
  log_archive_dest_2       = "service=dgcrm LGWR SYNC affirm  valid_for=(online_logfiles,primary_role) db_unique_name=dgcrm"
  log_archive_dest_state_1 = "ENABLE"
  log_archive_dest_state_2 = "ENABLE"
  fal_client               = "CRM"
  fal_server               = "DGCRM"
  log_archive_config       = "dg_config=(CRM,dgcrm)"
  log_archive_format       = "%t_%s_%r.dbf"
  db_recovery_file_dest    = "/oradata/fast_recovery_area"
  db_recovery_file_dest_size= 41820M
  standby_file_management  = "AUTO"
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=CRMXDB)"
  audit_file_dest          = "/u01/app/oracle/admin/CRM/adump"
  audit_trail              = "DB"
  db_name                  = "CRM"
  db_unique_name           = "CRM"
  open_cursors             = 300
  pga_aggregate_target     = 15559M
  diagnostic_dest          = "/u01/app/oracle"
USER (ospid: 16260): terminating the instance due to error 119
Instance terminated by USER, pid = 16260




SQL> startup nomount
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00130: invalid listener address '(ADDRESS=(PROTOCOL=TCP)(HOST=Redhat6.5T)(PORT=1521))'




机器名没有改变正确






报错6:备库没有接受到归档
SQL> show parameter LOG_ARCHIVE_DEST_2;


NAME                                 TYPE                              VALUE
------------------------------------ --------------------------------- ------------------------------
log_archive_dest_2                   string                            service=dg LGWR SYNC affirm  v
                                                                       alid_for=(online_logfiles,prim
                                                                       ary_role) db_unique_name=dg
log_archive_dest_20                  string
log_archive_dest_21                  string
log_archive_dest_22                  string
log_archive_dest_23                  string
log_archive_dest_24                  string
log_archive_dest_25                  string
log_archive_dest_26                  string
log_archive_dest_27                  string


NAME                                 TYPE                              VALUE
------------------------------------ --------------------------------- ------------------------------
log_archive_dest_28                  string
log_archive_dest_29                  string
SQL> select dest_id,error,status,log_sequence,applied_scn from v$archive_dest where dest_id=2;


   DEST_ID ERROR                                                             STATUS                      LOG_SEQUENCE APPLIED_SCN
---------- ----------------------------------------------------------------- --------------------------- ------------ -----------
         2 ORA-16047: DGID mismatch between destination setting and target   ERROR                                  0           0
           database




SQL> 




原因备库的log_archive_config忘记配了
alter system set log_archive_config='dg_config=(CRM,dgcrm)' scope=spfile;


配置后关闭,再starup mount; 再alter database recover managed standby database disconnect from session;
























///正常执行duplicate过程/




[oracle@Redhat6 ~]$ 
[oracle@Redhat6 ~]$ rman target sys/123456@CRM auxiliary sys/123456@dgcrm


Recovery Manager: Release 11.2.0.4.0 - Production on Thu Dec 1 17:23:21 2016


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


connected to target database: CRM (DBID=991398108)
connected to auxiliary database: CRM (not mounted)


RMAN> run {
2> allocate auxiliary channel c1 device type disk;
   allocate auxiliary channel c2 device type disk;
4> duplicate target database for standby nofilenamecheck dorecover;
release channel c1;
release channel c2;
7> }


using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=10 device type=DISK


allocated channel: c2
channel c2: SID=1146 device type=DISK


Starting Duplicate Db at 01-DEC-16


contents of Memory Script:
{
   set until scn  1064069;
   restore clone standby controlfile;
}
executing Memory Script


executing command: SET until clause


Starting restore at 01-DEC-16


channel c1: starting datafile backup set restore
channel c1: restoring control file
channel c1: reading from backup piece /oradata/fast_recovery_area/CRM/backupset/2016_12_01/o1_mf_ncsnf_TAG20161201T161453_d3zq060s_.bkp
channel c1: piece handle=/oradata/fast_recovery_area/CRM/backupset/2016_12_01/o1_mf_ncsnf_TAG20161201T161453_d3zq060s_.bkp tag=TAG20161201T161453
channel c1: restored backup piece 1
channel c1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oracle/oradata/CRM/control01.ctl
output file name=/oradata/fast_recovery_area/CRM/control02.ctl
output file name=/u01/app/oracle/oradata/CRM/control03.ctl
Finished restore at 01-DEC-16


contents of Memory Script:
{
   sql clone 'alter database mount standby database';
}
executing Memory Script


sql statement: alter database mount standby database


contents of Memory Script:
{
   set until scn  1064069;
   set newname for tempfile  1 to 
 "/oradata/CRM/temp01.dbf";
   switch clone tempfile all;
   set newname for datafile  1 to 
 "/oradata/CRM/system01.dbf";
   set newname for datafile  2 to 
 "/oradata/CRM/sysaux01.dbf";
   set newname for datafile  3 to 
 "/oradata/CRM/undotbs01.dbf";
   set newname for datafile  4 to 
 "/oradata/CRM/users01.dbf";
   restore
   clone database
   ;
}
executing Memory Script


executing command: SET until clause


executing command: SET NEWNAME


renamed tempfile 1 to /oradata/CRM/temp01.dbf in control file


executing command: SET NEWNAME


executing command: SET NEWNAME


executing command: SET NEWNAME


executing command: SET NEWNAME


Starting restore at 01-DEC-16


channel c1: starting datafile backup set restore
channel c1: specifying datafile(s) to restore from backup set
channel c1: restoring datafile 00001 to /oradata/CRM/system01.dbf
channel c1: restoring datafile 00002 to /oradata/CRM/sysaux01.dbf
channel c1: restoring datafile 00003 to /oradata/CRM/undotbs01.dbf
channel c1: restoring datafile 00004 to /oradata/CRM/users01.dbf
channel c1: reading from backup piece /oradata/fast_recovery_area/CRM/backupset/2016_12_01/o1_mf_nnndf_TAG20161201T161453_d3zpzxxx_.bkp
channel c1: piece handle=/oradata/fast_recovery_area/CRM/backupset/2016_12_01/o1_mf_nnndf_TAG20161201T161453_d3zpzxxx_.bkp tag=TAG20161201T161453
channel c1: restored backup piece 1
channel c1: restore complete, elapsed time: 00:00:15
Finished restore at 01-DEC-16


contents of Memory Script:
{
   switch clone datafile all;
}
executing Memory Script


datafile 1 switched to datafile copy
input datafile copy RECID=1 STAMP=929467441 file name=/oradata/CRM/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=2 STAMP=929467441 file name=/oradata/CRM/sysaux01.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=3 STAMP=929467441 file name=/oradata/CRM/undotbs01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=4 STAMP=929467441 file name=/oradata/CRM/users01.dbf


contents of Memory Script:
{
   set until scn  1064069;
   recover
   standby
   clone database
    delete archivelog
   ;
}
executing Memory Script


executing command: SET until clause


Starting recover at 01-DEC-16


starting media recovery


archived log for thread 1 with sequence 4 is already on disk as file /oradata/fast_recovery_area/CRM/archivelog/2016_12_01/o1_mf_1_4_d3zq077r_.arc
archived log file name=/oradata/fast_recovery_area/CRM/archivelog/2016_12_01/o1_mf_1_4_d3zq077r_.arc thread=1 sequence=4
media recovery complete, elapsed time: 00:00:00
Finished recover at 01-DEC-16
Finished Duplicate Db at 01-DEC-16


released channel: c1


released channel: c2


RMAN> 


RMAN> 


RMAN> 


RMAN> 


RMAN> 





这篇关于rman创建备库报错问题处理记录的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/833489

相关文章

解决IDEA报错:编码GBK的不可映射字符问题

《解决IDEA报错:编码GBK的不可映射字符问题》:本文主要介绍解决IDEA报错:编码GBK的不可映射字符问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录IDEA报错:编码GBK的不可映射字符终端软件问题描述原因分析解决方案方法1:将命令改为方法2:右下jav

Java 中的 @SneakyThrows 注解使用方法(简化异常处理的利与弊)

《Java中的@SneakyThrows注解使用方法(简化异常处理的利与弊)》为了简化异常处理,Lombok提供了一个强大的注解@SneakyThrows,本文将详细介绍@SneakyThro... 目录1. @SneakyThrows 简介 1.1 什么是 Lombok?2. @SneakyThrows

MyBatis模糊查询报错:ParserException: not supported.pos 问题解决

《MyBatis模糊查询报错:ParserException:notsupported.pos问题解决》本文主要介绍了MyBatis模糊查询报错:ParserException:notsuppo... 目录问题描述问题根源错误SQL解析逻辑深层原因分析三种解决方案方案一:使用CONCAT函数(推荐)方案二:

在 Spring Boot 中实现异常处理最佳实践

《在SpringBoot中实现异常处理最佳实践》本文介绍如何在SpringBoot中实现异常处理,涵盖核心概念、实现方法、与先前查询的集成、性能分析、常见问题和最佳实践,感兴趣的朋友一起看看吧... 目录一、Spring Boot 异常处理的背景与核心概念1.1 为什么需要异常处理?1.2 Spring B

python处理带有时区的日期和时间数据

《python处理带有时区的日期和时间数据》这篇文章主要为大家详细介绍了如何在Python中使用pytz库处理时区信息,包括获取当前UTC时间,转换为特定时区等,有需要的小伙伴可以参考一下... 目录时区基本信息python datetime使用timezonepandas处理时区数据知识延展时区基本信息

使用Python和Pyecharts创建交互式地图

《使用Python和Pyecharts创建交互式地图》在数据可视化领域,创建交互式地图是一种强大的方式,可以使受众能够以引人入胜且信息丰富的方式探索地理数据,下面我们看看如何使用Python和Pyec... 目录简介Pyecharts 简介创建上海地图代码说明运行结果总结简介在数据可视化领域,创建交互式地

Redis 热 key 和大 key 问题小结

《Redis热key和大key问题小结》:本文主要介绍Redis热key和大key问题小结,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录一、什么是 Redis 热 key?热 key(Hot Key)定义: 热 key 常见表现:热 key 的风险:二、

IntelliJ IDEA 中配置 Spring MVC 环境的详细步骤及问题解决

《IntelliJIDEA中配置SpringMVC环境的详细步骤及问题解决》:本文主要介绍IntelliJIDEA中配置SpringMVC环境的详细步骤及问题解决,本文分步骤结合实例给大... 目录步骤 1:创建 Maven Web 项目步骤 2:添加 Spring MVC 依赖1、保存后执行2、将新的依赖

Spring 中的循环引用问题解决方法

《Spring中的循环引用问题解决方法》:本文主要介绍Spring中的循环引用问题解决方法,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录什么是循环引用?循环依赖三级缓存解决循环依赖二级缓存三级缓存本章来聊聊Spring 中的循环引用问题该如何解决。这里聊

Spring Boot中JSON数值溢出问题从报错到优雅解决办法

《SpringBoot中JSON数值溢出问题从报错到优雅解决办法》:本文主要介绍SpringBoot中JSON数值溢出问题从报错到优雅的解决办法,通过修改字段类型为Long、添加全局异常处理和... 目录一、问题背景:为什么我的接口突然报错了?二、为什么会发生这个错误?1. Java 数据类型的“容量”限制