Re: Using dbexport

This is how we implemented it which works for version 5, or 6, or 7: 1. We are a UNIX shop and put a message in everyone's login profile that at a specific time each week, the database will be brought down. (Of course, this works well if all the databases are in the same instance and will "dbexport" at the same time.) 2. It can be via cron or via operator control, but have a script create a "boogus" file that everyone's profile looks for existence. If it exists, users are not allowed to log into the database or ap. The instance is put into quiescent mode to kill off any threads using the database. As soon as it is back into online mode, the script checks the online log to make certain everything is fine... then it kicks off the dbexport or tbunload which prevents anyone from getting back into the database until the job is completed. Then, the "boogus" file gets deleted. 3. Via a script... you can get pretty sophisticated and check the "-u" user threads, as each one ends... send them a "nice" message and log them off. You could lock them out by changing permissions on the database (depending how you are doing security). There are a million ways of doing it... we chose the simple and clean way of: "you were forewarned, you will be kicked off." Hope that helps a little.