Currently glast-oracle01 hosts the GLASTP database. We have plans which are nearing fruition of putting a logical standby database for GLASTP on glast-oracle02. Yasser Abdelrahim is a consultant helping us with such things as my workload has prevented me from moving forward with the project.
A logical standby database is one which is synched with the production database. If the production database goes down, the standby will take over. The logical standby database is kept synchonized to the production database by exectuting the same SQL statements as the production box. Besides the failover capability, we want to exploit this feature so that patching and some upgrades do not result in outages.
The standby database will be read only while it is in standby mode. Obviously if failover occurs, or during patching when it temporarily takes over for the production server it will be read write. It is not a development instance. It could be a reporting instance.
We could place a development database on glast-oracle02 as well, but that database may have to be shut down if that glast-oracle02 needs to takeover for glast-oracle01. If those conditions are satisfactory to you, we'll put a dedvelopment instance on glast-oracle02. If not you could use slacdev as your development instance.