I have recently recommended to use ORAchk in its new version 18.104.22.168 – and I can just emphasize on this.
During a conf call with a lead customer from the UK Roy and I learned about the uncertainness on how to log a Service Request (SR) or enhancement Request (ER) against ORAchk in case something is not working correctly or missing.
Especially as the documentation of ORAchk states:
Appendix B – How to Obtain Support
If problems are encountered either at runtime or if there are questions about the content of the findings of the tool, please post your issues/questions/concerns to the ORAchk thread within the ORAchk Thread of the Scalability RAC My Oracle Support Community.
Roy explored this topic in the past days and that is the outcome:
- Of course you can file SRs via MOS (and ERs as well).
If a Support Engineer told you that the product is only supported via the Community Forum this is not correct. Just insist 🙂
- There’s an official product ID (10655), component (ORACHK) and sub component (FRAMEWORK) for filing ORAchk bugs and enhancements internally in our bug database. But of course a customer will need to file an SR first via MOS.
We hope this helps 🙂