ISM issue.
Posted in 2010
A new ISM setup on IDS 11.50 on Linux left 'onbar -b -w' hanging with BAR_TIMEOUT warnings, while ism_watch/daemon.log repeatedly reported 'backup to pool ISMDiskData waiting for writable tape(s)/disk(s)' and showed both file devices with no volume label. Advice was to drop the stale tape device (/dev/nrst8), check for hung ism_op processes, and re-run the label/mount commands (optionally with -force) as the informix user rather than root. Running ism_op -label and -mount as informix fixed it: volumes ISMLogs/ISMData mounted and the backup wrote successfully. It was also noted that nsrd and nsrexecd are the running ISM processes.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Backup & Restore, Installation, Setup & Upgrades, Storage & Space Management, Server Administration, Platform-Specific Issues
Hi,
I just setup the ISM for the new install of Linux Dynamic Server Version
11.50.FC1, and I have issue with onbar b w in the new ISM setup. Please
advise.
Here is the ISM setup
Modified the onconfig file.
ISM_DATA_POOL ISMDiskData
ISM_LOG_POOL ISMDiskLogs
LTAPEDEV /apps/informix/savelogs_tri
Login as root:
ism_startup init
ism_add -admin informix@inftest2.newpiper.net
8. Add the storage devices to the ISM server by using the ism_add command with
the following syntax:
./ism_add -device /apps/informix/savelogs_tri -type file
./ism_add -device /apps/informix/savedata_tri -type file
9. Label the devices by using the ism_op command with this syntax:
./ism_op label /apps/informix/savelogs_tri pool ISMDiskLogs volume ISMLogs
./ism_op label /apps/informix/savedata_tri pool ISMDiskData volume ISMData
10. Mount the devices by using ism_op command with this syntax:
./ism_op -mount /apps/informix/savelogs_tri
./ism_op -mount /apps/informix/savedata_tri
Here is my on_bar.log:
2010-08-19 08:36:23 27164 27162 /apps/informix/bin/onbar_d -b -l
2010-08-19 08:36:23 27164 27162 /apps/informix/bin/onbar_d complete, returning
0 (0x00)
2010-08-19 08:36:30 27171 27169 /apps/informix/bin/onbar_d -b -w
2010-08-19 08:36:30 27171 27169 Archive started on rootdbs (Requested Level 0).
2010-08-19 08:36:30 27171 27169 Begin level 0 backup rootdbs.
2010-08-19 08:36:30 27171 27169 Successfully connected to Storage Manager.
2010-08-19 08:48:30 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 09:28:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 10:08:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 10:48:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 11:28:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 12:08:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 12:48:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 13:28:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
2010-08-19 14:08:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage Manager
Progress may be stalled.
Bew is the result from the ism_watch
Server: inftest1.newpiper.net Thu Aug 19 14:59:17 2010
Up since: Wed Aug 18 11:11:27 2010 Version: Informix_Storage_Manager
ISM.2.20.UC1.119-02/13 Server Edition
Saves: 0 session(s) Recovers: 0 session(s)
Device type volume
/dev/nrst8 8mm 5GB (none)
x/savelogs_tri file (none)
x/savedata_tri file (none)
Sessions:
Messages:
Thu 13:41:21 media event cleared: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(
Thu 13:41:51 media waiting event: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(
Thu 13:56:51 media critical event: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk
Thu 14:12:01 media event cleared: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(
Thu 14:12:33 media waiting event: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(
Thu 14:27:33 media critical event: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk
Thu 14:42:33 media event cleared: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(
Thu 14:43:05 media waiting event: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(
Thu 14:58:05 media critical event: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk
Pending:
Thu 14:43:05 media critical: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(s)
From your ism_watch output, I see that nothing is labeled and I think
that's where the problem is, though I'm not sure why your "ism_op -label"
command failed. Are "savelogs_tri" and "savedata_tri" directories that
exist on this box and can onbar write to them? I would manually rerun the
"ism_op -label" command and see what happens. If it fails again, please
send the output from either ism_watch or from /nsr/daemon.log.
You may also want to run "ism_rm -device /dev/nrst8" to get rid of that
device.
Joe
From: "TRI TRINH" <tri_trinh@hotmail.com>
To: ids@iiug.org
Date: 08/19/2010 02:08 PM
Subject: ISM issue. [20970]
Sent by: ids-bounces@iiug.org
Hi,
I just setup the ISM for the new install of Linux Dynamic Server Version
11.50.FC1, and I have issue with ?onbar ?b ?w? in the new ISM setup.
Please
advise.
Here is the ISM setup
Modified the onconfig file.
ISM_DATA_POOL ISMDiskData
ISM_LOG_POOL ISMDiskLogs
LTAPEDEV /apps/informix/savelogs_tri
Login as root:
ism_startup ?init
ism_add -admin informix@inftest2.newpiper.net
8. Add the storage devices to the ISM server by using the ism_add command
with
the following syntax:
../ism_add -device /apps/informix/savelogs_tri -type file
../ism_add -device /apps/informix/savedata_tri -type file
9. Label the devices by using the ism_op command with this syntax:
../ism_op ?label /apps/informix/savelogs_tri ?pool ISMDiskLogs ?volume
ISMLogs
../ism_op ?label /apps/informix/savedata_tri ?pool ISMDiskData ?volume
ISMData
10. Mount the devices by using ism_op command with this syntax:
../ism_op -mount /apps/informix/savelogs_tri
../ism_op -mount /apps/informix/savedata_tri
Here is my on_bar.log:
2010-08-19 08:36:23 27164 27162 /apps/informix/bin/onbar_d -b -l
2010-08-19 08:36:23 27164 27162 /apps/informix/bin/onbar_d complete,
returning
0 (0x00)
2010-08-19 08:36:30 27171 27169 /apps/informix/bin/onbar_d -b -w
2010-08-19 08:36:30 27171 27169 Archive started on rootdbs (Requested
Level
0).
2010-08-19 08:36:30 27171 27169 Begin level 0 backup rootdbs.
2010-08-19 08:36:30 27171 27169 Successfully connected to Storage Manager.
2010-08-19 08:48:30 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 09:28:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 10:08:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 10:48:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 11:28:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 12:08:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 12:48:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 13:28:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
2010-08-19 14:08:31 27171 27169 (-43296) WARNING: BAR_TIMEOUT Storage
Manager
Progress may be stalled.
Bew is the result from the ism_watch
Server: inftest1.newpiper.net Thu Aug 19 14:59:17 2010
Up since: Wed Aug 18 11:11:27 2010 Version: Informix_Storage_Manager
ISM.2.20.UC1.119-02/13 Server Edition
Saves: 0 session(s) Recovers: 0 session(s)
Device type volume
/dev/nrst8 8mm 5GB (none)
x/savelogs_tri file (none)
x/savedata_tri file (none)
Sessions:
Messages:
Thu 13:41:21 media event cleared: backup to pool 'ISMDiskData' waiting for
1
writable backup tape(s) or disk(
Thu 13:41:51 media waiting event: backup to pool 'ISMDiskData' waiting for
1
writable backup tape(s) or disk(
Thu 13:56:51 media critical event: backup to pool 'ISMDiskData' waiting
for 1
writable backup tape(s) or disk
Thu 14:12:01 media event cleared: backup to pool 'ISMDiskData' waiting for
1
writable backup tape(s) or disk(
Thu 14:12:33 media waiting event: backup to pool 'ISMDiskData' waiting for
1
writable backup tape(s) or disk(
Thu 14:27:33 media critical event: backup to pool 'ISMDiskData' waiting
for 1
writable backup tape(s) or disk
Thu 14:42:33 media event cleared: backup to pool 'ISMDiskData' waiting for
1
writable backup tape(s) or disk(
Thu 14:43:05 media waiting event: backup to pool 'ISMDiskData' waiting for
1
writable backup tape(s) or disk(
Thu 14:58:05 media critical event: backup to pool 'ISMDiskData' waiting
for 1
writable backup tape(s) or disk
Pending:
Thu 14:43:05 media critical: backup to pool 'ISMDiskData' waiting for 1
writable backup tape(s) or disk(s)
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I had the two directories created. drwxrwxr-x 2 informix informix 4096 Aug 18 14:58 savedata_tri drwxrwxr-x 2 informix informix 4096 Aug 18 11:19 savelogs_tri reapplied the ism_op -label without complain [root@inftest1 bin]# ./ism_op -label /apps/informix/savelogs_tri -pool ISMDiskLogs -volume ISMLogs [root@inftest1 bin]# ./ism_op -label /apps/informix/savedata_tri -pool ISMDiskData -volume ISMData [root@inftest1 bin]# ism_watch output Server: inftest1.newpiper.net Fri Aug 20 10:15:22 2010 Up since: Wed Aug 18 11:11:27 2010 Version: Informix_Storage_Manager ISM.2.20.UC1.119-02/13 Server Edition Saves: 0 session(s) Recovers: 0 session(s) Device type volume /dev/nrst8 8mm 5GB (none) x/savelogs_tri file (none) x/savedata_tri file (none) Sessions: Messages: Fri 08:55:01 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:10:01 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:25:11 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:25:41 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:40:42 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:55:42 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:56:14 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:11:14 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:12:03 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:12:03 media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s) Pending: Fri 10:12:03 media critical: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s) deamon.log output [root@inftest1 logs]# tail -f daemon.log 08/20/10 08:55:01 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:10:01 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:25:11 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:25:41 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:40:42 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:55:42 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:56:14 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:11:14 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:12:03 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:12:03 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s)
I removed the device /dev/nrst8 as your advise. Now the nbar knows the device is disk, but still does not backup. Server: inftest1.newpiper.net Fri Aug 20 10:29:19 2010 Up since: Wed Aug 18 11:11:27 2010 Version: Informix_Storage_Manager ISM.2.20.UC1.119-02/13 Server Edition Saves: 0 session(s) Recovers: 0 session(s) Device type volume x/savelogs_tri file (none) x/savedata_tri file (none) Sessions: Messages: Fri 09:25:41 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:40:42 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:55:42 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:56:14 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:11:14 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:12:03 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:12:03 media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s) Fri 10:26:14 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) Fri 10:26:46 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) Fri 10:26:46 media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup disk(s) Pending: Fri 10:26:46 media critical: backup to pool 'ISMDiskData' waiting for 2 writable backup disk(s) deamon.log [root@inftest1 logs]# tail -f daemon.log 08/20/10 08:55:01 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:10:01 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:25:11 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:25:41 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:40:42 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:55:42 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:56:14 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:11:14 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:12:03 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:12:03 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s) 08/20/10 10:26:14 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) 08/20/10 10:26:46 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) 08/20/10 10:26:46 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup disk(s)
Tri, Off the top of my head (and just guesses)... 1. ps -ef | grep for ism_op and make sure there is nothing else running/hung. If so, kill. 2. run your ism_op command as Informix 3. for your "ism_op -label" command, put a "-force" at the end of it. If none of this works, I think there has to be a more informative error message somewhere. The /nsr/logs/daemon.log will show success like: 08/20/10 05:45:09 nsrd: /data/ids_backup/full unmounted data20100819.054504 08/20/10 05:45:11 nsrd: /data/ids_backup/logs unmounted logs20100819.054504 08/20/10 05:45:13 nsrd: /data/ids_backup/full verify label operation in progress 08/20/10 05:45:13 nsrd: /data/ids_backup/full label without mount operation in progress 08/20/10 05:45:15 nsrd: /data/ids_backup/logs verify label operation in progress 08/20/10 05:45:15 nsrd: /data/ids_backup/logs label without mount operation in progress 08/20/10 05:45:17 nsrd: /data/ids_backup/full mount operation in progress 08/20/10 05:45:19 nsrd: /data/ids_backup/logs mount operation in progress So I thought it would show you an error message when the "ism_op -label" failed. Joe From: "TRI TRINH" <tri_trinh@hotmail.com> To: ids@iiug.org Date: 08/20/2010 09:32 AM Subject: Re: ISM issue. [20983] Sent by: ids-bounces@iiug.org I removed the device /dev/nrst8 as your advise. Now the nbar knows the device is disk, but still does not backup. Server: inftest1.newpiper.net Fri Aug 20 10:29:19 2010 Up since: Wed Aug 18 11:11:27 2010 Version: Informix_Storage_Manager ISM.2.20.UC1.119-02/13 Server Edition Saves: 0 session(s) Recovers: 0 session(s) Device type volume x/savelogs_tri file (none) x/savedata_tri file (none) Sessions: Messages: Fri 09:25:41 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:40:42 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:55:42 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 09:56:14 media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:11:14 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:12:03 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) Fri 10:12:03 media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s) Fri 10:26:14 media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) Fri 10:26:46 media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) Fri 10:26:46 media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup disk(s) Pending: Fri 10:26:46 media critical: backup to pool 'ISMDiskData' waiting for 2 writable backup disk(s) deamon.log [root@inftest1 logs]# tail -f daemon.log 08/20/10 08:55:01 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:10:01 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:25:11 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:25:41 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:40:42 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:55:42 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 09:56:14 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:11:14 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:12:03 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s) 08/20/10 10:12:03 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup tape(s) or disk(s) 08/20/10 10:26:14 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) 08/20/10 10:26:46 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s) 08/20/10 10:26:46 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 2 writable backup disk(s) ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Joseph, Thank you very much. The label and mount commands run by informix user as your advise. I issued by root and they did not work. The label and volume are correct, and it works now. I did "ps -ef|grep ism", and it returned no process. The "./ism_startup init" issued by root. Is this the proces /apps/informix/bin/nsrd? Device type volume x/savelogs_tri file ISMLogs writing, done x/savedata_tri file ISMData writing, done
Thank you very much for your patience with me. tri
Tri, You are very welcome. To answer your question, if I understand it, is "yes" the $INFORMIXDIR/bin/nsrd and also the $INFORMIXDIR/bin/nsrexecd processes are in fact your ISM running. If I'm wrong or further explanation is needed, maybe one of the forum gurus can chime in. Enjoy your weekend, Joe From: "TRI TRINH" <tri_trinh@hotmail.com> To: ids@iiug.org Date: 08/20/2010 10:06 AM Subject: Re: ISM issue. [20985] Sent by: ids-bounces@iiug.org Joseph, Thank you very much. The label and mount commands run by informix user as your advise. I issued by root and they did not work. The label and volume are correct, and it works now. I did "ps -ef|grep ism", and it returned no process. The "./ism_startup ?init" issued by root. Is this the proces /apps/informix/bin/nsrd? Device type volume x/savelogs_tri file ISMLogs writing, done x/savedata_tri file ISMData writing, done ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.