alter database open resetlogs时 alert的输出

SQL> alter database open resetlogs;

Database altered.

时的提示:

ORA-279 signalled during: ALTER DATABASE RECOVER  datafile 5  ...

ALTER DATABASE RECOVER    CANCEL

Media Recovery Canceled

Completed: ALTER DATABASE RECOVER    CANCEL

Sat Apr 18 18:41:33 2015

alter database open resetlogs

ORA-1139 signalled during: alter database open resetlogs...

Sat Apr 18 18:42:06 2015

ALTER DATABASE RECOVER  database until cancel

Media Recovery Start

started logmerger process

Parallel Media Recovery started with 4 slaves

Sat Apr 18 18:42:06 2015

Warning: Datafile 5 (/u01/app/oracle/oradata/test/ten01.dbf) is offline during full database recovery and will not be recovered

Media Recovery Not Required

Completed: ALTER DATABASE RECOVER  database until cancel

Sat Apr 18 18:42:23 2015

alter database open resetlogs

RESETLOGS after complete recovery through change 3580552

Archived Log entry 28 added for thread 1 sequence 155 ID 0x7d875fb4 dest 1:

Resetting resetlogs activation ID 2106023860 (0x7d875fb4)

Sat Apr 18 18:42:28 2015

Setting recovery target incarnation to 3

Sat Apr 18 18:42:28 2015

Assigning activation ID 2175494118 (0x81ab67e6)

LGWR: STARTING ARCH PROCESSES

Sat Apr 18 18:42:28 2015

ARC0 started with pid=20, OS id=3826

ARC0: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC0: STARTING ARCH PROCESSES

Sat Apr 18 18:42:29 2015

ARC1 started with pid=21, OS id=3828

Sat Apr 18 18:42:29 2015

ARC2 started with pid=22, OS id=3830

Sat Apr 18 18:42:29 2015

ARC3 started with pid=23, OS id=3832

ARC1: Archival started

ARC2: Archival started

ARC3: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

ARC0: Becoming the ‘no FAL‘ ARCH

ARC0: Becoming the ‘no SRL‘ ARCH

ARC1: Becoming the heartbeat ARCH

Thread 1 opened at log sequence 1

Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/test/redo01.log

Successful open of redo thread 1

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Sat Apr 18 18:42:29 2015

SMON: enabling cache recovery

[3781] Successfully onlined Undo Tablespace 2.

Undo initialization finished serial:0 start:11031024 end:11032224 diff:1200 (12 seconds)

Dictionary check beginning

File #5 is offline, but is part of an online tablespace.

data file 5: ‘/u01/app/oracle/oradata/test/ten01.dbf‘

File #12 is offline, but is part of an online tablespace.

data file 12: ‘/u01/app/oracle/oradata/test/test.dbf‘

Dictionary check complete

Verifying file header compatibility for 11g tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

SMON: enabling tx recovery

Database Characterset is ZHS16GBK

No Resource Manager plan active

Sat Apr 18 18:42:33 2015

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

Sat Apr 18 18:42:37 2015

QMNC started with pid=24, OS id=3834

LOGSTDBY: Validating controlfile with logical metadata

LOGSTDBY: Validation complete

Sat Apr 18 18:42:50 2015

Completed: alter database open resetlogs

Sat Apr 18 18:42:50 2015

Starting background process CJQ0

Sat Apr 18 18:42:50 2015

CJQ0 started with pid=27, OS id=3854

Sat Apr 18 18:42:51 2015

Checker run found 2 new persistent data failures

时间: 2024-11-08 11:48:29

alter database open resetlogs时 alert的输出的相关文章

不完全回复-alter database open resetlogs

先要弄清楚alter database open resetlogs是什么意思,为什么要用resetlogs打开数据库,这个命令发出后oracle都做了什么? alter database open resetlogs是要打开数据时,重置重做日志,即将重做日志的sequence置零,为什么要重置重做日志呢? 不完全恢复后,原来的online redo log里面包含的是未做恢复前的数据,而这些数据对于恢复后的数据库不再有效,所以数据库会要求在Open之前先对online redo log的seq

