ORA-15064: communication failure with ASM instance

最新推荐文章于 2024-10-07 17:03:31 发布
最新推荐文章于 2024-10-07 17:03:31 发布
阅读量8.1k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： Oracle ASM Storage ORA-xxx Oracle 10G RAC Oracle Production DB 文章标签： disk cache path domain file thread
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/deanza/article/details/7947798
此日志记录了Oracle ASM实例在特定日期的故障情况，包括IPC超时、通讯配置重新配置、集群资源目录冻结、错误日志记录、实例终止、系统状态转储等关键事件，展示了从故障发生到恢复的全过程。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

alert_ASM2.log
Wed Sep 05 03:32:56 2012
IPC Send timeout detected.Sender: ospid 13720
Receiver: inst 1 binc 22497 ospid 1431
IPC Send timeout to 1.1 inc 56 for msg type 65518 from opid 10
Wed Sep 05 03:32:58 2012
Communications reconfiguration: instance_number 1
Wed Sep 05 03:32:58 2012
Trace dumping is performing id=[cdmp_20120905033258]
Waiting for clusterware split-brain resolution
Wed Sep 05 03:43:00 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_lmon_13704.trc  (incident=40264):
ORA-29740: evicted by member 1, group incarnation 58
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM2/incident/incdir_40264/+ASM2_lmon_13704_i40264.trc
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_lmon_13704.trc:
ORA-29740: evicted by member 1, group incarnation 58
LMON (ospid: 13704): terminating the instance due to error 29740
Wed Sep 05 03:43:01 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_lms0_13720.trc  (incident=40280):
ORA-29740: evicted by member , group incarnation
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM2/incident/incdir_40280/+ASM2_lms0_13720_i40280.trc
Wed Sep 05 03:43:01 2012
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_diag_13682.trc
Wed Sep 05 03:43:01 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_mman_13724.trc  (incident=40288):
ORA-29740: evicted by member , group incarnation
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM2/incident/incdir_40288/+ASM2_mman_13724_i40288.trc
Wed Sep 05 03:43:02 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_smon_13732.trc  (incident=40320):
ORA-29740: evicted by member , group incarnation
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM2/incident/incdir_40320/+ASM2_smon_13732_i40320.trc
Wed Sep 05 03:43:02 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_gmon_13736.trc  (incident=40336):
ORA-29740: evicted by member , group incarnation
Incident details in: /u01/app/oracle/diag/asm/+asm/+ASM2/incident/incdir_40336/+ASM2_gmon_13736_i40336.trc
Wed Sep 05 03:43:02 2012


***********************************************************************

