MAX_ROWS_FETCHED Issue Reported in Bug 5503995 Still Exists After Applying 4.6.6.9 or 4.6.6.10 (Doc ID 2118079.1)

Last updated on MAY 04, 2017

Applies to:

Oracle Clinical - Version 4.6.6 and later
Information in this document applies to any platform.

Symptoms

When MAX_ROWS_FETCHED value is set to a particular value and, the session is disconnected, the value which was set earlier is lost and defaults back to 1000.  This issue is caused by Bug 5503995.

After applying patch 4.6.6.9 or 4.6.6.10, the problem still existed.

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