CMD> ubguard.sh status guard -i <ubguard_instance_alias>
Failover:
Prerequisites:
Standby database must be in MOUNT state.
Usage:
CMD> ubguard.sh failover to <ubguard_instance_alias> [-f]
Default Failover:
It is a failover without "-f" option. It gets all missing archivelogs from primary server, applies archivelogs to standby database, activates standby database as primary database. It causes less data loss, but longer failover time.
The alternative manual method by RMAN on standby:
CMD> ubguard.sh stop guard -i <ubguard_instance_alias>
--> Copy all missing archivelogs from primary server to standby server
CMD> SET ORACLE_SID=<SID>
CMD> rman target /
RMAN> SHUTDOWN IMMEDIATE;
RMAN> STARTUP MOUNT;
RMAN> RECOVER DATABASE;
RMAN> SQL 'ALTER DATABASE ACTIVATE STANDBY DATABASE';
RMAN> ALTER DATABASE OPEN;
RMAN> EXIT;
If the manual method is used, ubGuard setup must be run again to update ubGuard's catalog.
Forced Failover:
It is a failover with "-f" option. It doesn't get archivelogs from primary server and it doesn't apply archivelogs to standby database. It activates standby database as primary database. It causes more data loss, but less failover time.
ubTools Support - 26/Dec/17 01:55 PM - editedCOMMANDS:
ubGuard executable is <UBGUARD_HOME>/bin/ubguard.sh (ubguard.bat for Windows).
Prerequisite for all commands:
Regarding Oracle listeners must be running.
Setup:
Prerequisites:
<UBGUARD_HOME>conf/setup.properties must be filled.
CMD> ubguard.sh status guard -i <ubguard_instance_alias>
Failover:
Prerequisites:
Standby database must be in MOUNT state.
Usage:
CMD> ubguard.sh failover to <ubguard_instance_alias> [-f]
Default Failover:
It is a failover without "-f" option. It gets all missing archivelogs from primary server, applies archivelogs to standby database, activates standby database as primary database. It causes less data loss, but longer failover time.
The alternative manual method by RMAN on standby:
CMD> ubguard.sh stop guard -i <ubguard_instance_alias>
--> Copy all missing archivelogs from primary server to standby server
CMD> SET ORACLE_SID=<SID>
CMD> rman target /
RMAN> SHUTDOWN IMMEDIATE;
RMAN> STARTUP MOUNT;
RMAN> RECOVER DATABASE;
RMAN> SQL 'ALTER DATABASE ACTIVATE STANDBY DATABASE';
RMAN> ALTER DATABASE OPEN;
RMAN> EXIT;
If the manual method is used, ubGuard setup must be run again to update ubGuard's catalog.
Forced Failover:
It is a failover with "-f" option. It doesn't get archivelogs from primary server and it doesn't apply archivelogs to standby database. It activates standby database as primary database. It causes more data loss, but less failover time.
The alternative manual method by RMAN on standby:
ubGuard executable is <UBGUARD_HOME>/bin/ubguard.sh (ubguard.bat for Windows).
Prerequisite for all commands:
Setup:
Prerequisites:
Usage:
Start:
Prerequisites:
Usage:
Stop:
Usage:
Status:
Usage:
Failover:
Prerequisites:
Usage:
Default Failover:
It is a failover without "-f" option. It gets all missing archivelogs from primary server, applies archivelogs to standby database, activates standby database as primary database. It causes less data loss, but longer failover time.
The alternative manual method by RMAN on standby:
If the manual method is used, ubGuard setup must be run again to update ubGuard's catalog.
Forced Failover:
It is a failover with "-f" option. It doesn't get archivelogs from primary server and it doesn't apply archivelogs to standby database. It activates standby database as primary database. It causes more data loss, but less failover time.
The alternative manual method by RMAN on standby:
If the manual method is used, ubGuard setup must be run again to update ubGuard's catalog.