搜索
首页数据库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
相关文章
修复在 Windows 10/11 中设备禁用（错误代码 22）的方法修复在 Windows 10/11 中设备禁用（错误代码 22）的方法Aug 04, 2023 pm 03:17 PM

设备管理器中的“此设备已禁用”代码22错误是否阻止您在PC上使用新设备或旧设备？不用担心，因为我们在这里帮助您解决此问题。代码22错误意味着设备已被手动禁用，有时重新启用它无济于事。无论原因是什么，这里有10种方法可以修复Windows22/PC上的“此设备已禁用”代码10错误并使该硬件再次工作。1.拔下并重新插入新硬件您插入PC的新硬件可能会在快速卸下并重新安装后重新开始工作。因此，如果它是通过USB插入的设备，请继续拔下它。然后，等待几秒钟，然后重新插入。现在，检查设备是否显示在设备管理器中

重新安装 Safari 的 8 种方法，适用于 iPhone重新安装 Safari 的 8 种方法，适用于 iPhoneSep 16, 2023 am 11:17 AM

网页浏览是移动设备的基本功能，浏览器可以有效地促进它。这些浏览器还支持安装内容拦截器和其他工具，以个性化您的浏览体验。苹果的iOS平台使用Safari作为其默认浏览器。在极少数情况下，您可能会发现Safari浏览器从您的设备中丢失。如果遇到这种情况，以下步骤将指导您如何还原它。您可以在iPhone上重新安装Safari吗？Safari是iOS设备上的内置应用程序，由于其受保护的系统状态而无法删除或卸载。如果设备中似乎缺少该应用程序，则可能是您正在处理错误，或者该应用程序可能由于各种原因而被隐藏。

prru是什么设备prru是什么设备Apr 14, 2023 pm 04:59 PM

PRRU是指皮基站设备，是一种有源设备，是一种小型化、低功率、低功耗的室内覆盖射频单元，即一种室内基站。PRRU具备接收机和发射机两部分的功能，即都在远端将数字信号（先转换成中频信号）转换成射频信号，然后放大传送出去；或者接收天线收到的射频信号，转换成数字信号再传给基带处理单元。

修复：在 Windows 11 中无法在此设备上加载驱动程序修复：在 Windows 11 中无法在此设备上加载驱动程序Apr 15, 2023 pm 08:22 PM

驱动程序是促进操作系统和相应设备之间命令中继的关键软件。但是如果在Windows11中遇到Adrivercannotloadonthisdevice错误怎么办？您将在引导操作系统时看到此错误消息，其效果最初可能会或可能不会明显可见，具体取决于受影响的驱动程序。但是，随着时间的推移，驱动程序可能会停止与相应设备一起运行。因此，您必须对错误进行故障排除。此外，在大多数情况下，故障驱动程序会列在错误框中，便于您继续操作。如何修复Windows11中的A驱动程序无法在此设备上加载错误？1.

如何使用“隔空播放”流式传输视频或镜像 iPhone 或 iPad 屏幕如何使用“隔空播放”流式传输视频或镜像 iPhone 或 iPad 屏幕Jul 14, 2023 pm 07:53 PM

本快速指南将向您展示如何使用AirPlay，这是Apple的创新无线流媒体功能，可以轻松共享和显示内容。允许您使用Wi-Fi将iPhone或iPad连接到与AirPlay兼容的AppleTV、智能电视、扬声器和Mac以及某些第三方扬声器和智能电视，以实现无缝数据传输。“隔空播放”以点对点为基础运行，通过本地网络连接您的Apple设备。它使用多种技术的组合，包括用于流式传输音频和视频的实时传输协议（RTP）和用于设备发现的Bonjour。简而言之，当您使用“隔空播放”时，您的设备会发送数据流，然后

如何使用 Windows Copilot 打开暗模式、免打扰、管理蓝牙设备等如何使用 Windows Copilot 打开暗模式、免打扰、管理蓝牙设备等Aug 01, 2023 pm 09:58 PM

