There's a good news and not-so-good news.\nGood news is that Ingres/Actian X 11.x has a quiesce function.\nQuiesce function in Ingres stops the Communications Servers (iigcc) after all current sessions have terminated or disconnected.\nWhereas, Stop function force stop all the iigcn in an instant.\n\nSyntax:\nNetutil -file-\nstop | quiesce <ServerId>\n\nThe not-so-good news is that the use the quiesce function will prove challenging in HDMF's scenario due to the following reasons:\n\t1. The behavior of quiesce is that it will temporarily block all new and incoming connections by restricting the iigcc. \n\t2. Meaning, all users who terminated and/or disconnected all their connections to the server, cannot go back until the iigcc has started again.  \n\t3. Meanwhile, if a certain user did not terminated and/or disconnected his/her connection, iigcc cannot continue to stop and will be stalled until all user/s disconnects.  \n\t4. In addition, while the iigcc is at stall, rules still apply that all new and incoming connections are temporarily blocked.\n\nPossible resolution:\n\t1. Test the use case of quiesce carefully and create a policy supporting this approach\n\t2. Once a day, prior to the issuance of quiesce, help desk will announce an <x amount> of calm/quiet time for operation\n\t3. DBA will issue a quiesce command\n\t4. DBA will check all active connections without current transaction/s, and force disconnect until quiesce completely stops the iigcc\n\t5. <x amount> of calm/quiet time will be used for HPE Alletra's asynchronous replication\n\t6. After item# 5, restart iigcc by issuing an ingstart -iigcc\n\t7. Check if all users can already connect to the database server