裸设备权限导致的数据库部分数据库文件需要recover-mysql教程-PHP中文網

首頁

資料庫

mysql教程

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

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=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用戶授予權限May 09, 2025 am 12:16 AM

TograntpermissionstonewMySQLusers,followthesesteps:1)AccessMySQLasauserwithsufficientprivileges,2)CreateanewuserwiththeCREATEUSERcommand,3)UsetheGRANTcommandtospecifypermissionslikeSELECT,INSERT,UPDATE,orALLPRIVILEGESonspecificdatabasesortables,and4)

如何在MySQL中添加用戶：逐步指南May 09, 2025 am 12:14 AM

toadduserInmysqleffect和securly，跟隨台詞：1）USEtheCreateUserStattoDaneWuser，指定thehostandastrongpassword.2）GrantNecterAryAryaryPrivilegesSustherthing privilegesgeStatement，usifementStatement，adheringtotheprinciplelastprefilegege.3）

mysql：添加具有復雜權限的新用戶May 09, 2025 am 12:09 AM

toaddanewuserwithcomplexpermissionsinmysql，loldtheSesteps：1）創建eTheEserWithCreateuser'newuser'newuser'@''localhost'Indedify'pa ssword';。 2）GrantreadAccesstoalltablesin'mydatabase'withGrantSelectOnMyDatabase.to'newuser'@'localhost';。 3）GrantWriteAccessto'

mysql：字符串數據類型和coltrationsMay 09, 2025 am 12:08 AM

MySQL中的字符串數據類型包括CHAR、VARCHAR、BINARY、VARBINARY、BLOB、TEXT，排序規則（Collations）決定了字符串的比較和排序方式。 1.CHAR適合固定長度字符串，VARCHAR適合可變長度字符串。 2.BINARY和VARBINARY用於二進制數據，BLOB和TEXT用於大對像數據。 3.排序規則如utf8mb4_unicode_ci忽略大小寫，適合用戶名；utf8mb4_bin區分大小寫，適合需要精確比較的字段。

MySQL：我應該在Varchars上使用什麼長度？May 09, 2025 am 12:06 AM

最佳的MySQLVARCHAR列長度選擇應基於數據分析、考慮未來增長、評估性能影響及字符集需求。 1)分析數據以確定典型長度；2)預留未來擴展空間；3)注意大長度對性能的影響；4)考慮字符集對存儲的影響。通過這些步驟，可以優化數據庫的效率和擴展性。

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）考慮pperformance impactsandSandStorLageBlobSextern; 2）管理backbackupsandreplication carecration; 3）usepathsinst

MySQL：自動化用戶創建的最佳工具是什麼？May 08, 2025 am 12:22 AM

自動化在MySQL中創建用戶的最佳工具和技術包括：1.MySQLWorkbench，適用於小型到中型環境，易於使用但資源消耗大；2.Ansible，適用於多服務器環境，簡單但學習曲線陡峭；3.自定義Python腳本，靈活但需確保腳本安全性；4.Puppet和Chef，適用於大規模環境，複雜但可擴展。選擇時需考慮規模、學習曲線和集成需求。

mysql：我可以在斑點內搜索嗎？May 08, 2025 am 12:20 AM

是的，YouCansearchInIdeAblobInMysqlusingsPecificteChniques.1）轉換theblobtoautf-8StringWithConvertFunctionWithConvertFunctionandSearchUsiseLike.2）forCompresseBlysBlobs，useuncompresseblobs，useuncompressbeforeconversion.3）expperformance impperformance imptactSandDataEcoding.4）

See all articles