ORA-16055: FAL request rejected
- 2 Answers
- 15033 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-13227: SDO_LEVEL values for the two index tables do not match
ORA-04080: trigger 'string' does not exist
ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
ORA-07606: szprv: $CHKPRO failure
RMAN-06213: --------------- ---------------------------------------------------
NNO-00050: serious errors in configuration data, server cannot run
ORA-22160: element at index [string] does not exist
ORA-01195: online backup of file string needs more recovery to be consistent
ORA-04085: cannot change the value of an OLD reference variable
ORA-31181: PL/SQL DOM handle accesses node that is no longer available
UDI-00005: unexpected End-Of-File encountered while reading input.
ORA-13854: Tracing for service(module/action) string on instance string is not enabled
Oracle Errors 
