搜索
首页数据库mysql教程裸设备权限导致的数据库部分数据库文件需要recover

裸设备权限导致的数据库部分数据库文件需要recover

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB
WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB
Jun 07, 2016 pm 03:35 PM
recover导致数据库文件权限设备部分需要

Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc: ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [113] ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=

Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [113]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [113] [/dev/rrlv_20g_data18]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (65, 12) on object 2854119.
Tue Jan 20 16:23:22 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [112]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [112] [/dev/rrlv_20g_data16]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (87, 27) on object 3036334.
Tue Jan 20 16:23:23 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [113]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [113] [/dev/rrlv_20g_data18]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (65, 12) on object 2854119.
Tue Jan 20 16:23:24 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [112]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [112] [/dev/rrlv_20g_data16]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (87, 27) on object 3036334.
Tue Jan 20 16:23:25 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [113]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [113] [/dev/rrlv_20g_data18]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (65, 12) on object 2854119.
Tue Jan 20 16:23:26 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [112]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [112] [/dev/rrlv_20g_data16]
Tue Jan 20 16:23:27 BEIST 2015
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (87, 27) on object 3036334.
Tue Jan 20 16:23:27 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [113]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [113] [/dev/rrlv_20g_data18]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (65, 12) on object 2854119.
Tue Jan 20 16:23:28 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [112]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [112] [/dev/rrlv_20g_data16]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (87, 27) on object 3036334.
Tue Jan 20 16:23:30 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [113]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [113] [/dev/rrlv_20g_data18]
ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (65, 12) on object 2854119.
Tue Jan 20 16:23:31 BEIST 2015
Errors in file /ora10g/admin/dqb/bdump/dqb1_smon_185150.trc:
ORA-00376: Message 376 not found; No message file for product=RDBMS, facility=ORA; arguments: [112]
ORA-01110: Message 1110 not found; No message file for product=RDBMS, facility=ORA; arguments: [112] [/dev/rrlv_20g_data16]

ORACLE Instance dqb1 (pid = 17) - Error 376 encountered while recovering transaction (87, 27) on object 3036334.



上述错误信息一直在后台报错，查询部分表报错，查询数据库的数据文件状态很多是offline状态。

SQL> select name ,status from v$datafile where status'ONLINE';


NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrac_system_1g
SYSTEM


/dev/rrlv_20g_data01
OFFLINE


/dev/rrlv_20g_data03
OFFLINE




NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrlv_20g_data04
OFFLINE


/dev/rrlv_20g_data05
OFFLINE


/dev/rrlv_20g_data06
OFFLINE




NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrlv_20g_data07
OFFLINE


/dev/rrlv_20g_data09
OFFLINE


/dev/rrlv_20g_data10
OFFLINE




NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrlv_20g_data11
OFFLINE


/dev/rrlv_20g_data12
OFFLINE


/dev/rrlv_20g_data13
OFFLINE




NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrlv_20g_data14
OFFLINE


/dev/rrac_20g20
SYSTEM


/dev/rrac_20g21
SYSTEM




NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrlv_20g_data15
OFFLINE


/dev/rrlv_20g_data17
OFFLINE


/dev/rrlv_20g_data16
OFFLINE




NAME
--------------------------------------------------------------------------------
STATUS
-------
/dev/rrlv_20g_data18
OFFLINE




19 rows selected.



仔细查看数据库日志发现，在1月12日做了表空间增加数据文件操作。


查看两个节点的数据文件权限

两个节点的裸设备都是这个样子

brw-rw----    1 root     system       83,  1 Feb 20 2014  /dev/rlv_20g_data01
brw-rw----    1 root     system       83,  2 Feb 20 2014  /dev/rlv_20g_data02
brw-rw----    1 root     system       83,  3 Feb 20 2014  /dev/rlv_20g_data03
brw-rw----    1 root     system       83,  4 Feb 20 2014  /dev/rlv_20g_data04
brw-rw----    1 root     system       83,  5 Feb 20 2014  /dev/rlv_20g_data05
brw-rw----    1 root     system       83,  6 Feb 20 2014  /dev/rlv_20g_data06
brw-rw----    1 root     system       83,  7 Feb 20 2014  /dev/rlv_20g_data07
brw-rw----    1 root     system       83,  8 Feb 20 2014  /dev/rlv_20g_data08
brw-rw----    1 root     system       83,  9 Feb 20 2014  /dev/rlv_20g_data09
brw-rw----    1 root     system       83, 10 Feb 20 2014  /dev/rlv_20g_data10
brw-rw----    1 root     system       83, 11 Feb 20 2014  /dev/rlv_20g_data11
brw-rw----    1 root     system       83, 12 Feb 20 2014  /dev/rlv_20g_data12
brw-rw----    1 root     system       83, 13 Feb 20 2014  /dev/rlv_20g_data13
brw-rw----    1 root     system       83, 14 Feb 20 2014  /dev/rlv_20g_data14
brw-rw----    1 root     system       83, 15 Feb 20 2014  /dev/rlv_20g_data15
brw-rw----    1 root     system       83, 16 Feb 20 2014  /dev/rlv_20g_data16
brw-rw----    1 root     system       83, 17 Feb 20 2014  /dev/rlv_20g_data17
brw-rw----    1 root     system       83, 18 Feb 20 2014  /dev/rlv_20g_data18
brw-rw----    1 root     system       83, 19 Feb 20 2014  /dev/rlv_20g_data19
brw-rw----    1 root     system       83, 20 Feb 20 2014  /dev/rlv_20g_data20



