Re: dbexport - exclusive locking
Posted in 2005
Both messages refer to the same, someone is using the database so you can't do the unload.
You could do some onstat -u to test if there are users remaining. When there isn't you can di the dbexport.
Other approach is to shutdown your instance. Then bring it up online and inmediatly you do your dbexport. Your users won't connect to the database of course.
You can shutdown your instance when no users are connected to them (some kind of onmode I can't remember).
Thi may help.
J.
-----Original Message-----
From: gary.cobden@nhs.net
To: informix-list@iiug.org
Date: 16 Dec 2005 04:25:24 -0800
Subject: dbexport - exclusive locking
Morning all
I'm running the following script to export an informix database:-
INFORMIXDIR=/usr/informix export INFORMIXDIR
INFORMIXSERVER=ONLINELIVE
ONCONFIG=onconfig.live
PATH=$PATH:$INFORMIXDIR/bin
export INFORMIXSERVER ONCONFIG PATH /usr/informix/bin/dbexport dbname -c -o /scratch/schema
I get the following error messages
-425 - Database is currently opened by another user.
-107 - ISAM error: record is locked.
and sometimes
Cannot create message file
In respect of the firsterror, I am now aware of the need for
exclusivity in order for the dbexport command to run. Does anybody
have any additional code that I can incorporate into the above script
to facilitate this?
Any ideas on the second?
Many thanks
Gary Cobden
Jean Sagi
jeansagi@myrealbox.com
jeansagi@gmail.com
sending to informix-list