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 - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

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

update : 27-05-2017
ORA-16402

ORA-16402 - ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
ORA-16402 - ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support

  • ora-27433 : cannot alter state of step string for job string.string to string
  • ora-28169 : unsupported certificate type
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-02760 : Client close of file failed.
  • ora-16531 : unable to post message
  • ora-30966 : error detected in the XML Index layer
  • ora-25953 : join index cannot be a functional index
  • ora-22958 : This operation is not allowed in check constraints or triggers
  • ora-08464 : input raw decimal data contains more than 42 digits
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • ora-02764 : Invalid package mode
  • ora-16094 : database shutdown during archival operation
  • ora-19527 : physical standby redo log must be renamed
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-13041 : failed to compare tile with element string.string.string
  • ora-16240 : Waiting for logfile (thread# string, sequence# string)
  • ora-07481 : snlmatt: cannot attach to lock manager instance.
  • ora-31005 : Path name length string exceeds maximum length string
  • ora-39141 : dump file "string" is a duplicate of dump file "string"
  • ora-15013 : diskgroup "string" is already mounted
  • ora-25206 : enqueue failed, enqueue to exception queue string.string not permitted
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-13205 : internal error while parsing spatial parameters
  • ora-29952 : cannot issue DDL on a domain index partition marked as LOADING
  • ora-16579 : bad Data Guard NetSlave state detected
  • ora-13911 : Threshold not found
  • ora-27375 : valid agent name must be specified for secure queues
  • ora-00960 : ambiguous column naming in select list
  • ora-37050 : (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode.
  • ora-30198 : reserved for future use
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.