ITPub博客

首页 > 数据库 > Oracle > ORA-7445(kclfusion_1)错误

ORA-7445(kclfusion_1)错误

原创 Oracle 作者:yangtingkun 时间:2012-11-20 23:27:37 0 删除 编辑

客户10.2.0.4 RAC环境在启动时出现ORA-7445错误。

[@more@]

错误信息为:

Wed Jun 27 05:10:51 2012
Starting ORACLE instance (normal)
Wed Jun 27 05:11:24 2012
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 aggr1 192.168.168.0 configured from OCR for use as a cluster interconnect
Interface type 1 bge0 172.25.145.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 1024
sessions = 1131
__shared_pool_size = 11895046144
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 16777216
spfile = /orcldata/oradata/orcl/spfileorcl.ora
filesystemio_options = SetAll
sga_target = 33554432000
control_files = /orcldata/oradata/orcl/control01.ctl, /orcldata/oradata/orcl/control02.ctl, /orcldata/oradata/orcl/control03.ctl
db_block_size = 8192
__db_cache_size = 21592276992
compatible = 10.2.0.3.0
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_recovery_file_dest = /orcldata/archdata
db_recovery_file_dest_size= 209715200000
thread = 1
instance_number = 1
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
local_listener = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.25.145.88)(PORT=1521)))
remote_listener = LISTENERS_ORCL
job_queue_processes = 10
background_dump_dest = /oracle/admin/orcl/bdump
user_dump_dest = /oracle/admin/orcl/udump
core_dump_dest = /oracle/admin/orcl/cdump
audit_file_dest = /oracle/admin/orcl/adump
db_name = orcl
open_cursors = 300
pga_aggregate_target = 8388608000
Cluster communication is configured to use the following interface(s) for this instance
192.168.168.3
Wed Jun 27 05:11:27 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=12150
DIAG started with pid=3, OS id=12152
PSP0 started with pid=4, OS id=12154
LMON started with pid=5, OS id=12156
LMD0 started with pid=6, OS id=12158
LMS0 started with pid=7, OS id=12160
LMS1 started with pid=8, OS id=12164
LMS2 started with pid=9, OS id=12168
LMS3 started with pid=10, OS id=12172
LMS4 started with pid=11, OS id=12176
LMS5 started with pid=12, OS id=12180
LMS6 started with pid=13, OS id=12184
LMS7 started with pid=14, OS id=12188
MMAN started with pid=15, OS id=12192
DBW0 started with pid=16, OS id=12194
DBW1 started with pid=17, OS id=12196
DBW2 started with pid=18, OS id=12198
DBW3 started with pid=19, OS id=12200
LGWR started with pid=20, OS id=12202
CKPT started with pid=21, OS id=12204
SMON started with pid=22, OS id=12206
RECO started with pid=23, OS id=12208
CJQ0 started with pid=24, OS id=12210
MMON started with pid=25, OS id=12212
Wed Jun 27 05:11:28 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=26, OS id=12214
Wed Jun 27 05:11:28 2012
starting up 1 shared server(s) ...
Wed Jun 27 05:11:34 2012
Errors in file /oracle/admin/orcl/bdump/orcl1_lmon_12156.trc:
ORA-07445: exception encountered: core dump [kjfmact()+12] [SIGSEGV] [Address not mapped to object] [0x000000D5C] [] []
USER: terminating instance due to error 29702
Instance terminated by USER, pid = 11923

导致这个ORA-7445错误的原因是由于出现了ORA-29702错误。该现象与MOS文档Bug 11684221 : ORA-29702 AND ORA-304 WHILE STARTING THE INSTANCES描述的非常相似。基本上可以认为是是CLUSTER层面出现了异常导致实例启动报错。

ORA-29702: error occurred in Cluster Group Service operation
Cause: An unexpected error occurred while performing a CGS operation.
Action: Verify that the LMON process is still active. Also, check the Oracle LMON trace files for errors.

而随后的第二次启动并没有发生同样的问题,说明CLUSTER层面的异常只是一次性的,已经被解决。这个错误和CLUSTER的某些不正常的状态有关,不但出现概率很低,而且不会重现,可以安全的忽略掉。

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/4227/viewspace-1060791/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论
暂无介绍

注册时间:2007-12-29

  • 博文量
    1955
  • 访问量
    10437686