迁移数据库后启动报错ora-600[25025]_MySQL, Oracle及数据库讨论区_Weblogic技术|Tuxedo技术|中间件技术|Oracle论坛|JAVA论坛|Linux/Unix技术|hadoop论坛_联动北方技术论坛  
网站首页 | 关于我们 | 服务中心 | 经验交流 | 公司荣誉 | 成功案例 | 合作伙伴 | 联系我们 |
联动北方-国内领先的云技术服务提供商
»  游客             当前位置:  论坛首页 »  自由讨论区 »  MySQL, Oracle及数据库讨论区 »
总帖数
2
每页帖数
101/1页1
返回列表
0
发起投票  发起投票 发新帖子
查看: 2236 | 回复: 1   主题: 迁移数据库后启动报错ora-600[25025]        下一篇 
skaple
注册用户
等级:中士
经验:227
发帖:30
精华:0
注册:2012-3-5
状态:离线
发送短消息息给skaple 加好友    发送短消息息给skaple 发消息
发表于: IP:您无权察看 2015-8-21 9:44:52 | [全部帖] [楼主帖] 楼主

迁移脚本的日志中报错RMAN-06571: datafile 78 does not have recoverable copy,经查看发现78号文件曾经被offline drop掉。于是重建控制文件,在控制文件中把78号文件去掉,重建控制后,数据库能够mount,mount后数据文件是一致,但是open 时会报错ora-600,异常宕掉。

SYS@mydbtst> alter database open;
alter database open
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [25025], [78], [], [], [], [], [],
[], [], [], [], []
Process ID: 6028
Session ID: 521 Serial number: 15


经检查,这个78号文件是undo的一个文件。上述的处理方法,对于处理一般的数据文件是可行的,但是对于undo文件的问题,就不能用上述这个方法处理了。应该用下面的处理方法,具体的处理方法如下:

1. 加上管理方式为manual:

……
*.streams_pool_size=134217728
*.undo_retention=3600
*.undo_tablespace='UNDOTBS1'
*.undo_management='manual'
~


2. 启动之后,做recovery:

SYS@mydbtst> startup pfile='/tmp/pfile_bak.ora';
ORACLE instance started.
Total System Global Area 2522189824 bytes
Fixed Size 2230912 bytes
Variable Size 1157629312 bytes
Database Buffers 1342177280 bytes
Redo Buffers 20152320 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '+DG_DATA001/mydbtst/datafile/system.453.813666469'
SYS@mydbtst> recover database using backup controlfile;
ORA-00279: change 9436796441761 generated at 08/01/2014 10:07:10 needed for
thread 1
ORA-00289: suggestion : +FRA_SMALL_MDG
ORA-15173: entry 'ARCHIVELOG' does not exist in directory 'mydbtst'
ORA-00280: change 9436796441761 for thread 1 is in sequence #4 <<<<<<<需要sequence # 4的日志,查v$logv$logfile之后,确认哪个redolog放入
Specifylog: {<RET>=suggested filename AUTO CANCEL}
+DATA_SMALL_MDG/mydbtst/onlinelog/group_1.1156.854401821
Log applied.
Media recovery complete.
SYS@mydbtst>
SYS@mydbtst> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SYS@mydbtst> alter database open resetlogs;
Database altered.
SYS@mydbtst>
SYS@mydbtst>


3. 新建新的undo

SYS@mydbtst> create undo tablespace undo_new datafile '+DG_DATA001/mydbtst/datafile/undo_new01.dbf' size 200m;
Tablespace created.
SYS@mydbtst>


4. 检查UNDOTBS1的undo segment,幸运的是,没有发现needs recovery的undo segment,所以后续也不用隐含参数”_corrupted_rollback_segments”跳过need recovery的undo segment来重启了。

