oracle 00283,案例解决：一次oracle掉电的处理过程[转]

最新推荐文章于 2024-02-03 22:13:26 发布
最新推荐文章于 2024-02-03 22:13:26 发布
阅读量338 收藏
点赞数
文章标签： oracle 00283

来源： www.ixdba.net 作者：

Oracle+Linux专业技术门户 时间：2008-01-20

年关事情多，最近设备运行极度不正常，好像是过年了，也想罢工休息一样！昨日一台oracle

db主板坏掉，数据库也随之崩溃，oracle服务器重启后，无法open，以下是恢复过程！

/home/oracle$sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 1月 18 15:50:26

2008

Copyright (c) 1982, 2005, Oracle. All rights

reserved.

Connected to an idle instance.

SQL> startup

ORACLE instance started.

Total System Global Area 616562688 bytes

Fixed

Size 1220868 bytes

IXDBA.NET技术社区

Variable

Size 167775996 bytes

Database

Buffers 440401920 bytes

Redo

Buffers 7163904 bytes

Database mounted.

ORA-01589: must use RESETLOGS or NORESETLOGS option for database

open

SQL>

检查alter日志，发现如下错误：

Fri Jan 18 09:57:19 2008

ALTER DATABASE

RECOVER LOGFILE '/opt/oracle/oradata/oradb/redo03.log'

Fri Jan 18 09:57:19 2008

Media Recovery Log /opt/oracle/oradata/oradb/redo03.log

Fri Jan 18 09:57:19 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_p002_6556.trc:

ORA-00600: internal error code, arguments: [kddummy_blkchk],

[1], [4099], [6101], [], [], [], []

Fri Jan 18 09:57:19 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_p000_6552.trc:

ORA-00600: internal error code, arguments: [kddummy_blkchk],

[1], [3770], [6255], [], [], [], []

Fri Jan 18 09:57:19 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_p002_6556.trc:

ORA-10562: Error occurred while applying redo to data block

