LISTE CODE ERREURS ORACLE.

 

ORA-16400	ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST
Cause	Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.
Action	No action is required.

 

ORA-16401	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.

 

ORA-16402	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-16403	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-16406	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-16407	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-16408	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-16409	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-16411	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-16412	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-16413	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-16416	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-16417	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-16501	ORA-16501: the Data Guard broker operation failed
Cause	The Data Guard broker operation failed.
Action	See accompanying messages for details.

 

ORA-16502	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-16503	ORA-16503: site ID allocation failure
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16504	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-16505	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-16506	ORA-16506: out of memory
Cause	Process exceeded private or shared memory limits.
Action	Check for memory leaks, increase system parameters and restart.

 

ORA-16507	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-16508	ORA-16508: channel handle not initialized
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16509	ORA-16509: the request timed out
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16510	ORA-16510: messaging error using ksrwait
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16511	ORA-16511: messaging error using ksrget
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16512	ORA-16512: parameter exceeded maximum size limit
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16513	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-16514	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-16515	ORA-16515: no rcv channel
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16516	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:
Action	If this error is returned when attempting a switchover operation, make sure that:

 

ORA-16517	ORA-16517: the object handle is invalid
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16518	ORA-16518: unable to allocate virtual instance id
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16519	ORA-16519: the resource handle is invalid
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16520	ORA-16520: unable to allocate resource id
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16521	ORA-16521: unable to create generic template id
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16522	ORA-16522: generic template not found
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16523	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-16524	ORA-16524: unsupported operation
Cause	A command or option is not supported in this release.
Action	Contact Oracle Support Services.

 

ORA-16525	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-16526	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-16527	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-16528	ORA-16528: unable to allocate PGA heap
Cause	No space in PGA to allocate heap
Action	Increase process virtual memory.

 

ORA-16529	ORA-16529: bad sender id
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16530	ORA-16530: invalid buffer or length
Cause	A NULL buffer or a length of zero is specified.
Action	Correct command parameters and retry.

 

ORA-16531	ORA-16531: unable to post message
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16532	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-16533	ORA-16533: inconsistent Data Guard broker state
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16534	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-16535	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 'name' -O NONE. Then reissue the broker request.

 

ORA-16536	ORA-16536: unknown object type
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16537	ORA-16537: child count exceeded
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16538	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-16539	ORA-16539: task element not found
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16540	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-16541	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-16542	ORA-16542: unrecognized operation
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16543	ORA-16543: invalid request made to broker
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16544	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-16545	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-16546	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-16547	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-16548	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-16549	ORA-16549: invalid string
Cause	A request contained an invalid or NULL string value.
Action	Correct command parameters and retry.

 

ORA-16550	ORA-16550: truncated result
Cause	A string property value was truncated due to insufficient buffer size.
Action	Specify a larger receive buffer.

 

ORA-16551	ORA-16551: short string copied
Cause	A string property value that did not fill the receive buffer was placed in the receive buffer.
Action	This is an informational message only. It is not an error.

 

ORA-16552	ORA-16552: an error occurred when generating the CLIENT OPERATION table
Cause	An error occurred while Data Guard broker was generating the CLIENT OPERATION table.
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 Customer Support.

 

ORA-16553	ORA-16553: the Data Guard broker process (DMON) failed to shutdown
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16554	ORA-16554: translation not valid
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16555	ORA-16555: the Data Guard database is not active
Cause	An operation was attempted on a database that is currently not active (off path).
Action	Verify that the database is active.

 

ORA-16556	ORA-16556: error message is in XML already
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16557	ORA-16557: the database is already in use
Cause	An attempt was made to create a duplicate database in the broker configuration.
Action	Check the database to be added and be sure there are no duplicates.

 

ORA-16558	ORA-16558: the database specified for switchover is not a standby database
Cause	An attempt was made to switchover to a database that is not a standby database.
Action	Locate an enabled standby database and select that database as the target of the switchover.

 

ORA-16559	ORA-16559: out of memory at string
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16560	ORA-16560: unable to convert document, syntax error at "string"
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16561	ORA-16561: cannot remove an active instance
Cause	The instance to be removed is currently running.
Action	Shut down the instance and reissue the REMOVE command.

 

ORA-16562	ORA-16562: intended_state not used here, syntax error at "string"
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16563	ORA-16563: unable to add value, syntax error at "string"
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16564	ORA-16564: lookup failed, syntax error at string
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16565	ORA-16565: duplicate property, syntax error at "string"
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16566	ORA-16566: unsupported document type
Cause	The XML document submitted is not supported.
Action	Correct the errors and submit the request again.

 

ORA-16567	ORA-16567: Data Guard broker internal parser error at "string"
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16568	ORA-16568: cannot set property string
Cause	The named property could not be modified. The property may not be editable or may not exist.
Action	Retry the operation with a valid property.

 

