ORA-16548: object not enabled

ORA-16548: object not enabled

Cause: An attempt was made to modify or query a disabled Data Guard object, most likely a database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created. The broker also disables management of a database that lags behind in terms of DRC Unique ID sequence value. This value is updated after successful switchover and failover operations.

Action: If broker management of the database is disabled, enable it and reissue the request.

ORA-16547: cannot disable the primary database

ORA-16547: cannot disable the primary database

Cause: An attempt was made to explicitly disable broker management of the primary database.

Action: Broker management of the primary database cannot be explicitly disabled. Instead you must disable the entire broker configuration if you wish to disable the primary database.

ORA-16546: missing or invalid piece

ORA-16546: missing or invalid piece

Cause: The piece of the request to return was not specified or was invalid.

Action: Specify the piece of the response starting from 1.

ORA-16545: unable to get response

ORA-16545: unable to get response

Cause: The Data Guard broker was unable to return the result of a previous request.

Action: Contact Oracle Support Services.

ORA-16544: modifying DG_BROKER_START requires SID= * qualifier

ORA-16544: modifying DG_BROKER_START requires SID= * qualifier

Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID= * qualifier was required in the command.

Action: Reenter the command using the SID= * qualifier.

ORA-16543: invalid request made to broker

ORA-16543: invalid request made to broker

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16542: unrecognized operation

ORA-16542: unrecognized operation

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16541: site is not enabled

ORA-16541: site is not enabled

Cause: The site specified in the request was not enabled.

Action: Select an enabled site and reissue the request.

ORA-16540: invalid argument

ORA-16540: invalid argument

Cause: One of the arguments for the specified request was invalid for the request type.

Action: Verify arguments and then reissue the request.

ORA-16539: task element not found

ORA-16539: task element not found

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16538: no match on requested item

ORA-16538: no match on requested item

Cause: The Data Guard broker did not recognize the specified property or state name.

Action: Verify command parameters and reissue the request.

ORA-16537: child count exceeded

ORA-16537: child count exceeded

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16536: unknown object type

ORA-16536: unknown object type

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16535: CRS is preventing execution of a broker operation

ORA-16535: CRS is preventing execution of a broker operation

Cause: A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker s request on at least some of the instances, so the broker operation was canceled.

Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D lamp;lt;lamp;nbsp;namelamp;gt; -O NONE. Then reissue the broker request.

ORA-16534: no more requests accepted

ORA-16534: no more requests accepted

Cause: The Data Guard broker returns this status when:

Action: Wait until the operation is complete and then reissue the request.

ORA-16533: inconsistent Data Guard broker state

ORA-16533: inconsistent Data Guard broker state

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16532: Data Guard broker configuration does not exist

ORA-16532: Data Guard broker configuration does not exist

Cause: A broker operation was requested that requires an already existing broker configuration.

Action: Create a Data Guard broker configuration prior to issuing other requests.

ORA-16531: unable to post message

ORA-16531: unable to post message

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16530: invalid buffer or length

ORA-16530: invalid buffer or length

Cause: A NULL buffer or a length of zero is specified.

Action: Correct command parameters and retry.

ORA-16529: bad sender id

ORA-16529: bad sender id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16528: unable to allocate PGA heap

ORA-16528: unable to allocate PGA heap

Cause: No space in PGA to allocate heap

Action: Increase process virtual memory.

ORA-16527: unable to allocate SGA heap

ORA-16527: unable to allocate SGA heap

Cause: The Data Guard broker was unable to allocate a heap within the SGA.

Action: Increase SGA memory.

ORA-16526: unable to allocate task element

ORA-16526: unable to allocate task element

Cause: The Data Guard broker was unable to allocate memory for a request.

Action: Increase the size of your SGA.

ORA-16525: the Data Guard broker is not yet available

ORA-16525: the Data Guard broker is not yet available

Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start.

Action: If the broker has not been started, set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.

ORA-16524: unsupported operation

ORA-16524: unsupported operation

Cause: A command or option is not supported in this release.

Action: Contact Oracle Support Services.

ORA-16523: operation requires the client to connect to instance string

ORA-16523: operation requires the client to connect to instance string

Cause: The switchover or failover operation requires the client to connect to the apply instance of the target database.

Action: Connect to the indicated instance and reissue the switchover or failover command.

ORA-16522: generic template not found

ORA-16522: generic template not found

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16521: unable to create generic template id

ORA-16521: unable to create generic template id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16520: unable to allocate resource id

ORA-16520: unable to allocate resource id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16519: the resource handle is invalid

ORA-16519: the resource handle is invalid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16518: unable to allocate virtual instance id

ORA-16518: unable to allocate virtual instance id

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16517: the object handle is invalid

ORA-16517: the object handle is invalid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16516: the current state is invalid for the attempted operation

ORA-16516: the current state is invalid for the attempted operation

Cause: The broker may return this error for switchover operations and for database state change operations. If this error is returned for a switchover operation, the broker has determined that either: files. The broker returns this error for database state change operations if the database state specified is invalid.

Action: If this error is returned when attempting a switchover operation, make sure that: attempting a database state change operation, make sure you specify a valid state.

ORA-16515: no rcv channel

ORA-16515: no rcv channel

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16514: the request was not found

ORA-16514: the request was not found

Cause: An attempt was made to read a response but a matching request was not found.

Action: Verify request identifier is valid and references a previously issued request.

ORA-16513: maximum requests exceeded

ORA-16513: maximum requests exceeded

Cause: Non-blocking commands were issued but responses were not consumed or the commands did not complete.

Action: Read pending responses or delete outstanding requests and try again.

ORA-16512: parameter exceeded maximum size limit

ORA-16512: parameter exceeded maximum size limit

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16511: messaging error using ksrget

ORA-16511: messaging error using ksrget

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16510: messaging error using ksrwait

ORA-16510: messaging error using ksrwait

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16509: the request timed out

ORA-16509: the request timed out

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16508: channel handle not initialized

ORA-16508: channel handle not initialized

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16507: unrecognized request identifier

ORA-16507: unrecognized request identifier

Cause: The specified request identifier was not recognized by the Data Guard broker.

Action: Reissue the request using a valid request identifier.

ORA-16506: out of memory

ORA-16506: out of memory

Cause: Process exceeded private or shared memory limits.

Action: Check for memory leaks, increase system parameters and restart.

ORA-16505: site ID is invalid

ORA-16505: site ID is invalid

Cause: The request contained an invalid site ID.

Action: Make the request again with a valid site iD.

ORA-16504: the Data Guard configuration already exists

ORA-16504: the Data Guard configuration already exists

Cause: A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration.

Action: Delete the existing configuration if you want to create a new configuration.

ORA-16503: site ID allocation failure

ORA-16503: site ID allocation failure

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16502: the Data Guard broker operation succeeded with warnings

ORA-16502: the Data Guard broker operation succeeded with warnings

Cause: The Data Guard broker operation succeeded with warnings.

Action: See accompanying messages for details.

ORA-16501: the Data Guard broker operation failed

ORA-16501: the Data Guard broker operation failed

Cause: The Data Guard broker operation failed.

Action: See accompanying messages for details.

ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required

ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required

Cause: Activation occurred after recovery from standby redo log files.

Action: Take a full database backup.

ORA-16416: Switchover target is not synchronized with the primary

ORA-16416: Switchover target is not synchronized with the primary

Cause: The switchover target incurred an error or has a gap at the time the switchover operation was attempted.

Action: Allow the switchover target to become synchronized and then re-attempt the switchover.

ORA-16413: Unsupported database type for ONDEMAND archivelog destinations

ORA-16413: Unsupported database type for ONDEMAND archivelog destinations

Cause: The use of the ONDEMAND attribute for a standby database destination is supported for only physical and logical standby database types. Cross-Instance-Archival and repository database types are not valid for the ONDEMAND attribute.

Action: Verify the database corresponding to the archivelog destination is either a physical standby database or a logical standby database.

ORA-16412: ONDEMAND archival requires active SQL apply operation

ORA-16412: ONDEMAND archival requires active SQL apply operation

Cause: The use of the ONDEMAND attribute for a logical standby database destination requires that the SQL apply operation be active prior to establishing the network connection.

Action: Start the SQL apply operation on the standby database.

ORA-16411: ONDEMAND archival requires active managed recovery operation

ORA-16411: ONDEMAND archival requires active managed recovery operation

Cause: The use of the ONDEMAND attribute for a physical standby database destination requires that the managed recovery operation be active prior to establishing the network connection.

Action: Start the managed recovery operation on the standby database.

ORA-16409: Archive log switchover reference number mismatch

ORA-16409: Archive log switchover reference number mismatch

Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: No action is required.

ORA-16408: Incompatible archival Redo Branch lineage

ORA-16408: Incompatible archival Redo Branch lineage

Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs.

Action: No action is required.

ORA-16407: Standby database is in the future of the archive log

ORA-16407: Standby database is in the future of the archive log

Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs.

Action: No action is required.

ORA-16406: Primary and standby database software version mismatch

ORA-16406: Primary and standby database software version mismatch

Cause: The primary database and standby database Oracle software is not compatible.

Action: Install the correct Oracle software and try again.

ORA-16403: shutdown in progress - remote connection is not permitted

ORA-16403: shutdown in progress - remote connection is not permitted

Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.

Action: Wait for the remote instance to be restarted, or contact your DBA.

ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support

ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support

Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters.

Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error.

ORA-16401: archivelog rejected by RFS

ORA-16401: archivelog rejected by RFS

Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.

Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.