Our users are stumbling across 404 (page not found) pages caused by various ORA-* errors being raised within our web app. What we want to be able to do is present information about the error (such as line number, package/procedure name, and parameters passed in) which they can send to us to help us in debugging the problems.
The closest we've got to this is changing the wdbsvr.app configuration file to read "error_style = GatewayDebug". However, this presents the server configuration information and environment variables as well as the cause of the error which we don't want users to see. Additionally it is not in a format presentable to the user.
Does anyone know if it is possible to either a) Customise the output of the page generated by the GatewayDebug error style or b) Find out the same information that is available in the GatewayDebug output regarding procedure calls and present this as a web page.