Document and/or rework Redo Thread inconsistency log messages

[Naros]

The following log message, or similar inconsistent messages, often prompt community questions about why this happens. We often have to reexplain this repeatedly and provide ways for users to customize the behavior.

Redo Thread X is inconsistent; an archive log with sequence 12345 is not available

At a minimum, we should add a section to the documentation (either in the FAQ or as a standalone section) that discusses these log messages and explains why they occur. We should document the expected configuration options that can be tuned to tweak the behavior for environments that require it.

Secondly, we should consider removing the stack trace exception at the INFO level. The stack trace is often what catches users' attention, and I believe it causes more confusion than it helps. The only thing we should consider adjusting is whether to include the redo thread status (open or closed), which is provided by the stack trace but not by the log message. From there, we could include the stack trace at the DEBUG level.

[Naros]

@roldanbob from your perspective, do you think it makes sense to have a standalone section or just include this in the FAQ section of the oracle.adoc ?

[roldanbob]

@roldanbob from your perspective, do you think it makes sense to have a standalone section or just include this in the FAQ section of the oracle.adoc ?

Because the scope of the issue is fairly narrow, I'd hesitate to create a section i the main doc to address it.

Ideally, I think that what this calls for is either a Troubleshooting section, or a log message reference. Looking at the Oracle FAQ, a little over half of the entries there could be considered troubleshooting issues. The biggest share of those entries relate to Oracle ORA-* messages.