Re: SQL Table Name vs System Table Name

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Hi David

I recommend taking this to IBM Support now - this seems wrong.

What version of the OS are you running? What is the level of the DB2 
group PTF? (Use WRKPTFGRP for that in more recent releases.)

Anyhow, this shouldn't be happening.

Good luck!
Vern

On 9/12/2011 10:24 AM, dmosley@xxxxxxxxxx wrote:
> Just wanting to ask if anyone has experienced this problem before.
>
> We have several QTEMP files being created in programs, via SQL CREATE
> TABLE.  All the files exceed 10 characters, and most begin
> with the same prefix.  (OrderEntry_Header, OrderEntry_Details,
> OrderEntry_Messages, etc).
>
> So, to make a long story short, we experienced the program trying to
> access the wrong QTEMP file.
> Let's say I was trying to do a SELECT COUNT(*) FROM OrderEntry_Header
> (that would contain 1 record).
> Well, instead of getting a value of 1, we got a value of 13, which was the
> contents of OrderEntry_Details.
>
> Now, this was a very sporadic occurrence, but we applied some logging in
> the programs, and could visually see the wrong
> values be accessed.
>
> So, in an attempt to correct this from happening, we converted the long
> SQL names to normal 10<  characters, OE@HEADER, etc.
> And, the problem stopped occurring.
>
> I know the system, creates truncated system names, when the CREATE TABLE
> command is executed, (ie ORDE000001 ->  OrderEntry_Header),
> but is it possible that the pointers for those files got tangled somehow.
>
> Trust me, I know the iSeries is perfect (haha), so, I'm gonna guess
> gremlins were the culprits
> David
>
>
> David L. Mosley, Jr.
> Technical Solutions Architect | 919.379.3730
> Dancik International | www.dancik.com
> www.facebook.com/dancikinternational