Data Guard - need to add in a new server, have some questions
489554Jan 4 2008 — edited Jan 4 2008Hi all,
I have a current DataGuard environment, with one primary database and one standby database, both running on Windows 2000 servers, it has been all good for the last 5 years. Database version is 9.2.0.6.0.
The hardware is about to expire, so we need to roll out a new server for the primary database server. We are hoping to do this with a Windows 2003 server, and the method I was hoping to use is the following:
1. Take a backup of the production database, and get it up and running on the new server, put it into the DataGuard environment as a STANDBY database. At this point, we still have our old primary db, and it is using DataGuard to replicate to 2 standby dbs, one of which is on the new server.
2. When we are ready to test the application, then we want to BREAK the replication from the primary to the new server, and have it run as a standalone db server, so we can test the app against it.
3. When we are ready to go into production, then we re-instantiate DataGuard for this server, then perform a SWITCHOVER, so that the new server becomes the primary, and the old primary becomes a standby.
Some questions:
- Does this sound like a feasible way of implementing the new hardware, or am I over-complicating it??
- Will this even work, to replicate a db from a Win 2000 server to a Win 2003 server, and vice versa?
- In our current DataGuard scenario, the primary database name is PHARPROD and the standby is PHARSTBY. Do I have to name the new database on the new server something different, or can it be called PHARPROD?
Any help/advice is greatly appreciated from the DataGuard gurus out there!!