suse12启动mysql失败_数据库打完11.1.0.7.12补丁后数据库启动失败

操作系统版本：suse linux 11

数据库版本：11.1.0.7.0

数据库数据库打完11.1.0.7.12补丁后数据库启动失败：

ORACLE instance started.

Total System Global Area 1.2560E+10 bytes

Fixed Size                  2171344 bytes

Variable Size            7918849584 bytes

Database Buffers         4630511616 bytes

Redo Buffers                8601600 bytes

ORA-03113: end-of-file on communication channel

Process ID: 13056

Session ID: 1105 Serial number: 3

数据库后台日志：

ALTER DATABASE   MOUNT

Errors in file /oracle/app/diag/rdbms/ora11g/ora11g/trace/ora11g_mman_13032.trc:

ORA-27103: internal error

Linux-x86_64 Error: 11: Resource temporarily unavailable

Additional information: -1

Additional information: 1

MMAN (ospid: 13032): terminating the instance due to error 27103

Instance terminated by MMAN, pid = 13032

相关的trace日志：

oracle> more /oracle/app/diag/rdbms/ora11g/ora11g/trace/ora11g_mman_13032.trc

Trace file /oracle/app/diag/rdbms/ora11g/ora11g/trace/ora11g_mman_13032.trc

Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production

With the Partitioning, Oracle Label Security, OLAP, Data Mining,

Oracle Database Vault and Real Application Testing options

ORACLE_HOME = /oracle/app/product/11g/db

System name:    Linux

Node name:      PGM_DB1

Release:        2.6.32.45-0.3.2.4445.1.PTF-default

Version:        #1 SMP 2011-08-22 10:12:58 +0200

Machine:        x86_64

Instance name: ora11g

Redo thread mounted by this instance: 0 Oracle process number: 8

Unix process pid: 13032, image: oracle@PGM_DB1 (MMAN)

*** 2013-12-10 14:50:29.525

*** SESSION ID:(1098.1) 2013-12-10 14:50:29.525

*** CLIENT ID:() 2013-12-10 14:50:29.525

*** SERVICE NAME:() 2013-12-10 14:50:29.525

*** MODULE NAME:() 2013-12-10 14:50:29.525

*** ACTION NAME:() 2013-12-10 14:50:29.525

error 27103 detected in background process

ORA-27103: internal error

Linux-x86_64 Error: 11: Resource temporarily unavailable

Additional information: -1

Additional information: 1

*** 2013-12-10 14:50:29.525

MMAN (ospid: 13032): terminating the instance due to error 27103

这错误是一个bug，要打上补丁p7272646_111070_Linux-x86-64：

oracle@PGM_DB1:~/psu> cd 7272646/

oracle@PGM_DB1:~/psu/7272646>

oracle@PGM_DB1:~/psu/7272646> $ORACLE_HOME/OPatch/opatch apply

Oracle Interim Patch Installer version 11.1.0.9.10

Copyright (c) 2012, Oracle Corporation.  All rights reserved.

Oracle Home       : /oracle/app/product/11g/db

Central Inventory : /oracle/app/oraInventory

from           : /oracle/app/product/11g/db/oraInst.loc

OPatch version    : 11.1.0.9.10

OUI version       : 11.1.0.7.0

Log file location : /oracle/app/product/11g/db/cfgtoollogs/opatch/7272646_Dec_10_2013_14_59_02/apply2013-12-10_14-59-01PM_1.log

Applying interim patch '7272646' to OH '/oracle/app/product/11g/db'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/oracle/app/product/11g/db')

Is the local system ready for patching? [y|n]

y

User Responded with: Y

Backing up files...

Patching component oracle.rdbms, 11.1.0.7.0...

Verifying the update...

Patch 7272646 successfully applied

Log file location: /oracle/app/product/11g/db/cfgtoollogs/opatch/7272646_Dec_10_2013_14_59_02/apply2013-12-10_14-59-01PM_1.log

OPatch succeeded.

打上补丁后，数据库启动成功。