搜尋
首頁資料庫mysql教程裸设备权限导致的数据库部分数据库文件需要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:初學者的基本技能MySQL:初學者的基本技能Apr 18, 2025 am 12:24 AM

MySQL適合初學者學習數據庫技能。 1.安裝MySQL服務器和客戶端工具。 2.理解基本SQL查詢,如SELECT。 3.掌握數據操作:創建表、插入、更新、刪除數據。 4.學習高級技巧:子查詢和窗口函數。 5.調試和優化:檢查語法、使用索引、避免SELECT*,並使用LIMIT。

MySQL:結構化數據和關係數據庫MySQL:結構化數據和關係數據庫Apr 18, 2025 am 12:22 AM

MySQL通過表結構和SQL查詢高效管理結構化數據,並通過外鍵實現表間關係。 1.創建表時定義數據格式和類型。 2.使用外鍵建立表間關係。 3.通過索引和查詢優化提高性能。 4.定期備份和監控數據庫確保數據安全和性能優化。

MySQL:解釋的關鍵功能和功能MySQL:解釋的關鍵功能和功能Apr 18, 2025 am 12:17 AM

MySQL是一個開源的關係型數據庫管理系統,廣泛應用於Web開發。它的關鍵特性包括:1.支持多種存儲引擎,如InnoDB和MyISAM,適用於不同場景;2.提供主從復制功能,利於負載均衡和數據備份;3.通過查詢優化和索引使用提高查詢效率。

SQL的目的:與MySQL數據庫進行交互SQL的目的:與MySQL數據庫進行交互Apr 18, 2025 am 12:12 AM

SQL用於與MySQL數據庫交互,實現數據的增、刪、改、查及數據庫設計。 1)SQL通過SELECT、INSERT、UPDATE、DELETE語句進行數據操作;2)使用CREATE、ALTER、DROP語句進行數據庫設計和管理;3)複雜查詢和數據分析通過SQL實現,提升業務決策效率。

初學者的MySQL:開始數據庫管理初學者的MySQL:開始數據庫管理Apr 18, 2025 am 12:10 AM

MySQL的基本操作包括創建數據庫、表格,及使用SQL進行數據的CRUD操作。 1.創建數據庫:CREATEDATABASEmy_first_db;2.創建表格:CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY,titleVARCHAR(100)NOTNULL,authorVARCHAR(100)NOTNULL,published_yearINT);3.插入數據:INSERTINTObooks(title,author,published_year)VA

MySQL的角色:Web應用程序中的數據庫MySQL的角色:Web應用程序中的數據庫Apr 17, 2025 am 12:23 AM

MySQL在Web應用中的主要作用是存儲和管理數據。 1.MySQL高效處理用戶信息、產品目錄和交易記錄等數據。 2.通過SQL查詢,開發者能從數據庫提取信息生成動態內容。 3.MySQL基於客戶端-服務器模型工作,確保查詢速度可接受。

mysql:構建您的第一個數據庫mysql:構建您的第一個數據庫Apr 17, 2025 am 12:22 AM

構建MySQL數據庫的步驟包括:1.創建數據庫和表,2.插入數據,3.進行查詢。首先,使用CREATEDATABASE和CREATETABLE語句創建數據庫和表,然後用INSERTINTO語句插入數據,最後用SELECT語句查詢數據。

MySQL:一種對數據存儲的初學者友好方法MySQL:一種對數據存儲的初學者友好方法Apr 17, 2025 am 12:21 AM

MySQL適合初學者,因為它易用且功能強大。 1.MySQL是關係型數據庫,使用SQL進行CRUD操作。 2.安裝簡單,需配置root用戶密碼。 3.使用INSERT、UPDATE、DELETE、SELECT進行數據操作。 4.複雜查詢可使用ORDERBY、WHERE和JOIN。 5.調試需檢查語法,使用EXPLAIN分析查詢。 6.優化建議包括使用索引、選擇合適數據類型和良好編程習慣。

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.能量晶體解釋及其做什麼(黃色晶體)
1 個月前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.最佳圖形設置
1 個月前By尊渡假赌尊渡假赌尊渡假赌
威爾R.E.P.O.有交叉遊戲嗎?
1 個月前By尊渡假赌尊渡假赌尊渡假赌

熱工具

VSCode Windows 64位元 下載

VSCode Windows 64位元 下載

微軟推出的免費、功能強大的一款IDE編輯器

MantisBT

MantisBT

Mantis是一個易於部署的基於Web的缺陷追蹤工具,用於幫助產品缺陷追蹤。它需要PHP、MySQL和一個Web伺服器。請查看我們的演示和託管服務。

ZendStudio 13.5.1 Mac

ZendStudio 13.5.1 Mac

強大的PHP整合開發環境

Dreamweaver Mac版

Dreamweaver Mac版

視覺化網頁開發工具

MinGW - Minimalist GNU for Windows

MinGW - Minimalist GNU for Windows

這個專案正在遷移到osdn.net/projects/mingw的過程中,你可以繼續在那裡關注我們。 MinGW:GNU編譯器集合(GCC)的本機Windows移植版本,可自由分發的導入函式庫和用於建置本機Windows應用程式的頭檔;包括對MSVC執行時間的擴展,以支援C99功能。 MinGW的所有軟體都可以在64位元Windows平台上運作。