ORA-16055: FAL request rejected
Answers were Sorted based on User's Feedback
Answer / sharath kanala
The fetch archive log (FAL) client and server resolve gaps
detected in the range of archived redo log files generated
at the primary database and received at the physical
standby database.
When the Primary database is unable to connect to the
Standby database, we receive FAL request rejected error.
This error by itself is not conclusive. We need to check
the prior and after errors to resolve the problem.
| Is This Answer Correct ? | 3 Yes | 3 No |
Answer / guest
Cause: FAL server rejects the FAL request from the FAL
client. This may be caused by different reasons.
Action: to solve the problem.
Please add more information about this Error
| Is This Answer Correct ? | 4 Yes | 6 No |
PCC-02022: Found end of file while scanning a SQL statement
NNL-00347: Save_config_on_stop is now OFF
ORA-06018: NETASY: message send failure
ORA-24310: length specified for null connect string
RMAN-08120: WARNING: archive log not deleted, not yet applied by standby
ORA-19735: wrong creation SCN - control file expects initial plugged-in datafile
PCC-02035: CMD-LINE: CONFIG= option is invalid in a config file
ORA-06022: NETASY: channel open failure
NNL-00245: General request processing is currently enabled
ORA-19800: Unable to initialize Oracle Managed Destination
ORA-28112: failed to execute policy function
ORA-06009: NETASY: dialogue filename too long