码迷,mamicode.com
首页 > 其他好文 > 详细

adg故障处理记录---MRP中断

时间:2021-02-04 11:52:42      阅读:0      评论:0      收藏:0      [点我收藏+]

标签:intern   restore   server   for   总结   子公司   tab   mat   log   

physical standby errors ORA-00600 ORA-10567 ORA-10564 ORA-01110 ORA-10561
DECEMBER 26, 2016 ARCSDEGEOLEAVE A COMMENT
The following errors were thrown while trying to sync physical standby database with the primary database:
ORA-00600: internal error code, arguments: [3020], [239], [13749],
[1002452405], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 239, block# 13749, file
offset is 112631808 bytes)
ORA-10564: tablespace SYSAUX
ORA-01110: data file 211: ‘/database/orcl07/SYSAUX01.ORA’
ORA-10561: block type ‘TRANSACTION MANAGED INDEX BLOCK’, data object# 2877779
To resolve this you have 2 approaches …..choose one:
******************** First Approach *********************************
1. on the primary database
RMAN> rman target /
run
{
ALLOCATE CHANNEL ch1 DEVICE TYPE DISK format ‘/u01/inc_TMN_%U‘;
backup datafile 88;
release channel ch1;
}
—-  after executing the above rman command a backup of set for the data file will be generated and will require copying to the physical standby database server
scp inc_TMN_imvbhgf7_1_1 hwfcdb1:/tmp/oracle_inc/
2. on the standby database:
RMAN> catalog start with ‘/tmp/oracle_inc/‘;
RMAN> shutdown immediate;
RMAN> startup mount;
RMAN> restore datafile 239;
RMAN> exit;
SQL> RECOVER AUTOMATIC STANDBY DATABASE;
******************** Second Approach *********************************
1. on the standby database:
SQL> shutdown immediate;
2. on the primary database:
SQL> ALTER tablespace SYSAUX begin backup;
scp /database/orcl07/SYSAUX01.ORA standby_server:/database/orcl07/SYSAUX01.ORA
SQL> ALTER tablespace SDE end backup ;
3. on the standby database:
SQL> STARTUP NOMOUNT
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
SQL> RECOVER AUTOMATIC STANDBY DATABASE;

 

 

子公司的一个同事提到他的数据库默认归档目录大小2G被沾满,归档日志被移动到其他目录,数据库无法再识别到之前的归档日志文件,请我提供下解决办法,我没遇到过这种情况(手里的库都很规范:),哈哈)。于是上网搜出一些类似案例,并总结出对应的解决办法。
 
移动归档日志文件的原因,一般会有如下几种:
1、数据库初始安装时未仔细考虑归档存放路径问题,默认2G大小不够用,直接添加新的归档目录,旧的归档日志被直接移动到其他目录下。
2、原来存储数据库归档日志的硬盘或存储硬件损坏或需要更换,此时由于某些原因需要移动归档日志到新的目录(当然也可以新建和原目录同名的目录即可。)
3、DATAGUARD主库磁盘空爆满,日志传输异常,需要手工拷贝日志到备库,并手工注册归档日志
 
解决办法如下:
1、增加新的归档路径
alter system set log_archive_dest_state_n=enable
alter sysytem set log_archive_dest_n=‘location=路径; n为1到10                      
2、重新注册下老的归档日志
1)单个或少量日志注册
SQL> alter database register logfile  ‘/oraarch/archivelog_1_101.arc’;
2)大量日志注册
rman> catalog start with ‘/oracle/oraarch‘;

 

 

 

 

 

 

ORA-01111 ORA-01110 ORA-01157 in a physical standby database


[0927-10:51:55]Recovery Slave PR00 previously exited with exception 1111
[0927-10:51:55]2020-09-27T10:51:54.632728+08:00
[0927-10:51:55]Errors in file /u01/oracle/diag/rdbms/wydb/wydb1/trace/wydb1_mrp0_107284.trc:
[0927-10:51:55]ORA-01111: 数据文件 544 名称未知 - 请重命名以更正文件
[0927-10:51:55]ORA-01110: 数据文件 544: ‘/u01/oracle/product/12.2.0/dbs/UNNAMED00544‘
[0927-10:51:55]ORA-01157: 无法标识/锁定数据文件 544 - 请参阅 DBWR 跟踪文件
[0927-10:51:55]ORA-01111: 数据文件 544 名称未知 - 请重命名以更正文件
[0927-10:51:55]ORA-01110: 数据文件 544: ‘/u01/oracle/product/12.2.0/dbs/UNNAMED00544‘
[0927-10:51:55]2020-09-27T10:51:54.632812+08:00
[0927-10:51:55]MRP0: Background Media Recovery process shutdown (wydb1)

 

solution:

alter database create datafile‘/u01/oracle/product/12.2.0/dbs/UNNAMED00544‘ as ‘+DG2‘;


ALTER SYSTEM SET standby_file_management=‘AUTO‘ SCOPE=BOTH SID=‘*‘;


alter database recover managed standby database using current logfile disconnect from session;

 

adg故障处理记录---MRP中断

标签:intern   restore   server   for   总结   子公司   tab   mat   log   

原文地址:https://www.cnblogs.com/guaika/p/14367966.html

(0)
(0)
   
举报
评论 一句话评论(0
登录后才能评论!
© 2014 mamicode.com 版权所有  联系我们:gaon5@hotmail.com
迷上了代码!