SYS@mydbtst> select tablespace_name,segment_name,status from dba_rollback_segs;
TABLESPACE_NAME                SEGMENT_NAME                   STATUS
------------------------------ ------------------------------ ----------------
SYSTEM                         SYSTEM                         ONLINE
UNDOTBS1                       _SYSSMU1_3981220827$           OFFLINE
UNDOTBS1                       _SYSSMU2_2541240231$           OFFLINE
UNDOTBS1                       _SYSSMU3_4103266798$           OFFLINE
UNDOTBS1                       _SYSSMU4_1110676785$           OFFLINE
UNDOTBS1                       _SYSSMU5_3829116805$           OFFLINE
UNDOTBS1                       _SYSSMU6_347720470$            OFFLINE
UNDOTBS1                       _SYSSMU7_3507999319$           OFFLINE
UNDOTBS1                       _SYSSMU8_3681584916$           OFFLINE
UNDOTBS1                       _SYSSMU9_630455542$            OFFLINE
UNDOTBS1                       _SYSSMU10_2221096320$          OFFLINE
……
TABLESPACE_NAME                SEGMENT_NAME                   STATUS
------------------------------ ------------------------------ ----------------
UNDO_NEW                       _SYSSMU110_852046607$          OFFLINE
UNDO_NEW                       _SYSSMU111_1868020771$         OFFLINE
112 rows selected.
SYS@mydbtst>


5. 由于不需要隐含参数跳过,可以直接drop原来的undo:

SYS@mydbtst> drop tablespace UNDOTBS1 including contents and datafiles;
Tablespace dropped.


6. 修改pfile为auto和新的undo_new

cnsz181007:mydbtst > vi pfile_bak.ora
……
*.streams_pool_size=134217728
*.undo_retention=3600
*.undo_tablespace='undo_new'
*.undo_management='auto'
~


7. 用该pfile重启:

cnsz181007:mydbtst > sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.3.0 Production on Fri Aug 1 11:59:56 2014
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to an idle instance.
SYS@mydbtst> startup pfile='/tmp/pfile_bak.ora';
ORACLE instance started.
Total System Global Area 2522189824 bytes
Fixed Size                  2230912 bytes
Variable Size            1157629312 bytes
Database Buffers         1342177280 bytes
Redo Buffers               20152320 bytes
Database mounted.
Database opened.
SYS@mydbtst>


--转自 北京联动北方科技有限公司




赞(0)    操作        顶端 
联动大白
注册用户
等级:列兵
经验:91
发帖:0
精华:0
注册:2015-5-27
状态:离线
发送短消息息给联动大白 加好友    发送短消息息给联动大白 发消息
发表于: IP:您无权察看 2019-7-19 0:30:00 | [全部帖] [楼主帖] 2  楼

为了方便大家阅读,我对文章中错误号来解释一下吧!

Error Id: ORA-00279

Title: change string generated at string needed for thread string

Description:

change string generated at string needed for thread string

Action:

Please supply the requested log with "ALTER DATABASE RECOVER LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER CANCEL".

Cause:

The requested log is required to proceed with recovery.


Error Id: ORA-00280

Title: change string for thread string is in sequence #string

Description:

change string for thread string is in sequence #string

Action:

Use the information provided in this message to specify the required archived redo log files for other errors.

Cause:

This message helps to locate the redo log file with the specified change number requested by other messages.


Error Id: ORA-00289

Title: suggestion : string

Description:

suggestion : string

Action:

Consider using this filename for the next log needed for recovery.

Cause:

This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.


Error Id: ORA-00600

Title: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Description:

internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Action:

Report as a bug - the first argument is the internal error number

Cause:

This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition.


Error Id: ORA-01092

Title: ORACLE instance terminated. Disconnection forced

Description:

ORACLE instance terminated. Disconnection forced

Action:

Examine the alert log for more details. When the instance has been restarted, retry action.

Cause:

The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance.


Error Id: ORA-01110

Title: data file string: ’string’

Description:

data file string: ’string’

Action:

See associated error message

Cause:

Reporting file name for details of another error


Error Id: ORA-01113

Title: file string needs media recovery

Description:

file string needs media recovery

Action:

First apply media recovery to the file.

Cause:

An attempt was made to online or open a database with a file that is in need of media recovery.


Error Id: ORA-01589

Title: must use RESETLOGS or NORESETLOGS option for database open

Description:

must use RESETLOGS or NORESETLOGS option for database open

Action:

Specify the appropriate option.

Cause:

Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.


Error Id: ORA-15173

Title: entry ’string’ does not exist in directory ’string’

Description:

entry ’string’ does not exist in directory ’string’

Action:

Correct the alias path and try again.

Cause:

The specified alias did not exist in the given directory.


也许你已明白,但对一个人有用也是我存在的理由!^_^ By:持之以恒的大白

-- 来自: 北京联动北方科技有限公司



赞(0)    操作        顶端 
总帖数
2
每页帖数
101/1页1
返回列表
发新帖子
请输入验证码: 点击刷新验证码
您需要登录后才可以回帖 登录 | 注册
技术讨论