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 |
ORA-12431: invalid audit action
ORA-13137: failed to generate tablespace sequence number
RMAN-00564: host data too long
QSM-02154: MV is not fast refreshable even with view merging
ORA-24123: feature string is not yet implemented
RMAN-08546: channel string: autobackup found in the recovery area
NZE-28766: failure to terminate use of data source
RMAN-06500: skipping backupset key string; already backed up string time(s)
ORA-16764: log tranport service for some standby database unexpectedly offline
NNF-04001: Error converting input file
ORA-27504: IPC error creating OSD context
RMAN-06748: no or more than one tertiary storage channel found