Oracle Study之--RMAN启用block change tracking错误

Oracle Study之--RMAN启用block
change tracking错误

系统环境:

  操作系统: RedHat
EL6

  Oracle:   Oracle 11g
R2

Target DB:    prod

Catalog DB:  
orcl

在使用rman备份做增量备份后,启动“block change tracking” 出现了ORA-600错误!

案例分析:

1、启用block change
tracking

11:23:43 [email protected] prod>alter database enable
block change tracking using file ‘/home/oracle/blk.trc‘ reuse;

Database altered.

告警日志:
alter database enable block change
tracking using file ‘/home/oracle/blk.trc‘
Block change tracking file is
current.
Starting background process CTWR
Tue Apr 07 11:36:55
2015
CTWR started with pid=33, OS id=5576

Block change tracking service is active.

2、通过rman建立备份脚本

[[email protected] dbs]$ rman target / catalog
rman/[email protected]

Recovery Manager: Release 11.2.0.1.0 -
Production on Tue Apr 7 11:29:41 2015

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

connected to target database: PROD
(DBID=239333010)
connected to recovery catalog database

RMAN> create global script global_del_obso
comment ‘A script for obsolete backup and delete it‘
{
2> 3> 
crosscheck archivelog all;
4>  delete noprompt expired archivelog
all;
5>  allocate channel ch1 device type disk;
6>  delete noprompt
obsolete recovery window of 15 days;
7>  release channel ch1;
8> 
}

RMAN-00571:
===========================================================
RMAN-00569:
=============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571:
===========================================================
RMAN-03002:
failure of create script command at 04/07/2015 11:29:58
RMAN-06004: ORACLE
error from recovery catalog database: ORA-03114: not connected to
ORACLE

告警日志:

[[email protected] ~]$ tail -f
/u01/app/oracle/diag/rdbms/prod/prod/trace/alert_prod.log
Tue Apr 07 11:27:16 2015
Errors in file
/u01/app/oracle/diag/rdbms/prod/prod/trace/prod_ctwr_4912.trc 
(incident=39841):
ORA-00600: internal error code, arguments:
[krccacp_badfile], [1513065], [0], [624054], [0], [], [], [], [], [], [],
[]
Incident details in:
/u01/app/oracle/diag/rdbms/prod/prod/incident/incdir_39841/prod_ctwr_4912_i39841.trc
Errors
in file
/u01/app/oracle/diag/rdbms/prod/prod/trace/prod_ctwr_4912.trc:
ORA-00600:
internal error code, arguments: [krccacp_badfile], [1513065], [0], [624054],
[0], [], [], [], [], [], [], []
CTWR
(ospid: 4912): terminating the instance due to error 487
Tue Apr 07 11:27:19
2015
ORA-1092 : opitsk aborting process
Instance terminated by CTWR, pid =
4912

从日志可以看到CTRW进程关闭了Instance!

3、停止使用block change tracking

11:31:33 [email protected] prod>alter database disable
block change tracking;

Database altered.

Elapsed: 00:00:01.13

告警日志

alter database disable block change
tracking
Tue Apr 07 11:31:50 2015
Block change tracking service
stopping.
Stopping background process CTWR
Deleted file
/home/oracle/blk.trc
Completed: alter database disable block change
tracking
Tue Apr 07 11:34:36 2015

再通过rman建立备份脚本:

[[email protected] dbs]$ rman target / catalog
rman/[email protected]

Recovery Manager: Release 11.2.0.1.0 -
Production on Tue Apr 7 11:29:41 2015

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

connected to target database: PROD
(DBID=239333010)
connected to recovery catalog database

RMAN> create global script global_del_obso
comment ‘A script for obsolete backup and delete it‘
{
2> 3> 
crosscheck archivelog all;
4>  delete noprompt expired archivelog
all;
5>  allocate channel ch1 device type disk;
6>  delete noprompt
obsolete recovery window of 15 days;
7>  release channel ch1;
8> 
}

这是备份脚本建立成功!

 注:

      
在后面又出现了一样的错误,在操作系统下删除了trace文件“blk.trc”后,又恢复正常,现在还没有搞清楚造成这个问题的具体原因是什么?

