While journaling is generally a valuable safeguard in protecting your work, there are issues that may deter you from invoking it.
Journaling requires additional CPU cycles, memory, and disk access. This can impact application performance.
Journaling may duplicate features already built into your applications. In that case journaling provides no additional value to your organization.
A journal file has questionable value in the case where the database and the journal share a common point of failure that affects the information in both over a significant period of time. This can be addressed by using different disks and different disk controllers (where possible) for the journal and the associated database files.