Re: Just scratching my head...

"Neil Truby" <neil.truby@ardenta.com> wrote in message news:6n0t21Fj784oU1@mid.individual.net... > > > It's said to be fixed in 11.5xC2. Sorry, I forgot to thank you for this welcome news. Without rancor, and just to clarify, I guess this is pretty strong evidence that there, therefore, was something which required fixing Thank you, IBM. (Assuming it is really fixed this time.) Regards, DG

DGPretzel wrote: > "Neil Truby" <neil.truby@ardenta.com> wrote in message > news:6n0t21Fj784oU1@mid.individual.net... >> >> It's said to be fixed in 11.5xC2. > > > Sorry, I forgot to thank you for this welcome news. > > Without rancor, and just to clarify, I guess this is pretty strong evidence > that there, therefore, was something which required fixing > > Thank you, IBM. (Assuming it is really fixed this time.) > > Regards, > > DG > > This is a big confusion caused by similar symptoms. Let me try to clarify. You have opened two cases a few years ago (if I got your name right and you live in a state with wonderful natural sights). The first was mapped to bug "A", and the second was not mapped to any bug, although a bug "B" was referenced. On second case, dbimport v9.4 worked. Both of these bugs were fixed in very old versions (in family 7.31, 9.21, 8.x and 9.4 - there were no v10 at the time). I tried the reproduction script of these two bugs in v11.50.UC2 on Linux and they didn't reproduce. The bug Neil referenced (let's call it bug "C") is different, and has different symptoms. It also doesn't reproduce on 11.50.xC2 (I didn't test this one personally). And you are now having a bug with similar symptoms to bug "A" and "B" on version 11.50 or v10 (didn't catch which dbimport you were using, but I assume it was v10). So, all the bugs you reported are fixed. And in fact they were fixed long time ago. _This doesn't mean you're not hitting a bug. I'm sure you are_ But it should be reported in order to be clarified. It probably is not the same bug. It would be interesting to see a schema that reproduces it. I had similar situations when using reserved words. This doesn't help your situation, neither the bad impression already caused, but it may help other customers... As I wrote earlier, there have been several bugs in dbexport/dbimport. Some of them may report similar errors, which doesn't mean they're the same. I'm sorry to insist on this issue, but I really don't like situations where IBM doesn't fix things. I tell you this as a person who works 99.99% of my time in customers... So, their problems are really my problem... Regards, -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...

"Fernando Nunes" <domusonline@gmail.com> wrote in message news:gekv44$j14$1@registered.motzarella.org... > > This is a big confusion caused by similar symptoms. Let me try to clarify. > You have opened two cases a few years ago (if I got your name right and > you live in a state with wonderful natural sights). You got it, thank you for taking the time to research an individual case, especially when so old. >The first was mapped to bug "A", and the second was not mapped to any bug, >although a bug "B" was referenced. On second case, dbimport v9.4 worked. >Both of these bugs were fixed in very old versions (in family 7.31, 9.21, >8.x and 9.4 - there were no v10 at the time). > I tried the reproduction script of these two bugs in v11.50.UC2 on Linux > and they didn't reproduce. > > The bug Neil referenced (let's call it bug "C") is different, and has > different symptoms. It also doesn't reproduce on 11.50.xC2 (I didn't test > this one personally). > > And you are now having a bug with similar symptoms to bug "A" and "B" on > version 11.50 or v10 (didn't catch which dbimport you were using, but I > assume it was v10). > > So, all the bugs you reported are fixed. And in fact they were fixed long > time ago. _This doesn't mean you're not hitting a bug. I'm sure you are_ > But it should be reported in order to be clarified. It probably is not the > same bug. With full respect, I don't know if it is Bug A, B, C, or something else.