Re: Index advisor advising index on primary key

I opened a PMR.

Here's an interesting tidbit. Just because, I did the following:

CRTDUPOBJ OBJ(DMITMMST) FROMLIB(DBMSTF) OBJTYPE(*FILE)
TOLIB(JEFF) CST(*NO) TRG(*NO)

Note that I said CST(*NO). A DSPFD on the newly created file says:

Number of constraints . . . . : 0

but further down the DSPFD says:

Access Path Description Access path maintenance . . . : MAINT *IMMED Unique key values required . : UNIQUE Yes Access path journaled . . . . : No Access path . . . . . . . . . : Keyed Constraint Type . . . . . . . : NONE Number of key fields . . . . : 1 Record format . . . . . . . . : MBRECORD
Key field . . . . . . . . . : ITNBR Sequence . . . . . . . . : Ascending
Sign specified . . . . . : UNSIGNED
Zone/digit specified . . : *NONE Alternative collating seq : Yes So there's no 'constraint' but there's still a unique access path. Furthermore I *was* able to do an ALTER TABLE and *add* a unique constraint on ITNBR in this duplicated file.

Are we having fun yet?
rob@xxxxxxxxx wrote:

Keep me posted. One attendee at the session said he built the recommended index and it still wanted him to build the recommended index. I'm curious if that is the case, or the unique constraint, or ...

By the way, the person who really shines at these sessions is an IBMer by the name of Tom McKinley. He's the "John Sears" of our time.

Rob Berendt