ORA-16902
The specified standby database is not a valid fast-start failover target.
Cause
The attempted operation was not allowed because the specified database was not a valid fast-start failover target because of one of the following reasons:
- The specified database was not a physical standby database or logical standby database.
- The effective redo transport mode for the standby database was not set to SYNC or FASTSYNC if the protection mode was set to maximum availability mode.
- The effective redo transport mode for the standby database was not set to SYNC if the protection mode was set to maximum protection mode.
- The effective redo transport mode for the standby database was not set to ASYNC if the protection mode was set to maximum performance mode.
- The standby database was not configured to receive redo data directly from the primary database when the protection mode was set to maximum performance mode.
- The primary database had more than one rule in its RedoRoutes property to the standby database.
- The specified standby database was a logical standby database when the protection mode was set to maximum protection mode.
- The standby database was disabled.
- Redo transport-related properties of the standby database were inconsistent with the database setting.
- The specified standby database's FastStartFailoverTarget property did not specify the primary database when the standby is a logical standby database.
Action
Check that the specified standby database meets the requirements listed in the Cause section of this error message.
ORA-16902
The specified standby database is not a valid fast-start failover target.
Cause
The attempted operation was not allowed because the specified database is not a valid fast-start failover target because of one of the following reasons:
- The specified database was not a physical standby database or logical standby database.
- The effective redo transport mode for the standby database was not set to SYNC or FASTSYNC if the protection mode was set to maximum availability mode.
- The effective redo transport mode for the standby database was not set to SYNC if the protection mode was set to maximum protection mode.
- The effective redo transport mode for the standby database was not set to ASYNC if the protection mode was set to maximum performance mode.
- The standby database was not configured to receive redo data directly from the primary database when the protection mode was set to maximum performance mode.
- The primary database had one more than one rule in its RedoRoutes property to the standby database.
- The specified standby database was a logical standby database when the protection mode was set to maximum protection mode.
- The standby database was disabled.
- Redo transport-related properties of the standby database were inconsistent with the database settting.
- The specified standby database's FastStartFailoverTarget property did not specify the primary database when the standby is a logical standby database.
Action
Check that the specified standby database meets the requirements listed in the Cause section of this error message.
ORA-16902
The specified standby database is not a valid fast-start failover target.
Cause
The attempted operation was not allowed because the specified database is not a valid fast-start failover target because of one of the following reasons:
- The specified database was not a physical standby database or logical standby database.
- The effective redo transport mode for the standby database was not set to SYNC or FASTSYNC if the protection mode was set to maximum availability mode.
- The effective redo transport mode for the standby database was not set to SYNC if the protection mode was set to maximum protection mode.
- The effective redo transport mode for the standby database was not set to ASYNC if the protection mode was set to maximum performance mode.
- The standby database was not configured to receive redo data directly from the primary database when the protection mode was set to maximum performance mode.
- The primary database had one more than one rule in its RedoRoutes property to the standby database.
- The specified standby database was a logical standby database when the protection mode was set to maximum protection mode.
- The standby database was disabled.
- Redo transport-related properties of the standby database were inconsistent with the database settting.
- The specified standby database's FastStartFailoverTarget property did not specify the primary database when the standby is a logical standby database.
Action
Check that the specified standby database meets the requirements listed in the Cause section of this error message.