DGM-05103 to DGM-17540

28 DGM-05103 to DGM-17540

DGM-05103: one or more data files were not found: Cause: One or more data files for the specified standby pluggable database was not found.; Action: Ensure that the files associated with the standby pluggable database exist in the right location and then start Redo Apply services using the EDIT PLUGGABLE DATABASE SET STATE=APPLY-ON command.
DGM-05104: specified state is not valid: Cause: An invalid state was specified for the command.; Action: Specify a valid state and reissue the command. Valid states are APPLY-ON or APPLY-OFF.
DGM-16900: Unable to initialize client: Cause: The client could not be initialized.; Action: This is an internal error. Contact Oracle Support Services.
DGM-16901: Unable to initialize environment: Cause: The database environment could not be allocated and initialized.; Action: This is an internal error. Contact Oracle Support Services.
DGM-16902: Unable to allocate handle: Cause: The database handle could not be allocated.; Action: This is an internal error. Contact Oracle Support Services.
DGM-16903: Unable to connect to database using string: Cause: The Data Guard command-line interface (DGMGRL) was unable to connect to the database using the specified connect identifier.; Action: Check the connect identifier and ensure the instance or host is reachable.
DGM-16904: Unable to set attribute: Cause: The server attributes could not be set.; Action: Check additional error messages.
DGM-16905: Failed.: Cause: The command failed to execute.; Action: Check additional error messages.
DGM-16906: Unable to accept commands: no memory: Cause: No memory was available for the attempted operation.; Action: Check your system and retry the command.
DGM-16909: Fatal error - quitting...: Cause: A fatal error was encountered.; Action: See additional error messages and/or contact Oracle Support Services.
DGM-16910: Unable to issue command to server: Cause: Command could not be issued to the server.; Action: See additional error messages and/or contact Oracle Support Services.
DGM-16912: Unrecognized command "string", try "help": Cause: An unrecognized command was issued.; Action: Try again using a valid command.
DGM-16916: Missing site name, try "help": Cause: The site name is missing from the command.; Action: Try the command again using correct syntax.
DGM-16934: \tstart up instance "string" of database "string": Cause: The operation completed successfully and requires a restart of the specified instance. DGMGRL was unable to restart the instance.; Action: Start the specified instance manually.
DGM-16943: \tconnect to instance "string" of database "string": Cause: The operation required DGMGRL to connect to a specific instance to complete, but DGMGRL could not automatically connect to the given instance.; Action: Connect to the specified instance and issue the command again.
DGM-16944: Failover succeeded, new primary is "string".: Cause: The failover command completed successfully."; Action: No action is required.
DGM-16945: Syntax error before or at "string": Cause: The command could not be processed because of a syntax error in the named token.; Action: Try the command again using valid syntax.
DGM-16948: Unable to switchover, primary database is still "string": Cause: The switchover operation could not be executed due to the errors reported with this error message. The primary role has not been changed.; Action: Correct the errors and try the SWITCHOVER command again.
DGM-16949: Object "string" was not found: Cause: The named object was not found.; Action: Try the command again using a valid database name.
DGM-16951: Unable to failover: Cause: The failover operation could not be executed due to the errors reported with this error message.; Action: Correct the errors and try the FAILOVER command again.
DGM-16952: Configuration details cannot be determined by DGMGRL: Cause: The broker configuration could not be found.; Action: 1) The Data Guard broker process (DMON) could not be contacted. Verify that the DMON process is running. 2) No broker configuration currently exists. You must create one. 3) You are connected to a standby database in the broker configuration that has either been disabled or deleted. While the standby is in this state, the details of the broker configuration are not available on the standby database. Connect to the primary database and reissue the command. 4) You are connected to a database in the broker configuration that must be reinstated or reinstantiated. While in this state, details of the broker configuration are not available. Either reinstate or reinstantiate the database and reissue the command, or connect to the primary database and reissue the command.
DGM-16953: XML document is too long: Cause: The length of the XML document exceeded the internal limit.; Action: This is an internal error. Contact Oracle Support Services.
DGM-16959: No response from broker server process: Cause: No response was received from the broker server process (DMON).; Action: The Data Guard broker process (DMON) is not available. Verify that the DMON process is running and retry the command.
DGM-16960: Status not available: Cause: The status could not be retrieved.; Action: The Data Guard broker process (DMON) is not available. Verify that the DMON process is running and retry the command.
DGM-16979: Unable to log in to the primary or standby database: Cause: The username or password used by the observer to log in to the primary database and fast-start failover target standby database did not have valid SYSDBA or SYSDG credentials.; Action: Ensure that the primary database and fast-start failover target database are using a remote login password file. Ensure that the SYSDBA or SYSDG password is the same at both databases and that the SYSDBA or SYSDG password is used in the CONNECT command. Start the observer again.
DGM-16991: Two or more resources have the name "string": Cause: The named resource exists on more than one site.; Action: Use the ON SITE clause and reissue the command.
DGM-16999: Instance "string" was not found: Cause: The named instance could not be found.; Action: Try the command again using a valid instance name.
DGM-17000: Two or more instances have the name "string": Cause: The named instance exists on more than one database.; Action: Use the ON DATABASE clause and reissue the command.
DGM-17007: Unsupported platform, observer cannot start: Cause: The Observer was started on an operating system that does not support multi-threading.; Action: Start the Observer on an operating system that supports multi-threading.
DGM-17009: New primary database "string" is opening...: Cause: The Data Guard broker is opening the specified new primary database. The new primary database is ready to accept transactions once it is open.; Action: None
DGM-17016: failed to retrieve status for database "string": Cause: DGMGRL could not retrieve the StatusReport property from the given database and thus could not report the database status.; Action: See accompanying messages for details.
DGM-17017: unable to determine configuration status: Cause: The Data Guard broker could not execute a health check at the moment, so the configuration status could not be determined.; Action: See accompanying messages for details.
DGM-17023: far sync instance "string" was not found: Cause: A far sync instance with the given name was not found in the configuration.; Action: Try the command again using a valid far sync instance name. If the name refers to a database, use the corresponding database command syntax instead.
DGM-17025: member "string" was not found: Cause: A member with the specified name was not found in the configuration.; Action: Try the command again using a valid member name. If the name refers to a far sync instance, use the corresponding far sync instance command syntax instead, or use the member keyword instead.
DGM-17032: Wildcard string not supported for this command: Cause: The wildcard string was specified instead of an object name.; Action: Supply an object name instead of the wildcard string and retry the command.
DGM-17048: unable to open and lock the target file "string": Cause: The target file could not be opened or could not be locked for exclusive access.; Action: Ensure that the observer has the correct operating system privileges to write the file and that there is no other Observer using the same file. Try the command again.
DGM-17049: unable to get the length of the target file "string": Cause: An attempt to get the length of the target file failed.; Action: This is an internal error. Contact Oracle Support Services.
DGM-17050: unable to allocate enough memory for file buffer: Cause: An attempt to allocate enough memory for the file buffer failed.; Action: This is an internal error. Contact Oracle Support Services.
DGM-17051: unable to read the target file "string": Cause: An attempt to read the target file failed.; Action: This is an internal error. Contact Oracle Support Services.
DGM-17067: unable to retrieve the local host name: Cause: An attempt to retrieve the local host name failed.; Action: This is an internal error. Contact Oracle Support Services.
DGM-17088: observer external ID "string" is invalid: Cause: An invalid observer external ID was specified. A valid observer external ID should be 1, 2 or 3.; Action: Ensure the specified observer external ID is valid.
DGM-17090: unable to connect to database: no memory: Cause: Not enough memory was available for the attempted operation.; Action: Check your system and retry the command.
DGM-17105: Invalid value specified for the TRACE_LEVEL option.: Cause: An invalid value was specified for the TRACE_LEVEL option.; Action: Valid values for the TRACE_LEVEL option are USER or SUPPORT. Specify one of these values and retry the command.
DGM-17147: command not supported by the Oracle version running on database string: Cause: The DGMGRL CLI command could not be completed because the CLI was connected to a database that was running an older version of Oracle.; Action: Use another command or a version of the DGMGRL CLI that is the same as the version of Oracle the database is running.
DGM-17148: Invalid value specified for the WAIT option.: Cause: An invalid value was specified for the WAIT option.; Action: Valid values for the WAIT option are positive integers. Specify a positive interger value and rerun the command.
DGM-17152: invalid value "string" specified in file operation option: Cause: An invalid valued was specified for the file operation option.; Action: Valid values for the file operation option are CREATE, REPLACE and APPEND.
DGM-17175: Failed to set session container to string.: Cause: The DGMGRL CLI was unable to set the session container to the pluggable database identified in the error message text.; Action: Check that the pluggable database exists or look for errors that may have been recorded in the database alert log and correct them before retrying the command.
DGM-17176: Unable to query PDB_PLUG_IN_VIOLATIONS.: Cause: The DGMGRL CLI was unable to query the PDB_PLUG_IN_VIOLATIONS table.; Action: Check that the container is set to CDB$ROOT and that the container is open. Also check for any errors in the database alert log and correct them before retrying the command.
DGM-17290: Role change detected. This database may no longer be the primary database.: Cause: A role change was performed to a standby database in this configuration.; Action: Check if a role change has been performed to a standby database in this configuration. If a role change has been performed, this database needs to be reinstated or re-created from a copy of the new primary database. If a role change has not been performed and you want to open this database, enable the configuration and then open the database.
DGM-17295: Parameter "string" not updated.: Cause: The specified parameter corresponds to a property managed by Data Guard broker on members prior to Oracle Database release 19c.; Action: Use the EDIT command with the SET PROPERTY clause.
DGM-17297: This command requires a bequeath connection to the database.: Cause: The command failed because a bequeath connection was not created to the database. A bequeath connection is required because the database instance must be restarted.; Action: Connect to the database using a bequeath connection and retry the command.
DGM-17298: The DIRECTORY-LOCATION parameter was not specified.: Cause: The command failed because a DIRECTORY-LOCATION parameter was not specified and the database did not have a local archival destination established.; Action: Specify a value for the DIRECTORY-LOCATION parameter and retry the command.
DGM-17299: No local archival destinations are available.: Cause: The command failed because there were no local archival destinations available. Local archival requires a LOG_ARCHIVE_DEST_n initialization parameter numbered 10 or lower.; Action: If possible, clear a LOG_ARCHIVE_DEST_n initialization parameter numbered 10 or lower and retry the command.
DGM-17300: The SIZE parameter was not specified.: Cause: The command failed because the SIZE parameter was not specified when the DB_RECOVERY_FILE_DEST_SIZE initialization parameter was not set.; Action: Specify a value for the SIZE parameter and retry the command.
DGM-17301: Server parameter (SPFILE) not in use for RAC database.: Cause: The command failed because the database was a RAC database and and a server parameter file was not configured.; Action: Create a server parameter file for the database, restart all instances of the database to use the server parameter file, and then retry the command.
DGM-17328: The DIRECTORY_LOCATION parameter must be specified to enable Flashback Database.: Cause: The command failed because Flashback Database cannot be enabled if the DB_RECOVERY_FILE_DEST initialization parameter is not set.; Action: Specify DIRECTORY_LOCATION parameter and retry the command.
DGM-17379: Configuration "string" was not found.: Cause: A configuration with the specified name was not found.; Action: Try the command again using a valid configuration name. If the name refers to a configuration, use the corresponding configuration command syntax instead.
DGM-17380: Option is missing, try the command again with at least one option.: Cause: An option was not specified with the VALIDATE DATABASE STRICT command. There must be at least one option specified.; Action: Try the command again using the correct syntax.
DGM-17381: string string is disabled.: Cause: The command could not be completed because the specified member was disabled.; Action: If the operation references a pluggable database, and the container database that it is in is enabled, connect to that database and try the command again. Otherwise, enable the configuration and retry the command.
DGM-17408: Verification of successful migration requires apply services to be stopped.: Cause: Verification of pluggable database migration to another container database from a physical standby database requires redo apply services to be stopped.; Action: Stopping redo apply creates an apply lag situation on the standby database. If a verification of a pluggable database migration is required, re-issue the command with the IMMEDIATE option.
DGM-17416: SECRET and KEYSTORE IDENTIFIED BY clauses are required.: Cause: The pluggable database to migrate has TDE master keys. The keystore password of the destination's multitenant container database is required. A secret phrase and the keystore password of the destination's multitnent container database must be given.; Action: Use clause SECRET and KEYSTORE IDENTIFIED BY to specify a secret and the keystore password of the destination's multitenant container database.
DGM-17445: Source pluggable database 'string' must be open in read/write mode for this operation.: Cause: The source pluggable database was not open in read/write mode.; Action: Open the source pluggable database in read/write mode and retry the operation.
DGM-17450: not protected: Cause: The source pluggable database was not protected with an active target standby pluggable database.; Action: Check the status and connectivity with the target container database.
DGM-17465: Cannot remove configuration string.: Cause: Configuration could not be removed since the primary database contained either an active source or a target Data Guard pluggable database.; Action: Retry the operation when there are no active source or target Data Guard pluggable databases.
DGM-17474: Failed to stop redo transport services at database string.: Cause: The operation completed successfully but the attempt to stop redo transport services failed.; Action: Stop redo transport services by setting the source database state to TRANSPORT-OFF.
DGM-17479: invalid initialization parameter name "string" specified: Cause: An invalid initialization parameter name was specified for the operation.; Action: Reissue the command with a valid parameter name.
DGM-17488: Warning: DGConnectIdentifer 'string' does not have the same translation on all members.: Cause: The specified connect identifier did not translate to the same connect descriptor on all members.; Action: Ensure that each member has the same translation for the specified connect descriptor.
DGM-17507: The source and target container databases cannot be the same.: Cause: The specified source and target multitenant container database (CDB) were the same name or same DBID.; Action: Specify distinct multitenant container databases.
DGM-17515: The ASM alias of data file string is not in the expected location.: Cause: In order to reuse the standby database data files during the migration of a pluggable database, the data file must not have an ASM alias, or its alias located in <DB_UNIQUE_NAME>/GUID of pluggable database/DATAFILE.; Action: Remove the ASM alias of the specified data file and issue the command again.
DGM-17516: A multitenant container standby database in the Data Guard Broker configuration must be specified.: Cause: The command did not specify the multitenant container standby database in the Data Guard Broker configuration as being the migration source or destination.; Action: Use clause SOURCE STANDBY or DESTINATION STANDBY to specify a standby database in the broker configuration as being the migration source or destination, and issue the command again.
DGM-17537: KEYFILE and SOURCE IDENTIFIED BY clauses are required.: Cause: To migrate a pluggable database with TDE master keys from a standby database, the keys needs to be exported to a file and imported from the file at the destination's database. A key file path and the keystore password of the pluggable database to migrate must be given.; Action: Use clause KEYFILE and SOURCE KEYSTORE IDENTIFIED BY to specify a key file and the keystore password of the pluggable database to migrate.
DGM-17540: Environment does not support Data Guard per Pluggable Database.: Cause: Data Guard per Pluggable Database command was attempted when the environment did not support it.; Action: Data Guard per Pluggable Database operations require two primary container databases in independent, enabled configurations.