任何想要尽早了解Windows上AI未来的人都不需要再看Copilot预览。Copilot的功能很少，似乎只不过是侧面的BingAI任务栏，无疑是朝着正确方向前进的推动。即使是现在，用户也可以在浅色和深色主题之间切换，打开和关闭免打扰和蓝牙，并直接跳转到蓝牙设备设置页面来管理连接–所有这些都可以通过Copilot实现。以下是获取Windows11Copilot并完成所有这些操作的方法。如何在Windows11上启用Copilot要在Windows11上开始使用Copilot，

Tg7100c是什么设备Tg7100c是什么设备Mar 13, 2023 pm 03:11 PM

Tg7100c是智能新一代高集成Wi-Fi和BLE组合芯片，支持内部RTC时钟唤醒、外部中断唤醒，以达到低功耗睡眠唤醒机制。TG7100C搭载32位RISC-V处理器，配备2MB Flash/276KB RAM/EFuse存储资源，支持SDIO、SPI、UART、I2C、IR remote、PWM等外设接口；具有极简的电路设计，优异的射频性能，低功耗，宽工作温度等特点。

如何修复“iPhone不可用”消息如何修复“iPhone不可用”消息Sep 17, 2023 pm 09:25 PM

“iPhone不可用”安全功能如何操作？触发“iPhone不可用”消息的基本机制植根于系统设计的安全功能，该功能可跟踪每个不正确的密码条目。这种保护机制从第五次错误尝试解锁设备开始进入高速运转。一旦达到这个里程碑，iPhone就会设置一分钟的临时锁定期，在此期间，任何输入密码的额外尝试都将变得徒劳无功。此锁定持续时间不是静态的，而是遵循不断升级的模式。具体来说，在第五次密码尝试之后，每次后续错误密码尝试都会导致锁定计时器增加一分钟。例如，第六次错误尝试将导致2分钟锁定，第七次错误尝试将导致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脱衣机

AI Hentai Generator

AI Hentai Generator

免费生成ai无尽的。

显示更多

热门文章

R.E.P.O.能量晶体解释及其做什么（黄色晶体）
2 周前By尊渡假赌尊渡假赌尊渡假赌
仓库：如何复兴队友
4 周前By尊渡假赌尊渡假赌尊渡假赌
Hello Kitty Island冒险：如何获得巨型种子
3 周前By尊渡假赌尊渡假赌尊渡假赌
击败分裂小说需要多长时间？
3 周前ByDDD
R.E.P.O.保存文件位置：在哪里以及如何保护它？
3 周前ByDDD
显示更多

热工具

ZendStudio 13.5.1 Mac

ZendStudio 13.5.1 Mac

功能强大的PHP集成开发环境

适用于 Eclipse 的 SAP NetWeaver 服务器适配器

适用于 Eclipse 的 SAP NetWeaver 服务器适配器

将Eclipse与SAP NetWeaver应用服务器集成。

EditPlus 中文破解版

EditPlus 中文破解版

体积小，语法高亮，不支持代码提示功能

DVWA

DVWA

Damn Vulnerable Web App (DVWA) 是一个PHP/MySQL的Web应用程序，非常容易受到攻击。它的主要目标是成为安全专业人员在合法环境中测试自己的技能和工具的辅助工具，帮助Web开发人员更好地理解保护Web应用程序的过程，并帮助教师/学生在课堂环境中教授/学习Web应用程序安全。DVWA的目标是通过简单直接的界面练习一些最常见的Web漏洞，难度各不相同。请注意，该软件中

Atom编辑器mac版下载

Atom编辑器mac版下载

最流行的的开源编辑器

显示更多

热门话题

gmail邮箱登陆入口在哪里
7319
9
Java教程
1625
14
CakePHP 教程
1349
46
Laravel 教程
1261
25
PHP教程
1209
29
显示更多