裸设备权限导致的数据库部分数据库文件需要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: {
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: {
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: {
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: {
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: {
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: {
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: {
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: {
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: {
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: {
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: {
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: {
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: {
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;
最后成功执行。
What are stored procedures in MySQL?May 01, 2025 am 12:27 AMStored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.
How does query caching work in MySQL?May 01, 2025 am 12:26 AMThe working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.
What are the advantages of using MySQL over other relational databases?May 01, 2025 am 12:18 AMThe reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.
How do you handle database upgrades in MySQL?Apr 30, 2025 am 12:28 AMThe steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.
What are the different backup strategies you can use for MySQL?Apr 30, 2025 am 12:28 AMMySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.
What is MySQL clustering?Apr 30, 2025 am 12:28 AMMySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe
How do you optimize database schema design for performance in MySQL?Apr 30, 2025 am 12:27 AMOptimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.
How can you optimize MySQL performance?Apr 30, 2025 am 12:26 AMTooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.
WebStorm Mac version
Useful JavaScript development tools
SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.
SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.
Dreamweaver Mac version
Visual web development tools
