Bad Access Path For FETCH FIRST n ROWS or OPTIMISE FOR n ROWS

(Originally posted 2006-02-24.)

APAR PK18018 documents a condition where the use of either the

FETCH FIRST n ROWS

or

OPTIMISE FOR n ROWS

clauses leads to a suboptimal access path. Occasionally you can get an ABEND.

This APAR is marked for DB2 Version 8 only.

Published by Martin Packer

.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: