RDBPROD Clarification on closing a database that is being replicated
edited Jan 10, 2014 5:34AM in Rdb on OpenVMS, IBM zSeries and Oracle on OpenVMS (MOSC) 4 commentsAnswered
4-node OpenVMS cluster, all nodes are Integrity servers, all running OpenVMS 8.3 and Rdb 7.2-340
2 nodes are considered as the "production nodes" and each has "production" databases opened. All production databases are being replicated to a remote standby system using the "standard" Rdb hot standby options (that is not using the replication option or product).
The issue we have is that you can't close a database even if the log catch up server process is not actually running on the node that you wish to close the database on. We have no problem with the fact that you have to stop replication on the node that is actually running the LCS before closing the database, but wonder why you can't close the database on another node. If this is by design then it seems a little restrictive compared to the way most other things work with Rdb, however if this is not the way things
2 nodes are considered as the "production nodes" and each has "production" databases opened. All production databases are being replicated to a remote standby system using the "standard" Rdb hot standby options (that is not using the replication option or product).
The issue we have is that you can't close a database even if the log catch up server process is not actually running on the node that you wish to close the database on. We have no problem with the fact that you have to stop replication on the node that is actually running the LCS before closing the database, but wonder why you can't close the database on another node. If this is by design then it seems a little restrictive compared to the way most other things work with Rdb, however if this is not the way things
0