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 : 20-09-2017

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

  • ora-24903 : invalid namespace attribute passed into OCI call
  • ora-23318 : a ddl failure has occurred
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • ora-01257 : cannot reuse database file string, unknown file size
  • ora-39110 : error deleting worker processes
  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-16239 : IMMEDIATE option not available without standby redo logs
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-36920 : (XSVPMVTOPART01) workspace object cannot become anonymous because it has properties.
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-30956 : invalid option for XML Index
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-13110 : cannot drop topology with associated topo_geometry tables
  • ora-26086 : direct path does not support triggers
  • ora-14283 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-30726 : cannot specify referenced column list here
  • ora-23614 : Script string does not exist
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-02028 : fetching an exact number of rows is not supported by the server
  • ora-14407 : partitioned table contains subpartitions in a different tablespace
  • ora-19880 : Corrupted space header for datafile string, block string backup aborted
  • ora-07472 : snclrd: open error when opening sgadef.dbf file.
  • ora-38861 : flashback recovery stopped before reaching recovery target
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-01197 : thread string only contains one log
  • ora-00225 : expected size string of control file differs from actual size string
  • ora-25406 : could not generate a connect address
  • 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.