ORA-07445: exception encountered导致数据库实例无法启动问题处理

最新推荐文章于 2024-10-07 17:03:31 发布

原创

最新推荐文章于 2024-10-07 17:03:31 发布 · 2.6k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#oracle #dba #数据库

本文记录了一次Oracle 11.2.0.4数据库实例启动失败的问题排查过程，主要表现为一个节点因进程异常被PMON终止，通过分析错误日志定位到与/var/tmp/.oracle目录文件被误删除有关。

数据库版本：Oracle 11.2.0.4
数据库启动后其中一个节点Instance terminated by PMON, pid = 44253导致数据库实例无法启动
告警日志：

Fri Mar 25 17:41:08 2022
RCBG started with pid=51, OS id=44654 
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Mar 25 17:41:09 2022
QMNC started with pid=52, OS id=44658 
Errors in file /u01/app/oracle/diag/rdbms/syorcl/syorcl1/trace/syorcl1_ora_44429.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-23322: Privilege error accessing pipe
ORA-06512: at "HZMCASSET.TSECTOOLS", line 58
ORA-06512: at line 6
Completed: ALTER DATABASE OPEN /* db agent *//* {0:41:3} */
Thread 1 advanced to log sequence 58320 (LGWR switch)
  Current log# 10 seq# 58320 mem# 0: +DATA/syorcl/onlinelog/redo10.log
Fri Mar 25 17:41:13 2022
Archived Log entry 6955 added for thread 1 sequence 58319 ID 0xbcf06b10 dest 1:
******************************************************************
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_4
******************************************************************
LNS: Standby redo logfile selected for thread 1 sequence 58320 for destination LOG_ARCHIVE_DEST_4
Fri Mar 25 17:41:13 2022
ARC3: Standby redo logfile selected for thread 1 sequence 58319 for destination LOG_ARCHIVE_DEST_4
Fri Mar 25 17:41:21 2022
minact-scn: Inst 1 is a slave inc#:20734 mmon proc-id:44333 status:0x2
minact-scn status: grec-scn:0x0000.00000000 gmin-scn:0x0000.00000000 gcalc-scn:0x0000.00000000
Fri Mar 25 17:41:21 2022
Starting background process CJQ0
Fri Mar 25 17:41:21 2022
CJQ0 started with pid=85, OS id=44768 
Fri Mar 25 17:41:22 2022
Dumping diagnostic data in directory=[cdmp_20220325174135], requested by (instance=2, osid=25931 (LMS3)), summary=[incident=576121].
Fri Mar 25 17:41:23 2022
Reconfiguration started (old inc 20734, new inc 20736)
List of instances:
 1 (myinst: 1) 
 Global Resource Directory frozen
 * dead instance detected - domain 0 invalid = TRUE 
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Fri Mar 25 17:41:23 2022
Fri Mar 25 17:41:23 2022
 LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Fri Mar 25 17:41:23 2022
 LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
 LMS 2: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Fri Mar 25 17:41:23 2022
 LMS 3: 3 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
 Post SMON to start 1st pass IR
 Submitted all GCS remote-cache requests
 Post SMON to start 1st pass IR
 Fix write in gcs resources
Reconfiguration complete
Fri Mar 25 17:41:24 2022
Transaction recovery: lock conflict caught and ignored
Instance recovery: looking for dead threads
Beginning instance recovery of 1 threads
minact-scn: Inst 1 is now the master inc#:20736 mmon proc-id:44333 status:0x7
minact-scn status: grec-scn:0x0000.00000000 gmin-scn:0x0000.00000000 gcalc-scn:0x0000.00000000
minact-scn: master foun