alter database open resetlogs

使用resetlogs选项,会把当前的日志序号(log sequence number)重设为1,并抛弃所有日志信息.在以下条件时需要使用resetlogs选项: 在不完全恢复(介质恢复): 使用备份控制文件. 使用resetlogs打开数据库后,务必要完整地进行一次数据库备份. 不完全恢复只能做一次吗? 采用rman的默认设置,对数据库进行了backup database备份,进行了一些操作后,然后直接关闭启动到mount状态 RMAN> run{ 2> set until time &qu

(转)alter database open resetlogs 的意义

转自:http://blog.sina.com.cn/s/blog_63216bda0100zblr.html Oracle文档中提到,一旦用备份的控制文件进行数据库恢复,就需要使用resetlogs的方法打开数据库,但是resetlogs通常意味着不完全恢复,而且更重要的是一旦用resetlogs方法打开数据库,日志的序号用重新从1开始.其实如果只是控制文件损坏,日志文件都完整的话,数据库是可以完全恢复的,而且不必非得用resetlogs打开.接下来,我们就对不完全恢复做出总结,如图9-10所

sqlserver数据库脱机时发生异常:由于无法在数据库 'SMS' 上放置锁,ALTER DATABASE 失败。请稍后再试。 ALTER DATABASE 语句失败。 (.Net SqlClient Data Provider)

sqlserver数据库脱机时发生异常,如下: =================================== 设置脱机 对于 数据库“SMS”失败.  (Microsoft.SqlServer.Smo) ------------------------------ 有关帮助信息,请单击: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.2500.0+((KJ_PCU_Main).110

丢失全部控制文件,noresetlogs重建控制文件,alter database open

測试2: (1)一致性的全备 SQL> shutdown immediate; $ cp -rf $ORACLE_BASE/oradata/boss/*.dbf /oradata/bossbak/20140610allbackup $ cp -rf $ORACLE_BASE/oradata/boss/*.log /oradata/bossbak/20140610allbackup $ cp -rf $ORACLE_BASE/oradata/boss/*.ctl /oradata/bossbak/

丢失所有控制文件,noresetlogs重建控制文件,alter database open

测试2: (1)一致性的全备 SQL> shutdown immediate; $ cp -rf $ORACLE_BASE/oradata/boss/*.dbf /oradata/bossbak/20140610allbackup $ cp -rf $ORACLE_BASE/oradata/boss/*.log /oradata/bossbak/20140610allbackup $ cp -rf $ORACLE_BASE/oradata/boss/*.ctl /oradata/bossbak/

ORA-279 signalled during: alter database recover logfile

在RMAN的RECOVER还原过程中,RMAN界面正常,但是检查.刷新告警日志,发现告警日志里面有ORA-279,如下所示: alter database recover logfile '/u06/archivelog/2019_02_19/o1_mf_1_16228_g6oznpbv_.arc' Thu Feb 21 08:49:48 CST 2019 Media Recovery Log /u06/archivelog/2019_02_19/o1_mf_1_16228_g6oznpbv_.

backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized.

昨天在检查YourSQLDba备份时,发现有台数据库做备份时出现了下面错误信息,如下所示: <Exec>   <ctx>yMaint.ShrinkLog</ctx>   <inf>Log Shrink</inf>   <Sql> --  ======================================================================== -- Shrink of log file E:\SQ

【 翻译自mos文章】Alter Database Add Supplemental Log Data 命令挂起

Alter Database Add Supplemental Log Data 命令挂起 来源于: Alter Database Add Supplemental Log Data Hangs (文档 ID 406498.1) 适用于: Oracle Database - Enterprise Edition - Version 10.2.0.1 and later Information in this document applies to any platform. 症状: 作为流复制配