- The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set.
- An nlsparams operand is not in the database character set.
- String data with character set other than the database character set is passed to a built-in function not expecting it.
- The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.
- A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted.
- A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column.
- An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.
- it is a typed table
- it contains ADT columns
- it contains nested-table columns
- it contains REF columns
- it contains array columns
- it is an index-organized table
- it contains LOB columns
- it is a nested table
- it is created with row dependency and the partitioned table is not
- it is created without row dependency and the partitioned table is
2. ALTER DATABASE START LOGICAL STANDBY APPLY;
3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record.
4. Provide the log file to Oracle Support Services.
- The databases changing roles are offline.
- The primary database is not shipping log files.
- The standby database that will become the primary database is not applying log files. The broker returns this error for database state change operations if the database state specified is invalid.
- The databases changing roles are online.
- The primary database is shipping log files.
- The standby database is applying log files. If this error is returned when attempting a database state change operation, make sure you specify a valid state.
- A failover operation has been submitted or is currently is in progress.
- A switchover operation has been submitted or is currently is in progress.
- An instance restart is pending for one or more databases.
- While transmitting the configuration file between databases, DRCX detected an inconsistency in the block count of the file.
- The DRCX process got an error while writing the configuration file.
- cannot locate itself in the broker configuration file.
- fails to distinguish itself from two or more databases in the configuration file.
- determines it was not part of a change of primary database due to failover.
- confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.
- confirm that you have not created two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not indicate the same physical database.
- if you had performed a failover and have re-created your old primary database (or a standby database that had to be re-created), make sure the 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.
- The broker rejects an attempt to change the configuration"s overall protection mode since it could not find any online, enabled standby databases that support the proposed protection mode.
- The broker rejects an attempt to enable the configuration if it determines there are no online, enabled standby databases that support the overall protection mode.
- The broker rejects an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that can support the configuration"s overall protection mode.
- The broker rejects an attempt to set the configuration offline if doing so would violate the configuration"s overall protection mode.
- The broker rejects an attempt to set a standby database offline if doing so would violate the configuration"s overall protection mode.
- The broker rejects a switchover attempt if doing so would violate the configuration"s overall protection mode.
- The broker returns this error during a health check.
- For enable failures, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.
- For delete and disable failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode.
- For state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE you may have to downgrade the protection mode setting to maximum performance beforehand.
- For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary database and a single standby database, ensure that the LogXptMode configuration property established for the primary database supports the overall protection mode. After the switchover, the old primary database will become the standby database and its LogXptMode configuration property setting must support the overall protection mode.
- For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.
- The Data Guard configuration must be in MaxAvailability protection mode.
- The LogXptMode property for both the primary database and the Fast-Start Failover target standby database must be SYNC.
- The primary database and the Fast-Start Failover target standby database must both have flashback enabled.
- No valid target standby database was specified in the primary database"s FastStartFailoverTarget property prior to the attempt to enable Fast-Start Failover, and more than one standby database exists in the Data Guard configuration.
- Set the Data Guard configuration to MaxAvailability protection mode.
- Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target standby database are SYNC.
- Ensure that both the primary database and the Fast-Start Failover target standby database have flashback enabled.
- Set the primary database"s FastStartFailoverTarget property to the db_unique_name value of the desired target standby database add the desired target standby database"s FastStartFailoverTarget property to the db_unique_name value of the primary database.
- The FastStartFailoverTarget property may not be modified.
- The LogXptMode property for either the primary database or the FSFO target standby database may not be modified.
- Neither the broker configuration or the FSFO target standby database may be disabled using the DGMGRL CLI"s DISABLE command.
- Neither the broker configuration or the FSFO target standby database may be removed using the DGMGRL CLI"s REMOVE command.
- The FAILOVER IMMEDIATE command is not allowed.
- the net-service-name specified in DGMGRL"s CREATE CONFIGURATION or ADD DATABASE command is not one that provides access to the database being added, or
- there are no instances running for the database being added.
- The node where the observer was running was not available.
- The network connection between the observer and this database was not available.
- Observer process was terminated unexpectedly.
1. Apply service was started without specifying the real time apply option or without the NODELAY option while DelayMins is zero.
2. Apply service was started with the real-time apply option or with the NODELAY option while DelayMins is greater than zero.