(file# 1, block# 4099)

ORA-10564: tablespace SYSTEM

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data

object# 517

ORA-00607: Internal error occurred while making a change to a

data block

ORA-00600: internal error code, arguments: [kddummy_blkchk],

[1], [4099], [6101], [], [], [], []

Fri Jan 18 09:57:20 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_p000_6552.trc:

ORA-10562: Error occurred while applying redo to data block

(file# 1, block# 3770)

ORA-10564: tablespace SYSTEM

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data

object# 482

ORA-00607: Internal error occurred while making a change to a

data block

ORA-00600: internal error code, arguments: [kddummy_blkchk],

[1], [3770], [6255], [], [], [], []

Recovery interrupted!

Recovered data files to a consistent state at change 2433115

Fri Jan 18 09:57:24 2008

Media Recovery failed with error 12801

ORA-283 signalled during: ALTER DATABASE

RECOVER LOGFILE '/opt/oracle/oradata/oradb/redo03.log' ...

Fri Jan 18 09:57:24 2008

ALTER DATABASE RECOVER CANCEL

ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...

Shutting down instance: further logons disabled

初步断定是当前redo由于突然断电造成损坏，重启db后，造成系统表空间不一致，db无法起动。

经过询问和检查，数据库没有备份，并且处于非归档模式。

解决办法只有一个加上隐含参数起动试试！

_ALLOW_RESETLOGS_CORRUPTION = TRUE

SQL> show parameter spfile

NAME TYPE VALUE

-------------------- ----------------

---------------------

spfile string /opt/oracle/product/10.2.0.1/d

b_1/dbs/spfileoradb.ora

SQL> show parameter '_all'*

NAME TYPE

------------------------------------ ----------------------

VALUE

------------------------------

_allow_resetlogs_corruption boolean

FALSE

fast_start_parallel_rollback string

LOW

parallel_adaptive_multi_user boolean

TRUE

parallel_automatic_tuning boolean

FALSE

parallel_execution_message_size integer

NAME TYPE

------------------------------------ ----------------------

VALUE

------------------------------

2148

parallel_instance_group string

parallel_max_servers

integer

80

parallel_min_percent integer

0

parallel_min_servers integer

0

NAME TYPE

------------------------------------ ----------------------

VALUE

------------------------------

parallel_server boolean

FALSE

parallel_server_instances integer

1

parallel_threads_per_cpu integer

2

recovery_parallelism integer

0

SQL>

SQL> select status,name from

v$datafile;

STATUS

--------------

NAME

--------------------------------------------------------------------------------

SYSTEM

/opt/oracle/oradata/oradb/bak/system01.dbf

RECOVER

/opt/oracle/oradata/oradb/undotbs01.dbf

RECOVER

/opt/oracle/oradata/oradb/sysaux01.dbf

STATUS

--------------

NAME

--------------------------------------------------------------------------------

RECOVER

/opt/oracle/oradata/oradb/users01.dbf

RECOVER

/opt/oracle/oradata/oradb/tools01.dbf

RECOVER

/opt/oracle/oradata/oradb/indx01.dbf

STATUS

--------------

NAME

--------------------------------------------------------------------------------

RECOVER

/opt/oracle/oradata/oradb/cicrodb.dbf

7 rows selected.

SQL> recover database;

ORA-00283: recovery session canceled due to errors

ORA-01610: recovery using the BACKUP CONTROLFILE option must be

done

SQL> recover database using BACKUP CONTROLFILE;

ORA-00279: change 2433115 generated at 01/17/2008 04:00:40

needed for thread 1

ORA-00289: suggestion :

/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc

ORA-00280: change 2433115 for thread 1 is in sequence #42

Specify log: {=suggested |

filename | AUTO | CANCEL}

auto

ORA-00308: cannot open archived log

'/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc'

ORA-27037: unable to obtain file status

Linux Error: 2: No such file or directory

Additional information: 3

ORA-00308: cannot open archived log

'/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc'

ORA-27037: unable to obtain file status

Linux Error: 2: No such file or directory

Additional information: 3

SQL> recover database

using BACKUP CONTROLFILE;

ORA-00279: change 2433115 generated at 01/17/2008 04:00:40

needed for thread 1

ORA-00289: suggestion :

/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc

ORA-00280: change 2433115 for thread 1 is in sequence #42

Specify log: {=suggested |

filename | AUTO | CANCEL}

cancel

Media recovery cancelled.

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-01589: must use RESETLOGS or NORESETLOGS option for database

open

SQL> alter database open resetlogs;

alter database open resetlogs

*

ERROR at line 1:

ORA-01113: file 1 needs media recovery

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

上面显示系统表空间需要恢复

SQL> recover datafile 1;

ORA-00283: recovery session canceled due to errors

ORA-01610: recovery using the BACKUP CONTROLFILE option must be

done

SQL> recover database

using BACKUP CONTROLFILE until

cancel;

ORA-00279: change 2433115 generated at 01/17/2008 04:00:40

needed for thread 1

ORA-00289: suggestion :

/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc

ORA-00280: change 2433115 for thread 1 is in sequence #42

Specify log: {=suggested |

filename | AUTO | CANCEL}

cancel

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would

get error below

ORA-01194: file 1 needs more recovery to be consistent

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

ORA-01112: media recovery not started

SQL> alter database open

resetlogs;

alter database open resetlogs

*

ERROR at line 1:

ORA-01194: file 1 needs more recovery to be

consistent

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

仍然提示要恢复系统表空间！

SQL> recover datafile 1;

ORA-00283: recovery session canceled due to errors

ORA-01610: recovery using the BACKUP CONTROLFILE option must be

done

加入隐含参数！

SQL> alter system set

"_allow_resetlogs_corruption"=true scope=spfile;

System altered.

SQL> shutdown immediate

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

SQL> quit

Disconnected from Oracle Database 10g Enterprise Edition Release

10.2.0.1.0 - Production

With the Partitioning, OLAP and Data Mining options

/home/oracle$sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 1月 18 15:56:44

2008

Copyright (c) 1982, 2005, Oracle. All rights

reserved.

Connected to an idle instance.

SQL> startup mount

ORACLE instance started.

Total System Global Area 616562688 bytes

Fixed

Size 1220868 bytes

Variable

Size 167775996 bytes

Database

Buffers 440401920 bytes

Redo

Buffers 7163904 bytes

Database mounted.

SQL> select name,status from

v$datafile;

NAME

--------------------------------------------------------------------------------

STATUS

--------------

/opt/oracle/oradata/oradb/bak/system01.dbf

SYSTEM

/opt/oracle/oradata/oradb/undotbs01.dbf

RECOVER

/opt/oracle/oradata/oradb/sysaux01.dbf

RECOVER

NAME

--------------------------------------------------------------------------------

STATUS

--------------

/opt/oracle/oradata/oradb/users01.dbf

RECOVER

/opt/oracle/oradata/oradb/tools01.dbf

RECOVER

/opt/oracle/oradata/oradb/indx01.dbf

RECOVER

NAME

--------------------------------------------------------------------------------

STATUS

--------------

/opt/oracle/oradata/oradb/cicrodb.dbf

RECOVER

7 rows selected.

SQL> recover database;

ORA-00283: recovery session canceled due to errors

ORA-01610: recovery using the BACKUP CONTROLFILE option must be

done

SQL> recover database using backup

controlfile until cancel;

ORA-00279: change 2433115 generated at 01/17/2008 04:00:40

needed for thread 1

ORA-00289: suggestion :

/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc

ORA-00280: change 2433115 for thread 1 is in sequence #42

Specify log: {=suggested |

filename | AUTO | CANCEL}

auto

ORA-00308: cannot open archived log

'/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc'

ORA-27037: unable to obtain file status

Linux Error: 2: No such file or directory

Additional information: 3

ORA-00308: cannot open archived log

'/opt/oracle/flash_recovery_area/ORADB/archivelog/2008_01_18/o1_mf_1_42_%u_.arc'

ORA-27037: unable to obtain file status

Linux Error: 2: No such file or directory

Additional information: 3

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would

get error below

ORA-01194: file 1 needs more recovery to be consistent

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-01589: must use RESETLOGS or NORESETLOGS option for database

open

SQL> alter database open

RESETLOGS;

此时，系统好像hang住了一样，很长一段时间没有反映，过了一会，报错如下！

alter database open RESETLOGS

*

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

此时查看alter日志信息：又出现2662错误，

Errors in file

/opt/oracle/admin/oradb/udump/oradb_ora_10369.trc:

ORA-00600: internal error code, arguments: [2662], [0],

[2433141], [0], [2443300], [12595947], [], []

Fri Jan 18 15:58:21 2008

Errors in file

/opt/oracle/admin/oradb/udump/oradb_ora_10369.trc:

ORA-00600: internal error code, arguments: [2662], [0],

[2433141], [0], [2443300], [12595947], [], []

Fri Jan 18 15:58:21 2008

Error 600 happened during db open, shutting down database

USER: terminating instance due to error 600

Instance terminated by USER, pid = 10369

ORA-1092 signalled during: alter database open RESETLOGS...

SQL>

SQL> quit

Disconnected from Oracle Database 10g Enterprise Edition Release

10.2.0.1.0 - Production

With the Partitioning, OLAP and Data Mining options

再次重启登录：

/home/oracle$sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 1月 18 15:58:56

2008

Copyright (c) 1982, 2005, Oracle. All rights

reserved.

Connected to an idle instance.

SQL> startup

ORACLE instance started.

Total System Global Area 616562688 bytes

Fixed

Size 1220868 bytes

Variable

Size 167775996 bytes

Database

Buffers 440401920 bytes

Redo

Buffers 7163904 bytes

Database mounted.

ORA-01113: file 1 needs media recovery

ORA-01110: data file 1:

'/opt/oracle/oradata/oradb/bak/system01.dbf'

SQL> recover database;

Media recovery complete.

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-00603: ORACLE server session terminated by fatal

error

检查日志如下：爽呀，又出现了ORA-00600 中的4194错误，

Database Characterset is UTF8

Fri Jan 18 16:00:14 2008

Errors in file

/opt/oracle/admin/oradb/udump/oradb_ora_10443.trc:

ORA-00600: internal error code, arguments: [4194], [38], [34],

[], [], [], [], []

Fri Jan 18 16:00:14 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_smon_10429.trc:

ORA-00600: internal error code, arguments: [4194], [59], [57],

[], [], [], [], []

Doing block recovery for file 2 block 1135

Block recovery from logseq 2, block 43 to scn 2453192

Fri Jan 18 16:00:15 2008

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem

0

Mem# 0 errs 0:

/opt/oracle/oradata/oradb/redo01.log

Fri Jan 18 16:00:15 2008

Doing block recovery for file 2 block 281

Block recovery from logseq 2, block 45 to scn 2453193

Fri Jan 18 16:00:15 2008

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem

0

Mem# 0 errs 0:

/opt/oracle/oradata/oradb/redo01.log

Fri Jan 18 16:00:15 2008

Block recovery stopped at EOT rba 2.47.16

Block recovery completed at rba 2.47.16, scn 0.2453190

Fri Jan 18 16:00:15 2008

Block recovery stopped at EOT rba 2.47.16

Block recovery completed at rba 2.47.16, scn 0.2453190

Fri Jan 18 16:00:15 2008

Doing block recovery for file 2 block 153

Block recovery from logseq 2, block 43 to scn 2453187

Fri Jan 18 16:00:15 2008

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem

0

Mem# 0 errs 0:

/opt/oracle/oradata/oradb/redo01.log

Fri Jan 18 16:00:15 2008

Doing block recovery for file 2 block 105

Block recovery from logseq 2, block 45 to scn 2453189

Fri Jan 18 16:00:15 2008

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem

0

Mem# 0 errs 0:

/opt/oracle/oradata/oradb/redo01.log

Fri Jan 18 16:00:15 2008

Block recovery completed at rba 2.45.16, scn 0.2453189

Fri Jan 18 16:00:15 2008

Block recovery completed at rba 2.47.16, scn 0.2453190

Fri Jan 18 16:00:15 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_smon_10429.trc:

ORA-00604: error occurred at recursive SQL level 1

ORA-00607: Internal error occurred while making a change to a

data block

ORA-00600: internal error code, arguments: [4194], [59], [57],

[], [], [], [], []

Fri Jan 18 16:00:15 2008

Errors in file

/opt/oracle/admin/oradb/udump/oradb_ora_10443.trc:

ORA-00600: internal error code, arguments: [4193], [688],

[1013], [], [], [], [], []

Fri Jan 18 16:00:15 2008

DEBUG: Replaying xcb 0x43625908, pmd 0x4379add8 for failed op

8

Doing block recovery for file 2 block 612

No block recovery was needed

Fri Jan 18 16:00:16 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_smon_10429.trc:

ORA-00600: internal error code, arguments: [4194], [58], [56],

[], [], [], [], []

Fri Jan 18 16:00:17 2008

Doing block recovery for file 2 block 930

Block recovery from logseq 2, block 47 to scn 2453198

Fri Jan 18 16:00:17 2008

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem

0

Mem# 0 errs 0:

/opt/oracle/oradata/oradb/redo01.log

Block recovery stopped at EOT rba 2.48.16

Block recovery completed at rba 2.48.16, scn 0.2453197

Doing block recovery for file 2 block 9

Block recovery from logseq 2, block 47 to scn 2453196

Fri Jan 18 16:00:18 2008

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2 Reading mem

0

Mem# 0 errs 0:

/opt/oracle/oradata/oradb/redo01.log

Block recovery completed at rba 2.48.16, scn 0.2453197

Fri Jan 18 16:00:18 2008

Errors in file

/opt/oracle/admin/oradb/bdump/oradb_smon_10429.trc:

ORA-01595: error freeing extent (2) of rollback segment

(1))

ORA-00607: Internal error occurred while making a change to a

data block

ORA-00600: internal error code, arguments: [4194], [58], [56],

[], [], [], [], []

4149错误一般根undo有关系，因为当前redo损坏，undo数据也大都不一致了。

设置隐含参数：将undo改变成手工管理的，然后重启数据库。

/home/oracle$sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.1.0 - Production on

Copyright (c) 1982, 2005, Oracle. All rights

reserved.

Connected to an idle instance.

SQL> startup mount

ORACLE instance started.

Total System Global Area 616562688 bytes

Fixed

Size 1220868 bytes

Variable

Size 167775996 bytes

Database

Buffers 440401920 bytes

Redo

Buffers 7163904 bytes

Database mounted.

SQL> show parameter undo

NAME TYPE

------------------------------------ ----------------------

VALUE

------------------------------

undo_management string

AUTO

undo_retention

integer

900

undo_tablespace string

UNDOTBS1

SQL> alter system set

undo_management='manual' scope=spfile;

System altered.

然后重启数据库

SQL> shutdown immediate

ORA-01109: database not open

Database dismounted.

ORACLE instance shut down.

SQL> quit

Disconnected from Oracle Database 10g Enterprise Edition Release

10.2.0.1.0 - Production

With the Partitioning, OLAP and Data Mining options

/home/oracle$sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.1.0 - Production on 星期五 1月 18 16:13:22

2008

Copyright (c) 1982, 2005, Oracle. All rights

reserved.

Connected to an idle instance.

SQL> startup mount

ORACLE instance started.

Total System Global Area 616562688 bytes

Fixed

Size 1220868 bytes

Variable Size 167775996

bytes

Database

Buffers 440401920 bytes

Redo

Buffers 7163904 bytes

Database mounted.

SQL> col name format a30

SQL> select status,name from v$datafile;

STATUS NAME

--------------

------------------------------

SYSTEM /opt/oracle/oradata/oradb/bak/system01.dbf

ONLINE /opt/oracle/oradata/oradb/undotbs01.dbf

ONLINE /opt/oracle/oradata/oradb/sysaux01.dbf

ONLINE /opt/oracle/oradata/oradb/users01.dbf

STATUS NAME

--------------

------------------------------

ONLINE /opt/oracle/oradata/oradb/tools01.dbf

ONLINE /opt/oracle/oradata/oradb/indx01.dbf

ONLINE /opt/oracle/oradata/oradb/cicrodb.dbf

7 rows selected.

SQL> show parameter undo

NAME TYPE

------------------------------------ ----------------------

VALUE

------------------------------

undo_management string

MANUAL

undo_retention integer

900

undo_tablespace string

UNDOTBS1

SQL> alter database open;

Database altered.

SQL> !top

正常起动！

总结：

系统掉电一般引起redo损坏，最糟糕的就是引起当前redo损坏，针对当前redo损坏，又没有备份，数据库处于非归档模式时，只能通过加入隐含参数方式恢复！

一般步骤如下：

1：首先加入_ALLOW_RESETLOGS_CORRUPTION =

TRUE隐含参数，最后resetlogs打开数据库，如果无法打开，进入第二步。

2：查看日志信息，根据具体报错信息，确认方法，本例是出现ORA-00600:

internal error code, arguments: [2662], [0], [2433141], [0],

[2443300], [12595947], [], []，

ORA-600 [2662] "Block SCN is ahead of Current

SCN"，说明当前数据库的数据块的SCN早于当前的SCN，主要是和存储在UGA变量中的dependent

SCN进行比较，如果当前的SCN小于它，数据库就会产生这个ORA-600

[2662]的错误了.于是想到使用ADJUST_SCN事件来调整当前的SCN，使其大于dependent SCN.

此时我们可以通过Oracle的内部事件来调整SCN:

解决这个问题一般方法是：

调整SCN有两种常用方法:

1.通过immediate trace

name方式(在数据库Open状态下，即通过用_allow_resetlogs_corruption=TRUE隐含参数打开数据库之后报错600)

alter session set events 'IMMEDIATE trace name ADJUST_SCN level

x';

2.通过10015事件(在数据库无法打开，mount状态下)

alter session set events '10015 trace name adjust_scn level

x';注:level 1为增进SCN 10亿 (1 billion)

(1024*1024*1024),通常Level 1已经足够。也可以根据实际情况适当调整。

本文通过此种方法设置无效，scn没有得到提升！

3：一般情况下redo损坏的时候，undo数据也大都不一致，因此通过scn调整完毕，resetlogs数据库后还会出现ORA-00600:

internal error code, arguments:

[4194]错误，这个错误可以通过设置undo解决：

设置隐含参数：_corrupted_rollback_segments

将undo改变成手工管理的，然后重启数据库，

本例只是将undo改变成手工管理，问题解决。

weixin_39785081
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
oracle ora 00283,数据库出现ORA-00283/ORA-01610的问题
weixin_30775883的博客
04-04 3182
==================================================================================================问题应该是控制文件中的检查点信息与system01没有保持一致的原因，但不知如何去恢复问题描述：第一步：在做试验的过程中，先shutdown abort数据库SQL> shutdown abort;...
ORACLE 19c rman恢复 ORA-00283 ORA-01610 错误处理
拦不住的博客
10-30 2175
ORACLE 19c rman恢复 ORA-00283 ORA-01610 错误处理
Oracle:ORA-00283: recovery session canceled due to errors
weixin_42161670的博客
01-16 8207
我做了一个这样的实验：归档模式下进行手工热备并进行还原恢复，结果将数据文件还原后，却报出了如下错误：Oracle:ORA-00283: recovery session canceled due to errors，因此开始了艰辛的排错历程 首先看一下我做了哪些事： ※ 开启归档模式 ※ 向scott用户中的A表插入一条数据并提交，插入第二条数据未提交 ※ alter database begin...
从ORA-00283 ORA-16433报错开始恢复---惜分飞
02-03 728
接手一个客户无法正常启动的故障数据库，尝试recover 报ORA-00283 ORA-16433错误。由于redo和数据文件不匹配,无法正常recover库,尝试强制打开库报ORA-600 2662错误。第一次通过其他方法处理,由于计算失误导致数据库启动报ORA-600 2252错误。处理正确的scn值之后,数据库open成功,然后逻辑方式导出数据,恢复工作完成。通过对控制文件进行处理,再次尝试recover库。基于这种错误,尝试oradebug修改scn。
数据库出现ORA-00283/ORA-01610的问题
zidielang的专栏
03-31 965
================================================================================================== 问题应该是控制文件中的检查点信息与system01没有保持一致的原因，但不知如何去恢复 问题描述： 第一步： 在做试验的过程中，先shutdown abort数据库 SQL> shutdown ...
oracle 00283,oracle数据库恢复报ORA-00283，ORA-01610错误原因
weixin_39733232的博客
04-03 531
可能很多人在做数据库恢复时，都遇到过如下错误：SQL> recover database;ORA-00283: recovery session canceled due to errorsORA-01610: recovery using the BACKUP CONTROLFILE option must be done对于这个错误的处理方法很简单，相信大家都知道：(只要加上using ...
案例解决：一次oracle掉电的处理过程
04-22
在本案例中，我们遇到了一个Oracle数据库在服务器主板故障后无法正常启动的问题。数据库在重启后尝试打开时，出现了ORA-01589错误，提示必须使用RESETLOGS或NORESETLOGS选项进行数据库打开。这通常意味着数据库在...
oracle案例：VC下的Oracle数据库读写操作案例
最新发布
05-28
本案例将深入探讨如何在VC环境下进行Oracle数据库的读写操作，帮助开发者更好地理解和应用相关技术。 首先，要进行Oracle数据库操作，我们需要安装Oracle的客户端软件，如Instant Client，它包含了连接数据库所需的...
118个真实应用场景的Oracle存储过程案例及开发指南(从入门到熟练使用)
04-17
1、资料包含了作者编写的实际应用场景中使用的存储过程代码，共计118个案例，有完整注释说明。旨在帮助读者通过案例学习，快速掌握存储过程的应用方法和技巧。 2、博主博客：...
润乾报表调用oracle存储过程案例说明
03-15
在实际的业务场景中，有时我们需要调用数据库中的存储过程来获取或处理数据，本篇将详细介绍如何在润乾报表中调用Oracle存储过程。 首先，我们要在Oracle数据库中创建存储过程。以下是一个简单的存储过程示例，名为...
记一次Oracle数据恢复过程
12-16
本文以一个实际的Oracle数据库恢复案例为背景，探讨了如何处理数据错误并进行恢复的过程，涉及的知识点主要包括Oracle的数据恢复技术、Flashback Query、RMAN备份以及Log Miner。 首先，错误的源头是一个不严谨的...
oracle 00283,oracle控制文件的备份与恢复
weixin_34177601的博客
04-03 434
一、控制文件的定义控制文件是一个非常小的文件，最多能增长到64M左右，它包含其它数据库文件需要的目录。参数文件向实例提供控制文件的位置，控制文件向实例提供数据库文件和联机重做日志文件的具体信息。控制文件也包含数据库的一些其它信息，例如检查点发生的位置，数据库的名称，数据库创建的时间，归档日志的历史记录，RMAN的信息等。控制文件应该采用多路复用技术进行保护，应该copy多份，拷贝的文件应该分散在多...
oracle数据库恢复报ORA-00283，ORA-01610错误原因
热门推荐
渔夫数据库笔记
06-26 4万+
可能很多人在做数据库恢复时，都遇到过如下错误： SQL> recover database; ORA-00283: recovery session canceled due to errors ORA-01610: recovery using the BACKUP CONTROLFILE option must be done   对于这个错误的处理方法很简单，相信大家都知道：(只要加上u
oracle 00283,ORA-00283: recovery session canceled due to errors
weixin_42647395的博客
04-03 1592
某客户的核心数据库存储问题导致数据库重启后无法正常启动，根据客户反馈最开始在启动数据库时报错控制文件IO错误，如下：Sun Mar 15 11:59:37 2015Errors in file /oracle/app1/oracle/admin/xxxx/bdump/xxxx2_arc1_630876.trc:ORA-00204: error in reading (block 1, # bloc...
ORA-00283 & ORA-01610 的处理方法
shenghuiping2001的专栏
12-15 1万+
SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/u02/sheng/SYSTEM01.DBF' SQL>
RMAN备份恢复时报错ORA-00283 ORA-01610 ORA-00279 ORA-00289 ORA-00280 ORA-01194 ORA-01110
m0_49562857的博客
10-25 590
源库导出时为open状态就会导致此问题，要追平归档才能正常起库，为了避免不必要的麻烦，将源库为mount状态下再导出。在使用rman导出数据时，源库是open状态，会一直在写入归档，导入的时候scn不一致，就会导致以上报错。此案例只涉及以上报错，起库前注意数据文件，归档文件的路径是否正确。也就是说，目标库要先追平源库的归档日志，才能正常起库。
oracle 00283,【Oracleデータリカバリ】ORA-00283エラ
weixin_33592736的博客
04-03 183
プロのOracle Databaseの復旧サービスを提供携帯番号： +86 13764045638 メール：service@parnassusdata.comストレージがアクセス出来ないから、データベースがシャットダウンした。データベースを再起動したが、まともに起動出来ない。データベースがmountできるが、起動出来ない。ファイル3(sysaux01.dbf)がこわれたと気づき、メディアリカバリが...
oracle 00283,ORA-00283 – 专业Oracle数据库恢复，或许是您恢复数据的最后机会@phone:13429648788 - 专业Oracle数据库恢复技术支持...
weixin_42534103的博客
04-03 488
接到网友技术支持请求,win 2003 ntfs格式文件系统,Oracle 8.1.7版本,主机重启后,数据库无法正常启动,offline datafile 15,数据库open成功,但是datafile 无法正常online,报错为:ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file,请求协助处理SQL> ...
ora-00283
csnd2020的博客
04-26 319
问题描述：SQL> show user;USER is "SYS"SQL> recover datafile 9;ORA-00283: recovery session canceled due ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值