Fatal NI connect error 12537, connecting to:
 (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

  VERSION INFORMATION:
        TNS for Solaris: Version 11.1.0.7.0 - Production
        Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.1.0.7.0 - Production
  Time: 05-SEP-2012 03:43:02
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12537
    
TNS-12537: TNS:connection closed
    ns secondary err code: 12560
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
Wed Sep 05 03:43:02 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_13734.trc  (incident=40328):
ORA-29740: evicted by member , group incarnation
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_13734.trc  (incident=40329):
ORA-29740: evicted by member , group incarnation
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_13734.trc  (incident=40330):
ORA-29740: evicted by member , group incarnation
ORA-29740: evicted by member , group incarnation
ERROR: ORA-29740 thrown in RBAL for group number 1
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_13734.trc:
ORA-29740: evicted by member , group incarnation
ORA-29740: evicted by member , group incarnation
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_13734.trc:
ORA-29740: evicted by member , group incarnation
ORA-29740: evicted by member , group incarnation
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_13734.trc  (incident=40331):
ORA-29740: evicted by member , group incarnation
Trace dumping is performing id=[cdmp_20120905034301]
Wed Sep 05 03:43:06 2012
ORA-1092 : opitsk aborting process
Wed Sep 05 03:43:06 2012
License high water mark = 16
Instance terminated by LMON, pid = 13704
USER (ospid: 16961): terminating the instance
Instance terminated by USER, pid = 16961
Wed Sep 05 03:43:12 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/asm/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side pfile /u01/app/oracle/product/11.1.0/asm/dbs/init+ASM2.ora
System parameters with non-default values:
  shared_pool_size         = 200M
  large_pool_size          = 12M
  instance_type            = "asm"
  cluster_interconnects    = "192.168.1.4"
  memory_target            = 512M
  memory_max_target        = 1G
  cluster_database         = TRUE
  instance_number          = 2
  asm_diskgroups           = "DATA_DG1"
  asm_diskgroups           = "DATA_DG2"
  asm_diskgroups           = "DATA_DG3"
  asm_diskgroups           = "BACKUP_DG1"
  asm_diskgroups           = "BACKUP_DG2"
  diagnostic_dest          = "/u01/app/oracle"
Cluster communication is configured to use the following interface(s) for this instance
  192.168.1.4
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
Wed Sep 05 03:43:13 2012
PMON started with pid=2, OS id=17064
Wed Sep 05 03:43:13 2012
VKTM started with pid=3, OS id=17073 at elevated priority
VKTM running at (20)ms precision
Wed Sep 05 03:43:13 2012
DIAG started with pid=4, OS id=17078
Wed Sep 05 03:43:13 2012
PING started with pid=5, OS id=17083
Wed Sep 05 03:43:13 2012
PSP0 started with pid=6, OS id=17085
Wed Sep 05 03:43:13 2012
DIA0 started with pid=7, OS id=17088
Wed Sep 05 03:43:13 2012
LMON started with pid=8, OS id=17091
Wed Sep 05 03:43:13 2012
LMD0 started with pid=9, OS id=17093
Wed Sep 05 03:43:13 2012
LMS0 started with pid=10, OS id=17100 at elevated priority
Wed Sep 05 03:43:13 2012
MMAN started with pid=11, OS id=17104
Wed Sep 05 03:43:13 2012
DBW0 started with pid=12, OS id=17109
Wed Sep 05 03:43:13 2012
LGWR started with pid=13, OS id=17112
Wed Sep 05 03:43:13 2012
CKPT started with pid=14, OS id=17114
Wed Sep 05 03:43:13 2012
SMON started with pid=15, OS id=17116
Wed Sep 05 03:43:13 2012
RBAL started with pid=16, OS id=17119
Wed Sep 05 03:43:13 2012
GMON started with pid=17, OS id=17121
DISM started, OS id=17123
lmon registered with NM - instance id 2 (internal mem no 1)
Reconfiguration started (old inc 0, new inc 62)
ASM instance
List of nodes:
 0 1
 Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
 Communication channels reestablished
 * domain 0 valid = 1 according to instance 0
* allocate domain 1, invalid = TRUE
 * domain 1 valid = 1 according to instance 0
* allocate domain 2, invalid = TRUE
 * domain 2 valid = 1 according to instance 0
* allocate domain 3, invalid = TRUE
 * domain 3 valid = 1 according to instance 0
* allocate domain 4, invalid = TRUE
 * domain 4 valid = 1 according to instance 0
* allocate domain 5, invalid = TRUE
 * domain 5 valid = 1 according to instance 0
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
 LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
 Set master node info
 Submitted all remote-enqueue requests
 Dwn-cvts replayed, VALBLKs dubious
 All grantable enqueues granted
 LMS 0: 0 GCS shadows traversed, 0 replayed
 Submitted all GCS remote-cache requests
 Post SMON to start 1st pass IR
 Fix write in gcs resources
Reconfiguration complete
Wed Sep 05 03:43:14 2012
LCK0 started with pid=18, OS id=17151
ORACLE_BASE from environment = /u01/app/oracle
Wed Sep 05 03:43:15 2012
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: cache registered group BACKUP_DG1 number=1 incarn=0xbcfb9c9b
NOTE: cache began mount (not first) of group BACKUP_DG1 number=1 incarn=0xbcfb9c9b
NOTE: cache registered group BACKUP_DG2 number=2 incarn=0xbd0b9c9c
NOTE: cache began mount (not first) of group BACKUP_DG2 number=2 incarn=0xbd0b9c9c
NOTE: cache registered group DATA_DG1 number=3 incarn=0xbd0b9c9d
NOTE: cache began mount (not first) of group DATA_DG1 number=3 incarn=0xbd0b9c9d
NOTE: cache registered group DATA_DG2 number=4 incarn=0xbd0b9c9e
NOTE: cache began mount (not first) of group DATA_DG2 number=4 incarn=0xbd0b9c9e
NOTE: cache registered group DATA_DG3 number=5 incarn=0xbd0b9c9f
NOTE: cache began mount (not first) of group DATA_DG3 number=5 incarn=0xbd0b9c9f
WARNING::ASMLIB library not found. See trace file for details.
NOTE: Assigning number (1,3) to disk (/dev/rdsk/c3t6006016029012200ACC05F9D295CDE11d0s6)
NOTE: Assigning number (1,2) to disk (/dev/rdsk/c3t6006016029012200ABC05F9D295CDE11d0s6)
NOTE: Assigning number (1,1) to disk (/dev/rdsk/c3t6006016029012200AAC05F9D295CDE11d0s6)
NOTE: Assigning number (1,7) to disk (/dev/rdsk/c3t600601602901220061CD9F90295CDE11d0s6)
NOTE: Assigning number (1,6) to disk (/dev/rdsk/c3t60060160290122005C4A5D75295CDE11d0s6)
NOTE: Assigning number (1,5) to disk (/dev/rdsk/c3t60060160290122005B4A5D75295CDE11d0s6)
NOTE: Assigning number (1,0) to disk (/dev/rdsk/c3t60060160290122005A4A5D75295CDE11d0s6)
NOTE: Assigning number (1,4) to disk (/dev/rdsk/c3t60060160290122004AD4AF6E295CDE11d0s6)
NOTE: Assigning number (2,5) to disk (/dev/rdsk/c3t60060160290122004DFED3A3295CDE11d0s6)
NOTE: Assigning number (2,13) to disk (/dev/rdsk/c3t6006016029012200ED34DD96295CDE11d0s6)
NOTE: Assigning number (2,12) to disk (/dev/rdsk/c3t6006016029012200EC34DD96295CDE11d0s6)
NOTE: Assigning number (2,2) to disk (/dev/rdsk/c3t6006016029012200D2E98A82295CDE11d0s6)
NOTE: Assigning number (2,1) to disk (/dev/rdsk/c3t6006016029012200D1E98A82295CDE11d0s6)
NOTE: Assigning number (2,0) to disk (/dev/rdsk/c3t6006016029012200D0E98A82295CDE11d0s6)
NOTE: Assigning number (2,11) to disk (/dev/rdsk/c3t6006016029012200EAE8F27B295CDE11d0s6)
NOTE: Assigning number (2,7) to disk (/dev/rdsk/c3t6006016029012200E9E8F27B295CDE11d0s6)
NOTE: Assigning number (2,6) to disk (/dev/rdsk/c3t6006016029012200E8E8F27B295CDE11d0s6)
NOTE: Assigning number (2,4) to disk (/dev/rdsk/c3t600601602901220049D4AF6E295CDE11d0s6)
NOTE: Assigning number (2,3) to disk (/dev/rdsk/c3t600601602901220048D4AF6E295CDE11d0s6)
NOTE: Assigning number (2,8) to disk (/dev/rdsk/c3t600601602901220056E36868295CDE11d0s6)
NOTE: Assigning number (2,9) to disk (/dev/rdsk/c3t600601602901220055E36868295CDE11d0s6)
NOTE: Assigning number (2,10) to disk (/dev/rdsk/c3t600601602901220054E36868295CDE11d0s6)
NOTE: Assigning number (3,3) to disk (/dev/rdsk/c3t6006016029012200AC30026A5A5BDE11d0s6)
NOTE: Assigning number (3,2) to disk (/dev/rdsk/c3t6006016029012200AB30026A5A5BDE11d0s6)
NOTE: Assigning number (3,1) to disk (/dev/rdsk/c3t6006016029012200AA30026A5A5BDE11d0s6)
NOTE: Assigning number (3,11) to disk (/dev/rdsk/c3t6006016029012200EE774E625A5BDE11d0s6)
NOTE: Assigning number (3,12) to disk (/dev/rdsk/c3t6006016029012200ED774E625A5BDE11d0s6)
NOTE: Assigning number (3,15) to disk (/dev/rdsk/c3t6006016029012200EC774E625A5BDE11d0s6)
NOTE: Assigning number (3,8) to disk (/dev/rdsk/c3t60060160290122008B73502D5A5BDE11d0s6)
NOTE: Assigning number (3,0) to disk (/dev/rdsk/c3t60060160290122008A73502D5A5BDE11d0s6)
NOTE: Assigning number (3,14) to disk (/dev/rdsk/c3t60060160290122002D9576255A5BDE11d0s6)
NOTE: Assigning number (3,9) to disk (/dev/rdsk/c3t60060160290122002B9576255A5BDE11d0s6)
NOTE: Assigning number (3,5) to disk (/dev/rdsk/c3t600601602901220038040AF9595BDE11d0s6)
NOTE: Assigning number (3,7) to disk (/dev/rdsk/c3t600601602901220037040AF9595BDE11d0s6)
NOTE: Assigning number (3,6) to disk (/dev/rdsk/c3t600601602901220036040AF9595BDE11d0s6)
NOTE: Assigning number (3,13) to disk (/dev/rdsk/c3t60060160290122002DD902F1595BDE11d0s6)
NOTE: Assigning number (3,10) to disk (/dev/rdsk/c3t60060160290122002BD902F1595BDE11d0s6)
NOTE: Assigning number (3,4) to disk (/dev/rdsk/c3t60060160290122002AD902F1595BDE11d0s6)
NOTE: Assigning number (4,2) to disk (/dev/rdsk/c3t60060160290122008973502D5A5BDE11d0s6)
NOTE: Assigning number (4,3) to disk (/dev/rdsk/c3t60060160290122008873502D5A5BDE11d0s6)
NOTE: Assigning number (4,0) to disk (/dev/rdsk/c3t60060160290122002C9576255A5BDE11d0s6)
NOTE: Assigning number (4,1) to disk (/dev/rdsk/c3t60060160290122002CD902F1595BDE11d0s6)
NOTE: Assigning number (5,6) to disk (/dev/rdsk/c3t60060160290122004EFED3A3295CDE11d0s6)
NOTE: Assigning number (5,0) to disk (/dev/rdsk/c3t60060160290122004CFED3A3295CDE11d0s6)
NOTE: Assigning number (5,7) to disk (/dev/rdsk/c3t6006016029012200EE34DD96295CDE11d0s6)
NOTE: Assigning number (5,2) to disk (/dev/rdsk/c3t600601602901220062CD9F90295CDE11d0s6)
NOTE: Assigning number (5,1) to disk (/dev/rdsk/c3t600601602901220060CD9F90295CDE11d0s6)
NOTE: Assigning number (5,3) to disk (/dev/rdsk/c3t6006016029012200F6F4EF89295CDE11d0s6)
NOTE: Assigning number (5,4) to disk (/dev/rdsk/c3t6006016029012200F5F4EF89295CDE11d0s6)
NOTE: Assigning number (5,5) to disk (/dev/rdsk/c3t6006016029012200F4F4EF89295CDE11d0s6)
kfdp_query(): 6
kfdp_queryBg(): 6
NOTE: cache opening disk 0 of grp 1: BACKUP_DG1_0000 path:/dev/rdsk/c3t60060160290122005A4A5D75295CDE11d0s6
NOTE: F1X0 found on disk 0 fcn 0.258
NOTE: cache opening disk 1 of grp 1: BACKUP_DG1_0001 path:/dev/rdsk/c3t6006016029012200AAC05F9D295CDE11d0s6
NOTE: cache opening disk 2 of grp 1: BACKUP_DG1_0002 path:/dev/rdsk/c3t6006016029012200ABC05F9D295CDE11d0s6
NOTE: cache opening disk 3 of grp 1: BACKUP_DG1_0003 path:/dev/rdsk/c3t6006016029012200ACC05F9D295CDE11d0s6
NOTE: cache opening disk 4 of grp 1: BACKUP_DG1_0004 path:/dev/rdsk/c3t60060160290122004AD4AF6E295CDE11d0s6
NOTE: cache opening disk 5 of grp 1: BACKUP_DG1_0005 path:/dev/rdsk/c3t60060160290122005B4A5D75295CDE11d0s6
NOTE: cache opening disk 6 of grp 1: BACKUP_DG1_0006 path:/dev/rdsk/c3t60060160290122005C4A5D75295CDE11d0s6
NOTE: cache opening disk 7 of grp 1: BACKUP_DG1_0007 path:/dev/rdsk/c3t600601602901220061CD9F90295CDE11d0s6
NOTE: cache mounting (not first) group 1/0xBCFB9C9B (BACKUP_DG1)
kjbdomatt send to node 0
NOTE: attached to recovery domain 1
NOTE: LGWR attempting to mount thread 1 for diskgroup 1
NOTE: LGWR mounted thread 1 for disk group 1
NOTE: opening chunk 1 at fcn 0.703535333 ABA
NOTE: seq=534 blk=2990
NOTE: cache mounting group 1/0xBCFB9C9B (BACKUP_DG1) succeeded
NOTE: cache ending mount (success) of group BACKUP_DG1 number=1 incarn=0xbcfb9c9b
kfdp_query(): 7
kfdp_queryBg(): 7
NOTE: cache opening disk 0 of grp 2: BACKUP_DG2_0000 path:/dev/rdsk/c3t6006016029012200D0E98A82295CDE11d0s6
NOTE: F1X0 found on disk 0 fcn 0.169
NOTE: cache opening disk 1 of grp 2: BACKUP_DG2_0001 path:/dev/rdsk/c3t6006016029012200D1E98A82295CDE11d0s6
NOTE: cache opening disk 2 of grp 2: BACKUP_DG2_0002 path:/dev/rdsk/c3t6006016029012200D2E98A82295CDE11d0s6
NOTE: cache opening disk 3 of grp 2: BACKUP_DG2_0003 path:/dev/rdsk/c3t600601602901220048D4AF6E295CDE11d0s6
NOTE: cache opening disk 4 of grp 2: BACKUP_DG2_0004 path:/dev/rdsk/c3t600601602901220049D4AF6E295CDE11d0s6
NOTE: cache opening disk 5 of grp 2: BACKUP_DG2_0005 path:/dev/rdsk/c3t60060160290122004DFED3A3295CDE11d0s6
NOTE: cache opening disk 6 of grp 2: BACKUP_DG2_0006 path:/dev/rdsk/c3t6006016029012200E8E8F27B295CDE11d0s6
NOTE: cache opening disk 7 of grp 2: BACKUP_DG2_0007 path:/dev/rdsk/c3t6006016029012200E9E8F27B295CDE11d0s6
NOTE: cache opening disk 8 of grp 2: BACKUP_DG2_0008 path:/dev/rdsk/c3t600601602901220056E36868295CDE11d0s6
NOTE: cache opening disk 9 of grp 2: BACKUP_DG2_0009 path:/dev/rdsk/c3t600601602901220055E36868295CDE11d0s6
NOTE: cache opening disk 10 of grp 2: BACKUP_DG2_0010 path:/dev/rdsk/c3t600601602901220054E36868295CDE11d0s6
NOTE: cache opening disk 11 of grp 2: BACKUP_DG2_0011 path:/dev/rdsk/c3t6006016029012200EAE8F27B295CDE11d0s6
NOTE: cache opening disk 12 of grp 2: BACKUP_DG2_0012 path:/dev/rdsk/c3t6006016029012200EC34DD96295CDE11d0s6
NOTE: cache opening disk 13 of grp 2: BACKUP_DG2_0013 path:/dev/rdsk/c3t6006016029012200ED34DD96295CDE11d0s6
NOTE: cache mounting (not first) group 2/0xBD0B9C9C (BACKUP_DG2)
kjbdomatt send to node 0
NOTE: attached to recovery domain 2
NOTE: LGWR attempting to mount thread 1 for diskgroup 2
NOTE: LGWR mounted thread 1 for disk group 2
NOTE: opening chunk 1 at fcn 0.544141956 ABA
NOTE: seq=685 blk=8752
NOTE: cache mounting group 2/0xBD0B9C9C (BACKUP_DG2) succeeded
NOTE: cache ending mount (success) of group BACKUP_DG2 number=2 incarn=0xbd0b9c9c
kfdp_query(): 8
kfdp_queryBg(): 8
NOTE: cache opening disk 0 of grp 3: DATA_DG1_0000 path:/dev/rdsk/c3t60060160290122008A73502D5A5BDE11d0s6
NOTE: F1X0 found on disk 0 fcn 0.152
NOTE: cache opening disk 1 of grp 3: DATA_DG1_0001 path:/dev/rdsk/c3t6006016029012200AA30026A5A5BDE11d0s6
NOTE: cache opening disk 2 of grp 3: DATA_DG1_0002 path:/dev/rdsk/c3t6006016029012200AB30026A5A5BDE11d0s6
NOTE: cache opening disk 3 of grp 3: DATA_DG1_0003 path:/dev/rdsk/c3t6006016029012200AC30026A5A5BDE11d0s6
NOTE: cache opening disk 4 of grp 3: DATA_DG1_0004 path:/dev/rdsk/c3t60060160290122002AD902F1595BDE11d0s6
NOTE: cache opening disk 5 of grp 3: DATA_DG1_0005 path:/dev/rdsk/c3t600601602901220038040AF9595BDE11d0s6
NOTE: cache opening disk 6 of grp 3: DATA_DG1_0006 path:/dev/rdsk/c3t600601602901220036040AF9595BDE11d0s6
NOTE: cache opening disk 7 of grp 3: DATA_DG1_0007 path:/dev/rdsk/c3t600601602901220037040AF9595BDE11d0s6
NOTE: cache opening disk 8 of grp 3: DATA_DG1_0008 path:/dev/rdsk/c3t60060160290122008B73502D5A5BDE11d0s6
NOTE: cache opening disk 9 of grp 3: DATA_DG1_0009 path:/dev/rdsk/c3t60060160290122002B9576255A5BDE11d0s6
NOTE: cache opening disk 10 of grp 3: DATA_DG1_0010 path:/dev/rdsk/c3t60060160290122002BD902F1595BDE11d0s6
NOTE: cache opening disk 11 of grp 3: DATA_DG1_0011 path:/dev/rdsk/c3t6006016029012200EE774E625A5BDE11d0s6
NOTE: cache opening disk 12 of grp 3: DATA_DG1_0012 path:/dev/rdsk/c3t6006016029012200ED774E625A5BDE11d0s6
NOTE: cache opening disk 13 of grp 3: DATA_DG1_0013 path:/dev/rdsk/c3t60060160290122002DD902F1595BDE11d0s6
NOTE: cache opening disk 14 of grp 3: DATA_DG1_0014 path:/dev/rdsk/c3t60060160290122002D9576255A5BDE11d0s6
NOTE: cache opening disk 15 of grp 3: DATA_DG1_0015 path:/dev/rdsk/c3t6006016029012200EC774E625A5BDE11d0s6
NOTE: cache mounting (not first) group 3/0xBD0B9C9D (DATA_DG1)
kjbdomatt send to node 0
NOTE: attached to recovery domain 3
NOTE: LGWR attempting to mount thread 1 for diskgroup 3
NOTE: LGWR mounted thread 1 for disk group 3
NOTE: opening chunk 1 at fcn 0.2874008 ABA
NOTE: seq=43 blk=5509
NOTE: cache mounting group 3/0xBD0B9C9D (DATA_DG1) succeeded
NOTE: cache ending mount (success) of group DATA_DG1 number=3 incarn=0xbd0b9c9d
kfdp_query(): 9
kfdp_queryBg(): 9
NOTE: cache opening disk 0 of grp 4: DATA_DG2_0000 path:/dev/rdsk/c3t60060160290122002C9576255A5BDE11d0s6
NOTE: F1X0 found on disk 0 fcn 0.746372
NOTE: cache opening disk 1 of grp 4: DATA_DG2_0001 path:/dev/rdsk/c3t60060160290122002CD902F1595BDE11d0s6
NOTE: cache opening disk 2 of grp 4: DATA_DG2_0002 path:/dev/rdsk/c3t60060160290122008973502D5A5BDE11d0s6
NOTE: cache opening disk 3 of grp 4: DATA_DG2_0003 path:/dev/rdsk/c3t60060160290122008873502D5A5BDE11d0s6
NOTE: cache mounting (not first) group 4/0xBD0B9C9E (DATA_DG2)
kjbdomatt send to node 0
NOTE: attached to recovery domain 4
NOTE: LGWR attempting to mount thread 1 for diskgroup 4
NOTE: LGWR mounted thread 1 for disk group 4
NOTE: opening chunk 1 at fcn 0.915102 ABA
NOTE: seq=31 blk=7869
NOTE: cache mounting group 4/0xBD0B9C9E (DATA_DG2) succeeded
NOTE: cache ending mount (success) of group DATA_DG2 number=4 incarn=0xbd0b9c9e
kfdp_query(): 10
kfdp_queryBg(): 10
NOTE: cache opening disk 0 of grp 5: DATA_DG3_0000 path:/dev/rdsk/c3t60060160290122004CFED3A3295CDE11d0s6
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache opening disk 1 of grp 5: DATA_DG3_0001 path:/dev/rdsk/c3t600601602901220060CD9F90295CDE11d0s6
NOTE: cache opening disk 2 of grp 5: DATA_DG3_0002 path:/dev/rdsk/c3t600601602901220062CD9F90295CDE11d0s6
NOTE: cache opening disk 3 of grp 5: DATA_DG3_0003 path:/dev/rdsk/c3t6006016029012200F6F4EF89295CDE11d0s6
NOTE: cache opening disk 4 of grp 5: DATA_DG3_0004 path:/dev/rdsk/c3t6006016029012200F5F4EF89295CDE11d0s6
NOTE: cache opening disk 5 of grp 5: DATA_DG3_0005 path:/dev/rdsk/c3t6006016029012200F4F4EF89295CDE11d0s6
NOTE: cache opening disk 6 of grp 5: DATA_DG3_0006 path:/dev/rdsk/c3t60060160290122004EFED3A3295CDE11d0s6
NOTE: cache opening disk 7 of grp 5: DATA_DG3_0007 path:/dev/rdsk/c3t6006016029012200EE34DD96295CDE11d0s6
NOTE: cache mounting (not first) group 5/0xBD0B9C9F (DATA_DG3)
kjbdomatt send to node 0
NOTE: attached to recovery domain 5
NOTE: LGWR attempting to mount thread 1 for diskgroup 5
NOTE: LGWR mounted thread 1 for disk group 5
NOTE: opening chunk 1 at fcn 0.1061356 ABA
NOTE: seq=37 blk=10556
NOTE: cache mounting group 5/0xBD0B9C9F (DATA_DG3) succeeded
NOTE: cache ending mount (success) of group DATA_DG3 number=5 incarn=0xbd0b9c9f
kfdp_query(): 11
kfdp_queryBg(): 11
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 1
SUCCESS: diskgroup BACKUP_DG1 was mounted
kfdp_query(): 12
kfdp_queryBg(): 12
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 2
SUCCESS: diskgroup BACKUP_DG2 was mounted
kfdp_query(): 13
kfdp_queryBg(): 13
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 3
SUCCESS: diskgroup DATA_DG1 was mounted
kfdp_query(): 14
kfdp_queryBg(): 14
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 4
SUCCESS: diskgroup DATA_DG2 was mounted
kfdp_query(): 15
kfdp_queryBg(): 15
NOTE: Instance updated compatible.asm to 10.1.0.0.0 for grp 5
SUCCESS: diskgroup DATA_DG3 was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT
Wed Sep 05 03:43:31 2012
Starting background process ASMB
Wed Sep 05 03:43:31 2012
ASMB started with pid=21, OS id=17551
NOTE: ASMB process exiting due to lack of ASM file activity for 5 seconds
alert_PFRM_A2.log
Wed Sep  5 01:06:39 2012
ALTER SYSTEM ARCHIVE LOG
Wed Sep  5 01:06:39 2012
Thread 2 advanced to log sequence 9994 (LGWR switch)
  Current log# 4 seq# 9994 mem# 0: +BACKUP_DG2/pfrm_a/onlinelog/group_4.266.692725317
  Current log# 4 seq# 9994 mem# 1: +DATA_DG3/pfrm_a/onlinelog/group_4.371.716207107
Wed Sep  5 01:06:43 2012
ALTER SYSTEM ARCHIVE LOG
Wed Sep  5 01:06:46 2012
Thread 2 advanced to log sequence 9995 (LGWR switch)
  Current log# 3 seq# 9995 mem# 0: +BACKUP_DG2/pfrm_a/onlinelog/group_3.265.692725317
  Current log# 3 seq# 9995 mem# 1: +DATA_DG3/pfrm_a/onlinelog/group_3.370.716207101
Wed Sep  5 01:07:00 2012
Starting control autobackup
Control autobackup written to DISK device
        handle '+BACKUP_DG2/pfrm_a/autobackup/2012_09_05/s_793156020.4229.793156023'
Wed Sep  5 03:43:02 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/PFRM_A/bdump/pfrm_a2_asmb_14034.trc:
ORA-15064: communication failure with ASM instance
ORA-03113: end-of-file on communication channel
Wed Sep  5 03:43:02 2012
ASMB: terminating instance due to error 15064
Wed Sep  5 03:43:02 2012
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/product/10.2.0/db/admin/PFRM_A/bdump/pfrm_a2_diag_13894.trc
Wed Sep  5 03:43:05 2012
Shutting down instance (abort)
License high water mark = 22
Wed Sep  5 03:43:06 2012
Trace dumping is performing id=[cdmp_20120905034302]
Wed Sep  5 03:43:07 2012
Instance terminated by ASMB, pid = 14034
Wed Sep  5 03:43:10 2012
Instance terminated by USER, pid = 16926
alert_PFRM_C2.log
Wed Sep  5 03:43:02 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/PFRM_C/bdump/pfrm_c2_asmb_14061.trc:
ORA-15064: communication failure with ASM instance
ORA-03113: end-of-file on communication channel
Wed Sep  5 03:43:02 2012
ASMB: terminating instance due to error 15064
Wed Sep  5 03:43:02 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/PFRM_C/bdump/pfrm_c2_lmon_13912.trc:
ORA-15064: communication failure with ASM instance
Wed Sep  5 03:43:02 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/PFRM_C/bdump/pfrm_c2_lms0_13918.trc:
ORA-15064: communication failure with ASM instance
Wed Sep  5 03:43:02 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/PFRM_C/bdump/pfrm_c2_pmon_13902.trc:
ORA-15064: communication failure with ASM instance
Wed Sep  5 03:43:02 2012
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/product/10.2.0/db/admin/PFRM_C/bdump/pfrm_c2_diag_13906.trc
Wed Sep  5 03:43:06 2012
Shutting down instance (abort)
License high water mark = 37
Wed Sep  5 03:43:07 2012
Trace dumping is performing id=[cdmp_20120905034302]
Wed Sep  5 03:43:07 2012
Instance terminated by ASMB, pid = 14061
Wed Sep  5 03:43:11 2012
Instance terminated by USER, pid = 16959
alert_COXCALL2.log
Wed Sep  5 03:43:01 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/COXCALL/bdump/coxcall2_asmb_14369.trc:
ORA-15064: communication failure with ASM instance
ORA-03113: end-of-file on communication channel
Wed Sep  5 03:43:01 2012
ASMB: terminating instance due to error 15064
Wed Sep  5 03:43:01 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/COXCALL/bdump/coxcall2_lms1_14277.trc:
ORA-15064: communication failure with ASM instance
Wed Sep  5 03:43:01 2012
Errors in file /u01/app/oracle/product/10.2.0/db/admin/COXCALL/bdump/coxcall2_lms0_14271.trc:
ORA-15064: communication failure with ASM instance
Wed Sep  5 03:43:01 2012
System state dump is made for local instance
System State dumped to trace file /u01/app/oracle/product/10.2.0/db/admin/COXCALL/bdump/coxcall2_diag_14255.trc
Wed Sep  5 03:43:05 2012
Shutting down instance (abort)
License high water mark = 53
Wed Sep  5 03:43:07 2012
Trace dumping is performing id=[cdmp_20120905034301]
Wed Sep  5 03:43:07 2012
Instance terminated by ASMB, pid = 14369
Wed Sep  5 03:43:10 2012
Instance terminated by USER, pid = 16931
Wed Sep  5 03:43:31 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
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                = 1500
  sessions                 = 1800
  __shared_pool_size       = 469762048
  __large_pool_size        = 16777216
  __java_pool_size         = 16777216
  __streams_pool_size      = 16777216
  spfile                   = +BACKUP_DG1/coxcalls/spfilecoxcall.ora
  cluster_interconnects    = 192.168.1.4
  sga_target               = 3221225472
  control_files            = +DATA_DG1/coxcalls/controlfile/current.305.697217041, +BACKUP_DG1/coxcalls/controlfile/current.268.6972
17041
  db_file_name_convert     = +COXCALL_DATA/COXCALL, +DATA_DG1/COXCALLS, +COXCALL_BACKUP/COXCALL, +BACKUP_DG1/COXCALLS
  log_file_name_convert    = +COXCALL_DATA/COXCALL, +DATA_DG1/COXCALLS, +COXCALL_BACKUP/COXCALL, +BACKUP_DG1/COXCALLS
  db_block_size            = 8192
  __db_cache_size          = 2684354560
  compatible               = 10.2.0.2.0
  log_archive_config       = dg_config=(COXCALL,COXCALLS)
  log_archive_dest_1       = LOCATION=USE_DB_RECOVERY_FILE_DEST
  log_archive_dest_2       =
  log_archive_max_processes= 5
  log_archive_format       = %t_%s_%r.arc
  fal_client               = COXCALLS
  fal_server               = COXCALL
  db_file_multiblock_read_count= 16
  cluster_database         = TRUE
  cluster_database_instances= 2
  db_create_file_dest      = +DATA_DG1
  db_recovery_file_dest    = +BACKUP_DG1
  db_recovery_file_dest_size= 1073741824000
  standby_file_management  = auto
  thread                   = 2
  instance_number          = 2
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS2
  undo_retention           = 20000
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  service_names            = RKSCALL,PHONETOOLS,BTSUSER,ITV_SVC,ACCALL,COXCALL,COXCALLS,BTA_SVC
  dispatchers              = (PROTOCOL=TCP) (SERVICE=COXCALLXDB)
  local_listener           =
  remote_listener          =
  job_queue_processes      = 10
  background_dump_dest     = /u01/app/oracle/product/10.2.0/db/admin/COXCALL/bdump
  user_dump_dest           = /u01/app/oracle/product/10.2.0/db/admin/COXCALL/udump
  core_dump_dest           = /u01/app/oracle/product/10.2.0/db/admin/COXCALL/cdump
  audit_file_dest          = /u01/app/oracle/product/10.2.0/db/admin/COXCALL/adump
  db_name                  = COXCALL
  db_unique_name           = COXCALLS
  open_cursors             = 500
  pga_aggregate_target     = 1706033152
Cluster communication is configured to use the following interface(s) for this instance
  192.168.1.4
Wed Sep  5 03:43:34 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=17625
DIAG started with pid=3, OS id=17629
PSP0 started with pid=4, OS id=17633
LMON started with pid=5, OS id=17637
LMD0 started with pid=6, OS id=17639
LMS0 started with pid=7, OS id=17643
LMS1 started with pid=8, OS id=17649
MMAN started with pid=9, OS id=17657
DBW0 started with pid=10, OS id=17661
LGWR started with pid=11, OS id=17665
CKPT started with pid=12, OS id=17669
SMON started with pid=13, OS id=17673
RECO started with pid=14, OS id=17677
CJQ0 started with pid=15, OS id=17679
MMON started with pid=16, OS id=17681
Wed Sep  5 03:43:35 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=17683
Wed Sep  5 03:43:35 2012
starting up 1 shared server(s) ...
Wed Sep  5 03:43:36 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Sep  5 03:43:37 2012
Reconfiguration started (old inc 0, new inc 48)
List of nodes:
 0 1
 Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
 Communication channels reestablished
 * domain 0 valid = 1 according to instance 0
Wed Sep  5 03:43:37 2012
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Wed Sep  5 03:43:37 2012
 LMS 1: 0 GCS shadows cancelled, 0 closed
Wed Sep  5 03:43:37 2012
 LMS 0: 0 GCS shadows cancelled, 0 closed
 Set master node info
 Submitted all remote-enqueue requests
 Dwn-cvts replayed, VALBLKs dubious
 All grantable enqueues granted
Wed Sep  5 03:43:37 2012
 LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Sep  5 03:43:37 2012
 LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Sep  5 03:43:37 2012
 Submitted all GCS remote-cache requests
 Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=17727
Wed Sep  5 03:43:38 2012
ALTER DATABASE   MOUNT
Wed Sep  5 03:43:39 2012
Starting background process ASMB
ASMB started with pid=22, OS id=17738
Starting background process RBAL
RBAL started with pid=23, OS id=17742
Wed Sep  5 03:43:42 2012
SUCCESS: diskgroup DATA_DG1 was mounted
SUCCESS: diskgroup BACKUP_DG1 was mounted
Wed Sep  5 03:43:46 2012
Setting recovery target incarnation to 2
Wed Sep  5 03:43:46 2012
Successful mount of redo thread 2, with mount id 819078902
Wed Sep  5 03:43:46 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE   MOUNT
Wed Sep  5 03:43:47 2012
ALTER DATABASE OPEN
Picked broadcast on commit scheme to generate SCNs
Wed Sep  5 03:43:52 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=27, OS id=17912
ARC1 started with pid=28, OS id=17914
ARC2 started with pid=29, OS id=17916
ARC3 started with pid=30, OS id=17918
Wed Sep  5 03:43:52 2012
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC4 started with pid=31, OS id=17920
Wed Sep  5 03:43:52 2012
Thread 2 opened at log sequence 100362
  Current log# 10 seq# 100362 mem# 0: +DATA_DG1/coxcalls/onlinelog/group_10.353.697219913
  Current log# 10 seq# 100362 mem# 1: +BACKUP_DG1/coxcalls/onlinelog/group_10.278.697219913
Successful open of redo thread 2
Wed Sep  5 03:43:52 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Sep  5 03:43:52 2012
SMON: enabling cache recovery
Wed Sep  5 03:43:52 2012
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Wed Sep  5 03:43:52 2012
ARC3: Becoming the heartbeat ARCH
Wed Sep  5 03:43:53 2012
Successfully onlined Undo Tablespace 5
Wed Sep  5 03:43:53 2012
SMON: enabling tx recovery
Wed Sep  5 03:43:53 2012
Database Characterset is WE8ISO8859P1
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=35, OS id=17983
Wed Sep  5 03:43:57 2012
Completed: ALTER DATABASE OPEN
由 BUG 引发 ORA-15064 进而导致数据库实例意外中止
aaron8219's Oracle&Linux Technology Blog
01-05 3389
今天早上刚到公司一会，就接到南京客户打来的电话，说他们的核心会员数据库宕机了，让我远程帮忙查看一下。 还没来得急看报纸的我赶紧打开电脑，远程连接到客户的服务器进行诊断。 客户的生产环境是AIX 6.1上的Oracle 11.2.0.3.0，在凌晨1:40分左右发生的故障。为了不涉及泄露客户隐私，把数据库实例名进行了替换。下面看具体的分析： 1. 数据库al
oracle报03113,【案例】Oracle报错ORA-03113 ORA-15064产生原因和解决办法
weixin_28674303的博客
04-03 3912
【案例】Oracle报错ORA-03113 ORA-15064产生原因和解决办法时间:2016-12-11 18:47来源:Oracle研究中心作者:网络点击:次天萃荷净Oracle研究中心案例分析：运维DBA反映Oracle RAC数据库报错ORA-03113 ORA-15064，分析原因为数据库实例的asmb进程crash，然后导致数据库实例crash，进而被crs给重启了。...
oracle 11g rac asm ORA-15064错误
03-28 549
数据库是11.2.0.3.0 的rac在使用impdp导入数据时导入进程终止了.后检查告警日志发现如下信息Time drift detected. Please check VKTM trace file for more de...
ORA-15064与ASM
lwei_998的专栏
03-26 7688
<br />早上例行检查时发现集群中节点3已经宕掉。但crs显示集群中各节点资源正常。<br /><br />在检查节点3数据库实例日志，ASM日志，及CRS日志后发现：<br /><br />节点3在凌晨4：14分被踢出集群，导致操作系统重启，数据库实例宕掉。同时检查集群中其它三个节点日志，未发现异常情况。<br /> <br />以下是节点3的检查信息：<br />1. crs_stat   –t  显示集群中各项资源状态都正常。此命令是在其它节点上运行的，节点3执行crs_stat -t无响应<br
oracle -15064,由 BUG 引发 ORA-15064 进而导致数据库实例意外中止
weixin_42604188的博客
04-04 1786
Mon Jan 05 01:40:50 2015WARNING: ASM communication error: op 18 state 0x50 (3113)ERROR: slave communication error with ASMNOTE: Deferred communication with ASM instanceErrors in file /u01/app/oracle/d...
ORA-15064 ORA-03113 - 测试库案例
09-18 3981
错误日志 2013-0912 16:20:00 ############### alert_prod1.log ############### Thu Sep 12 16:19:17 2013 NOTE: ASMB terminating Errors in file /prod/oracle/diag/rdbms/prod/prod2/trace/prod2_asmb_26138.trc: O
ORA-15064 tips
weixin_34111790的博客
09-12 217
Question:I am getting this RAC ORA-15064error:ORA-15064: communication failure with ASM instanceTrace dumping is performing id=[cdmp_20111118024517]Instance terminated by ASMB, pid = 121...
ORA-12547: TNS:lost contact导致数据库无法启动
Enmotech的博客
06-30 3282
墨墨导读：一个诡异的案例：ORA-12547: TNS:lost contact导致数据库无法启动，甚至sqlplus都无法登录，让我们一一来解开这个案例的真面目。1. 背景概述某客户出...
Oracle 11g RAC 节点异常重启问题分析
听雪楼主
10-07 1753
Oracle 11g RAC 节点异常重启问题分析
IMP-00003: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel
weixin_33748818的博客
02-29 843
IMP-00003: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel . . importing table "SFP_FILE_6" 11179rows imported IMP-00017: following ...
oracle数据库启动报错，不能启动ASM实例
LUMIS的博客
06-09 2437
数据库rac启动时报错，日志如下，后来使用 Sat Jun  7 06:02:11 2014 GATHER_STATS_JOB encountered errors.  Check the trace file. Sat Jun  7 06:02:11 2014 Errors in file /oracle/product/admin/dqb/bdump/dqb2_j001_1
首次遭遇ORA-15064
OS is DB,DB is OS
06-13 7628
整理一下前段时间遇到的ORA-15064错误。 有一套测试环境是11gR2的rac使用ASM，应用在测试时发现一个节点宕机了，检查了一下alert日志如下错误： Mon Jun 04 23:27:32 2012 NOTE: ASMB terminating Errors in file /soft/oracle/diag/rdbms/pt1db/pt1db2/trace/pt1db2_as
Oracle rac ora29283,oracle 11g rac asm ORA-15064错误
weixin_26841743的博客
04-03 206
数据库是11.2.0.3.0 的rac在使用impdp导入数据时导入进程终止了.后检查告警日志发现如下信息Time drift detected. Please check VKTM trace file for more details.Thu Mar 28 05:45:49 2013Time drift detected. Please check VKTM trace file for mo...
10gR2 rac(asm) crash with ora-15064
数据库天地
09-27 138
原文博客地址：10gR2 rac(asm) crash with ora-15064
记一次ORA-15064,ORA-12012,ORA-01565
yingdovezuo的博客
12-26 507
记一次ORACLE报错的处理 1.1配置 项目 DB Info 类型 RAC Version 12.1.0.2 Storage ASM 1.2故障现象及Log 故障现象：并未发现系统异常 **Alert Log：** Tue Dec 25 22:49:02 2018 Errors in file /oracle/app/diag/rdbms/fdcoffdb/FDCOF...
mysql ora-1064_ORA-15064 错误解决
weixin_29781865的博客
01-19 863
整理一下前段时间遇到的ORA-15064错误。有一套测试环境是11gR2的rac使用ASM，应用在测试时发现一个节点宕机了，检查了一下alert日整理一下前段时间遇到的ORA-15064错误。有一套测试环境是11gR2的rac使用ASM，应用在测试时发现一个节点宕机了，检查了一下alert日志如下错误：Mon Jun 04 23:27:32 2012NOTE: ASMB terminatingEr...
ora-15064会不会跟没有安装asmlib有关?
congchenjin2969的博客
01-15 134
SQL> ALTER DISKGROUP ALL MOUNTNOTE: cache registered group DATA number=1 incarn=0x41fce947NOTE: cache began mou...
网卡mtu 值不同导致rac 2节点ASM不能同时启动 ORA-27550: Target ID protocol check failed.
Lixora's DB Home
02-26 2211
在安装完10205 rac 后准备配置 asm dg ，发现节点二上的ASM 没法启动： en12 为private 网卡 en13 为 public 网卡 ---->> 查看 oracle asm alert log 报错显示： LMD0 started with pid=6, OS id=565728 LMS0 started with pid=7, OS id=491812
调整oracle服务器时间,oracle数据库因一次服务器时间调整引发的实例宕机注意事项及解决方案...
weixin_39821330的博客
04-03 554
详情：问题描述：1. 数据库实例突然crash，原因是ASMB有200多秒没有响应：Mon Sep 04 15:07:47 2017WARNING: ASMB has not responded for 200 seconds <<<<<<<<<<<< ASMB has not responsed for 200 second...
ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory
最新发布
05-10
<think>好的，我现在要解决用户在Linux环境下连接Oracle数据库时遇到的ORA-01034和ORA-27101错误。首先，我需要仔细理解用户的问题描述和提供的引用内容。 根据用户提供的引用[1]、[2]、[3]，这些错误通常与Oracle实例未启动或共享内存配置问题有关。用户尝试过登录并执行shutdown immediate，但同样报错，提示实例未启动。这可能意味着实例根本没有运行，或者共享内存区域无法访问。 首先，ORA-01034表明Oracle不可用，通常是因为实例未启动。而ORA-27101指出共享内存域不存在，可能涉及内存配置或权限问题。结合引用中的信息，特别是引用[2]提到管理员登录后无法关闭实例，因为实例未启动，这说明用户可能在尝试操作前未正确启动实例。 接下来，我需要考虑可能的原因和解决方案： 1. **实例未启动**：用户可能没有正确启动Oracle实例。需要检查实例状态，并尝试启动它。 2. **共享内存配置问题**：Oracle使用共享内存段，如果配置不正确或权限不足，会导致ORA-27101错误。 3. **环境变量设置错误**：ORACLE_SID或ORACLE_HOME未正确设置，导致实例无法识别。 4. **权限问题**：运行Oracle进程的用户（通常是oracle用户）没有足够的权限访问共享内存或相关文件。 5. **文件路径错误**：某些关键文件（如参数文件、控制文件）的路径不正确，导致实例无法启动。 6. **内存不足**：系统可用内存不足，无法分配共享内存区域。 接下来，我需要按照步骤逐步排查这些问题。首先检查实例状态，确认是否已启动。如果未启动，尝试启动实例。在启动过程中，可能会遇到更多错误，需要查看alert日志获取详细信息。同时，检查共享内存设置，确认Oracle用户有权访问相关资源。此外，验证环境变量是否正确配置，确保ORACLE_SID和ORACLE_HOME正确无误。如果问题依旧，可能需要检查参数文件（如init.ora或spfile）中的配置，特别是内存相关参数是否正确。最后，确认系统资源（如内存和交换空间）是否充足，避免因资源不足导致实例启动失败。 在用户提供的引用中，引用[3]提到解决方案可能涉及重新配置共享内存或调整内核参数。因此，可能需要检查/etc/sysctl.conf中的设置，如kernel.shmmax、kernel.shmall等，并确保其符合Oracle的要求。同时，检查Oracle用户的权限，确保其属于正确的用户组，如dba组。 另外，用户提到之前尝试shutdown immediate时出错，这可能是因为实例未处于运行状态，无法执行关闭操作。需要先启动实例，然后再进行关闭或其它操作。 总结，解决步骤可能包括： - 检查并启动Oracle实例 - 验证环境变量和参数配置 - 检查共享内存设置和权限 - 查看日志文件以获取详细错误信息 - 调整内核参数和Oracle配置 在回答时，需要将这些步骤详细列出，并给出具体的命令和检查方法，帮助用户逐步排查问题。同时，要确保命令的正确性和适用性，避免因操作不当导致问题加重。最后，可能需要提供相关的参考资料或进一步的问题，帮助用户深入理解问题原因和解决方案。</think>### 分步解决 Linux 环境下 Oracle 数据库 ORA-01034 和 ORA-27101 错误指南 --- #### 一、核心错误解析 - **ORA-01034: ORACLE not available** 表示数据库实例未启动或处于异常关闭状态[^1]。 - **ORA-27101: shared memory realm does not exist** 指 Oracle 无法访问共享内存段，通常由配置错误或权限问题导致[^2]。 --- #### 二、快速诊断流程 ```mermaid graph TD A[检查实例状态] -->|未运行| B[启动实例] A -->|已运行| C[检查共享内存] B --> D[查看启动日志] C --> E[验证内存配置] D --> F[分析错误详情] E --> G[调整内核参数] ``` --- #### 三、具体操作步骤 ##### 1. **验证实例状态** ```bash # 以 oracle 用户执行 su - oracle sqlplus / as sysdba SQL> SELECT status FROM v$instance; # 若返回 "STARTED" 或 "MOUNTED" 表示未完全打开 # 若返回空值说明实例未启动 ``` ##### 2. **强制启动实例** ```bash # 清理残留进程 ps -ef | grep ora_ | grep -v grep | awk '{print $2}' | xargs kill -9 # 分步启动数据库 sqlplus / as sysdba SQL> startup nomount; -- 启动到 NOMOUNT 状态 SQL> alter database mount; -- 挂载数据库 SQL> alter database open; -- 打开数据库 ``` ##### 3. **共享内存配置检查** ```bash # 查看当前共享内存分配 ipcs -m # 验证内核参数 (需 root 权限) sysctl -a | grep -E 'shmmax|shmall|shmmni' ``` - **关键参数要求**： - `kernel.shmmax >= 物理内存的 50%`（建议值） - `kernel.shmall >= 总物理内存/页大小`（页大小通过 `getconf PAGE_SIZE` 查看） - `kernel.shmmni >= 4096` ##### 4. **修正配置示例** ```bash # 临时修改（立即生效） sudo sysctl -w kernel.shmmax=4294967296 # 4GB sudo sysctl -w kernel.shmall=2097152 # 页大小4KB时对应8GB # 永久修改（写入 /etc/sysctl.conf） echo "kernel.shmmax=4294967296" | sudo tee -a /etc/sysctl.conf echo "kernel.shmall=2097152" | sudo tee -a /etc/sysctl.conf sudo sysctl -p ``` ##### 5. **权限修复操作** ```bash # 确认 oracle 用户权限 id oracle # 应包含 dba 组 # 重建共享内存段 sudo rm -f /dev/shm/* sudo chown oracle:dba /dev/shm sudo chmod 6755 /dev/shm ``` ##### 6. **关键日志分析** ```bash # 查看 alert 日志（路径示例） tail -100f $ORACLE_BASE/diag/rdbms/${ORACLE_SID,,}/${ORACLE_SID}/trace/alert_${ORACLE_SID}.log # 常见错误线索： # - ORA-00205: error in identifying control file # - ORA-03113: end-of-file on communication channel ``` --- #### 四、进阶故障排查 ##### 1. **参数文件验证** ```sql # 检查使用的 spfile/pfile SQL> show parameter spfile; # 若使用 pfile 需检查路径正确性 SQL> create pfile from spfile; -- 生成可读文本文件 vi $ORACLE_HOME/dbs/init${ORACLE_SID}.ora ``` ##### 2. **内存泄漏检测** ```bash # 检查共享内存段残留 ipcs -m | grep -v oracle | awk '{print $2}' | xargs -n1 ipcrm -m ``` ##### 3. **环境变量确认** ```bash # 检查关键变量 echo $ORACLE_SID # 必须与实际实例名一致 echo $ORACLE_HOME # 必须指向正确安装路径 echo $LD_LIBRARY_PATH # 应包含 $ORACLE_HOME/lib ``` --- #### 五、特殊场景处理 | 场景 | 解决方案 | |------|----------| | **RAC 环境** | 检查 `crsctl stat res -t` 确认集群资源状态 | | **ASM 存储** | 使用 `asmcmd lsctl` 验证磁盘组挂载 | | **容器数据库 (CDB)** | 确认 PDB 已正确打开：`ALTER PLUGGABLE DATABASE ALL OPEN;` | --- #### 六、预防措施 1. **创建启动监控脚本** ```bash #!/bin/bash if ! pgrep -f ora_pmon_${ORACLE_SID} >/dev/null; then echo "$(date): 检测到实例停止，尝试重启..." >> /var/log/oracle_monitor.log su - oracle -c "sqlplus / as sysdba <<EOF startup; exit; EOF" fi ``` 2. **配置 systemd 服务单元** ```ini # /etc/systemd/system/oracle.service [Unit] Description=Oracle DB After=network.target [Service] Type=forking User=oracle Environment="ORACLE_SID=ORCL" ExecStart=/u01/app/oracle/product/12.2.0/dbhome_1/bin/dbstart /u01/app/oracle/product/12.2.0/dbhome_1 ExecStop=/u01/app/oracle/product/12.2.0/dbhome_1/bin/dbshut /u01/app/oracle/product/12.2.0/dbhome_1 Restart=on-failure [Install] WantedBy=multi-user.target ``` --- ### 相关问题 1. **如何通过 Crash Recovery 修复因突然断电导致的数据库损坏？** 2. **Oracle 数据库在 Docker 容器中运行时出现 ORA-27101 应如何排查？** 3. **怎样配置 HugePages 来优化 Oracle 共享内存管理？** [^1]: 实例未启动时访问数据库会触发 ORA-01034 [^2]: 共享内存配置错误会导致操作系统级资源访问失败
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值