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 |
IMP-00400: Warning: Object type "string"."string" already exists with a different typeid
PCC-02209: Macro invocation has incorrect number of arguments
NNO-00256: using administrative region "string"
ORA-23535: instantiating templates from multiple back ends is not allowed.
ORA-39317: illegal validation_check() call: only applys after clone/sync_code/valdation_check
ORA-30438: unable to access named pipe 'string'
ORA-16192: Primary and standby network integrity mismatch
ORA-01074: cannot shut down ORACLE; inside a login session - log off first
ORA-26062: Can not continue from previous errors.
ORA-01217: logfile member belongs to a different logfile group
ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.
QSM-02031: materialized view cannot support any type of query rewrite