ORA-16569	ORA-16569: Data Guard configuration is not enabled
Cause	The requested operation required that broker management of the Data Guard configuration must be enabled.
Action	Enable the Data Guard configuration and reissue the request.

 

ORA-16570	ORA-16570: operation requires restart of database "string"
Cause	The Data Guard broker operation required a database to be shutdown and restarted.
Action	If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it.

 

ORA-16571	ORA-16571: Data Guard configuration file creation failure
Cause	The Data Guard broker was unable to create the configuration file on permanent storage.
Action	Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters and retry.

 

ORA-16572	ORA-16572: Data Guard configuration file not found
Cause	The Data Guard broker configuration file was either unavailable or did not exist.
Action	Verify that the configuration file was successfully created. If the dg_broker_config_file[1|2] parameter was changed, ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.

 

ORA-16573	ORA-16573: attempt to change configuration file for an enabled broker configuration
Cause	The Data Guard broker configuration file parameter was currently in use because broker management of the configuration was enabled. The attempt to alter that parameter was rejected.
Action	Disable the configuration and shut down the Data Guard broker before changing this value. Be sure to rename the configuration file at the OS level to match the new value before reenabling broker management of the configuration.

 

ORA-16574	ORA-16574: switchover disallowed when required databases are offline
Cause	Switchover failed because the primary database and/or the designated standby database are offline.
Action	Check the states of the broker configuration, primary database and standby database. Set their states to ONLINE if necessary.

 

ORA-16575	ORA-16575: request terminated at broker discretion
Cause	This status is returned when the broker terminates a user- initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.
Action	There is no action to be taken.

 

ORA-16576	ORA-16576: failed to update Data Guard configuration file
Cause	A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.
Action	Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters.

 

ORA-16577	ORA-16577: corruption detected in Data Guard configuration file
Cause	The Data Guard broker detected errors while loading the configuration file.
Action	Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters. Contact Oracle Support Services.

 

ORA-16578	ORA-16578: failed to read Data Guard configuration file
Cause	A failure was encountered while the broker was reading the configuration file on permanent storage.
Action	Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters.

 

ORA-16579	ORA-16579: bad Data Guard NetSlave state detected
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16580	ORA-16580: bad Data Guard NetSlave network link
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16581	ORA-16581: Data Guard NetSlave failed to send message to DRCX
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16582	ORA-16582: could not edit instance specific property
Cause	The request intended to change an instance specific property, but specified a database with two or more instances.
Action	Specify a specific instance instead to change the property value.

 

ORA-16583	ORA-16583: bad Data Guard Connection Process DRCX state
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16584	ORA-16584: illegal operation on a standby site
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16585	ORA-16585: illegal operation on a primary site
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16586	ORA-16586: could not edit database property through instance
Cause	The request intended to change a database property but specified an instance.
Action	Specify the database instead to change the database property.

 

ORA-16587	ORA-16587: ambiguous object specified to Data Guard broker
Cause	The request specified an object that the broker could not uniquely distinguish between other objects in the configuration.
Action	Try to further distinguish the object specified for the operation and reissue the request.

 

ORA-16588	ORA-16588: no more internal buffers
Cause	See trace file.
Action	Contact Oracle Support Services.

 

ORA-16589	ORA-16589: Data Guard Connection process detected a network transfer error
Cause	The Data Guard Connection process (DRCX) detected an error while transferring data from one database to another. This error is returned in the following situations:
Action	Contact Oracle Support Services.

 

ORA-16590	ORA-16590: Data Guard configuration does not contain a primary database
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16591	ORA-16591: unknown field "string" in document
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16592	ORA-16592: missing field "string" in document
Cause	There was an error at the given token.
Action	Correct the errors and submit the request again.

 

ORA-16593	ORA-16593: XML conversion failed
Cause	There was an error in the XML request document
Action	Correct the errors and submit the request again.

 

ORA-16594	ORA-16594: %s process discovered that DMON process does not exist
Cause	The Data Guard broker process (DMON) that was expected to be running on this instance was found to be missing by the Data Guard NetSlave (NSV*) process(es).
Action	Check the Data Guard broker log and DMON process trace file to determine why the DMON process is missing.

 

ORA-16595	ORA-16595: NetSlave process string failed to terminate
Cause	The specified NetSlave process did not terminate at the request of the Data Guard broker.
Action	Contact Oracle Support Services.

 

ORA-16596	ORA-16596: object not part of the Data Guard broker configuration
Cause	A request was made on a database object that is not in the Data Guard broker configuration. The request cannot be completed.
Action	Reissue the request on a database object that is in the broker configuration.

 

ORA-16597	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 cannot continue.
Action	Contact Oracle Support Services.

 

ORA-16598	ORA-16598: Data Guard broker detected a mismatch in configuration
Cause	The Data Guard broker detected a significant mismatch in configuration validation between two or more databases in the broker configuration. This can occur when the primary database has a stale broker configuration file.
Action	Contact Oracle Support Services.

 

ORA-16599	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.