正确是以下：

crw-rw----    1 ora10g   dba          83,  1 Jan 20 08:19 /dev/rrlv_20g_data01
crw-rw----    1 ora10g   dba          83,  2 Jan 20 20:28 /dev/rrlv_20g_data02
crw-rw----    1 ora10g   dba          83,  3 Jan 20 08:19 /dev/rrlv_20g_data03
crw-rw----    1 ora10g   dba          83,  4 Jan 20 08:19 /dev/rrlv_20g_data04
crw-rw----    1 ora10g   dba          83,  5 Jan 20 08:19 /dev/rrlv_20g_data05
crw-rw----    1 ora10g   dba          83,  6 Jan 20 08:19 /dev/rrlv_20g_data06
crw-rw----    1 ora10g   dba          83,  7 Jan 20 08:19 /dev/rrlv_20g_data07
crw-rw----    1 ora10g   dba          83,  8 Jan 20 20:28 /dev/rrlv_20g_data08
crw-rw----    1 ora10g   dba          83,  9 Jan 20 08:19 /dev/rrlv_20g_data09
crw-rw----    1 ora10g   dba          83, 10 Jan 20 08:19 /dev/rrlv_20g_data10
crw-rw----    1 ora10g   dba          83, 11 Jan 20 08:19 /dev/rrlv_20g_data11
crw-rw----    1 ora10g   dba          83, 12 Jan 20 08:19 /dev/rrlv_20g_data12
crw-rw----    1 ora10g   dba          83, 13 Jan 20 08:19 /dev/rrlv_20g_data13
crw-rw----    1 ora10g   dba          83, 14 Jan 20 08:19 /dev/rrlv_20g_data14
crw-rw----    1 ora10g   dba          83, 15 Jan 20 08:19 /dev/rrlv_20g_data15
crw-rw----    1 ora10g   dba          83, 16 Jan 20 08:19 /dev/rrlv_20g_data16
crw-rw----    1 ora10g   dba          83, 17 Jan 20 08:19 /dev/rrlv_20g_data17
crw-rw----    1 ora10g   dba          83, 18 Jan 20 08:19 /dev/rrlv_20g_data18
crw-rw----    1 ora10g   dba          83, 19 Jan 20 20:28 /dev/rrlv_20g_data19
crw-rw----    1 ora10g   dba          83, 20 Jan 20 20:28 /dev/rrlv_20g_data20



这样子问题就清楚了，执行权限修改，后执行数据文件恢复

1、chown -R oracle;dba /dev/rrlv_20g_data*

2、停掉两个节点的数据库，启动第一个节点到mount，执行recover操作

[BEGIN] 2015-1-21 10:43:09
ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile       14;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER   datafile      17;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile     18;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER     datafile      19;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    21;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    22;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    23;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    26;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    29;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    55;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    103;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    104;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> RECOVER    datafile    112;
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:33 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92772_727466139.dbf
ORA-00280: change 14242805827356 for thread 2 is in sequence #92772




