ORA-16055: FAL request rejected
- 2 Answers
- 14035 Views
- I also Faced
- E-Mail Answers
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 |
ORA-19717: for non-OMF search the pattern must be specified
AMD-00148: Workspace "string" is not currently open. No update done.
ORA-31007: Attempted to delete non-empty container string/string
TNS-12674: Shared server: proxy context not saved
ORA-12980: checkpoint option not allowed with SET UNUSED
ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
ORA-32333: disable table scn update for Materialized view
ORA-33282: (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
PCC-00075: ":" expected before indicator variable
ORA-16175: cannot shut down database when media recovery is active
ORA-16603: Data Guard broker detected a mismatch in configuration ID.
ORA-39136: cannot specify an SCN on a transportable job
Oracle Errors 
