IT其它宕机

备份停止导致宕机问题

数据库每周6晚上自动备份,查看日志准备备份完成就宕机了,日志贴出来,各位大大能帮看一下吗?是不是这个版本的BUG呢?理论上即使备份停止了,应该也不会导致宕机啊23:40:54  Level 0 Archive started on rootdbs23:43:03  Archive on rootdbs Completed.23:43...显示全部
数据库每周6晚上自动备份,查看日志准备备份完成就宕机了,日志贴出来,各位大大能帮看一下吗?是不是这个版本的BUG呢?理论上即使备份停止了,应该也不会导致宕机啊



23:40:54  Level 0 Archive started on rootdbs
23:43:03  Archive on rootdbs Completed.
23:43:04  Level 0 Archive started on kpidbs09
23:43:04  Level 0 Archive started on kpidbs11
23:43:04  Level 0 Archive started on kpidbs02
23:43:04  Level 0 Archive started on kpidbs04
23:43:04  Level 0 Archive started on kpidbs03
23:43:04  Level 0 Archive started on kpidbs06
23:43:04  Level 0 Archive started on kpidbs12
23:43:04  Level 0 Archive started on kpidbs10
23:43:04  Level 0 Archive started on kpidbs07
23:43:04  Level 0 Archive started on kpidbs05
23:43:04  Level 0 Archive started on kpidbs01
23:43:04  Level 0 Archive started on kpidbs
23:43:04  Level 0 Archive started on tmpdbs05
23:43:04  Level 0 Archive started on kpidbs08
23:43:04  Level 0 Archive started on tmpdbs04
23:43:04  Level 0 Archive started on tmpdbs06
23:43:04  Level 0 Archive started on tmpdbs01
23:43:04  Level 0 Archive started on tmpdbs03
23:43:04  Level 0 Archive started on tmpdbs02
23:43:04  Level 0 Archive started on plogdbs
23:43:04  Level 0 Archive started on llogdbs
23:43:56  Archive on tmpdbs02 Completed.
23:44:21  Archive on llogdbs Completed.
23:44:21  Archive on tmpdbs03 Completed.
23:44:21  Archive on plogdbs Completed.
23:44:26  Archive on tmpdbs05 Completed.
23:44:26  Archive on tmpdbs04 Completed.
23:44:31  Archive on tmpdbs01 Completed.
23:45:26  Checkpoint Completed:  duration was 1 seconds.
23:45:26  Sat Jan 19 - loguniq 56596, logpos 0xf508018, timestamp: 0x6ea0d8e2 Interval: 334780

23:45:26  Maximum server connections 16
23:45:26  Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 127, Llog used 21661

23:48:10  Archive on tmpdbs06 Completed.
23:48:17  Archive on kpidbs08 Completed.
23:50:28  Checkpoint Completed:  duration was 1 seconds.
23:50:28  Sat Jan 19 - loguniq 56596, logpos 0x158dd480, timestamp: 0x6eaa19a6 Interval: 334781

23:50:28  Maximum server connections 16
23:50:28  Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 1, Plog used 987, Llog used 25771

23:51:03  Archive on kpidbs02 ABORTED.
23:51:03  Aborted by client.
23:51:04  Archive on rootdbs ABORTED.
23:51:04  Aborted by client.
23:51:59  stack trace for pid 918 written to /opt/informix3/tmp/af.1bf1c11e
23:51:59  Assert Failed: No Exception Handler
23:51:59  IBM Informix Dynamic Server Version 11.50.FC3   
23:51:59   Who: Session(130632, informix@nms-hdb, 5939, 1f8a64f68)
                Thread(202761, arcbackup1, 1f8a2cda8, 1)
                File: mtex.c Line: 481
23:51:59   Results: Exception Caught. Type: MT_EX_OS, Context: mem
23:51:59   Action: Please notify IBM Informix Technical Support.
23:51:59   See Also: /opt/informix3/tmp/af.1bf1c11e
23:52:21  stack trace for pid 946 written to /opt/informix3/tmp/af.1bf4c134
23:52:21  Assert Failed: No Exception Handler
23:52:21  IBM Informix Dynamic Server Version 11.50.FC3   
23:52:21   Who: Session(130635, informix@nms-hdb, 5942, 1f8a614a8)
                Thread(202764, ontape, 1f8a328c0, 5)
                File: mtex.c Line: 481
23:52:21   Results: Exception Caught. Type: MT_EX_OS, Context: mem
23:52:21   Action: Please notify IBM Informix Technical Support.
23:52:21   See Also: /opt/informix3/tmp/af.1bf4c134
23:54:02  stack trace for pid 941 written to /opt/informix3/tmp/af.1be8c199
23:54:02  Assert Failed: No Exception Handler
23:54:02  IBM Informix Dynamic Server Version 11.50.FC3   
23:54:02   Who: Session(130629, informix@nms-hdb, 5936, 1f8a608e8)
                Thread(202752, ontape, 1f8a2de38, 4)
                File: mtex.c Line: 481