Specify log: {=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 14242805827356 generated at 01/20/2015 08:19:29 needed for
thread 1
ORA-00289: suggestion : +ARCH/archive/arch1/arch1_30832_727466139.dbf
ORA-00280: change 14242805827356 for thread 1 is in sequence #30832




ORA-00279: change 14242883477423 generated at 01/20/2015 08:23:26 needed for
thread 2
ORA-00289: suggestion : +ARCH/archive/arch1/arch2_92773_727466139.dbf
ORA-00280: change 14242883477423 for thread 2 is in sequence #92773
ORA-00278: log file '+ARCH/archive/arch1/arch2_92772_727466139.dbf' no longer
needed for this recovery




Log applied.
Media recovery complete.
SQL> alter database open;

最后成功执行。


声明
本文内容由网友自发贡献，版权归原作者所有，本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容，请联系admin@php.cn
相关文章
mysql blob：有什么限制吗？mysql blob：有什么限制吗？May 08, 2025 am 12:22 AM

mysqlblobshavelimits：tinyblob（255bytes），blob（65,535 bytes），中间布洛布（16,777,215个比例），andlongblob（4,294,967,967,295 bytes）.tousebl观察性：1）考虑performance impactsandSandStorelargeblobsextern; 2）管理backbackupsandreplication carecration; 3）usepathsinst

MySQL：自动化用户创建的最佳工具是什么？MySQL：自动化用户创建的最佳工具是什么？May 08, 2025 am 12:22 AM

自动化在MySQL中创建用户的最佳工具和技术包括：1.MySQLWorkbench，适用于小型到中型环境，易于使用但资源消耗大；2.Ansible，适用于多服务器环境，简单但学习曲线陡峭；3.自定义Python脚本，灵活但需确保脚本安全性；4.Puppet和Chef，适用于大规模环境，复杂但可扩展。选择时需考虑规模、学习曲线和集成需求。

mysql：我可以在斑点内搜索吗？mysql：我可以在斑点内搜索吗？May 08, 2025 am 12:20 AM

是的，YouCansearchInIdeAblobInMysqlusingsPecificteChniques.1）转换theblobtoautf-8StringWithConvertFunctionWithConvertFunctionandSearchusiseLike.2）forCompresseBlyblobs，useuncompresseblobs，useuncompressbeforeconversion.3）acpperformance impperformance imperformance imptactsanddataEccoding.4）

MySQL字符串数据类型：综合指南MySQL字符串数据类型：综合指南May 08, 2025 am 12:14 AM

mysqloffersvariousStringDatatYpes：1）charforfixed Lengtth Strings，IdealforConsistLengthDatalikeCountryCodes; 2）varcharforvariable长度长，合适的forfieldslikenames; 3）texttypefesforepesforlargertext，forforlargertext，goodforforblogblogpostsbutcan impactcuctcuctcuctpercrance; 4）biland;

掌握mysql blobs：逐步教程掌握mysql blobs：逐步教程May 08, 2025 am 12:01 AM

TomasterMySQLBLOBs,followthesesteps:1)ChoosetheappropriateBLOBtype(TINYBLOB,BLOB,MEDIUMBLOB,LONGBLOB)basedondatasize.2)InsertdatausingLOAD_FILEforefficiency.3)Storefilereferencesinsteadoffilestoimproveperformance.4)UseDUMPFILEtoretrieveandsaveBLOBsco

MySQL中的BLOB数据类型：开发人员的详细概述MySQL中的BLOB数据类型：开发人员的详细概述May 07, 2025 pm 05:41 PM

blobdatatypesinmysqlareusedforvorvoringlargebinarydatalikeimagesoraudio.1）useblobtypes（tinyblobtolonglongblob）基于dondatasizeneeds。 2）库孔素pet petooptimize绩效。3）考虑Xternal Storage Forel Blob romana databasesizerIndimprovebackupe

如何将用户从命令行添加到MySQL如何将用户从命令行添加到MySQLMay 07, 2025 pm 05:01 PM

toadDuserStomySqlfromtheCommandline，loginasroot，thenusecreateuser'username'@'host'host'Indessifiedby'password'; tocreateanewuser.grantpermissionswithgrantprantallprivilegesondatabase

MySQL中有哪些不同的字符串数据类型？详细的概述MySQL中有哪些不同的字符串数据类型？详细的概述May 07, 2025 pm 03:33 PM

mySqlofferSeightStringDatateTypes：char，varchar，二进制，二进制，varbinary，blob，文本，枚举，枚举和set.1）长度，理想的forconsistentDatatalIkeCountryCodes.2）varcharisvariable长度，长度，效率foriforitifforiticforiticforiticforiticforiticforitic forvaryingdatalikename.3）

See all articles

热AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智能驱动的应用程序，用于创建逼真的裸体照片

AI Clothes Remover

AI Clothes Remover

用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool

Undress AI Tool

免费脱衣服图片

Clothoff.io

Clothoff.io

AI脱衣机

Video Face Swap

Video Face Swap

使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸！

显示更多

热门文章

如何修复KB5055523无法在Windows 11中安装？
4 周前ByDDD
如何修复KB5055518无法在Windows 10中安装？
4 周前ByDDD
<🎜>：种植花园 - 完整的突变指南
2 周前ByDDD
<🎜>：泡泡胶模拟器无穷大 - 如何获取和使用皇家钥匙
3 周前By尊渡假赌尊渡假赌尊渡假赌
如何修复KB5055612无法在Windows 10中安装？
3 周前ByDDD
显示更多

热工具

mPDF

mPDF

mPDF是一个PHP库，可以从UTF-8编码的HTML生成PDF文件。原作者Ian Back编写mPDF以从他的网站上“即时”输出PDF文件，并处理不同的语言。与原始脚本如HTML2FPDF相比，它的速度较慢，并且在使用Unicode字体时生成的文件较大，但支持CSS样式等，并进行了大量增强。支持几乎所有语言，包括RTL（阿拉伯语和希伯来语）和CJK（中日韩）。支持嵌套的块级元素（如P、DIV），

记事本++7.3.1

记事本++7.3.1

好用且免费的代码编辑器

SublimeText3汉化版

SublimeText3汉化版

中文版，非常好用

安全考试浏览器

安全考试浏览器

Safe Exam Browser是一个安全的浏览器环境，用于安全地进行在线考试。该软件将任何计算机变成一个安全的工作站。它控制对任何实用工具的访问，并防止学生使用未经授权的资源。

SublimeText3 英文版

SublimeText3 英文版

推荐：为Win版本，支持代码提示！

显示更多

热门话题

Java教程
1663
14
CakePHP 教程
1420
52
Laravel 教程
1315
25
PHP教程
1266
29
C# 教程
1239
24
显示更多