informix 10 數(shù)據(jù)庫突然宕掉

ebupt

具體日志如下：
23:11:02  WARNING! Physical Log size 50000 is too small.
          Physical Log overflows may occur during peak activity.
          Recommended minimum Physical Log size is 20 times maximum
          concurrent user threads.

23:11:02  Process exited with return code 1: /bin/sh /bin/sh -c /home/informix/alarmAPI/log_full.sh 3 7 "Dynamic Server Initialization failure." "WARNING! Physical Lo
23:17:41  mtex.c, line 472, thread 0, proc id 28203, No Exception Handler.
23:18:00  VP Notify mechanism incomplete after 5 minutes. This can be due to slow network file access. Will try 12 more times
23:18:00  Affinitied VP 1 to phys proc 1
23:18:00  VP Notify mechanism completed
23:18:00  Dynamically allocated new virtual shared memory segment (size 200000KB)
23:18:00  Memory sizes:resident:4358200 KB, virtual:1000000 KB, no SHMTOTAL limit
23:18:00  invoke_alarm(): /bin/sh -c '/home/informix/alarmAPI/log_full.sh 5 6 "Internal Subsystem failure: 'MT'" "mtex.c, line 472, thread 0, proc id 28203, No Exception Handler." '
23:18:00  invoke_alarm(): mt_exec failed, status 256, errno 0
23:18:01  The Master Daemon Died
23:18:01  The Master Daemon Died
23:18:01  invoke_alarm(): /bin/sh -c '/home/informix/alarmAPI/log_full.sh 5 6 "Internal Subsystem failure: 'MT'" "The Master Daemon Died" '
23:18:01  invoke_alarm(): mt_exec failed, status 256, errno 0
23:18:01  invoke_alarm(): /bin/sh -c '/home/informix/alarmAPI/log_full.sh 5 6 "Internal Subsystem failure: 'MT'" "The Master Daemon Died" '
23:18:01  invoke_alarm(): mt_exec failed, status 256, errno 0
23:18:01  PANIC: Attempting to bring system down
不清楚是什么原因造成的，哪位大俠給分析一下，給個建議。這臺主機從來沒出現(xiàn)過這種問題，今天第一次出現(xiàn)。

liaosnet

沒有af輸出？

大夢

前面報的好象是物理日志太小了。

lmwzmf

VP Notify mechanism incomplete after 5 minutes. This can be due to slow network file access. Will try 12 more times
對于這樣的錯誤，最好檢查下磁陣的問題，如果12次檢查均失敗，數(shù)據(jù)庫也會直接宕的；
你發(fā)的日志里，應(yīng)該很難看出宕的原因，還需要af文件支持