11.1.2.2 Report Engines Fail To Work After a Report Job With PARAMFORM=YES Parameter Failed (Doc ID 2000611.1)

Last updated on MARCH 07, 2016

Applies to:

Oracle Reports Developer - Version 11.1.2.2.0 and later
Information in this document applies to any platform.

Symptoms

After applying 11.1.2.2 patchset any report request using PARAMFORM=YES parameter that fails to run with any error, will cause the report engine to fail to run any subsequent requests.

The first error displayed for the first request that failed will be the normal error (Example: REP-1401 or REP-300 or any other error).

The subsequent report request, that uses PARAMFORM=YES, will display the following error :

Error 500--Internal Server Error 

The error displayed via SHOWJOBS for the above request will be as follows :

The report terminated with error:

null

The report engine will recover of this behavior after reaching engLife configuration parameter value. 

Changes

 Patching to 11.1.2.2 version or new 11.1.2.2 installations.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms