ORA-16589: Data Guard broker detected network
transfer error
Cause:
The Data Guard broker detected an error while transferring data from one
database to another. This may happen when:
- the broker
detects an inconsistency in the block count of configuration file when the file
is transmitted between databases.
- the broker
encountered an error when writing the configuration file.
Action:
Contact Oracle Support Services.
ORA-16594: DMON background process is not running
Cause:
The Data Guard broker background process, DMON, was not running.
Action:
Check the Data Guard broker log and DMON process trace file to determine why
the DMON process is not running.
ORA-16595: process string failed to
terminate
Cause:
The specified process did not terminate at the request of the Data Guard
broker.
Action:
Contact Oracle Support Services.
ORA-16596: database not part of the Data Guard
broker configuration
Cause:
The specified database is not in the Data Guard broker configuration.
Action:
Retry the command with a database that is in the broker configuration.
ORA-16597: Data Guard broker detects two or more
primary databases
Cause:
The Data Guard broker detected two or more primary databases in the broker
configuration and could not continue.
Action:
Contact Oracle Support Services.
ORA-16598: Data Guard broker detected a mismatch in
configuration
Cause:
The Data Guard broker detected a significant mismatch while performing
configuration membership validation between two or more databases in the broker
configuration. This can occur when the primary database has stale broker
configuration files.
Action:
Contact Oracle Support Services.
ORA-16599: Data Guard broker detected a stale
configuration
Cause:
The Data Guard broker detected a stale configuration during initialization for
this database.
Action:
The broker will automatically resolve this situation once the primary database
completes its initialization.
ORA-16600: not connected to target standby database
for failover
Cause:
The failover command failed because the client was not connected to the target
standby database.
Action:
Explicitly connect to the standby database to be failed over to and retry the
failover command.
ORA-16602: database must be disabled to perform
this operation
Cause:
An attempt was made to edit a database property while the database was enabled.
Action:
Disable the database and retry the command.
ORA-16603: Data Guard broker detected a mismatch in
configuration ID
Cause:
There was a mismatch in configuration unique ID. This could occur if the
original configuration was re-created while this database was disconnected from
the network or the same database was added to two different Data Guard broker
configurations.
Action:
Make sure the database belongs to only one broker configuration. Shut down the
broker by setting the DG_BROKER_START initialization parameter to false. Then
remove the Data Guard broker configuration files. Finally restart the broker by
setting the DG_BROKER_START initialization parameter to true.
ORA-16606: unable to find property "string"
Cause:
The specified property did not exist.
Action:
Specify a valid property name and reissue the request.
ORA-16607: one or more databases have failed
Cause:
A failure was detected for one or more databases in the Data Guard broker configuration.
Action:
Locate the database(s) with a failure status and correct it.
ORA-16608: one or more databases have warnings
Cause:
A warning was detected for one or more databases in the Data Guard broker
configuration.
Action:
Locate the database(s) with a warning status and correct it.
ORA-16609: database is being disabled
Cause:
A command was attempted on a database that was being disabled. For example,
attempting to reinstate the old primary database, the database that was the
primary database prior to the most recent failover, before it was ready to be
reinstated.
Action:
Wait for the Data Guard broker to disable the database and then retry the
command.
ORA-16610: command "string" in
progress
Cause:
The specified broker command was already running and the command issued could
not be completed.
Action:
Wait for the specified command to finish and then retry the command.
ORA-16611: command aborted at user request
Cause:
The command was aborted at the user's request.
Action:
No action required.
ORA-16612: string value too long for attribute
"string"
Cause:
The string value for the named attribute was too long.
Action:
Specify a shorter string value.
ORA-16613: initialization in progress for database
Cause:
A request was made to modify the Data Guard broker configuration before the
Data Guard broker had completed initialization.
Action:
Wait until the Data Guard broker has completed initialization before attempting
to modify the broker configuration.
ORA-16614: Data Guard broker configuration is
disabled
Cause:
An attempt to enable a database failed because the Data Guard broker
configuration was disabled.
Action:
Enable the Data Guard broker configuration and issue the DGMGRL CLI SHOW
CONFIGURATION command to see if there are any databases that are still
disabled. If the database you tried to enable is still disabled, issue the
DGMGRL CLI SHOW DATABASE command to check the status of the database. If the
database status indicates that the database needs to be reinstated then issue
the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database.
If the database does not require reinstatement then issue the DGMGRL CLI ENABLE
DATABASE command to enable the database.
ORA-16617: unknown object identifier specified in
request
Cause:
Object identifier specified in the request was invalid or unknown.
Action:
Verify that a valid object identifier is specified and reissue reissue the
request.
ORA-16619: health check timed out
Cause:
The standby database could not be reached during a routine health check.
Action:
This typically indicates a network problem where the standby database is unable
to respond to the primary database within a predefined time frame. Check the
network connections between the primary and standby databases.
ORA-16620: one or more databases could not be
reached for a delete operation
Cause:
One or more standby databases could not be reached for either a DGMGRL CLI
REMOVE DATABASE or a REMOVE CONFIGURATION command.
Action:
This typically indicates a network problem where the standby database is unable
to respond to the primary database. In the event of this situation, examine the
primary database Data Guard broker log to determine which standby databases
could not be reached. For each standby database not reached, connect to that
database and shut down the broker by setting the initialization parameter,
DG_BROKER_START, to false. After the broker has been shut down for the standby
database, locate the Data Guard broker configuration files from the standby
database DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete
them. Then restart the broker by setting DG_BROKER_START to true.
ORA-16621: database name for ADD DATABASE must be
unique
Cause:
An attempt was made to add a database to the broker configuration that already
included a database with the specified name. The database names must be unique.
Action:
Verify that a unique name is specified for the new database to be added. Also,
the database name must match the DB_UNIQUE_NAME initialization parameter of the
database.
ORA-16622: two or more broker database objects
resolve to the same database
Cause:
Multiple database objects referred to the same database.
Action:
Examine the details of all databases in the broker configuration and verify
that there are not two or more databases referring to the same database. If two
or more database profiles in the broker configuration have the same value for
the DGConnectIdentifier database property, either:
- Remove and
re-add the erroneously defined database(s) to resolve the ambiguity.
- Ensure that
the DGConnectIdentifier database property for each database allows the broker
to properly connect to that database.
ORA-16623: database detected role change
Cause:
A successful switchover or failover operation had been completed and was
detected during database startup or broker health check. If this database was
unavailable during a switchover or failover operation, it may not be a viable
standby database for the new primary database and was disabled by the Data Guard
broker.
Action:
Connect to the new primary database and examine the broker configuration for
databases that were disabled and that may require reinstatement or re-creation.
ORA-16624: broker protocol version mismatch
detected
Cause:
A network protocol version number mismatch was detected. This could happen if
the databases in the broker configuration were not running the same version of
Oracle. The broker would disable standby databases that were not running the
same version of Oracle as the primary database if this situation was detected.
Action:
Examine the version of Oracle installed on all databases in the broker
configuration to ensure they are identical. Once all of the datbases in the
broker configuration are running the same version of Oracle, reenable the
standby databases that were disabled.
ORA-16625: cannot reach the database
Cause:
The command could not be executed because the database required to complete the
command was not reachable from the database where the command was issued. If the
command modifies the configuration, the command must be processed by the copy
of the broker running on an instance of the primary database.
Action:
Check the network connections between all of the databases in the
configuration. Alternatively, connect to a different database in the Data Guard
broker configuration and retry the command. If an attempt was made to determine
the status of a particular database in the configuration, connect to that
database and get the current value of the StatusReport property for that
database.
ORA-16626: failed to enable specified database
Cause:
This status was returned when attempting to enable a standby database that:
- Could not
locate itself in the broker configuration file.
- Failed to
distinguish itself from two or more databases in the configuration file.
- Determined it
missed a role change within the configuration.
Action:
To correct the problem, try one of these actions:
- 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
there are not two or more databases with the same connect identifier. That is,
multiple databases in the broker configuration should not reach the same
database.
- If a failover
had been performed and the old primary database has been re-created (or a
standby database has been 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.
ORA-16627: operation disallowed since no standby
databases would remain to support protection mode
Cause:
This status was returned because of one of the following:
- The broker
rejected an attempt to change the overall configuration protection mode since
it could not find any enabled standby databases that supported the proposed
protection mode.
- The broker
rejected an attempt to enable the configuration if it determined that there
were no enabled standby databases that supported the overall protection mode.
- The broker
rejected an attempt to disable or remove a database that, if disabled or
deleted, would result in no remaining standby databases that could support the
overall configuration protection mode.
- The broker
rejected an attempt to switchover if doing so would violate the overall
configuration protection mode.
- Performing
automatic health check if the broker determined that no standby datbases
supported the overall protection mode.
Action:
- If changing the overall protection mode, confirm that at least one standby
database satisfies the new protection mode.
- For enable
failures, confirm that at least one standby database has a LogXptMode
configurable 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 configurable property setting that supports the overall protection
mode.
- For switchover
failures that occur when the configuration is operating in maximum protection
or maximum availability mode, confirm that at least one other standby database
has its LogXptMode configurable property set to the value "SYNC". If
the configuration contains a primary database and a single standby database and
is operating in either maximum protection or maximum availability mode, ensure
that the LogXptMode configurable property of the primary database is set to the
value "SYNC". Since the old primary database will become the standby
database after switchover completes, its LogXptMode configurable property
setting must support the configuration protection mode.
- For health
check error, confirm that at least one standby database has a LogXptMode
configurable property setting that supports the current overall protection
mode.
ORA-16628: broker protection mode inconsistent with
the database setting
Cause:
The Data Guard broker protection mode saved in the broker configuration file
was inconsistent with the actual database setting.
Action:
Reset the protection mode through the Data Guard broker.
ORA-16629: database reports a different protection
level from the protection mode
Cause:
The actual or current database protection level was different from the
configured protection mode. This typically is caused by redo transport
problems.
Action:
Check the database alert logs and Data Guard broker logs for more details.
Also, check the redo transport status. Ensure that one standby database
supports the configured protection mode and that the network to that standby
database is working properly.
ORA-16630: database property has been deprecated
Cause:
The property that was specified in the command was deprecated.
Action:
Check the broker documentation to identify a replacement property or SQL
command for the deprecated property.
ORA-16631: operation requires shutdown of database
or instance "string"
Cause:
The Data Guard broker operation required a shutdown of the database or
instance.
Action:
If database or instance has not been shutdown by the DGMGRL CLI or Enterprise
Manager, shutdown the database or instance manually.
ORA-16632: instance being added to database profile
Cause:
The Data Guard broker determined that an instance successfully found its
database profile within the broker configuration file, but lacked an
instance-specific profile. The broker automatically created an
instance-specific profile and associated the instance with its database
profile.
Action:
No user action is required. The broker will automatically associate the
instance with its database profile and incorporate the instance into broker
activity.
ORA-16633: the only instance of the database cannot
be removed
Cause:
The instance to be removed was the only instance of the corresponding database
that was known to the broker.
Action:
Remove the corresponding database object from the broker configuration instead
of the individual instance object of the database.
ORA-16635: network connection failed during
transmission
Cause:
The Data Guard broker detected a connection failure to a remote database in the
broker configuration. This failure happened in the middle of a transmission
session. A transmission session usually requires more than one send operation
for sending a large amount of data (for example, the broker configuration file)
to the remote database.
Action:
In most cases, no user action is required. The Data Guard broker always tries
to resend the data. This error will be reported if the problem persists. This
error indicates there are some problems with the network connection between
broker managed databases. Further network troubleshooting should be done to
identify and correct the actual problem.
ORA-16636: fast-start failover target standby in
error state, cannot stop observer
Cause:
A STOP OBSERVER operation could not be completed when fast-start failover was enabled
because the target standby database could not participate in the STOP OBSERVER
operation.
Action:
Additional information about this failure is recorded in the Data Guard broker
log file for the primary database. This information helps to identify the
reason why the target standby database was unable to participate in the STOP
OBSERVER operation. If the problem can be corrected by the information in the
broker log file, retry the operation. Alternatively, fast-start failover may be
forcibly disabled by connecting to the primary database and issuing the DISABLE
FAST_START FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover
has been forcibly disabled, the observer can be stopped regardless of the
current state of the target standby database.
ORA-16637: an instance failed to access the Data
Guard broker configuration
Cause:
The broker could not access the broker configuration files on one or more
database instances. This can happen when the DG_BROKER_CONFIG_FILE[1|2]
initialization parameter values are not to the same set of file locations for a
RAC database.
Action:
Shut off the broker by setting the DG_BROKER_START initialization parameter to
false. Then set the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2
initialization parameters to file locations that are shared by all instances of
a RAC database. Finally, restart the broker by setting the DG_BROKER_START
initialization parameter to true.
ORA-16638: could not get the instance status
Cause:
The broker could not determine whether the specified instance was running.
Action:
See the next error message in the error stack for more detailed information. If
the situation described in the next error in the stack can be corrected, do so;
otherwise, contact Oracle Support Services.
ORA-16639: specified instance inactive or currently
unavailable
Cause:
An attempt was made to perform an operation on an instance that was not running
or was unavailable.
Action:
Ensure that the instance specified in the operation is running and then retry
the operation.
ORA-16640: CRS warns that multiple instances may
still be running
Cause:
The broker failed to have CRS stop instance monitoring and shut down all but
one instance. CRS instance monitoring did stop, but CRS may not have been able
to shut down all but one instance. The broker operation was canceled.
Action:
Suspend CRS management of this database using SRVCTL STOP DATABASE -D
<name> -O NONE. Reissue the broker request.
ORA-16642: DB_UNIQUE_NAME mismatch
Cause:
The expected DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value
for the database that the broker contacted using the connect identifier that
was associated with that database.
Action:
Verify that the connect identifier correctly connects to the intended database.
Verify that the name of the database the broker expects to find by that connect
identifier matches the actual DB_UNIQUE_NAME for that database.
ORA-16643: unable to determine location of broker
configuration files
Cause:
The Data Guard broker was unable to determine the location of its configuration
files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Action:
Retry the operation and, if the error persists, contact Oracle Support
Services.
ORA-16644: apply instance not available
Cause:
The broker operation could not finish, because it requires a running apply
instance for the standby database, and either there was no such instance
designated for the standby database or the designated apply instance was not
currently available.
Action:
Start the designated apply instance or wait until the broker specifies an
instance to be the apply instance and reissue the command.
ORA-16645: unexpected new instance interrupted
current operation
Cause:
A new instance unexpectedly joined the Data Guard configuration at a point when
the current operation may proceed only if the set of known instances is not
changing dynamically.
Action:
Reissue the operation after the new instance has joined the Data Guard
configuration.
ORA-16646: fast-start failover is disabled
Cause:
The operation was not allowed because fast-start failover was disabled.
Action:
Enable fast-start failover and retry the operation.
ORA-16647: could not start more than one observer
Cause:
The observer could not start because there was another observer already
observing the Data Guard configuration for which fast-start failover may have
been enabled.
Action:
Stop the running observer. Retry the operation.
ORA-16648: a new observer registered with
identifier string
Cause:
The observer was registered with the Data Guard broker and will begin observing
the Data Guard configuration for conditions that warrant doing a fast-start
failover.
Action:
None
ORA-16649: possible failover to another database
prevents this database being opened
Cause:
An attempt to open the database was made either when a failover occurred or
while fast-start failover was enabled and the fast-start failover status could
not be evaluated.
Action:
Check if a failover did occur. If fast-start failover is enabled, and a
failover did not occur, ensure that connectivity exists between this database
and either the observer or the target standby database. Then, try opening the
database again.
ORA-16650: command incompatible when fast-start
failover is enabled
Cause:
An attempt was made to issue a command that is not permitted when fast-start
failover is enabled. The command was not issued using the Data Guard broker.
Action:
The command must be issued using the Data Guard broker.
ORA-16651: requirements not met for enabling
fast-start failover
Cause:
The attempt to enable fast-start failover could not be completed because one or
more requirements were not met:
- The Data Guard
configuration must be in either MaxAvailability or MaxPerformance protection
mode.
- The LogXptMode
property for both the primary database and the fast-start failover target
standby database must be set to SYNC if the configuration protection mode is
set to MaxAvailability mode.
- The LogXptMode
property for both the primary database and the fast-start failover target
standby database must be set to ASYNC if the configuration protection mode is
set to MaxPerformance mode.
- 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
FastStartFailoverTarget property prior to the attempt to enable fast-start
failover, and more than one standby database exists in the Data Guard
configuration.
Action:
Retry the command after correcting the issue:
- Set the Data
Guard configuration to either MaxAvailability or MaxPerformance protection
mode.
- Ensure that
the LogXptMode property for both the primary database and the fast-start
failover target standby database are set to SYNC if the configuration protection
mode is set to MaxAvailability.
- Ensure that
the LogXptMode property for both the primary database and the fast-start
failover target standby database are set to ASYNC if the configuration
protection mode is set to MaxPerformance.
- Ensure that
both the primary database and the fast-start failover target standby database
have flashback enabled.
- Set the
primary database FastStartFailoverTarget property to the DB_UNIQUE_NAME value
of the desired target standby database and the desired target standby database
FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary
database.
ORA-16652: fast-start failover target standby
database is disabled
Cause:
The command to enable or disable fast-start failover could not be completed
because Data Guard broker management of the fast-start failover target standby
database is currently disabled.
Action:
Enable broker management of the target standby database and reissue the
command. If an attempt was made to disable fast-start failover when this error
was reported, disable fast-start failover forcibly using the DGMGRL DISABLE
FAST_START FAILOVER FORCE command. Consult the documentation for more
information.
ORA-16653: failed to reinstate database
Cause:
The Data Guard broker failed to reinstate the specified database because the
REINSTATE command failed or because the database is already enabled.
Action:
Additional information about this failure is recorded in the primary database
or the specified database Data Guard broker log files. This information is
helpful in determining how to proceed.
ORA-16654: fast-start failover is enabled
Cause:
The attempted command was not allowed while fast-start failover was enabled:
- The
FastStartFailoverTarget property may not be modified.
- The LogXptMode
property for either the primary database or the fast-start failover target
standby database may not be modified.
- The
configuration's protection mode may not be modified.
- Neither the
broker configuration nor the fast-start failover target standby database may be
disabled using the DGMGRL CLI DISABLE command.
- Neither the
broker configuration nor the fast-start failover target standby database may be
removed using the DGMGRL CLI REMOVE command.
- The FAILOVER
IMMEDIATE command is not allowed.
- The DG_BROKER_START
initialization parameter may not be set to FALSE.
Action:
Disable fast-start failover, using the FORCE option if required. Then retry the
attempted command.
ORA-16655: specified target standby database
invalid
Cause:
The attempted command was not allowed because fast-start failover was enabled
for this Data Guard configuration and the target standby database specified in
the command differs from the standby database that was indicated by the
FastStartFailoverTarget property associated with the current primary database.
Action:
Retry the attempted command by specifying the standby database that is
indicated by the FastStartFailoverTarget property that is associated with the
current primary database. Alternatively, fast-start failover may be disabled. Then
retry the command using the originally specified target standby database.
ORA-16656: Data Guard broker detected role change
Cause:
The Data Guard broker detected a role during database startup or health check.
Action:
Additional information about this failure is recorded in the Data Guard broker
log files, one for the primary database and one for each standby database in
the Data Guard configuration. This information is helpful in determining how
best to proceed from this failure.
ORA-16657: reinstatement of database in progress
Cause:
Reinstatement of this database was in progress.
Action:
None
ORA-16658: unobserved fast-start failover
configuration
Cause:
The fast-start failover configuration was currently unobserved so failover was
disallowed.
Action:
Make sure the observer is running and has connectivity to both the primary and
the target standby databases. Otherwise, disable fast-start failover to perform
a failover in the absence of the observer process.
ORA-16659: failover operation in progress
Cause:
A primary database that restarted contacted a standby database that is being
failed over to.
Action:
Shut down the primary database and wait for failover to complete on the standby
database. Once failover is complete, restart the old primary database. If the
failover occurred due to fast-start failover, restarting the primary database
after failover is complete allows it to be automatically reinstated as a
standby database to the new primary database.
ORA-16660: fast-start failover operation attempted
in absence of a broker configuration
Cause:
An attempt was made to enable or disable fast-start failover when connected to
a standby database for which broker configuration details are currently
unavailable. For instance, the standby database may currently require
re-creation (or flashback reinstantiation) before it may respond to broker
client commands.
Action:
1) An attempt to enable or disable (non-FORCE) fast-start failover at this
standby database will be rejected until such time that the broker configuration
details have been made available to that standby database from the primary
database. This normally occurs when the standby database is successfully
re-created or flashed back, and then reenabled at the primary database. 2) Use
the FORCE option to override fast-start failover that has been enabled at the
standby database even when the broker configuration details are currently
unavailable to the standby database. In this case, this status message is only
a warning. Note that fast-start failover is not formally disabled in the broker
configuration. The effect of this command issued under these circumstances may
or may not be permanent, depending upon when the primary and standby databases
regain full communication between each other and if the state of fast-start
failover has been altered at the primary database in the meantime.
ORA-16661: the standby database needs to be
reinstated
Cause:
A switchover or failover operation has caused this database to require
reinstatement.
Action:
Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate
the database. If the target database has flashback enabled and it has
sufficient flashback logs, the database will be reinstated as a standby
database for the current primary database.
ORA-16662: network timeout when contacting a
database
Cause:
In response to the issued command, the Data Guard broker attempted to contact a
database in the Data Guard configuration. That attempt failed because there was
no response from that database after the period of time specified by the
NetTimeout property for that database.
Action:
Check the Data Guard broker log for the details of the failure. Fix the problem
and try the command again.
ORA-16664: unable to receive the result from a
database
Cause:
During execution of a command, a database in the Data Guard broker
configuration failed to return a result.
Action:
Check Data Guard broker logs for the details of the failure. Fix any possible
network problems and try the command again.
ORA-16665: timeout waiting for the result from a
database
Cause:
The Data Guard broker was forced to time out a network connection
Action:
Check Data Guard broker logs for the details of the failure. Fix any possible
network problems and reissue the command.
ORA-16666: unable to initiate fast-start failover
on a standby database
Cause:
The request to initiate a fast-start failover using
DBMS_DG.INITIATE_FS_FAILOVER was made to a standby database. An application may
only request that fast-start failover be initiated by calling
DBMS_DG.INITIATE_FS_FAILOVER on a primary database.
Action:
Call DBMS_DG.INITIATE_FS_FAILOVER on the primary database.
ORA-16667: request Data Guard broker client to
reissue command
Cause:
The Data Guard broker operation required the same command be issued again from
the client.
Action:
If DGMGRL or Enterprise Manager has not already done so, reissue the same
command to the Data Guard broker manually.
ORA-16668: operation invalid on fast-start failover
target database
Cause:
The attempted command was not allowed on the fast-start failover target standby
database when fast-start failover is currently enabled.
Action:
Retry the attempted command on a database other than the fast-start failover
target standby database. Alternatively, disable fast-start failover and reissue
the same command to the fast-start failover target standby database.
ORA-16700: the standby database has diverged from
the primary database
Cause:
The primary database may have been flashed back or restored from a backup set
and then reopened with the RESETLOGS option.
Action:
Re-create the standby database from the primary database or flash back the
standby database to the same point the primary database had been flashed back
to.
ORA-16701: Data Guard broker command failed
Cause:
Command to modify or query the database failed.
Action:
Check the Data Guard broker log for the reason for the failure, and reissue the
command.
ORA-16702: Data Guard broker command warning
Cause:
A command to modify or query the database resulted in a warning.
Action:
Check the Data Guard broker log for the warning and, if necessary, reissue the
command.
ORA-16703: cannot set property while the database
is enabled
Cause:
An attempt was made to change a database property while the database was
enabled.
Action:
Disable the database first, update the property and then, reenable the
database.
ORA-16704: cannot modify a read-only property
Cause:
An attempt was made to change a read-only property.
Action:
The property is controlled internally by the Data Guard broker and cannot be
modified.
span><�
]s a �Or
0s N style='font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-font-family:
"Times New Roman";color:#222222;mso-ansi-language:EN;mso-fareast-language:ES-AR'>
Verify space, permissions and file name as indicated by the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
No hay comentarios:
Publicar un comentario