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 : 26-07-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-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-16790 : the value of the configurable property is invalid
  • ora-19619 : cannot call restoreValidate after files have been named
  • ora-38481 : ADT "string" is used for a dependent object.
  • ora-36920 : (XSVPMVTOPART01) workspace object cannot become anonymous because it has properties.
  • ora-23365 : site string does not exist
  • ora-07607 : szaud: $SNDOPR failure
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-16140 : standby online logs have not been recovered
  • ora-23619 : non-Oracle system error: string
  • ora-24060 : cannot convert QUEUE_TABLE, string already is compatible with release string
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-00480 : LCK* process terminated with error
  • ora-40286 : remote operations not permitted on mining models
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-30156 : Out of disk space
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-00483 : During shutdown a process abnormally terminated
  • ora-12923 : tablespace string is in force logging mode
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-01316 : Already attached to a Logminer session
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-29546 : badly formed resource: string
  • ora-19229 : XP0009 - schema import not supported
  • ora-13336 : failure in converting standard diminfo/geometry to LRS dim/geom
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-28172 : distinguished name not provided by proxy
  • ora-12992 : cannot drop parent key column
  • ora-19505 : failed to identify file "string"
  • ora-02020 : too many database links in 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.