Database Error Messages

This status was returned when attempting to enable a member that:

• Could not locate itself in the broker configuration file.
• Failed to distinguish itself from two or more members in the configuration file.
• Determined it missed a role change within the configuration.

To correct the problem, try one of these actions:

• Confirm that the host and SID names for the member exactly match the values in the HOST_NAME and INSTANCE_NAME columns of the V$INSTANCE view.
• Confirm that two or more members do not have the same connect identifier. That is, multiple members in the broker configuration should not reach the same member.
• If a failover has been performed and the old primary database has been re-created (or a standby database has been re-created), then ensure that the Oracle Data Guard broker configuration files have been removed for that database. Do not remove the configuration files that are in use by the new primary database.

This status was returned when attempting to enable a member that:

• Could not locate itself in the broker configuration file.
• Failed to distinguish itself from two or more members in the configuration file.
• Determined it missed a role change within the configuration.

To correct the problem, try one of these actions:

• Confirm that the host and SID names for the member exactly match the values in the HOST_NAME and INSTANCE_NAME columns of the V$INSTANCE view.
• Confirm that two or more members do not have the same connect identifier. That is, multiple members in the broker configuration should not reach the same member.
• If a failover has been performed and the old primary database has been re-created (or a standby database has been re-created), ensure that the Oracle Data Guard broker configuration files have been removed for that database. Do not remove the configuration files that are in use by the new primary database.

This status was returned when attempting to enable a member that:

• Could not locate itself in the broker configuration file.
• Failed to distinguish itself from two or more members in the configuration file.
• Determined it missed a role change within the configuration.

To correct the problem, try one of these actions:

• Confirm that the host and SID names for the member exactly match the values in the HOST_NAME and INSTANCE_NAME columns of the V$INSTANCE view.
• Confirm that two or more members do not have the same connect identifier. That is, multiple members in the broker configuration should not reach the same member.
• If a failover has been performed and the old primary database has been re-created (or a standby database has been re-created), ensure that the Oracle Data Guard broker configuration files have been removed for that database. Do not remove the configuration files that are in use by the new primary database.