S
Simon L. Prinsloo
Guest
I think that this question highlights a short coming that I encountered myself before. You want to get the database into a state where users are kicked out and no new users are allowed in, the only reliable way is to shut the database. But if you want replication to catch up, you need to start the database. What I need from time to time is the ablity to switch the database to a state where a) Users are disconnected as soon as they have no open transactions, b) (Almost) no new connections are allowed. (Promon is still needed to detect and disconnect users with long running processes and if the replication server crashed, it needs to be possible to restart it. Keeping the ai archiver going is also a benefit). c) Replication process normally. d) The database shuts down automatically as soon as there are no more users and replication is up to date. Idealy, if the ai archiver is configured, the very last step should be to switch to a new ai extent and to finish archiving the remaining ones. I do suspect that ChUIMonster has a very similar need, prompting this question. The closest I could get is in applications that requires connection to more than one database, where you force the startup procedure to access at least two databases. Then you shut one of these and wait for processing to finish on the others. Then you shut those and start the one that was shut first, wait for it to finish processing and shut it again. But this is a manual, labor intensive process that cannot be scripted (easily).
Continue reading...
Continue reading...