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 : 23-04-2017

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

  • ora-23463 : flavor incompatible with object "string"."string"
  • ora-32583 : query passed to table function has wrong number of elements in select list
  • ora-07495 : spwat: lm_wait failed.
  • ora-07225 : sldext: translation error, unable to expand file name.
  • ora-25196 : keyword MOVE in ALTER TABLE MOVE must immediately follow
  • ora-01612 : instance string (thread string) is already enabled
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-09978 : skxfqhdel: Error Disconnecting from another endpoint.
  • ora-09787 : sllfop: unrecognizable processing option, incorrect format.
  • ora-12986 : columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-02299 : cannot validate (string.string) - duplicate keys found
  • ora-01062 : unable to allocate memory for define buffer
  • ora-22818 : subquery expressions not allowed here
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-02085 : database link string connects to string
  • ora-13403 : invalid rasterDataTable specification: string
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-07643 : smsalo: SMSVAR is invalid
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-06511 : PL/SQL: cursor already open
  • ora-00311 : cannot read header from archived log
  • ora-29867 : cannot create a domain index on a LONG column
  • ora-24122 : invalid block range specification
  • ora-27163 : out of memory
  • ora-19769 : missing FILE keyword
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-02063 : preceding stringstring from stringstring
  • ora-26762 : Cannot autogenerate name for parameter string because of the following reason: string
  • 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.