You can’t bake an omelet without breaking eggs. This also applies to Oracle. Sometimes, we find flaws in the patches. An example is a bug in the patch Reporting 188.8.131.52.703. What is this bug and how can you beat it?
Recently, we applied the Reporting patch 184.108.40.206.703 at a client of ours. During the test of this Reporting patch, we found a small but significant bug. Our client was using batch scheduling to export reports to a folder on the server. Once the patch was installed, it was impossible to change the folder destination.
How did this bug in the Oracle Reporting patch arise?
The explanation of this bug is simple. Oracle forgot to change the ExportFolders – Writable option in the Mbeans. Normally this option is set to ‘true’, now it is set to ‘false’. This means that you cannot add or change any Export folder.
Figure 1. Oracle did not change the writable option in patch 220.127.116.11.703.
The current situation
Swap Support has immediately addressed this issue to Oracle. By now, Oracle Development has created a fix for it in patch 18.104.22.168.704.
Figure 2. Oracle has fixed the bug in version 22.214.171.124.704.
If you’re hampered by this bug, there are two solutions:
Install patch .704.
Would you prefer to keep using .703? That’s possible. Rollback to your prior version. Change or add the export folder and then apply the .703 patch again.
If you encounter a bug in your Oracle application
Bugs in software and software patches are a reality. Did you encounter a bug? Please contact us and we will help you solve or circumvent the bug. Also, we’ll ensure that Oracle is aware of any bug that we discover.