Errfile Parameter Needed But Is Getting Deprecated (Doc ID 1290480.1)

Last updated on AUGUST 06, 2020

Applies to:

Symptoms

When running reports via rwclient in 10gR2 and NOT using the ERRFILE parameter because it has been deprecated, it returns a windows dialog box containing the error (ie. error can be any multitude of errors and specific errors are not relevant here) and requires user action to click the "OK" button which is not ideal in situations where business practices try to minimize user intervention.

Scenario:

The system administrator prefers that during a reports failure, the errors be logged into a file and ends instead of the application prompting a window on the client server awaiting user intervention.  Otherwise, the system administrator has to log onto the client server to end the rwclient.exe process.  If they do not, the execution queue is blocked and their client cannot execute reports.

Running reports in the background is not possible for them because their scheduler might need to have some script to launch when a report execution ends and, therefore, they have to know when the report stops.

With rwclient, they can use the ERRFILE parameter to do this, but the logs indicate ERRFILE is being deprecated (ie. meaning slated for removal in a future release).

This prompts the error dialog box (no ERRFILE parameter used):

-->  error is logged without displaying an error window dialog box prompting for user intervention (ie. clicking the "OK" button) in order to end/continue.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.