ORA-16059: Empty Log File Or Invalid Next Available Block
(Doc ID 2686014.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 20.3.0.0.0 [Release 11.2 to 20.0]Information in this document applies to any platform.
Symptoms
One or more archive log files may not get shipped to a Standby/Downstream/Mining database. Intermittently the error ORA-16059 is reported on the Source and the Sequence is rejected at the target side.
ORA-16059: empty log file or invalid next available block
for Example: redo transfer from a source 12.1 or 12.2 database to Destination 19c Downstream DB.
The RFS** traces shows messages like below:
During the write operation of the archivelog to the downstream/mining/standby side, when there is ORA-16059 encountered on the Source DB, the write operation is rejected on the target side, and the partially written file is replaced with the next sequence.
Changes
none
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |