Discoverer Connection Blocked by EBS SECURE Parameter

Yes, it is a known issue that if the database security parameter `SECURE` is set to a secure value, Discoverer often fails to work . Oracle Support Document 1574364.1 confirms that while the parameter should be set to `SECURE` in general EBS security notes, setting it as such prevents Discoverer from functioning . Since Discoverer is desupported, Oracle is unlikely to provide a fix .

The workaround, as suggested in the context of this issue, is to keep the `SECURE` parameter value set to OFF for standalone Business Intelligence (BI) tools like Discoverer . This is necessary because Discoverer lacks the server ID mechanism required to be recognized as a trusted machine by the database when `SECURE` is enabled .

When `SECURE` is enabled, application servers are registered as trusted machines by generating a large random ID number (the server ID) and storing it in both the application server’s DBC file and the database . The `AdminAppServer` utility is specifically used to generate these server IDs and register them with the database server . When the application server connects, the database verifies this ID .

If you are considering moving away from the desupported Discoverer, you should evaluate other reporting solutions . Enginatics Blitz Report is presented as a strong alternative, capable of automated Discoverer report migration, offering highly efficient operational reporting fully integrated with Oracle EBS , , .