时间: 2024-08-02 06:59:13

Oracle Study之--RMAN启用block change tracking错误的相关文章

Oracle 10g Block Change Tracking特性

Using Block Change Tracking to Improve Incremental Backup Performance 使用块改变跟踪改善增量备份的性能 The block change tracking feature for incremental backups improves backup performance by recording changed blocks for each data file.    块改变跟踪特性通过记录每个数据文件的块改变来改善增量

Oracle备份之RMAN

1.备份:物理备份时文件层次的备份,逻辑备份时数据层次的备份,物理备份为主,逻辑备份作为补充.物理备份分为用户管理备份和RMAN备份,前者使用SQL命令和OS的cp命令进行文件备份,后者使用RMAN工具份.Undo Segment:修改记录过程中,记录修改前的状态会被记录到Undo Segment中,这条记录叫作前镜像(before images).当需要撤销修改比如执行rollback时,就用这条前镜像覆盖现有记录.对于Insert操作,前镜像就是一个空记录,对于Update,Delete操作

Oracle Study之--Oracle 11gR2通过RMAN克隆数据库

Oracle Study之--Oracle 11gR2通过RMAN克隆数据库 Purpose of Database Duplication A duplicate database is useful for a variety of purposes, most of which involve testing. You can perform the following tasks in a duplicate database: Test backup and recovery proc

-Oracle 11gR2通过RMAN克隆数据库

Oracle Study之--Oracle 11gR2通过RMAN克隆数据库 Purpose of Database Duplication A duplicate database is useful for a variety of purposes, most of which involve testing. You can perform the following tasks in a duplicate database: Test backup and recovery proc

Oracle 学习之RMAN(四)增量备份

RMAN不但能进行数据库.数据文件等全量备份,而且还能做增量备份.增量备份有两大优点: 减少数据库恢复的时间. 数据库恢复是利用归档日志,不断的应用归档日志,将数据库恢复到最新(或者指定状态).但是增量备份只备份被修改了的数据块,在执行恢复时,直接用备份出来的数据块去覆盖数据文件中被更改的数据块. 减少备份时间 增量备份只需备份被修改过的数据块,备份时间和备份存储空间都有相应的减少. 做增量备份的前提,是需要一个基准备份,所有的增量都是针对这个基准来说的.要不然,增量备份无从谈起. 增量备份使用

Oracle Study之案例--RMAN备份配置参数

Oracle Study之案例--RMAN备份配置参数 1.PARALLELISM  我们还可以通过parallelism参数来指定同时"自动"创建多少个通道:RMAN > configure device type disk parallelism 3 ; 表示启动三个通道,可以加快备份恢复的速度. 案例分析: RMAN> show all; using target database control file instead of recovery catalog CO

Oracle Study之案例--RMAN ORA-19921错误

Oracle Study之案例--RMAN ORA-19921错误 系统环境: 操作系统: AIX5.3 Oracle:   Oracle 10gR2 错误现象:         数据库在通过rman连接时出现以下错误: [11:01:51 [email protected]: ~]$rman target / Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jan 19 11:01:53 2015 Copyright (c) 1

Oracle Study之案例--Oracle 数据块地址(Block Address)

Oracle Study之案例--Oracle 数据块地址(Block Address) Oracle访问数据是以block为单位,本文简单介绍了如何通过Block Address在内存中获取所需要的block. DBA(data block address): A DBA is the address of an oracle data block for access purposes. RDBA (Tablespace relative database block address): R

Oracle Study之案例--Oracle 11g DataGuard Snapshot Standby

Oracle Study之案例--Oracle 11g  DataGuard Snapshot Standby Oracle 11g的Data Guard不仅仅带给我们的是Active Data Guard实时查询特性,同时还带来了另外一个新特性,这便是Snapshot Standby数据库功能,此项功能可将备库置身于"可读写状态"用于不方便在生产环境主库中测试的内容,比如模拟上线测试等任务.当备库读写状态下任务完成后,可以非常轻松的完成Snapshot Standby数据库角色切换回