Reversing Graceful Switchover back to original state

To reverse the switchover so that the new standby database transitions back to the original primary database and the new primary database transitions back to the original standby database, the same process as before is initiated. For completion the steps are shown below. However, they are exactly the same as above (starting the Graceful Switchover).
Note that the standby server contains the new primary database and the primary server contains the new standby database. 
Transition overview:
[Primary server] standby database > primary database
[Standby server] primary database > standby database

1. On the standbyserver start the Graceful Switchover procedure.

2. On the primaryserver start the Graceful Switchover procedure.

3. Enter a unique key on the standbyserver.

The standby database must be up to date before starting the switchover process. Dbvisit Standby will check the archive log gap and will not initiate the switchover if the standby database is not up to date.

4. Enter the same unique key on the primaryserver. This ensures that both processes are linked to each other.

The switchover process has now started. For more information about the messages during the switchover, please see the Complete switchover processing section below.

5. At the end of the switchover the primary database has transitioned to its original standby database:

6. At the end of the switchover the standby database has transitioned to its original primary database:

7. Graceful Switchover has been completed and is back to its original state. The primary database is now back on the primary server, and the standby database is now back on the standby server.

8. To confirm that the original primary database is now once again the primary database, the following command maybe run:

9. To confirm that the original standby database is now once again the standby database, the following command maybe run:

10. To keep the primarydatabase in sync with the standby database, Dbvisit Standby may be run as per usual.

11. To keep the standbydatabase in sync with the new primary database. Dbvisit Standby may be run as per normal.

12. Enable the scheduling of Dbvisit Standby on both the primary and standby server to keep the standby database up to date as per normal.