Keeping users off during maintenance.
Keith wanted to keep users off the instance during dbexport/dbimport because quiescent mode did not suit. Suggestions: Michael Krzepkowski, shut down the sqlhosts TCP line or rename startup scripts; John Carlson, revoke CONNECT; Fernando Nunes, a group file restricting connections (needs restart); Art Kagel, swap an empty database with the real one by renaming. No single outcome.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello All,
I am trying to automate a database reorg process. One thing I'd like
to do is keep users/applications off the instance while I'm doing the
dbexport/dbimport. Unfortunately quiescent mode doesn't even allow
the user informix access to a database.
The only thing I can think of is to rename all the databases --
perform the reorg -- then rename them back. Seems like a crazy way to
do it. Does anyone have any good ideas to achieve this?
Thanks in advance,
Keith
Keith wrote:
>Hello All,
>
>I am trying to automate a database reorg process. One thing I'd like
>to do is keep users/applications off the instance while I'm doing the
>dbexport/dbimport. Unfortunately quiescent mode doesn't even allow
>the user informix access to a database.
>
>The only thing I can think of is to rename all the databases --
>perform the reorg -- then rename them back. Seems like a crazy way to
>do it. Does anyone have any good ideas to achieve this?
>
>Thanks in advance,
>Keith
>
>
If they are accessing through tcp/ip shutdown one line on sqlhosts,
(but you have to use shmem connection),
if they are on the same server rename their startup script/executable
and dbaccess.
HTH
Michael
On 15 Oct 2003 11:58:50 -0700, kknauss@yahoo.com (Keith) wrote:
>Hello All,
>
>I am trying to automate a database reorg process. One thing I'd like
>to do is keep users/applications off the instance while I'm doing the
>dbexport/dbimport. Unfortunately quiescent mode doesn't even allow
>the user informix access to a database.
>
>The only thing I can think of is to rename all the databases --
>perform the reorg -- then rename them back. Seems like a crazy way to
>do it. Does anyone have any good ideas to achieve this?
>
Revoke connect privileges to the database?
Keith wrote:
> Hello All,
>
> I am trying to automate a database reorg process. One thing I'd like
> to do is keep users/applications off the instance while I'm doing the
> dbexport/dbimport. Unfortunately quiescent mode doesn't even allow
> the user informix access to a database.
>
> The only thing I can think of is to rename all the databases --
> perform the reorg -- then rename them back. Seems like a crazy way to
> do it. Does anyone have any good ideas to achieve this?
>
> Thanks in advance,
> Keith
There is a file where you can put the group name(s) of the users who are
allowed to connect to the instance.
This apply to all database in the instance and require the engine shutdown.
You can also revoke connect priviledges... and grant them again when done.
Regards.
On Wed, 15 Oct 2003 14:58:50 -0400, Keith wrote:
Rename the database! Create an empty database, rename the one you want to work
on to be some temporary name, rename the empty one to the original name, reorg
into the temp name, drop the dummy database, finally rename the good one.
Art S. Kagel
> Hello All,
>
> I am trying to automate a database reorg process. One thing I'd like to do is
> keep users/applications off the instance while I'm doing the
> dbexport/dbimport. Unfortunately quiescent mode doesn't even allow the user
> informix access to a database.
>
> The only thing I can think of is to rename all the databases -- perform the
> reorg -- then rename them back. Seems like a crazy way to do it. Does anyone
> have any good ideas to achieve this?
>
> Thanks in advance,
> Keith