- 论坛徽章:
- 0
|
输入：ontape -s -L 0
报错：Please mount tape 1 on /space1/informix/back/bak_db and press Return to continue ...
Archive failed - ISAM error: An error has occurred during archive back up.
LOG里的相关日志：
10:22:21 IBM Informix Dynamic Server Version 9.40.FC3W1
10:22:21 Who: Session(8750968, informix@informix, 19284, 1ad506c90)
Thread(11503298, ontape, 1b26579d8, 5)
File: rsarcutl.c Line: 120
10:22:21 Action: init_archive()/ALLOC()
10:22:21 stack trace for pid 21391 written to /tmp/af.8aaa01dc
10:22:21 See Also: /tmp/af.8aaa01dc
10:22:21 shmget: [EINVAL][22]: key 531e4805: invalid segment size
10:22:21 create_tcb: cannot allocate memory
10:22:21 Assert Failed: Invalid Mutex Type
10:22:21 IBM Informix Dynamic Server Version 9.40.FC3W1
10:22:21 Who: Session(8751016, user@informix, 19310, 1ac08c540)
Thread(11503424, xchg_1.0, 1bb6a2068, 4)
File: mt.c Line: 7747
10:22:21 stack trace for pid 21390 written to /tmp/af.8b2801dc
10:22:21 See Also: /tmp/af.8b2801dc, shmem.8b2801dc.0
10:22:22 ISAM error: An error has occurred during archive back up.
并没有做什么操作，数据库就宕了，用oninit -v 重启时很顺利的就起来了。此时再作0级备份就没问题了。
数据库宕时的日志：
10:22:47 mt.c, line 7747, thread 11503424, proc id 21390, Invalid Mutex Type.
10:22:47 Fatal error in ADM VP at mt.c:12298
10:22:47 Unexpected virtual processor termination, pid = 21390, exit = 0x100
10:22:47 PANIC: Attempting to bring system down
10:33:04 IBM Informix Dynamic Server Started.
Tue Jun 16 10:33:09 2009
10:33:09 Event alarms enabled. ALARMPROG = '/opt/informix/etc/no_log.sh'
10:33:09 Booting Language <c> from module <>
10:33:09 Loading Module <CNULL>
10:33:09 Booting Language <builtin> from module <>
10:33:09 Loading Module <BUILTINNULL>
10:33:16 Requested shared memory segment size rounded from 680KB to 1024KB
10:33:16 IBM Informix Dynamic Server Version 9.40.FC3W1 Software Serial Number AAA#B000000
10:33:18 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.
10:33:18 Physical Recovery Started at Page (2:964502).
10:33:19 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
10:33:19 Logical Recovery Started.
10:33:19 20 recovery worker threads will be started.
10:33:22 Logical Recovery has reached the transaction cleanup phase.
10:33:22 Logical Recovery Complete.
0 Committed, 1 Rolled Back, 0 Open, 0 Bad Locks
10:33:24 Dataskip is now OFF for all dbspaces
10:33:24 (2 connection rejected - no calls allowed for srvinfx
10:33:24 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic
Server quiescent mode.
10:33:24 (29) connection rejected - no calls allowed for srvinfx
10:33:24 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic
Server quiescent mode.
10:33:24 (30) connection rejected - no calls allowed for srvinfx
10:33:24 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic
Server quiescent mode.
10:33:24 Checkpoint Completed: duration was 0 seconds.
10:33:24 Checkpoint loguniq 159384, logpos 0x8b7b048, timestamp: -127564850
10:33:24 Maximum server connections 0
10:33:25 (31) connection rejected - no calls allowed for srvinfx
10:33:25 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic
Server quiescent mode.
10:33:25 On-Line Mode
10:33:25 Affinitied VP 3 to phys proc 1
10:33:25 Affinitied VP 4 to phys proc 0
10:33:25 Affinitied VP 5 to phys proc 1
10:33:25 Affinitied VP 6 to phys proc 0
10:33:25 Affinitied VP 1 to phys proc 0
10:33:30 Booting Language <spl> from module <>
10:33:30 Loading Module <SPLNULL>
10:33:53 Checkpoint Completed: duration was 0 seconds.
10:33:53 Checkpoint loguniq 159384, logpos 0x8c06018, timestamp: -127557973
10:33:53 Maximum server connections 6
10:34:50 Checkpoint Completed: duration was 0 seconds.
10:34:50 Checkpoint loguniq 159384, logpos 0xa8d1018, timestamp: -127339929
10:34:50 Maximum server connections 14
10:34:53 Level 0 Archive started on rootdbs, plogdbs, llogdbs,oddbs
10:35:28 Logical Log 159384 Complete, timestamp:-127095141.
为什么会重启？？？ |
|
免费注册
发表于 2009-06-16 14:04