23:54:02   Results: Exception Caught. Type: MT_EX_OS, Context: mem
23:54:02   Action: Please notify IBM Informix Technical Support.
23:54:02   See Also: /opt/informix3/tmp/af.1be8c199
23:55:36  stack trace for pid 950 written to /opt/informix3/tmp/af.1bf5c1f8
23:55:37  Assert Failed: No Exception Handler
23:55:37  IBM Informix Dynamic Server Version 11.50.FC3   
23:55:37   Who: Session(130636, informix@nms-hdb, 5943, 1f8a634f8)
                Thread(202765, ontape, 1f8a29bf8, 9)
                File: mtex.c Line: 481
23:55:37   Results: Exception Caught. Type: MT_EX_OS, Context: mem
23:55:37   Action: Please notify IBM Informix Technical Support.
23:55:37   See Also: /opt/informix3/tmp/af.1bf5c1f8
23:58:24  mtex.c, line 481, thread 202761, proc id 918, No Exception Handler.
23:58:25  The Master Daemon Died
23:58:25  PANIC: Attempting to bring system down
13:46:57  IBM Informix Dynamic Server Started.
13:46:57  Requested shared memory segment size rounded from 1824000KB to 1824768KB

Sun Jan 20 13:47:00 2013

13:47:00  Event alarms enabled.  ALARMPROG = '/opt/informix3/etc/no_log.sh'
13:47:00  Booting Language from module <>
13:47:00  Loading Module
13:47:00  Booting Language from module <>
13:47:00  Loading Module
13:47:00  Warning: CONSOLE = /opt/informix3/tmp/online.con open failed. Redirecting output to '/dev/null'.
13:47:06  DR: DRAUTO is 0 (Off)
13:47:06  DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)
13:47:06  Requested shared memory segment size rounded from 560KB to 1024KB
13:47:06  Fast poll /dev/poll enabled.
13:47:06  IBM Informix Dynamic Server Version 11.50.FC3     Software Serial Number AAA#B000000
13:47:15  IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.

13:47:15  Started 1 B-tree scanners.
13:47:15  B-tree scanner threshold set at 5000.
13:47:15  B-tree scanner range scan size set to -1.
13:47:15  B-tree scanner ALICE mode set to 6.
13:47:15  B-tree scanner index compression level set to med.
13:47:15  Physical Recovery Started at Page (2:389352).
13:47:15  Physical Recovery Complete: 993 Pages Examined, 993 Pages Restored.
13:47:15  Logical Recovery Started.
13:47:15  16 recovery worker threads will be started.
13:47:17  Logical Recovery has reached the transaction cleanup phase.
13:47:17  Logical Recovery Complete.
          25 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

13:47:18  Dataskip is now OFF for all dbspaces
13:47:18  Checkpoint Completed:  duration was 0 seconds.
13:47:18  Sun Jan 20 - loguniq 56596, logpos 0x16220018, timestamp: 0x6eaae76b Interval: 334782

13:47:18  Maximum server connections 0
13:47:18  Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 1114, Llog used 1

13:47:18  On-Line Mode
13:47:20  SCHAPI: Started dbScheduler thread.
13:47:20  Booting Language from module <>
13:47:20  Loading Module
13:47:20  SCHAPI: Started 2 dbWorker threads.
13:47:28  Logical Log 56596 Complete, timestamp: 0x6eae4821.
13:51:06  IBM Informix Dynamic Server Started.
13:51:06  shmget: [EEXIST][17]: key 525d4801: shared memory already exists
13:51:06  mt_shm_init: can't create resident segment

13:52:49  Checkpoint Completed:  duration was 2 seconds.
13:52:49  Sun Jan 20 - loguniq 56597, logpos 0x5b57018, timestamp: 0x6eb6aa83 Interval: 334783

把af文件也贴出来了  谢谢各位了
            

附件:

附件图标af.1be8c199 (912.3 KB)

附件图标af.1bf1c11e (1.86 MB)

附件图标af.1bf4c134 (1.22 MB)

附件图标af.1bf5c1f8 (348.13 KB)

收起
参与5

查看其它 4 个回答chenchao79的回答

chenchao79chenchao79技术经理浪潮通信
记不清是不是11.5了,记得有个bug,就是在备份的时候,会申请内存,在内存占用率超过80%时,就会引起宕机现象,我在之前碰到过。
你要看看你的其中一个dbs是不是数据量很大,导致备份很慢。
如果是这样的就要减轻这个空间的数据量,如删除表或迁移数据。
还有就是增加cpu和内存,也可以解决这问题。
电信设备制造商 · 2013-01-30
浏览815

回答者

chenchao79
技术经理浪潮通信

chenchao79 最近回答过的问题

回答状态

  • 发布时间:2013-01-30
  • 关注会员:0 人
  • 回答浏览:815
  • X社区推广